Why Is Your Website So Slow, and Does It Actually Cost You Customers?

A visitor taps your homepage on their phone, waits, and taps back to Google before your logo has even finished loading. You never see that bounce in your analytics as "slow website." It just shows up as a visit that lasted four seconds and went nowhere.

Website speed gets talked about as a technical nice-to-have, something for developers to worry about. It isn't. It's one of the few things on your website that directly affects both how many people find you on Google and how many of the people who do find you actually get in touch. Here's what's actually being measured, why it matters more than it used to, and what's worth fixing first.

The three numbers Google actually cares about

Google measures your site using three metrics it calls Core Web Vitals. You don't need to become an expert in them, but it helps to know what they mean in plain terms, because these are the numbers that show up if you ever run your site through a speed checker.

Largest Contentful Paint (LCP) is how long it takes for the biggest visible thing on the page, usually a hero image or headline, to actually appear. Google wants this under 2.5 seconds. Past 4 seconds, it's rated poor.

Interaction to Next Paint (INP) measures how quickly the page responds when someone actually does something, like tapping a menu or a "Get a Quote" button. Under 200 milliseconds is good. Past 500ms, it feels broken to the user even if it technically still works.

Cumulative Layout Shift (CLS) is the one you've felt without knowing its name: you go to tap a button and the page jumps right as your thumb lands, because an image or ad loaded in late and pushed everything down. Google scores anything under 0.1 as good.

Google checks these using real visitor data, not a lab test, and it needs roughly three out of four of your actual visitors to have a "good" experience before it counts your page as passing. A site that loads fast on a decent office broadband connection can still fail this if most of your real traffic is on patchy mobile signal, which for a lot of UK small business sites, it is.

Why this is a sales problem, not just an SEO one

The ranking impact is real but modest. The bigger cost is the one you don't see in a rankings report.

Research going back several years, and repeated since, has consistently found the same pattern: as a page's load time goes from one second to three seconds, the chance a visitor bounces straight back out increases by around 32%. Push that to five seconds and it roughly doubles again. More than half of mobile visitors will abandon a page that takes longer than three seconds to load.

It adds up on the conversion side too. A delay of just 100 milliseconds, a tenth of a second, has been shown to cost retailers around 7% of conversions. That's not a typo. Shaving even 0.1 seconds off load time has produced measurable conversion gains in the other direction for both retail and travel sites. None of this requires your site to be "broken." It just needs to be a bit slower than the alternative your visitor has already half-decided to try instead.

For a trades business, consultancy, or local service provider relying on a contact form or a phone number tap, a slow site isn't losing you rankings quietly in the background. It's losing you the enquiry that already landed on your page and then left before filling in the form.

What's usually actually causing it

In our experience rebuilding and auditing sites for UK small businesses, the same handful of culprits show up again and again, roughly in this order of how often we find them:

Unoptimised images are the single biggest offender. A photo straight off a phone camera or a stock photo site can be 4-8MB. On a page with five of those, you're asking a visitor's phone to download tens of megabytes before they've read a word.

Too many plugins or third-party scripts come next, especially on WordPress sites that have accumulated a chat widget, two different analytics tools, a popup builder, and a form plugin over several years, each one loading its own JavaScript on every single page whether it's needed there or not.

Cheap or shared hosting is a quieter cause. If your site sits on hosting shared with hundreds of other small sites, your "fast enough" day can become "painfully slow" the moment another site on the same server has a traffic spike.

A bloated theme or template, particularly multipurpose WordPress themes built to handle every possible layout, loads code for features your site never actually uses.

Checking your own site in five minutes

Before paying anyone to fix anything, it's worth seeing where you actually stand. Google's free PageSpeed Insights tool (just search for it) will run your homepage through both a lab test and, if you get enough traffic, real visitor data, and hand you a score along with the specific things slowing you down. If you have a Google Search Console account set up for your site, its Core Web Vitals report shows the same picture across every page on your site, not just one.

Don't panic over a score in the 70s or 80s. Don't ignore one in the 30s or 40s, especially on mobile, which is almost always worse than desktop and is usually where most of your actual visitors are.

What's worth fixing, and what isn't

Not every slow site needs a full rebuild, and we'd rather tell you that upfront than sell you one you don't need. If the issue is a handful of oversized images and an unused plugin or two, that's often a half-day job on an existing site. If the underlying problem is the hosting, the theme, or a site that was built years ago on a platform that's since been abandoned by its developer, patching around it starts costing more than starting again properly would.

The honest answer depends on what's actually wrong, and that's not something you can tell from the outside. If you want a second opinion on where your own site stands and what, if anything, is actually worth fixing, Digital Hand offers a free 15-minute consultation where we'll look at your real numbers and tell you straight, not just quote you a rebuild.