Why Your Website's Speed Decides Whether Customers Ever See It

Your website has about as long as it takes to sigh before a visitor gives up on it. On a phone, on rural coverage, with three other tabs open — if the page is still assembling itself, they're back on Google tapping the next result. Your competitor's.

Speed isn't a technical nicety. It decides whether people — and Google — take your site seriously. Here's the plain-English version of how that works.

What Google actually measures

Google grades every site on a set of metrics called Core Web Vitals, and uses them as part of how it ranks search results. There are three, and Google publishes the thresholds openly:

• Largest Contentful Paint (LCP) — how long until the main content is visible. Good is 2.5 seconds or less.
• Interaction to Next Paint (INP) — how quickly the page responds when someone taps or clicks. Good is 200 milliseconds or less.
• Cumulative Layout Shift (CLS) — how much the page jumps around while loading (the reason you tapped the wrong button on a news site). Good is 0.1 or less.

Fail these and you're fighting uphill twice: rankings suffer, and the visitors who do arrive are quietly leaving before the page settles.

Why so many small business sites fail

Most slow sites aren't slow because of anything the business did wrong. They're slow because of how they were built:

• Page builders and heavy themes load their entire toolkit on every page — sliders, animations, plugin scripts — whether the page uses them or not.
• Unoptimised images straight off a phone camera can weigh more than everything else on the page combined.
• Plugin stacking — each one adds its own scripts and styles, and nobody ever removes them.
• Cheap shared hosting adds a delay before the page even starts loading.

Each one alone is survivable. Stacked together — which is exactly what the "quick and cheap" route produces — you get a site that fails all three vitals on a mid-range phone.

Check your own site in two minutes

You don't need to take anyone's word for this, ours included:

1. Go to pagespeed.web.dev — Google's own free testing tool.
2. Enter your website address.
3. Look at the mobile score first — that's how most of your customers experience your site.

The report shows your Core Web Vitals with pass/fail marks. Run your main competitor while you're there; it's an education.

What "fixing it" looks like

Sometimes a slow site can be rescued: compressing images, removing dead plugins, upgrading hosting. That's real work worth doing, and if the structure underneath is sound, it can move the numbers meaningfully.

But if the site was built on a heavyweight foundation, tuning it is like tuning a tractor for a race. This is why we hand-code our sites instead of assembling them: every page ships only the code it actually needs, images are optimised automatically, and passing Core Web Vitals is a design requirement from day one — not an optimisation project afterwards.

The honest takeaway

Speed is one of the few things in web design you can verify yourself, for free, in two minutes — before ever talking to a designer. Test your site. If the mobile numbers are red, that's not a cosmetic problem; it's rankings and customers leaking away daily.

And if you'd like someone to look at the results with you and give you a straight answer about whether your site needs tuning or rebuilding, send it our way — the review is free and the advice is honest either way.