A slow, jumpy website costs you money. Someone taps your ad or clicks your listing, the page takes four seconds to show anything useful, the layout lurches as they go to tap a button, and they are gone before they ever read your offer. Core Web Vitals are Google's attempt to measure exactly this kind of frustration — and because they are a ranking factor, fixing them helps you twice: better rankings and more of the visitors you already have turning into enquiries.
This guide explains what Core Web Vitals are, what counts as good, why they matter for a UK small business, and the concrete fixes that move the numbers.
What Core Web Vitals actually measure
Core Web Vitals are three metrics that capture different parts of the loading and interaction experience. Google measures them from real Chrome users visiting your site — field data — not just lab simulations.
LCP — Largest Contentful Paint
LCP measures how long it takes for the largest visible element to render — usually a hero image, a big heading or a banner. In plain terms, it is how long until the page looks like it has loaded.
- Good: under 2.5 seconds
* Needs improvement: 2.5 to 4 seconds
- Poor: over 4 seconds
INP — Interaction to Next Paint
INP measures responsiveness: when someone taps or clicks, how long before the page visibly reacts? It replaced First Input Delay (FID) as a Core Web Vital in 2024 because it captures the whole interaction, not just the first one. A sluggish INP feels like tapping a button and waiting, unsure if it registered.
- Good: under 200 milliseconds
* Needs improvement: 200 to 500 milliseconds
- Poor: over 500 milliseconds
CLS — Cumulative Layout Shift
CLS measures visual stability: how much the page jumps around as it loads. The classic annoyance is going to tap a link, an image loads above it, everything shifts down, and you tap an advert instead. CLS is a score, not a time.
- Good: under 0.1
* Needs improvement: 0.1 to 0.25
- Poor: over 0.25
Why this matters for a UK small business
It is tempting to treat this as a technical nicety, but the business case is direct. Industry analyses consistently link faster, more stable pages to lower bounce rates and higher conversions. The effect is sharpest on mobile, and a large share of local searches in the UK — someone looking for a plumber, a dentist, a solicitor while out and about — happen on a phone on a patchy 4G connection.
Consider a Manchester dental practice paying for Google Ads. If a slow, shifting landing page loses even one in ten prospective patients before the page settles, that is wasted ad spend every single day, plus the organic visitors who never convert. Improving Core Web Vitals does not require more traffic; it makes the traffic you already pay for and earn work harder. That is why we treat it as a conversion project as much as an SEO one.
How to diagnose your Core Web Vitals
You need two tools, both free.
Google Search Console
The Core Web Vitals report in Search Console uses real-world field data from actual visitors, grouped by URL pattern. This tells you which templates have problems and how many URLs are affected. It is the source of truth for whether Google considers your pages passing, because it reflects real users on real devices and connections.
PageSpeed Insights
Enter any URL at pagespeed.web.dev and PageSpeed Insights returns both field data (if enough real traffic exists) and lab data from a controlled test, plus a specific diagnostics list: "Largest Contentful Paint element", "Reduce unused JavaScript", "Image elements do not have explicit width and height" and so on. This is your fix list. Test on the mobile tab first, since that is what Google indexes and where problems bite hardest.
Run your homepage, your most important service or product page, and a typical blog page. Those three usually represent your main templates.
Fixing LCP
LCP problems almost always come down to a slow server response, render-blocking resources or a large, unoptimised hero image.
Optimise the largest element
If your LCP element is a hero image, this is your biggest lever:
-
Serve modern formats (WebP or AVIF), which are dramatically smaller than old JPEGs and PNGs at the same quality.
-
Size the image correctly. Do not load a 3000px-wide photo into a 800px space. Use responsive srcset so phones get a smaller file.
-
Preload the hero image so the browser fetches it early.
-
Avoid loading the main image via JavaScript, which delays it.
Speed up the server and delivery
A slow time to first byte drags everything down. Good UK hosting, caching and a content delivery network (CDN) all help. If you are on the cheapest shared hosting plan and your server response is over 600 milliseconds, upgrading hosting is often the single most cost-effective fix — sometimes more so than any code change.
Remove render-blocking resources
Large CSS and JavaScript files that must load before anything shows will delay LCP. Minify them, defer non-critical JavaScript, and inline only the critical CSS needed for the first view.
Fixing INP
INP problems come from JavaScript hogging the main thread, so when a user interacts the browser is too busy to respond quickly.
-
Reduce and defer JavaScript. Audit third-party scripts — chat widgets, heatmaps, multiple analytics tags, social embeds. Each one competes for the main thread. Remove what you do not genuinely use. On many small-business sites, a stack of half-forgotten marketing tags is the real culprit.
-
Break up long tasks. Long-running scripts block interaction. Splitting work into smaller chunks lets the browser respond to taps between them. This is developer work, but the tools above will flag the offending scripts.
-
Load third-party embeds lazily. A map, a video or a booking widget can load only when scrolled into view rather than fighting for resources on initial load.
Fixing CLS
CLS is often the easiest to fix and the most satisfying, because the jumpiness disappears visibly.
-
Set dimensions on images and videos. Always include width and height attributes (or a CSS aspect ratio) so the browser reserves the correct space before the file loads. This alone resolves a large share of CLS issues.
-
Reserve space for ads and embeds. Give ad slots and dynamic content a fixed container so surrounding content does not shift when they populate.
-
Handle web fonts carefully. Fonts swapping in can nudge layout. Use font-display: swap sensibly and preload key fonts.
-
Avoid inserting content above existing content. Cookie banners and notification bars that push everything down after load are common offenders. Overlay them or reserve their space.
A realistic worked example
Take a typical WordPress site for a Birmingham firm of accountants. PageSpeed Insights on mobile shows LCP at 4.1 seconds, INP at 260 milliseconds and CLS at 0.22 — all in "poor" or "needs improvement".
Working the list: the hero image is a 1.8MB PNG, so it is converted to a properly sized WebP and preloaded, cutting LCP toward 2.4 seconds. Three unused tracking scripts and a heavy chat widget are removed and the remaining scripts deferred, pulling INP under 200 milliseconds. Images throughout are given explicit dimensions and the cookie banner is set to overlay rather than push content, dropping CLS to 0.05.
None of these are exotic. They are the same handful of fixes that resolve the majority of Core Web Vitals problems on small-business sites. The effort is measured in hours, not weeks, and the payoff shows up in both rankings and enquiry rates.
Do not over-optimise
Chasing a perfect 100 score in PageSpeed Insights is usually a poor use of money. The lab score is a lab score; what matters is passing the real-world thresholds in Search Console. Once your field data sits in the green — good LCP, INP and CLS — further micro-optimisation delivers diminishing returns. Spend the saved budget on content or conversion instead. Honesty here saves clients money, and we would rather tell you when you have done enough.
Where NetTrackers fits
Core Web Vitals sit right where technical SEO meets web development, which is exactly the overlap we handle in one team. Our web design and development work builds sites that pass these thresholds from the start, and our SEO audits diagnose and prioritise fixes on your existing site so you are not guessing. Improving page experience also feeds directly into organic SEO performance.
We work month-to-month with no long contracts. Book a free strategy call, or get a free SEO audit that includes a Core Web Vitals check.
Frequently asked questions
Are Core Web Vitals a ranking factor?
Yes. They form part of Google's page-experience signals. They will not outweigh strong, relevant content, but between two similar pages the better experience tends to win, and speed improves conversions regardless.
What replaced FID?
Interaction to Next Paint (INP) replaced First Input Delay in 2024 because it measures responsiveness across all interactions, not just the first one.
Should I use field data or lab data?
Field data in Search Console is what Google actually assesses, since it reflects real users. Lab data in PageSpeed Insights is useful for diagnosing specific issues. Use both together.
My score is 100 in the lab but Search Console says I am failing. Why?
Because real users on slower devices and connections experience your site differently from a controlled lab test. Trust the field data and optimise for real conditions.
How long do fixes take to show up?
Field data in Search Console is based on a rolling 28-day window, so allow several weeks after fixes for the reported scores to update.