Core Web Vitals: a guide for Welsh business websites.

Core Web Vitals are Google's three measurements of how a website actually feels to use: how fast the main content appears, how quickly the page responds when you tap something, and how much the layout jumps around while loading. They matter to a Welsh business for one simple reason: Google uses them as a ranking signal, and your customers feel them whether they can name them or not. Here is what each vital means in plain English, how to check your own site in two minutes for free, and the honest truth about when scores matter and when they are a distraction.

The three vitals, without the jargon

Largest Contentful Paint (LCP) is how long the main thing on the page takes to appear: the hero image, the headline, the bit you came for. Google's bar is 2.5 seconds. Slower than that and visitors are staring at a blank or half-drawn page, deciding whether to give up.

Interaction to Next Paint (INP) is how quickly the page reacts when someone taps a button or opens a menu. The bar is 200 milliseconds. Fail it and the site feels broken even when it works: taps that do nothing for a beat make people tap again, swear, and leave. INP replaced the older First Input Delay measurement in 2024, so if a guide or a provider still talks about FID, you are reading old advice.

Cumulative Layout Shift (CLS) is how much the page jumps about while loading. The bar is 0.1, and everyone knows the failure: you go to tap a button and something loads above it, shoving everything down so you tap the wrong thing. Google measures that shove.

That is the whole system. Not marketing scores, just three ways of measuring the irritation your customers feel on a slow, janky site.

Vital	What it measures	Google's bar	How the failure feels
LCP	Main content appearing	2.5 seconds	Staring at a blank page
INP	Response to taps	200 milliseconds	Taps that do nothing
CLS	Layout jumping about	0.1	Pressing the wrong thing

Check your own site in two minutes

Go to PageSpeed Insights (pagespeed.web.dev), paste your address, and read the mobile result first, because that is where your local customers are. The top section shows real-visitor data where Google has enough traffic to report it; the lab score below is a controlled test of the same page. If you have Google Search Console set up, its Core Web Vitals report goes further and lists which pages pass and fail across your whole site; our guide to getting your website on Google covers setting Search Console up, and it is worth doing for this report alone.

Two minutes, no cost, no expertise needed. If your site passes all three on mobile, you can stop worrying about vitals and go back to running your business. If it fails, read on before paying anyone anything.

Why business sites fail the vitals

The pattern behind most failures is the same one behind most slow Welsh business websites generally: template weight. A typical page-builder site ships hundreds of kilobytes of theme code and plugin JavaScript it never uses, and every kilobyte is time on the 4G connection your customer is standing in a car park with. LCP fails because the browser is wading through scripts before it can draw the page. INP fails because those same scripts are hogging the phone's attention when the customer taps. CLS fails because images and embeds load without reserved space and shove the layout around.

This is why our sites are custom-coded with no page builders and no plugin stack: not ideology, arithmetic. Pages that only contain what they need launch loading in under a second and score 95+ on Google's own tests, and those are published claims you can verify by running any site in our portfolio through PageSpeed yourself.

The time our own site failed one

Honesty makes this stick better than theory. Shortly after we relaunched our own website this summer, our lab testing caught a Cumulative Layout Shift score of 0.4, four times over Google's bar, on a site we had just built to be fast. The culprit was subtle: a loading skeleton, the grey placeholder boxes shown while a page streams in, was flashing in and pushing the layout down before the real content arrived. It looked like polish and measured like jank.

We traced it frame by frame, removed the offending pattern, and the score went to 0.000, not just passing but perfect. Two lessons from the inside. First, even careful builds pick up vitals problems, which is why we measure ours instead of assuming. Second, these scores are diagnosable and fixable with method rather than magic, and anyone selling vitals fixes should be able to tell you a story like this one about their own work.

Core Web Vitals are not a test you cram for. They are a symptom sheet, and the disease is nearly always the same: a site carrying weight it never needed.

When the scores matter, and when they are a distraction

The honest priority order for a Welsh small business: vitals matter more the more competitive your searches are. In a crowded market like the one our South Wales guide describes, where several optimised rivals contest every map pack, a failing LCP is a genuine handicap, both as a ranking signal and because slow pages lose the customers who do arrive. In a quiet market where your competitors' sites are ten-year-old templates, you likely outrank them anyway, and content, reviews and your Google profile deserve your attention first.

What vitals are never worth is panic-buying. Scores of 85 versus 92 on the lab test are not an emergency; a mobile page that takes six seconds to show anything is. Fix by symptom severity, not by chasing a perfect number, and be suspicious of anyone quoting a monthly fee to "optimise Core Web Vitals" on a site whose real problem is the platform it stands on. That situation calls for the rebuild conversation, and our website redesign guide covers what that honestly costs.

What actually fixes failing vitals

In rough order of impact: get images sized and compressed properly, because oversized images are the single commonest LCP killer; strip plugins and scripts the site does not use, or accept the platform ceiling; reserve space for images and embeds so nothing shoves the layout, which is the CLS fix; and get hosting that responds quickly, because no front-end work saves a slow server. On a well-built custom site these are solved during the build, which is the cheapest time to solve anything. On a template site there is a limit to how far patching goes, and an honest provider will tell you where that limit is before taking your money.

Speed is the technical half of ranking well. Our SEO and performance service pairs the sub-second builds this guide describes with the content and local signals that actually move positions.

The bottom line

Run your site through PageSpeed Insights today, mobile first, and let the result decide your next move: pass and move on, or fail and diagnose before you spend. Treat the three bars, 2.5 seconds, 200 milliseconds, 0.1, as customer-patience measurements rather than technical trivia, because that is what they are. And if the diagnosis points at the platform itself, that is a build conversation rather than a tuning one: ours start at £675 +VAT with the vitals passing on launch day, and every site in the portfolio is live for you to test before you believe a word of it.