Skip to content

A/B test calculator

Before you run an A/B test, check that your traffic can answer the question. See how long a test takes, what it can detect, and whether AI Optimize has enough to learn from.

CalculatorAbout 5 minutesReviewed October 2026

Enter your traffic and the smallest lift you care about.

Conversions divided by sessions, the way Shopify and Webflow Optimize report it.

Smallest lift worth detecting
Variations, including No Change

No Change is your current page, the control every variation is compared against.

95% significance against No Change and 80% power, the standard settings for a trustworthy test. Webflow Optimize uses sequential testing, so treat these numbers as a planning estimate.

26 weeks

26 weeks

With 5,000 sessions a week at a 2.5% conversion rate, each of your 2 variations needs about 64,196 sessions, 128,392 in total.

To finish in 4 weeks instead, you’d need about 32,098 sessions a week, or a lift of 27% or more.

Not enough traffic for this test

A reliable answer would take 26 weeks. Test a bolder change or a busier page, use an earlier goal like add to cart, or improve from research instead.

Weeks needed at each lift
Weeks needed at each lift
Smallest lift worth detectingWeeks you can run it
5%101 weeks
10%26 weeks
15%12 weeks
20%7 weeks
25%5 weeks
30%4 weeks
35%3 weeks
40%2 weeks
45%2 weeks
50%2 weeks

Test, AI Optimize or personalize?

  • A test splits traffic between your current page, No Change, and one or more variations, and declares a winner once the result is statistically significant. Use it when you want one clear answer.[1][2]
  • AI Optimize shows each visitor the variation most likely to lead to a conversion, sending more traffic to what performs better as it learns. It doesn’t declare a single winner; it keeps optimizing.[3][4]
  • Personalize shows different content to an audience you define, like visitors from one ad campaign, from one country, or coming back for a second visit.[5]

Webflow’s own advice: use a classic test when you need clarity and control, and AI Optimize when speed, scale or flexibility matter most.[6]

What “smallest lift” means

It’s the smallest improvement the test is set up to detect reliably, measured relative to your current rate. At a 2.5% conversion rate, a 10% lift means telling 2.5% apart from 2.75%. Small lifts need far more traffic than big ones, and Webflow suggests aiming for at least a 5% lift in your goal.[17][18][7]

Run whole weeks, at least two

Shoppers behave differently on a Tuesday than on a Saturday. Webflow recommends running a test for at least one to two weeks, and notes that a 30-day test is typically more reliable than a 7-day one. Researchers at Microsoft recommend whole weeks too. That’s why the calculator never shows fewer than two.[7][8][19]

Why a real test can finish sooner or later

This calculator plans a fixed-length test. Webflow Optimize calculates significance with sequential hypothesis testing and declares a winner once significance is reached, so a real test can finish sooner or later than this estimate.[9][2]

If your tool uses a fixed sample instead, decide the length up front and don’t stop early: peek ten times, and what looks like 1% significance is really only 5%.[20]

How AI Optimize reports results

AI Optimize doesn’t use statistical significance, because its traffic isn’t split evenly. It reports Strength instead: every variation starts at 50%, and above 70% counts as a success while below 30% doesn’t.[9][10][11]

By default, AI Optimize runs for 80% of visitors, and the rest are held out to measure the difference. Webflow’s rule of thumb is that the holdout should see at least 100 sessions a day, on a goal that converts at 10% or more. That’s what the AI Optimize check above measures.[3][12]

Personalize with a light touch

Start simple, with a high-signal audience you already understand, like visitors from one paid campaign, and tie every personalization to a goal. Webflow also warns that a site that seems all-knowing comes across as off-putting.[13][14]

What to test first

  • Pages with the most traffic and high bounce or exit rates.[11]
  • Prominent copy first: headlines, subheadings and section headings often give the best return.[11]
  • Write each idea as if, then, because: if we change this, then this goal moves, because of what we saw in the data.[11]
  • Expect most tests to lose. Webflow puts the win rate for teams that use data at roughly 20 to 30%.[11]

Check the split before you read the result

If you set a 50/50 split and the session counts come out noticeably uneven, something in the setup is broken, and the result can’t be trusted until you find out what. Microsoft found this in about 6% of its own tests.[21]

