Why a slow website costs enquiries
Speed is not a technical score. It is the number of people who never saw your page at all, because they left while it was still deciding what to show them.
6 min read·Updated August 2026
The part that gets missed
People do not experience a slow website as slow. They experience it as not having found anything, and they go back and tap the next result. There is no signal in your analytics that says this happened, which is why it is so easy to keep paying for.
It compounds on a phone on mobile data, which is how most people arrive from a message or a search. The site you tested on office wifi on a laptop is not the site your customer is using.
What actually makes sites slow
Images, overwhelmingly. A photograph straight off a camera can be several megabytes; the same photograph sized for the space it appears in and served in a modern format is a fraction of that and looks identical. This one issue accounts for most of the weight on most small business websites.
Then plugins and third-party scripts. Every chat widget, popup builder, analytics tool and review embed is code from someone else that runs before your page finishes. Five of them is normal on a template site and any one can be the thing holding everything up.
Then fonts. Loading six weights of two families when the design uses three is invisible in a design tool and expensive on a phone.
The one nobody mentions: layout that moves
A page that finishes loading in good time can still feel broken if things jump while it settles — an image arriving and pushing text down, a banner appearing above the fold and shifting everything. Everyone has tapped the wrong thing because of this.
It is measurable, it is one of the things search engines score, and it is almost always caused by not telling the browser how big something will be before it arrives. It is also one of the cheapest things to fix.
What is worth doing about it
Test the real thing on a real phone on mobile data, not on the office connection. Then look at the images before anything else, because that is where the weight is. Then count the third-party scripts and remove the ones nobody looks at, which is usually most of them.
Be wary of speed as a product. Caching plugins and optimisation services can help a heavy site, but they are compensating for weight that should not be there. A site that is light to begin with does not need them, and a site that needs them permanently has a structural problem being managed rather than fixed.