free_tool
What is slowness costing you?
"The site feels slow" never wins a roadmap fight. A dollar figure does. Put in your load time, traffic, conversion rate and order value, set a target, and see the revenue you'd capture by getting faster, plus what a single 100 milliseconds is worth every month.
Default 1% is in line with the often-cited Walmart / Amazon retail figures. Lower it for low-intent traffic, raise it for checkout flows.
Revenue uplift / month
+$20.6K
$246.8K / year · +428 conversions / mo
Shaving 1.7s lifts conversion 17.0% relative.
- Revenue now
- $121.0K/mo
- Revenue at target
- $141.5K/mo
- Conversion rate
- 2.1% → 2.46%
That uplift is the business case for the performance work. I'll find where your real load time goes and what it takes to actually hit the target.
Make the speed case: book a callA modeling tool, not a guarantee. It scales conversion linearly with the time saved at a sensitivity you control, and caps the modeled lift so an extreme speedup can't imply a fantasy multiplier. Use it to size the opportunity and frame the conversation, then validate with a real A/B test.
how_it_works
Speed is a conversion lever, not a vibe
The math is on the table: current revenue is visits × conversion rate × order value. Faster pages convert better, so the uplift is that revenue times the relative lift the speedup buys you. The only judgement call is the sensitivity, how much conversion moves per 100ms, and you set it.
Walmart, Amazon and Deloitte have all published versions of the same finding: every fraction of a second moves revenue measurably. This puts your numbers into that frame so "make it faster" arrives at the planning meeting with a price tag attached.
faq
Questions & answers
- How does the Page Speed to Revenue Calculator estimate lost revenue?
- It works out your current monthly revenue from visits, conversion rate and value per conversion, then models a conversion lift that scales with the milliseconds you save at a sensitivity you set. The lift is capped so an extreme speedup cannot imply an unrealistic multiplier.
- Where does the default sensitivity of 1% per 100ms come from?
- It reflects widely cited retail studies from Walmart and Amazon. Lower it for low-intent traffic and raise it for high-intent flows like checkout, since the right number depends on your funnel.
- Is this a guarantee of revenue gain?
- No. It is a modeling tool to size the opportunity and frame the conversation, not a promise. Validate the actual lift with a real A/B test before you bank on it.
- Does it account for the cost of the performance work?
- No. It models the revenue upside of a speedup but not the engineering effort to reach the target, seasonality, or traffic mix. Use it to justify a project, then weigh it against the work involved.
- Are my traffic and revenue figures kept private?
- Yes. Everything is computed in your browser and nothing is sent to a server. Your numbers only enter the URL if you choose to share a link.
Ready to capture that uplift?
I'll find where your load time actually goes and what it takes to hit the target, so the revenue case turns into shipped milliseconds. Book a call, or leave your email.
Prefer proof first? See how this plays out in real case studies →