When you don’t have the traffic

  • Test a bigger change. A bold change is more likely to produce an effect large enough to detect with fewer visitors.[22]
  • Measure an earlier step. Add to cart happens far more often than an order, so enter your add-to-cart rate instead and see how the numbers change.[22]
  • Test two versions, not several. Every extra variation needs its own share of traffic.[22]
  • Don’t treat AI Optimize as a shortcut. Webflow notes it needs enough traffic to learn.[1]
  • Learn from research instead. An A/B test tells you which version won, not why. Session recordings, customer questions and an audit show you where shoppers struggle.[23]

Running tests on a Shopify store

Webflow Optimize runs natively on Webflow sites, and on Shopify stores through Webflow’s app for Shopify. Without Shopify Plus, it can’t run in checkout, so checkout-based goals aren’t available.[15]

Shopify’s own Rollouts can also split traffic between your current theme and a changed version, 50/50 by default. Experiments need the Grow plan or higher. Testing apps such as Intelligems and Shoplift add other test types; Shopify’s roundup lists Intelligems for testing prices, shipping and post-purchase offers.[24][25][26][28]

Count sessions and conversions the same way in every tool. Shopify and Webflow Optimize both report conversion rate per session.[27][16]

The math behind it

The calculator uses the standard fixed-sample formula for comparing two conversion rates: a two-sided test at 95% confidence with 80% power, and equal traffic to each version. Visitors per version equal (1.96 + 0.84)² times the sum of each version’s rate times one minus that rate, divided by the squared difference between the two rates.[29]

Other calculators use slightly different versions of the formula, so their answers can differ by several percent. Evan Miller’s popular calculator, for example, shows about 7,700 visitors per version for a 5% to 6% test, where this one shows about 8,200. Either is fine for planning.[30]

Sources

  1. Webflow Optimize Help Center, Compare optimization types (opens in a new tab)
  2. Webflow Optimize Help Center, Create test optimizations (opens in a new tab)
  3. Webflow Optimize Help Center, Create AI Optimize optimizations (opens in a new tab)
  4. Webflow Help Center, AI-optimized optimizations overview (opens in a new tab)
  5. Webflow Optimize Help Center, Build rules-based audiences (opens in a new tab)
  6. Webflow University, Test optimizations (opens in a new tab)
  7. Webflow University, Plan your optimization strategy (opens in a new tab)
  8. Webflow Optimize Help Center, Statistical significance (opens in a new tab)
  9. Webflow Optimize Help Center, Why doesn’t AI Optimize use stat. sig.? (opens in a new tab)
  10. Webflow Optimize Help Center, Strength (opens in a new tab)
  11. Webflow Optimize Help Center, Conversion rate optimization (CRO) best practices (opens in a new tab)
  12. Webflow Optimize Help Center, Holdout group (opens in a new tab)
  13. Webflow University, Optimize checklist for non-Webflow sites (opens in a new tab)
  14. Webflow Optimize Help Center, Key concepts for optimizing webpages (opens in a new tab)
  15. Webflow Optimize Help Center, Install Optimize on a Shopify site (opens in a new tab)
  16. Webflow Optimize Help Center, Review optimization results (opens in a new tab)
  17. Optimizely, Use minimum detectable effect when you design an experiment (opens in a new tab)
  18. Optimizely, How long to run an experiment (opens in a new tab)
  19. Kohavi, Henne and Sommerfield, Practical Guide to Controlled Experiments on the Web (KDD 2007) (opens in a new tab)
  20. Evan Miller, How Not To Run an A/B Test (opens in a new tab)
  21. Microsoft Research, Diagnosing Sample Ratio Mismatch in A/B Testing (opens in a new tab)
  22. Optimizely, Test tips for low-traffic sites (opens in a new tab)
  23. Nielsen Norman Group, Putting A/B Testing in Its Place (opens in a new tab)
  24. Shopify Help Center, Rollouts (opens in a new tab)
  25. Shopify Help Center, Types of rollouts and changes (opens in a new tab)
  26. Shopify Help Center, Rollouts requirements and considerations (opens in a new tab)
  27. Shopify Help Center, Rollout analytics (opens in a new tab)
  28. Shopify, User-Friendly A/B Testing Tools for Ecommerce in 2026 (opens in a new tab)
  29. van Belle and Millard, Statistical Rules of Thumb, Chapter 2: Sample Size (opens in a new tab)
  30. Evan Miller, Sample Size Calculator (opens in a new tab)

What needs attention on your store?

Pick a service and check out, or send a short note about what you want to improve. Either way, you work with me, and you get a written scope before work starts.

Your cart

Nothing here yet. Pick a fixed-price service, or start with the audit.

Browse services

You’ll work directly with Vinney, from the kickoff call to launch.