Works out how many visitors per variant an A/B test needs to detect a given lift, and how many days that takes at your traffic.
p1 is the baseline conversion rate, p2 is the rate you would get if the change worked. The z values come from the two error rates you are willing to accept: 1.96 for 95 percent confidence, 0.84 for 80 percent power.
The shortcut worth remembering is that sample size scales with the inverse square of the effect. Halve the lift you want to detect and the test gets roughly four times longer. That single fact kills most test plans before they start.
Most teams pick a variant, launch it, and find out afterwards what it could have proved. That is backwards. The minimum detectable effect is an input, not a result.
Low traffic sites are not barred from testing. They are barred from testing small changes. Button colours need millions of visitors. Rewriting an offer does not.
Confidence controls false positives: shipping a change that did nothing. Power controls false negatives: binning a change that worked. Almost every calculator lets you set the first and quietly fixes the second at 80 percent.
Eighty percent power means one in five real improvements will be missed. That is the accepted trade, but it is a trade, and it is worth knowing you made it.
The sample size is a commitment, not a suggestion.
The number this page gives you only holds if you look once, at the end. Checking daily and stopping the moment the result goes green turns a 5 percent false positive rate into something closer to 20 or 30 percent, depending on how often you peek.
This is why so many winning tests fail to replicate in revenue. The test did not lie. The stopping rule did.