Free tool Core Web Vitals · Revenue impact
Speed Test, Revenue Lost
Every second costs you money. This is the invoice.
Test any page, add your traffic and revenue numbers, and see what the delay is costing you a year. Then download the fix list, ordered by what moves the needle first.
1 · Test the page
Using a PageSpeed API key?
Optional. Without one you get a small free quota that can rate-limit on a busy day.
2 · Your numbers
3 · How cautious should the estimate be?
Balanced: every second of delay moves conversion rate by about 12%. Sits between the widely cited Akamai and Deloitte findings.
Leaking every year
£0
Add your numbers and this updates as you type.
Per month
£0
Per day
£0
CVR at target
0%
Monthly revenue at each load time
Revenue by connection type
Same page, different networks. Estimated from your page weight, so it updates when you test a URL.
Using this in your ad targeting
Meta: the ad set device settings include "only when connected to Wi-Fi". Worth switching on if the gap above is wide, or if the conversion needs a big download.
Google: connection-type targeting is gone — you now target carriers regardless of connection, with a Wi-Fi traffic option on Display. Use device and location bid adjustments as the proxy.
Location: 5G and full fibre skew to city centres and newer housing; rural and edge-of-network areas sit on 4G or worse. If the 3G and 4G rows look bad, tighten your radius to urban postcodes until the page is fixed — don't pay for clicks the page can't serve.
Your fix list
Ordered by impact. Uses your real audit if you've tested a URL, otherwise the standard priority order.
Conversion rate is modelled as decaying with load time using the setting you pick above, capped at 2.5× current conversion so the output stays defensible. It sizes the opportunity — your own before/after data is the real answer.