Does a plumber in Bridgnorth really need to care about Core Web Vitals?

Somebody has probably sent you a report with a number out of 100 on it, coloured red, along with a suggestion that this is why your phone isn’t ringing.

The honest answer to the question in the title is: no, not really, and also yes, but not for the reason you’ve been given.

Here’s the version without the jargon.

What the three measurements actually are

Google watches three things about how a page behaves for real visitors. They have forbidding names and extremely ordinary meanings.

That’s it. Does it appear quickly, does it respond when poked, and does it stay still. Every small business owner already has strong opinions about all three, they just express them as “that website is rubbish on my phone”.

The third one is the most underrated. Layout shift is the reason you tap Call us and hit Cookie settings instead, because an advert loaded a fraction of a second late and shoved the page down. Everybody has done it. Everybody has been annoyed by it. Almost nobody knows it has a name.

How much does it affect your ranking?

Less than the people selling speed audits would like you to think.

Speed is a genuine ranking signal, but a small one, and it behaves like a tie-breaker rather than a lever. If two pages are equally useful and equally relevant, the faster one may edge ahead. A fast page about the wrong subject will not outrank a slow page that actually answers the question.

So if you are on page four for “boiler repair Bridgnorth”, your Core Web Vitals are almost certainly not the reason. The reason is more likely to be one of the things in our piece on websites that quietly stop working, or the local search mechanics covered in why you show up in one town and not another.

The real reason to care

Not Google. People standing in the rain.

Consider the actual customer. Somebody is in a lay-by near Clun with one bar of signal and a leak in the kitchen. They search, they tap the first likely result, and they wait. If your page takes eight seconds to show a phone number, they’ve gone back and tapped the next one before it finishes.

This is not an abstract concern in Shropshire. Mobile coverage across the county is patchy in a way that people in cities genuinely do not experience, and a good proportion of your customers are looking for you outdoors, on a phone, in a hurry, on a connection doing its best. A heavy website punishes exactly those people, and they are frequently the ones ready to buy.

The three things that actually slow small business websites down

In our experience it is nearly always one of these, and usually the first.

1. Photographs straight off a phone or camera

A modern phone takes a photograph five or six megabytes in size and several thousand pixels wide. Uploaded straight to a website, that image is then shrunk by the visitor’s browser after it has downloaded all of it. Put eight of them on a page and you have asked somebody on rural 4G to download forty megabytes to look at your kitchen fitting.

This is the single biggest cause, it is free to fix, and almost nobody does it.

2. Accumulated extras

A chat widget, two tracking scripts, a reviews badge, a cookie banner, a booking add-on and a social feed. Each one seemed harmless. Together they can easily double the weight of a page, and several of them arrive late, which is what causes the jumping about.

3. Cheap, oversold hosting

If the server your site sits on is shared with several hundred other websites, your page starts slowly no matter how tidy it is. This is rarely the problem on a well-built small site, but when it is the problem, nothing else you do will help.

Checking it yourself, without pretending to be technical

Put your address into Google’s free PageSpeed Insights tool at pagespeed.web.dev. Two things to know before you do.

First, the big score out of 100 is a simulation. It is useful, but it is not what Google uses. If there is a section near the top showing data from real visitors, that is the part that matters.

Second, a red score is not an emergency. Plenty of perfectly successful websites score badly and rank well. Treat it as a to-do list rather than a diagnosis.

The other test costs nothing at all: open your own website on your own phone, outside, on mobile data, somewhere with mediocre signal. You will learn more in thirty seconds than any report will tell you.

What to actually do, in order

• Resize your photographs before uploading. Around 1,600 to 2,000 pixels wide, saved at a sensible quality, usually lands under 300KB and looks identical on screen.
• Remove anything on the page you cannot explain the purpose of.
• Make sure the phone number and the main message appear first, not last.
• Only then worry about the score.

What to ignore

Anyone who sends you an unsolicited email containing a red score and an offer to fix it for a fee. It is a mail merge. They have not looked at your website, and a speed score is trivially easy to make alarming.

Good photography helps here as well as everywhere else, which is why our photo and film work includes supplying images at sizes that are actually meant for a website. Every site we build is put together with this in mind from the start, which is a great deal less bother than fixing it afterwards. And if page weight is on your mind, our accessibility guide is worth reading alongside this, because the things that make a page fast tend to be the same things that make it usable.