A slow website rarely announces itself. Nobody rings to say your homepage took six seconds to load. They just leave, and you never know they were there.
That is what makes speed such a quiet problem. The cost is real, but it hides in the gaps: the enquiry that never came, the ranking you never won, the customer who went to a competitor whose site felt sharper.
We spend a lot of time fixing slow sites, so here is a straight explanation of what slow actually costs, and how to work out whether your site has a problem.
Why speed costs you money
Speed affects three things at once, and they compound.
People leave. When a page hangs, visitors bounce. This is worst on mobile, where a lot of your traffic now sits, and where connections are patchier than the office wifi you built the site on. A user on a train with two bars does not experience your site the way you do on a fibre line.
Google notices. Page experience is part of how Google ranks pages. Its Core Web Vitals measure loading, interactivity and visual stability. A slow site is not automatically buried, but when you and a competitor are otherwise even, speed can be the tie-breaker. All else being equal, the faster page tends to win.
Trust drops. A site that stutters, jumps around while loading, or takes a beat to respond to a tap feels cheap. People read that as a signal about the business behind it. Fair or not, a sluggish checkout makes them doubt whether their card details are safe.
The frustrating part is that these three feed each other. Fewer visitors and higher bounce rates send weak signals to Google, which lowers rankings, which cuts traffic further.
How to tell if your site is slow
You cannot trust your own gut here. Your browser has the site cached, you are on good broadband, and you know exactly where everything is. You are the worst possible judge of your own site's speed.
Use real tools instead. All of these are free.
PageSpeed Insights. Google's own tool. Paste in a URL and it gives you a score for mobile and desktop, plus the specific problems. Test your homepage, but also test a product page and a service page, because they often behave very differently.
The field data section. In PageSpeed Insights, look for real-world data from actual Chrome users rather than the lab test. This is the closest thing to how your real audience experiences the site. If it says your Largest Contentful Paint is over 2.5 seconds, that is your headline problem.
Your phone, on mobile data. Turn off wifi. Clear the cache or use a private window. Load your site cold and count. If you are waiting and wondering whether it has broken, so are your customers.
What actually makes sites slow
In our experience, the culprits are boringly consistent.
Enormous images. By far the most common offender. Someone uploads a 4000 pixel wide photo straight off a camera and the browser has to download all of it to show a small thumbnail. Images should be sized and compressed for the web, and served in modern formats.
Plugin sprawl. This is the WordPress classic. Every plugin adds code that has to load. A site with thirty active plugins is dragging a lot of extra weight, much of it for features nobody uses. We wrote more about this trade-off in custom website vs WordPress vs template.
Third-party scripts. Chat widgets, analytics, heatmaps, ad pixels, embedded videos. Each one phones home to another server and can block your page while it does. Marketing tools have a habit of piling up until nobody remembers why half of them are there.
Cheap or overloaded hosting. If your host crams thousands of sites onto one server, your site fights everyone else for resources. Bargain hosting often shows up as inconsistent load times: quick sometimes, painfully slow at others.
No caching. Without caching, the server rebuilds every page from scratch for every visitor. Caching stores a ready-made version so it can be served instantly. Its absence is a quick win when we find it.
What good looks like
You do not need a perfect score. A green score is nice, but the honest target is that your main content appears fast and the page responds immediately to taps and clicks.
Practically, aim for the largest visible element to load within about 2.5 seconds on mobile field data, and for the layout to stay put while it loads rather than shifting under the reader's thumb. Get those right and the score usually follows.
Do not chase a hundred out of a hundred at the cost of everything else. We have seen sites gutted of useful features in pursuit of a number that made no difference to a single customer. Speed serves the business, not the other way round.
Where to start if yours is slow
Work in order of effort versus payoff.
- Fix the images first. Compress and resize them. This alone often takes seconds off load time and requires no developer.
- Audit your scripts. List every third-party tool loading on the site. Remove anything you are not actively using. Be ruthless.
- Turn on caching. Most platforms support it. If yours does not by default, this is worth a conversation with whoever maintains the site.
- Check your hosting. If you are on the cheapest shared plan and the site is important to your business, that is a false economy.
- Rebuild if the foundations are rotten. Sometimes a site is slow because it was built badly, layered with themes and page builders that fight each other. No plugin fixes that. At that point a proper rebuild is cheaper than endless patching.
If you get to step five, this is where good engineering earns its keep. A site built lean from the start does not need heroic optimisation later, because it was never bloated in the first place.
The bottom line
Speed is not a vanity metric. It is the difference between a visitor becoming a customer and a visitor becoming a bounce statistic you never see.
Test your site honestly, on a phone, on mobile data, with a clear cache. Then start with the images. Most sites we look at can shed a large chunk of their load time with a morning's work and no rebuild at all.
The ones that cannot are usually the ones that most need looking at properly.
Lewis, Technical Director
