Core Web Vitals: A Simple UK Guide for Small Business

Your website's speed isn't a vanity metric — it's a confirmed Google ranking signal and a direct line to enquiries, sales, and bookings from UK customers. Core Web Vitals are the three specific user-experience measurements Google uses to judge how usable your site feels in the real world, and this Core Web Vitals guide UK small business owners can actually act on will walk you through what they are, how to measure them, and what to fix first.

If you run a small business, your website is usually the shopfront, the sales rep, and the booking system rolled into one. If a page stutters, jumps around as it loads, or takes too long to become usable, people leave before they've seen what you offer — and Google is watching. Core Web Vitals are measured using real-user data from Chrome browsers in the field, so a sluggish page on a patchy 4G connection in rural Northumberland counts just as much as one loading in central London.

What Core Web Vitals actually measure

Core Web Vitals is the umbrella term for three specific user-experience signals Google tracks across the web. Unlike the dozens of metrics buried inside browser dev tools, these three are publicly documented, used in ranking, and reported on per-URL in tools you already have access to. Understanding them properly is the difference between guessing why your site feels slow and knowing exactly which element to fix.

The three are Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. Each one captures a different moment in the user journey: the initial load, what happens when someone interacts with the page, and whether the layout behaves itself as it loads.

• Largest Contentful Paint (LCP) — how quickly the largest visible element on the page becomes ready. Usually a hero image, a headline, or a video thumbnail. It captures perceived load speed.
• Interaction to Next Paint (INP) — how fast the page responds when someone clicks, taps, or types. It replaced First Input Delay in 2024 and measures the full delay until the next visual update.
• Cumulative Layout Shift (CLS) — how much visible content unexpectedly moves around as the page loads. Think of a button sliding down just as you were about to click it.

How to check your scores for free

You don't need a paid audit to get started. Google provides two complementary ways to look at Core Web Vitals: lab data (a simulated test) and field data (real users on real devices and connections). Lab data is useful for debugging because it isolates issues, while field data is what Google actually uses for ranking. For UK small businesses, the field data is the one to care about.

The simplest place to start is PageSpeed Insights — paste in a URL and you get a report card covering all three metrics, with both lab and field figures. For a portfolio view across your whole site, the Core Web Vitals report inside Google Search Console groups pages by status and is the easiest way to see which URLs need attention.

• PageSpeed Insights — quick per-URL check with lab and field data side by side
• Google Search Console → Experience → Core Web Vitals — site-wide view, grouped by status
• Chrome UX Report (CrUX) — public dataset, useful for benchmarking against competitors
• The web-vitals.js library — for sending your own real-user data into your analytics platform
• A curated shortlist of the tools we use day to day lives on our tools page if you want a starting point

What 'good' actually looks like

Google publishes thresholds for each metric, and the same thresholds apply globally — to a plumber in Plymouth or a SaaS startup in Manchester. A page is considered to be passing Core Web Vitals if it hits the 'good' threshold for all three at the 75th percentile of real-user sessions. Anything in the middle band counts as 'needs improvement' and the worst tier is 'poor'.

The thresholds themselves are well documented: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. You don't need to memorise them — the tools above colour-code your results green, amber, or red. What matters more is that the field data reflects real users on real devices, so a passing lab score doesn't guarantee a passing field score.

Practical fixes that move the needle

Most Core Web Vitals problems on small-business sites come from a handful of recurring causes: oversized images, third-party scripts (chat widgets, review pop-ups, analytics tags), render-blocking CSS, late-loading web fonts, and a slow or overloaded hosting setup. You don't need to fix everything at once — start with whichever metric is in the red and work down.

A useful rule of thumb is to test changes on a mid-range Android device over throttled mobile network in Chrome's dev tools. If it feels fast there, it's probably going to feel fast in the real world. UK audiences on the move, checking your site on a phone between meetings, are the audience that matters.

• LCP: compress and resize the hero image, preload it, and serve it in a modern format like WebP or AVIF
• LCP: defer non-critical CSS and JavaScript, and audit third-party scripts that load in the head
• LCP: consider a faster host or content delivery network if your current setup is consistently slow
• INP: break up long-running JavaScript tasks and avoid heavy synchronous code on the main thread
• INP: lazy-load chat widgets, review pop-ups, and exit-intent scripts until after the page is interactive
• INP: test menus, form fields, and add-to-cart flows on real devices, not just on a fast desktop
• CLS: always set explicit width and height on images, videos, and embeds
• CLS: reserve fixed space for ad slots, cookie banners, and any content injected by JavaScript
• CLS: use font-display: swap and preload key web fonts so text doesn't jump when they load

Tying Core Web Vitals into your wider analytics

Core Web Vitals tell you whether the site is performing well, but they don't tell you whether that performance is moving the needle on enquiries, sales, or sign-ups. To get the full picture, you need to join them up with your analytics — which is where GA4 comes in. Our GA4 setup guide walks through how to track the events that actually matter for a small UK business, and you can find more of our analytics and performance writing on the blog.

A good starting point once GA4 is set up is to build a custom exploration that compares conversion rates between pages passing Core Web Vitals and pages that aren't. If your slow pages convert at half the rate of your fast ones, you have a clear business case for fixing them — and a clear way to measure the impact afterwards.

Common mistakes UK small businesses make

Two patterns come up time and again. The first is treating Core Web Vitals as a one-off project rather than an ongoing habit — scores drift over time as new plugins are added, themes are updated, and content is uploaded by people who aren't thinking about performance. The second is optimising for lab scores alone, which can lead to a fast test page but a slow real-world experience.

It's also worth remembering that field data lags by roughly a month's worth of visits, so a fix you ship today might not show up in Search Console for a few weeks. That's normal. Keep an eye on the report monthly rather than daily, and you'll spot genuine trends rather than noise.

Speed is a feature you ship once and then keep shipping — every new plugin, image, or third-party tag can quietly undo months of work.