Technical SEO
Core Web Vitals Explained for Business Owners: What They Are and Why They Matter
By Zenivertex Digital Team · · 13 min read
Our founder brings 10 years' hands-on experience in SEO, digital marketing and web development.
Core Web Vitals explained in plain English: what LCP, INP and CLS actually measure, how they affect your Google rankings and enquiries, and the fixes that matter most.
Core Web Vitals explained in one minute
Core Web Vitals are three measurements Google uses to judge how your website feels to use. Not what it says, not how it looks in a screenshot — how it actually behaves when a real person on a real phone tries to load it, tap something and read it. Google measures these on real visits, uses them as a ranking signal, and reports them to you free of charge.
Here is Core Web Vitals explained without jargon. LCP (Largest Contentful Paint) measures loading: how long the biggest thing on the screen takes to appear. INP (Interaction to Next Paint) measures responsiveness: how quickly the page reacts when someone taps a button. CLS (Cumulative Layout Shift) measures stability: whether things jump around while the page loads, causing mis-taps and frustration.
Each metric has three grades — good, needs improvement, poor — based on thresholds we will cover below. This guide explains what each one means for your business, what typically causes poor scores, and which fixes are worth paying for. If you would rather have specialists handle it, this is core to our technical SEO work.
LCP explained: how fast your page shows its main content
Largest Contentful Paint measures the time from when the page starts loading to when its largest visible element — usually a hero image, a banner or a big heading — finishes rendering. Google's thresholds: under 2.5 seconds is good, 2.5 to 4 seconds needs improvement, over 4 seconds is poor.
Think about what LCP means commercially. A visitor who clicked your site from Google is making a snap judgement. If your main content appears in two seconds, they stay and read. If they stare at a blank or half-built page for five seconds, a meaningful share of them press the back button and choose your competitor instead. That lost visitor never shows up as a bounce you can fix with better copy — they never saw the copy at all.
The usual culprits behind poor LCP are oversized hero images (a 4MB photo straight from a camera), slow hosting, render-blocking scripts, and sliders that load five images when only one is visible. The fixes are usually straightforward: compress and resize images, serve modern formats like WebP, and make sure your hosting responds quickly.
INP explained: how quickly your page responds to taps and clicks
Interaction to Next Paint replaced the older First Input Delay metric in March 2024, and it is stricter. INP measures the delay between a user interacting with your page — tapping a menu, clicking a button, opening an accordion — and the page visibly responding. Under 200 milliseconds is good, 200–500 needs improvement, over 500 is poor. Crucially, INP considers every interaction during the visit, not just the first, so a page that gets progressively more sluggish scores badly.
Poor INP almost always means too much JavaScript. Page builders with dozens of plugins, multiple tracking scripts, chat widgets, pop-up tools and animation libraries all compete for the browser's attention. When a visitor taps your 'Get a Quote' button and nothing happens for half a second, that is INP failing at the worst possible moment — right at the point of conversion.
Fixing INP is developer work: removing unused scripts, deferring non-essential code, and simplifying bloated templates. It is one of the highest-value jobs in any website development project because it improves both rankings and conversion rate at once.
CLS explained: stopping your page from jumping around
Cumulative Layout Shift measures how much the visible content moves unexpectedly while the page loads. You have experienced it: you go to tap a link, an advert or image loads above it, the page jumps, and you tap the wrong thing. Google scores CLS as a unitless number — under 0.1 is good, 0.1 to 0.25 needs improvement, over 0.25 is poor.
The common causes are images without defined dimensions (the browser does not know how much space to reserve, so everything shifts when the image arrives), late-loading fonts that swap and reflow the text, banners and cookie notices that push content down, and embedded content like maps or videos without reserved space.
Most CLS fixes are cheap and permanent: set width and height attributes on images, reserve space for embeds, preload key fonts, and avoid injecting content above existing content. It is unglamorous work with a direct payoff in user experience.
Do Core Web Vitals actually affect rankings?
Yes, but with important context. Core Web Vitals form part of Google's page experience signals, which are genuine ranking factors. However, they are relatively weak signals compared to relevance and content quality. A brilliant, fast page about the wrong topic will not outrank a slower page that genuinely answers the searcher's question.
Where Core Web Vitals matter most is as a tie-breaker. When two pages are similarly relevant and authoritative — which is common in competitive local and commercial searches — the better user experience can tip the balance. And in highly competitive sectors, tie-breakers are exactly what rankings are decided by.
The bigger reason to care is not rankings at all: it is conversion. Study after study shows that faster, more stable pages convert more visitors into enquiries and sales. Even if Google ignored speed entirely, a one-second improvement in load time would still be worth money to your business. Treat Core Web Vitals as a conversion investment that happens to carry an SEO bonus.
How to check your Core Web Vitals for free
Start with Google PageSpeed Insights: enter any URL and you get both lab data (a simulated test) and, for pages with enough traffic, field data from real Chrome users over the past 28 days. Field data is what Google actually uses for rankings, so prioritise it when both are available.
Google Search Console has a dedicated Core Web Vitals report showing which groups of pages on your site pass or fail, based on real user data. This is the report to watch over time, because it covers your whole site rather than one URL at a time.
One caution: do not obsess over the lab score number. A PageSpeed score of 65 with good field data is better than a score of 90 achieved by gaming the test. The goal is a fast experience for real visitors, not a flattering screenshot. If your report looks confusing, our free SEO audit includes a plain-English Core Web Vitals assessment.
The fixes that matter most, in order
After auditing dozens of UK business websites, we see the same handful of fixes delivering most of the improvement. First, images: compress them, resize them to the dimensions they are actually displayed at, convert to WebP, and lazy-load anything below the fold. This alone fixes the majority of LCP problems.
Second, hosting. Cheap shared hosting with slow server response times caps everything else you do. Quality hosting with UK or European servers makes a measurable difference for a UK audience — and matters for local SEO too, since server location influences speed for nearby searchers.
Third, JavaScript discipline. Audit every script on your site and ask what it earns. Remove the ones you cannot justify, defer the rest, and be ruthless with page-builder plugins. Fourth, reserve space for everything: images, embeds, ads and banners. That fixes most CLS issues. If your site is due for broader work, our guide to planning a website redesign explains how to build these improvements in from the start.
Core Web Vitals and your wider SEO strategy
Core Web Vitals sit within technical SEO, which sits within your wider search strategy. They are necessary but not sufficient: a technically perfect site with thin content and no authority will still not rank. The sensible order of operations for most businesses is: fix genuine technical failures first (including poor Core Web Vitals), then invest in content and authority, while keeping performance healthy as the site grows.
Watch for regression, too. Scores drift as sites accumulate new scripts, images and features. A quarterly check in Search Console takes ten minutes and catches problems while they are small.
If your scores are poor and you are not sure where to start, talk to us. Our technical SEO audits prioritise fixes by business impact, so you spend money where it actually moves rankings and enquiries — not on chasing a perfect score for its own sake.
Core Web Vitals on mobile: where most UK businesses fail
One detail catches many business owners out: Google assesses Core Web Vitals primarily on mobile. Since mobile-first indexing, the mobile version of your site is the version that counts for rankings — and mobile is where scores are hardest to keep healthy, because phones have slower processors and patchier connections than the office desktop you probably tested on.
This matters commercially as much as technically. Well over half of UK web traffic is mobile, and for local searches — 'near me' queries, opening hours, directions — mobile dominates completely. A site that feels acceptable on your laptop can be genuinely painful on a mid-range phone on 4G, and that is the experience Google measures and your customers have.
The practical takeaway: always check the mobile tab in PageSpeed Insights, not just desktop, and test your own site on an actual phone over mobile data rather than office Wi-Fi. If the experience frustrates you, it is frustrating your customers — and showing in your Core Web Vitals data. Fixing mobile performance is one of the most reliable conversion improvements available to any business, and it is a core part of our website development work.
FAQs
What are Core Web Vitals in simple terms?
Three measurements of how your website feels to use: LCP measures loading speed, INP measures how quickly the page responds to taps and clicks, and CLS measures whether content jumps around while loading.
Are Core Web Vitals a Google ranking factor?
Yes, they form part of Google's page experience signals. They are a relatively weak signal compared to content relevance and authority, but they often act as the tie-breaker between similarly strong pages.
What is a good LCP score?
Under 2.5 seconds is good, 2.5 to 4 seconds needs improvement, and over 4 seconds is poor. LCP measures how long the largest visible element — usually your hero image or main heading — takes to appear.
What is INP and why did it replace FID?
INP (Interaction to Next Paint) measures how quickly your page visibly responds to any interaction throughout a visit. It replaced First Input Delay in March 2024 because FID only measured the first interaction, missing pages that grow sluggish over time.
How do I check my Core Web Vitals?
Use Google PageSpeed Insights for individual URLs and the Core Web Vitals report in Google Search Console for your whole site. Prioritise the field data from real users — that is what Google uses for rankings.
What usually causes poor Core Web Vitals scores?
Oversized uncompressed images, slow shared hosting, too much JavaScript from plugins and tracking tools, and images or embeds without reserved space. These four causes account for the majority of failures we see.
Do Core Web Vitals matter more than content?
No. Content relevance and authority remain far stronger ranking signals. But Core Web Vitals affect conversions directly — faster, stable pages turn more visitors into enquiries — so they are worth fixing regardless of rankings.
Can I improve Core Web Vitals without a developer?
Some fixes, yes: compressing and resizing images, removing unused plugins and upgrading hosting are achievable on most platforms. JavaScript optimisation and template changes usually need a developer.
How often should I check my scores?
Quarterly is sensible for most businesses. Scores drift as new scripts, images and features are added to the site, so a regular ten-minute check in Search Console catches regressions while they are small.