UserProof

UserProof / Free tools / Fix check calculator

Fix check calculator: did a site change work? A before and after conversion rate calculator

Free tool · runs in your browser · Updated November 14, 2026
TL;DRA before and after conversion rate calculator that does UserProof's fix check once, free. Enter visits and conversions before and after a change, and optionally the same for your site's other pages. It shows both rates, the change in points with a 95% interval, and a verdict: worked, got worse or inconclusive. Under 30 visits after the change it never gives a verdict. The numbers you type stay in your browser.

For founders who build with a coding agent and have before and after visit counts: in the example, the rate went from 5.0% to 8.9%, up 3.9 points (95% interval 0.4 to 7.7), so it worked. Our own check on Sales.co (1 check, 203 visits, October 26, 2026) read 90 of 118 visits bouncing before and 45 of 85 after: down 23 points, interval 10 to 36 (worked example).

By Ryan Doyle, founder of UserProof, which runs this check on recorded visits after your coding agent ships a fix.

Your numbers

Your page or change

VisitsConversions

Before the change
After the change
Optional: the site's other pages, as a control

Same two periods, same definition of a conversion, pages you did not change. Fill in all four or leave all four empty.

VisitsConversions

Before the change
After the change

The calculator needs JavaScript and its script hasn't run, so editing changes nothing here. The result below is the example, worked out in full.

Example result

Worked. The rate went from 5.0% to 8.9%, a change of +3.9 points (95% interval 0.4 to 7.7). The interval stays on the good side of zero, so this looks like it worked. With no control, anything else that changed in the same weeks is mixed in.

UserProof's fix check would call this: improved.

The result, in rate points (1 point = 1 percentage point)
GroupBeforeAfterChange95% interval
This page or change5.0% (20 of 400)8.9% (34 of 380)+3.9 points0.4 to 7.7

How to read the result

A verdict is about the rate, not the cause. Read it with what else changed on the page and on the site in the same weeks.

When a lift becomes clear

The same move, a 5% rate going to 9%, at four traffic levels. The lift is identical in each row; only the number of visits changes what you can say about it.

Result of a 5.0% to 9.0% change at different traffic (no control, higher is better)
VisitsBeforeAfter95% interval, pointsVerdict
100 before, 100 after5 of 100 (5.0%)9 of 100 (9.0%)−3.5 to 11.8Inconclusive (no clear change)
500 before, 500 after25 of 500 (5.0%)45 of 500 (9.0%)0.8 to 7.2Worked (improved)
2,000 before, 2,000 after100 of 2,000 (5.0%)180 of 2,000 (9.0%)2.4 to 5.6Worked (improved)
100 before, 25 after5 of 100 (5.0%)3 of 25 (12.0%)no interval: under 30 visits afterInconclusive (needs 5 more visits)

With 100 visits on each side the interval runs from −3.5 to 11.8 points and includes zero, so a lift of 4 points is inconclusive. With 500 it is 0.8 to 7.2, which clears zero. With 2,000 it narrows to 2.4 to 5.6. A rate that jumps from 5% to 12% on 25 visits is still inconclusive, because the floor is 30.

How it works

The method is the one in UserProof's fix check (src/lib/engine/verify.mjs and the interval helpers in findings.mjs), applied once to the four to eight numbers you type.

Where the product reads a before window of 14 days and an after window of up to 14 days, here you choose the periods. Use the same number of days on each side, and for a control the same days too.

Worked example

The example above: 20 of 400 visits converted before (5.0%) and 34 of 380 after (8.9%), so the change is 3.9 points. Wilson 95% intervals: 5.0% before is about 3.3% to 7.6%, and 8.9% after is about 6.5% to 12.2%. Combined, the change interval is 0.4 to 7.7 points. Its low end is above zero, so with no control it reads worked. To see a 20% relative change from 5.0% (a move to 6.0%) you would need about 7,448 visits on each side, so this result is a big lift that the data happen to support, not a precise size.

Now add a control. Say the site's other pages went from 150 of 3,000 (5.0%) to 160 of 2,900 (5.5%): up 0.5 points on their own. The net change is 3.4 points with a 95% interval of −0.3 to 7.3. That reaches zero, so the page moved the right way but the verdict is inconclusive (UserProof: rose, not confirmed against other pages). Press "Try the example with a control" to see it.

Check against a real read: the Sales.co check on the fix check page had 90 of 118 visits bounce before and 45 of 85 after. Enter it with "lower is better" and the calculator gives a change of −23.3 points with a 95% interval of −35.8 to −10.1. The page prints it as a 23-point drop, 10 to 36.

What the numbers say

Limits: what it can't tell you

Run the check on recorded visits

The calculator reads the four numbers you type. UserProof does the same check on recorded visits. When your coding agent ships a fix and marks it applied, UserProof compares the page before and after against your other pages, with the same interval and the same 30-visit floor. Then it tells the agent whether the fix worked. Read how on the fix check page. Free for 3 sites and 5,000 recorded visits a month; Pro is $29 a month for 50,000; Scale is $99 for 250,000 (pricing).

Before you ship the next change, the conversion rate increase calculator says what the lift would be worth a month and whether your traffic can show it in 14 days.

Related: the funnel calculator, the dead click finder, all free tools.

Sources, read November 14, 2026

Cite this

UserProof, "Fix check calculator," https://getuserproof.com/fix-check-calculator, updated November 14, 2026. Change in a rate between two periods with a 95% Wilson-based interval, no verdict under 30 visits after the change, and a difference in differences against a control.

FAQ

How do I calculate a before and after conversion rate?

Divide the conversions by the visits for each period, then subtract the before rate from the after rate. In the example, 20 of 400 visits is 5.0% and 34 of 380 is 8.9%, a change of 3.9 points. The change alone is not enough: the 95% interval says how much of it could be chance, which depends on how many visits each side has.

How many visits do I need after a change?

At least 30 for the calculator to say anything, which is UserProof's own floor. To see a 20% relative change from a 5% rate (5.0% to 6.0%) with 95% confidence and 80% power you need about 7,448 visits on each side. Small changes on low rates need far more traffic than most pages get in a week.

Is this the same as an A/B test?

No. An A/B test splits visitors between two versions at the same time, so the only difference between the groups is the change. A before and after read compares two different weeks, so a holiday, a new traffic source or a second change on the same page shows up as part of the result. If you can build both versions and split traffic, use an A/B testing tool. This calculator is for the change you already shipped.

What is the control, and do I need one?

The control is the rest of your site, measured over the same two periods. If it moved by the same amount, the change on your page was probably not your fix. With a control the calculator reports the difference in differences: the page's change minus the control's change, with its own 95% interval. You don't need one, but without it a seasonal swing can look like a win.

What does the 95% interval mean here?

It is the range of changes consistent with your counts. If the whole range is above zero, the rate very probably went up; if it spans zero, the data can't tell a real change from noise. It is built from a range on each rate, combined for the difference, the same method UserProof's fix check uses. It tells you how far off the real change could be.

Does the calculator store or send my numbers?

No. The calculator runs in your browser, makes no requests and saves nothing. The page itself has the same visit analytics as the rest of this site, and the form and the result are marked so that analytics never records what you type or what the result shows. Reload the page and it starts from the example again.