A/B Testing Website Load Time Formula
Learn how to calculate per-page load-time improvement and total monthly visitor waiting time saved when variant B replaces variant A.
This calculation estimates the aggregate page-load waiting time that changes when an A/B test variant is rolled out to all expected monthly traffic. It combines traffic volume, pages viewed per visitor, and the average load-time difference between the two variants.
- 100% Free
- No Sign-Up Required
- Private & Secure
- Mobile Friendly
Monthly Visitor Time Saved
Where:
First estimate monthly page views. Then multiply them by the seconds that variant B is faster than variant A, and divide by 3,600 to convert total seconds into hours.
Variables Explained
| Variable | What It Means | Unit |
|---|---|---|
| monthlyVisitors - Monthly visitors | Estimated unique visitors who would see the selected variant in a typical month. | number |
| pageViewsPerVisitor - Average page views per visitor | Average number of page loads per visitor during the month or relevant session period. | number |
| variantALoadTime - Variant A average load time | Average page load time for the control or current version. | seconds |
| variantBLoadTime - Variant B average load time | Average page load time for the test or proposed version. | seconds |
Step-by-Step Calculation
Estimate monthly page views
Multiply expected monthly visitors by the average number of pages each visitor loads.
monthlyPageViews = monthlyVisitors * pageViewsPerVisitor
Find the per-page load-time difference
A positive result means variant B loads faster. A negative result means variant B is slower.
loadTimeDifference = variantALoadTime - variantBLoadTime
Calculate the percentage improvement
Divide the time difference by variant A's load time to express the change as a percentage.
loadTimeImprovement = (loadTimeDifference / variantALoadTime) * 100
Calculate total seconds changed
Apply the per-page time difference to every estimated monthly page view.
monthlyTimeSavedSeconds = monthlyPageViews * loadTimeDifference
Convert the total to hours
Divide aggregate seconds by 3,600 to show the monthly result in hours.
monthlyTimeSavedHours = monthlyTimeSavedSeconds / 3600
Example: Variant B is 2 seconds faster
Monthly page views
100,000 × 3
300,000 page views
Per-page load-time difference
3.2 − 1.2
2.0 seconds per page
Load-time improvement
(2.0 ÷ 3.2) × 100
62.5%
Total waiting time saved
300,000 × 2.0
600,000 seconds
Convert to hours
600,000 ÷ 3,600
166.7 hours
Final Result
If all estimated traffic uses variant B, it saves approximately 166.7 aggregate visitor waiting hours per month versus variant A.
Assumptions
- ✓Monthly visitor volume and pages per visitor represent a typical month.
- ✓Both variants use comparable average load-time measurements from the same metric, pages, devices, locations, and testing conditions.
- ✓All estimated monthly page views are assumed to move from variant A to variant B.
- ✓Each page view is weighted equally in the aggregate waiting-time estimate.
- ✓The calculation treats the entered load times as averages rather than showing the distribution of individual visitor experiences.
Limitations
- !The result estimates waiting time only and does not predict conversion rate, engagement, revenue, retention, or search performance.
- !Averages can hide slower experiences for particular device types, regions, connection speeds, or page templates.
- !Actual rollout traffic may be lower than total monthly traffic if the improved variant is used on only some pages or audiences.
- !Caching, third-party services, seasonal traffic, and changes in visitor behavior can make future results differ from the estimate.
Common Mistakes to Avoid
Entering total page views as monthly visitors and then also entering pages per visitor, which counts page loads twice.
Comparing different performance metrics, such as a median value for variant A and a percentile value for variant B.
Using load times measured on different page types, device mixes, traffic sources, or date ranges.
Treating a positive time-saved result as proof that conversions or revenue will increase.
Ignoring a negative result, which indicates that variant B is slower than variant A.
Using a small test-sample load time as though it represents all production traffic without checking comparability.
Related Formulas
Frequently Asked Questions
How is monthly visitor time saved calculated?
Monthly visitors are multiplied by page views per visitor to estimate page views. That number is multiplied by variant A's load time minus variant B's load time, then divided by 3,600 to convert seconds to hours.
What does a positive load-time difference mean?
A positive difference means variant B is faster than variant A by that number of seconds per page load.
What does a negative monthly time saved result mean?
It means variant B is slower than variant A based on the entered values, so a full rollout would add estimated aggregate visitor waiting time.
How is load-time improvement percentage calculated?
The calculator divides the load-time difference by variant A's load time and multiplies by 100. This shows the relative reduction from the control version.
Should I use average, median, or percentile load time?
Use one consistent metric for both variants. Median or percentile measurements may be useful when outliers matter, but the two values must be measured in like-for-like conditions.
Why are results shown in aggregate hours?
Aggregate hours translate a small per-page difference into the total waiting-time change across all estimated page loads in a month.
Ready to calculate your result?
Use the calculator to get instant results with your own inputs.