A slow website is a quiet tax on every enquiry.

Speed is the easiest thing on a website to ignore. It doesn't show up in a design review, it doesn't feel like marketing, and on the office wifi the site loads fine. So it sits there, quietly costing you visitors, while everyone looks at the things that are easier to see.

The trouble is that your visitors aren't on your office wifi. They're on a phone, on a train, with three other tabs open and no patience. And if your page makes them wait, a good number of them are gone before they've seen a word of it.

What slow actually costs

People leave slow pages, and they leave fast. Google's own research put it plainly years ago: as page load time goes from one second to three, the chance of someone bouncing rises sharply, and it keeps climbing with every extra second. These are people who wanted what you offer enough to click. They just weren't willing to wait for it.

That loss is invisible in a way that makes it dangerous. You never see the enquiry that didn't happen because the page hadn't loaded. There's no bounce notification, no angry email. The visitor simply goes back to the results and clicks the next business down, and you're none the wiser.

A slow site doesn't announce the damage. It just quietly hands your visitors to whoever loads faster.

Google is watching the clock too

It isn't only visitors who notice. Google measures the loading experience of your pages through a set of metrics called Core Web Vitals, and it uses them as a ranking signal. They cover three things a visitor feels directly: how quickly the main content appears, how fast the page responds when they interact with it, and whether things jump around as it loads.

Speed alone won't lift a weak page above a strong one. But when two pages are close, the faster one has the edge, and a genuinely slow page can be held back by it. So a slow site gets hit twice: fewer people stay, and you're competing from further down the results to begin with.

Why sites end up slow

Most slow sites didn't start that way. They got heavy over time. An oversized image straight from a phone camera. A stack of plugins and tracking scripts, each added for a good reason and never removed. A video autoplaying in the background. A template doing far more than the site actually needs. None of it feels like a problem on its own. Together, they add up to a page that takes its time.

The frustrating part is that speed problems are usually fixable, and often without touching how the site looks. Compressing images, cutting scripts that aren't earning their place, and sorting out how the page loads can take seconds off the experience without a single visible change to the design.

What to do about it

Start by measuring it properly, on a phone, on a normal connection, not on the office broadband. Free tools will show you your Core Web Vitals and where the time is going. That tells you whether you have a problem worth fixing.

Then deal with the heavy things first, which is almost always images and scripts. That's where the biggest wins usually hide, and where a small amount of work makes the most visible difference to how fast the page feels.

Then keep an eye on it, because sites get slow the way they got slow the first time: gradually, through small additions no one thinks twice about. A fast site today drifts back to slow if no one is watching.

This is part of what we look after. Speed sits underneath everything else in search, quietly shaping how many people arrive, how many stay, and how many get in touch. If your site feels sluggish, or you've never actually checked, it's usually costing you more than you'd think.