AB Test Significance Calculator
Tests whether a difference in conversion rates between two variants is statistically significant, using a two-proportion z-test.
Tool guide
What this tool does
AB Test Significance Calculator runs a two-proportion z-test comparing variant A (control) against variant B (treatment), reporting each variant’s conversion rate, the relative uplift, the z-score and p-value, and a plain-language verdict on statistical significance at the standard 95% confidence level.
Seeing variant B outperform variant A in an A/B test doesn’t automatically mean the difference is real, with limited traffic, random fluctuation alone can easily produce an apparent uplift that wouldn’t hold up with more data.
This calculator runs a proper two-proportion z-test comparing your two variants’ conversion rates, reporting the z-score, p-value, and a plain-language verdict on whether the observed difference is statistically significant.
How to use AB Test Significance Calculator
- Enter variant A’s (control) visitor and conversion counts.
- Enter variant B’s (treatment) visitor and conversion counts.
- Review the conversion rates, relative uplift, z-score and p-value.
- Check the plain-language significance verdict.
Tips for better results
- A p-value below 0.05 is the standard (though somewhat arbitrary) threshold for declaring statistical significance at 95% confidence, it means the observed difference would be unlikely to occur by random chance alone if there were truly no real difference.
- Statistical significance doesn’t guarantee practical importance, always weigh the relative uplift’s real-world size (is a 2% relative improvement actually worth implementing?) alongside the p-value.
- Deciding your sample size or test duration in advance and sticking to it matters, stopping a test early as soon as it happens to look significant ("peeking") inflates the false-positive rate well beyond the nominal 5%.
- A test with too few visitors to either variant produces an unreliable result regardless of how the numbers look, use the Sample Size Calculator beforehand to plan an adequately powered test.
Common use cases
- Determining whether an A/B test’s observed difference in conversion rate is statistically real or likely random noise.
- Comparing two landing page, email, or feature variants’ performance rigorously.
- Deciding whether to roll out a tested change based on solid statistical evidence.
- Checking a marketing or product test result before making a final decision.
Common mistakes to avoid
- Stopping a test as soon as it looks significant and declaring victory, this "peeking" behaviour inflates the real false-positive rate well beyond the nominal 5%, decide your sample size or test duration in advance and stick to it.
- Treating a statistically significant result as automatically meaning the uplift is large enough to matter practically, a tiny but statistically significant improvement may not be worth the cost or complexity of implementing.
- Running a test with too few visitors per variant and trusting the result regardless, an underpowered test’s result (significant or not) carries much less reliability than one with an adequately planned sample size.
Frequently asked questions
What does p < 0.05 mean here?
That the observed difference between variants would be unlikely (less than 5% probability) to occur by random chance alone if there were truly no real underlying difference, the standard threshold for declaring statistical significance at 95% confidence.
Does statistical significance mean I should implement the change?
Not automatically, also weigh the relative uplift’s real-world size and the cost/complexity of implementing the change; a statistically significant but tiny uplift may not be worth it in practice.
Why shouldn’t I stop the test early once it looks significant?
Because repeatedly checking and stopping as soon as a result looks significant ("peeking") inflates the real false-positive rate well beyond the nominal 5%, decide your sample size or duration in advance and stick to it.
Is my data uploaded anywhere?
No, the z-test is computed entirely client-side in your browser; your visitor and conversion counts stay on your device.
Feedback & suggestions
Help us improve AB Test Significance Calculator. We read every message.