Page Speed Revenue Loss Calculator
Model how a difference in page speed could affect a revenue scenario. The calculator assumes a 7% conversion-rate change per second; it does not test your site or predict actual sales.
Page Speed Revenue Loss Calculator
Explore a scenario using an illustrative 7% reduction in conversion rate for each additional second. This fixed assumption does not measure your visitors or lost sales.
Estimated lost conversions / month
—
Estimated lost revenue / month
£—
Illustrative annual value
£—
The model compounds its fixed 7% assumption across the time difference you enter. It uses your traffic, conversion rate and customer value; it is not a forecast or a guarantee of recovery.
Save & share this result
How to check your real load time
- PageSpeed Insights, Google's own tool, shows Core Web Vitals.
- WebPageTest, more detailed waterfall view.
- Google Search Console → Core Web Vitals report, shows real-user data from your actual visitors.
Common causes of slow sites
- Oversized images.
- Too many plugins (WordPress especially).
- Render-blocking JavaScript and CSS.
- Heavy third-party scripts (chat widgets, analytics, retargeting tags).
- Slow server response.
Frequently asked questions
What does the 7% assumption mean? +
This calculator uses a fixed illustrative assumption: each extra second reduces the conversion rate by 7%, compounded. It is not an industry average or a measurement of your website. Compare actual visitor and conversion data before deciding what a speed improvement is worth.
How should I check my actual performance? +
Use PageSpeed Insights and the Core Web Vitals report in Google Search Console to inspect real-user experience where data is available. A page-load estimate alone does not explain how your own visitors convert.
Where should I start improving speed? +
Inspect the page first. Oversized images, unused scripts, font loading, cache settings and server response can all matter. Prioritise the bottleneck shown by a performance trace and compare before and after under the same conditions.
Will a hosting upgrade fix it? +
It can help when server response is the bottleneck. Image weight, scripts and other front-end work may require separate changes. Measure the cause before choosing an upgrade.