The short answer
People leave slow pages, and on a paid click that departure costs money directly. The loss does not appear as a line item, which is why it persists.
Test the page you actually advertise, on mobile data, from where your customers are.
Measure the real experience
- Throttle to a realistic mobile connection, not office broadband
- Use a mid-range device profile, not the latest phone
- Test the advertised page, not the home page
- Test from the region your customers are in
- Repeat after every deployment
Development machines on fast connections make everything look acceptable. The gap between that and a real phone on mobile data is where the spend disappears.
What usually causes it
| Cause | Typical fix |
|---|---|
| Large unoptimised images | Resize and use modern formats |
| Render-blocking scripts | Load asynchronously or defer |
| Too many third-party tags | Audit and remove the unused |
| Fonts blocking text display | Preload, with a visible fallback |
| Form loading separately | Include it in the initial render |
Images and third-party tags account for most of it on the business sites we look at, and both are fixable without touching the application.
Fix in order of effect
- Find the largest resources blocking the first render.
- Fix those, then re-measure before moving on.
- Audit third-party scripts and remove anything with no owner.
- Make sure the form is part of the first render, not loaded after.
- Set a budget and monitor it so regressions are caught.
Step five is what keeps the improvement. Pages get slower as features are added, and without monitoring the gain is lost within a few releases.
The compounding benefit
A faster page improves paid conversion, organic conversion and user experience at the same time. Unlike a campaign change, it does not stop working when you stop paying.
For a modest advertising budget, fixing the page is frequently a better first investment than increasing the spend.