Most people will never tell you your website is slow. They will not email to complain or leave a review about it. They will simply be somewhere else by the time your homepage has finished loading, and you will never know they were there at all. That is what makes speed such an easy problem to ignore: the cost of it is invisible.
I have lost count of the small business owners who assumed their site was fine because it loaded quickly for them. Of course it did. It was already in their browser cache, they were sitting on decent office broadband, and they were looking at it on a laptop. Their customers are often none of those things. They are on a phone, on patchy mobile signal, halfway through comparing three businesses at once. Give them a spinning screen and they are gone.
How slow is too slow
There is a well-worn figure worth knowing. As a page's loading time climbs from one second to three, the chance of someone giving up and leaving rises sharply, and it keeps climbing after that. You do not need to memorise the exact numbers. The point is that the first couple of seconds do most of the damage, and every second beyond that is quietly costing you people who were interested enough to click.
Google has its own way of measuring this, a set of scores it calls Core Web Vitals. Strip away the jargon and they are really asking three plain questions. How long before the main content appears? How quickly can someone actually tap or type once it is there? And does the page jump about while it loads, so people tap the wrong thing? You can check your own site for free using Google's PageSpeed Insights. Type in your address and it will grade you, both on real-world data and a lab test, and flag what is dragging you down.
Be warned, the report is technical and a bit gloomy. Do not panic at a low score. Read it as a rough temperature check, not a verdict.
It is not just about losing impatient visitors
The obvious cost of a slow site is the person who leaves. There is a second cost that hurts more, and it is the one most owners miss.
If you pay for Google Ads, your landing page speed feeds directly into what Google calls your Quality Score. Put simply, Google would rather not send someone who just clicked an advert to a page that takes an age to load, so it quietly charges you more for the privilege. A slow page can mean you pay a higher cost per click than a competitor bidding on the very same keyword. You are handing money to Google for the sin of being slow. This is one of the reasons a proper landing page built for speed usually earns its keep several times over.
Organic search works on the same instinct. Speed is not the single biggest thing Google weighs when deciding who ranks, and anyone who tells you it is is overselling it. But when two businesses are otherwise evenly matched, the faster, smoother experience tends to edge ahead. It is a tie-breaker, and in a competitive local market tie-breakers matter. Good SEO has always been part content, part technical housekeeping, and speed sits firmly in the housekeeping.
What actually makes a site slow
In my experience it is nearly always one of a small handful of culprits, and the biggest one by a mile is images.
Someone uploads a photo straight off their phone, a lovely 6,000-pixel-wide image several megabytes in size, and drops it on the homepage where it is displayed at a fraction of that. The browser still has to download the whole enormous thing. Multiply that across a gallery and you have a page that weighs as much as a small video. Resizing images to sensible dimensions and saving them in a modern format is often the single most effective thing you can do, and it costs nothing but a bit of care.
After images, the usual suspects are:
- Cheap, overloaded hosting, where your site shares a straining server with hundreds of others and slows to a crawl at busy times.
- A page buried under plugins and tracking scripts, each one loading its own little parcel of code. This is the classic fate of an ageing WordPress site that has had features bolted on for years.
- Bloated page builders and heavy themes that ship far more code than a simple business site will ever use.
None of these are exotic. They are the ordinary consequences of a site that was built quickly, cheaply, or a long time ago, and then left alone.
What to actually do about it
If you take nothing else from this, start with your images, because that is where the quick win almost always hides. Compress the big ones, resize anything larger than it needs to be, and you will often shave a second or two off the load time in an afternoon.
Beyond that, be honest about the foundations. Some sites are slow because of a few fixable things. Others are slow because of how they were built, and no amount of tinkering will truly fix a heavy old site sitting on tired hosting. There comes a point where patching costs more time and worry than starting fresh on something built properly. A modern, lightweight website that loads fast on a phone is not a luxury any more, it is the baseline your customers quietly expect.
And do measure the effect, rather than trusting your gut. Speed up a page, then watch what happens to how many people stay and get in touch over the following weeks. This is the same habit I bang on about with any website change: make the improvement, check the numbers, keep what works. If your traffic is healthy but the enquiries are not, speed is well worth ruling in or out, and it is one of the first things I look at when a site gets visitors but no enquiries.
Worth an hour of your time
Speed is one of those problems that feels technical and therefore easy to put off. It needn't be. Run your homepage and your busiest service page through PageSpeed Insights, sort out any oversized images, and you will have done more than most of your competitors have bothered to.
If the report leaves you none the wiser, or you suspect the trouble runs deeper than a few big photos, get in touch. We will take an honest look at what is slowing your site down and tell you plainly whether it is a quick fix or a sign the foundations need rethinking.