Why Your Website Speed Matters (And What "Fast" Actually Means)

Here is a number to sit with: if your website takes longer than three seconds to load on a phone, roughly half the people who tapped your link have already left. They are not waiting. They are back on Google, tapping your competitor.

That is not a guess. Google's own research says the chance of someone leaving goes up 32% when a page takes one to three seconds to load. At five seconds, it is 90% higher. Those percentages are real people. Real phone calls you never got.

What "fast" actually means

You do not need to care about milliseconds. Here is the simple version: your website should feel instant. Tap a link, the page appears. Not "appears after a white screen." Not "appears one section at a time while images shuffle into place." Instant.

Google splits this into three measurements they call Core Web Vitals. Ignore the jargon. Here is what each one actually means for your site:

LCP (Largest Contentful Paint). How long until the main thing on the page appears. For a trades website, that is usually your hero heading or your main photo. Google says under 2.5 seconds is good. Over 4 seconds is poor. If someone taps your link and stares at a blank white screen for three seconds, that is a bad LCP.

INP (Interaction to Next Paint). How fast the site reacts when someone taps a button or opens your menu. If they tap "Call Now" and nothing happens for half a second, that feels broken. It builds doubt. "Is this site even real?"

CLS (Cumulative Layout Shift). Whether things jump around on the page while it loads. You know this one. You go to tap a button, a photo suddenly loads in and the button moves, and you tap the wrong thing. That drives people mad. It is also a signal to Google that your site is poorly built.

What slows a site down

Most slow local business sites have the same three problems, and none of them need a developer to spot:

1. Massive images. A photo straight from your phone might be 4,000 pixels wide and 5MB. Your website needs it to be maybe 800 pixels wide and under 100KB. That is an enormous difference, and most sites never compress their images properly.

2. Too much stuff loading at once. Tracking scripts, social media feeds, video backgrounds, chat widgets. Every extra thing your site loads adds time. Most of it you do not need. That Facebook feed widget showing your last three posts? It is loading from Facebook's servers, and it is slower than everything else on your page.

3. Cheap hosting. If you are paying £3 a month for hosting, your site is sitting on a server shared with hundreds of other sites, running on hardware that was slow five years ago. Fast hosting costs more. But losing customers costs more than that.

Real numbers from the real world

Google found that mobile sites taking five seconds to load earn up to twice as much ad revenue as sites taking 19 seconds. Not a typo: twice as much revenue from a 14-second difference. That is an ad-funded study, but the principle holds for a plumber or a roofer too. Faster site, more people stick around, more phone calls.

Another study from Portent showed that a site loading in one second converts about three times better than a site loading in five seconds. For a trades business, that means: one-second load time, three jobs booked. Five-second load time, one job booked. Same traffic, same ads, same everything. Just the speed.

What you can check right now

Open your website on your phone. Not on WiFi. On mobile data. Count how long it takes to actually show something you can read. If it is more than three seconds, you have a problem.

Then go to PageSpeed Insights. It is Google's free speed test tool. Just search for it. Paste in your web address and hit "Analyze." It gives you a score out of 100 for both mobile and desktop. Anything below 50 on mobile is urgent. Below 30 is costing you real money.

The report looks technical, but scroll past the charts to the "Opportunities" section. It tells you in plain English what to fix: "Serve images in next-gen formats," "Reduce unused JavaScript," "Eliminate render-blocking resources." Each one has an estimated time saving. Start with the biggest saving.

The bottom line

Speed is not a tech problem. It is a customer problem. Every extra second your site takes to load is another person who went back to Google and called someone else. The fix might be as simple as resizing your photos or switching hosts. And the payback is immediate.