What a slow website costs you is measurable, not theoretical

Aug 29
3 min read

Updated: 2 days ago

Introduction

The site works. Everybody at the company opens it daily, it loads acceptably on the office connection, and nobody has complained. The conclusion drawn is that speed is not a problem worth spending money on.

The people it is a problem for are not in a position to complain. They tapped a link on a phone with a weak signal, waited, and went back to the results page. They do not appear in your enquiry count, they do not send an email, and the only trace they leave is a gap between the traffic you paid for and the traffic that arrived.

1. What a slow website costs you shows up as absence, not as failure

The reason it stays invisible.

Nothing breaks. No error is logged, no customer telephones, and the analytics show fewer sessions than the advertising platform reports clicks. That discrepancy is the cost, and it is routinely attributed to tracking problems rather than to people leaving.

2. Measure it on the connection your customers actually use

Office broadband is the wrong test.

Throttle a test to a mid-range phone on a mobile connection and load the page you send paid traffic to. The difference between that result and the one you get on a desktop over fibre is usually several seconds, and the mobile figure is the one that governs behaviour.

3. Work out the money using your own conversion rate

The calculation is simple enough to do on paper.

Take your monthly sessions, your conversion rate, and your average order or enquiry value. A recovery of even a small proportion of abandoned sessions produces a figure the business recognises, which is what turns speed from a technical preference into a funded project.

4. Look at the entry page, not the home page

Speed tests are usually run on the wrong address.

Most visitors arrive on a service page, a product page or an article from search or an advert. Those pages often carry more images and more embedded scripts than the home page does, and they are the ones being judged.

5. Find out what is actually heavy

Diagnosis before spending.

Open the network view in a browser developer tool, sort by size, and look at the largest items. On most small business sites the answer is uncompressed images, a slider nobody scrolls to, and three or four tracking scripts added over the years and never removed.

6. Understand which delays visitors actually feel

Not every second is equal.

A page that shows its main content quickly and finishes loading peripheral items afterwards feels fast, even when the total load time is unchanged. Perceived speed is what governs whether somebody stays, and it can often be improved without reducing the page weight at all.

7. Count the advertising you are wasting

The cost falls hardest on paid traffic.

Every click you pay for that leaves before the page renders is spend converted into nothing. If a meaningful share of paid sessions never reach a rendered page, your real cost per acquisition is higher than the platform reports it to be.

8. Accept that the search effect is real but secondary

Get the emphasis right.

Speed influences rankings, but modestly, and a fast page with weak content does not outrank a slow page with strong content. The business case rests on the visitors you keep, not on a position change, and framing it that way survives contact with reality.

9. Fix the largest item first and stop there for now

Sequence matters more than completeness.

Compressing images and removing unused scripts typically recovers most of the available improvement for a fraction of the effort. Pursuing a perfect score on a testing tool consumes far more time and delivers far less than the first two changes already did.

Re-measure after any significant site change, because speed regresses quietly. A new plugin, an added tracking pixel or a marketing video embed can undo a year of work, and nobody notices until the numbers have already moved.

Conclusion

Recognise that the cost appears as absence rather than as a fault report, which is why it goes unfunded for years.

Test on a mid-range phone over a mobile connection rather than on office broadband, calculate the money using your own sessions and conversion rate, measure the pages people actually land on rather than the home page, identify the heaviest items before changing anything, understand that perceived speed governs behaviour, count the paid clicks that never reach a rendered page, keep the ranking argument secondary to the retention argument, fix the biggest item first, and re-measure after every significant change.