Core Web Vitals for Non-Developers: LCP, INP & CLS (2026)

Core Web Vitals are three metrics Google uses to measure real-world user experience on a web page: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. A page “passes” when 75% of real visits score “good” — LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1.

If that sentence already told you most of what you need, good — that is the point of this guide. Below is Core Web Vitals explained in plain English: we translate each metric, explain why they matter for search and conversion, and give you a practical checklist you can hand to whoever builds your site. No jargon dumps, no lectures on JavaScript.

What are Core Web Vitals, exactly?

Core Web Vitals are a subset of Google’s wider “page experience” signals — the handful of measurements Google decided matter most to how a page feels to a real person on a real phone. They are not about your content, your keywords or your design taste. They measure three things: how quickly the main content appears, how fast the page reacts when you tap or click, and whether things jump around while you are trying to read.

Crucially, Google grades these on field data — anonymised measurements from actual Chrome users visiting your site — not a one-off lab test. It uses the 75th percentile, which means three in four visits need to score “good” for the page to pass. A fast connection on your own laptop is not the benchmark; a mid-range Android on London Underground Wi-Fi is closer to it.

What do LCP, INP and CLS mean in plain English?

LCP — Largest Contentful Paint (loading)

LCP measures how long it takes for the biggest visible element — usually a hero image, a headline block or a video poster — to finish loading. If a visitor stares at a blank or half-built page for four seconds, that is a poor LCP. The usual culprits are oversized images, slow servers and “render-blocking” code that has to load before anything shows.

INP — Interaction to Next Paint (responsiveness)

INP measures the lag between a user doing something — tapping a menu, opening a dropdown, hitting “add to basket” — and the page visibly responding. It replaced the older First Input Delay metric on 12 March 2024 because INP watches every interaction across a visit, not just the first one. A sluggish INP usually means heavy scripts (chat widgets, trackers, bloated page builders) are hogging the browser’s main thread.

CLS — Cumulative Layout Shift (visual stability)

CLS measures how much the page unexpectedly moves about as it loads. You have felt this: you go to tap a link, an advert or a banner loads in above it, and you tap the wrong thing. The common causes are images and ads without reserved space, and web fonts that swap in and reflow the text.

What are the 2026 Core Web Vitals thresholds?

Here is the full scorecard. “Good” is what you are aiming for; anything in “Poor” is actively costing you.

These are the thresholds Google publishes on web.dev, measured at the 75th percentile of real visits. To pass overall, a page needs “good” on all three.

Do Core Web Vitals actually affect SEO?

Yes — but keep it in proportion. Core Web Vitals are a genuine Google ranking signal, but they are a tie-breaker, not a trump card. Great content on a slightly slow page will usually still beat thin content on a lightning-fast one. Where Vitals earn their keep is when you are competing against sites of similar quality, and — more importantly — in conversion. A one-off delay or a page that lurches around while loading pushes people to bounce before they ever read your offer.

Think of it this way: Core Web Vitals are less “the reason you rank” and more “the reason a good page doesn’t quietly leak visitors and revenue.” For a London brand paying for traffic through Meta or Google Ads, a fast, stable landing page also lowers your effective cost per lead.

Google publishes the evidence for that rather than leaving us to assert it. Its business impact of Core Web Vitals collection reports Vodafone Italy taking 8% more sales from a 31% LCP improvement, iCook earning 10% more ad revenue from a 15% CLS improvement, and NDTV recording a 50% better bounce rate (web.dev, last updated 1 September 2021). Those are other companies’ sites and other companies’ traffic, so treat them as direction rather than a forecast. To size it for your own business, multiply your monthly visits by your conversion rate by your average order value, then run the same sum with the conversion rate a tenth of a percentage point higher. The difference over twelve months is your honest budget for performance work. For an online shop the arithmetic bites harder, which is why e-commerce build budgets should carry a performance line from the start.

How do you check your Core Web Vitals?

You do not need to install anything. Two free Google tools cover most needs:

• PageSpeed Insights — paste in a URL and it shows both lab data (a simulated test) and field data (real-world Chrome visits, if your traffic is high enough).
• Google Search Console — its “Core Web Vitals” report groups your whole site into good / needs-improvement / poor URLs, so you can see patterns rather than one page at a time.

A useful habit: check the “mobile” tab first. UK traffic is close to evenly split, with Statcounter putting mobile at 46.11% and desktop at 49.17% for August 2026, so mobile is not quite the majority. It is still where Vitals problems bite hardest, because slow networks, mid-range processors and small screens all land there at once. Search Console also grades mobile and desktop separately, so a page can pass on one and fail on the other.

How do you improve Core Web Vitals?

Most fixes fall into a short, repeatable checklist. Hand this to your developer or agency, and work through it in this order, because the sequence saves money. Images first, since that is the biggest LCP win for the least effort. Then reserved space for anything that loads late, which kills most CLS. Then third-party scripts, the usual INP culprit. Then hosting and a CDN, then fonts. Only when all five have been done properly is a rebuild worth discussing, and if the first five barely move the numbers, that is your evidence that the platform is the problem rather than your opinion.

• Compress and right-size images — serve modern formats (WebP/AVIF), never a 4,000px photo squeezed into a 600px slot. This is the single biggest LCP win.
• Reserve space for images, videos and ads — set explicit width and height so nothing shifts as it loads. This kills most CLS problems.
• Trim third-party scripts — every chat widget, heat-map and tracker adds weight. Audit them and drop what you do not use. This is usually the fastest INP win.
• Use a good host and a CDN — a fast server response underpins LCP; a content delivery network serves your files from closer to the visitor.
• Preload fonts and control font swapping — so text appears quickly and stops the layout reflowing.
• Choose the right foundation — a modern framework such as Next.js handles image optimisation, code-splitting and lazy-loading out of the box, which is why it tends to score well by default. If you are weighing your options, our guide to Next.js vs WordPress for a business website covers the performance trade-offs in detail.

One honest caveat: some sites are slow because of the platform they are built on, not a few stray images. A heavily plugged-in WordPress site or a bloated page-builder theme can hit a ceiling that no amount of tuning fully clears. In those cases a rebuild on the right foundation is the real fix — and worth budgeting for. If you are costing that up, our honest breakdown of what a website costs in the UK sets realistic expectations.

Why work with 9495 Creative?

At 9495 Creative, performance is not an afterthought we bolt on before launch — it is baked into how we build. Our sites are developed in-house on modern frameworks like Next.js, with image optimisation, clean code and Core Web Vitals in mind from the first commit. No stock templates loaded with scripts you will never use, no outsourcing to whoever is cheapest that week. A typical corporate site runs 4–6 weeks; portals and e-commerce 8–12 weeks, and you will get a clear visual treatment and proposal within 5 business days of your brief.

The result is a site that loads fast, feels stable, and gives Google — and your customers — nothing to complain about. You can see the standard on our portfolio, or explore what’s involved on our web and app development services.

Why does PageSpeed Insights pass but Search Console fail?

Because they are measuring two different things. PageSpeed Insights gives you two blocks. The top one is field data: anonymised measurements from real Chrome users, pulled from the Chrome User Experience Report. The bottom one is lab data: a single simulated load on a throttled mid-range phone, run the second you press the button. Search Console’s Core Web Vitals report uses field data only. So a green lab score sitting next to a red Search Console report is normal, not a bug.

Two details explain most of the confusion:

• Field data is a 28-day rolling average. Chrome’s own documentation says the values are “calculated from the previous 28 days as a rolling window”, refreshed daily. Yesterday’s fix is one day out of twenty-eight, so the number barely twitches at first.
• Quiet pages have no field data at all. If a URL has too few real visits, PageSpeed Insights falls back to origin-level data for the whole domain, and if that is thin too you get a No Data message. Plenty of UK small-business pages never earn enough traffic to be measured individually.
• Lab data is deliberately pessimistic. It throttles the connection and the processor on purpose, so it looks worse than the site feels on your laptop.

The working rule: use lab data to diagnose, field data to judge. Fix, deploy, then leave it four weeks before deciding whether it worked. If this sits inside a bigger rebuild, our website redesign checklist sets out what to monitor in the first 30 days after launch.

Which website platforms struggle most with Core Web Vitals?

Platform is not destiny, but it does set your starting position. The HTTP Archive’s Web Almanac measured the share of origins passing all three Core Web Vitals on mobile in 2024: WordPress 40%, Joomla 45%, Drupal 56%, Wix 57%, Squarespace 60% and Duda 73%, against a global pass rate of 51% for all origins as of June 2024. WordPress runs a large share of the UK small-business web and sits below that average, usually because of what gets bolted onto it rather than the core software.

Where each platform tends to break first, based on the failure patterns we see most often rather than measured averages:

Notice the pattern: on everything except the framework, the first lever is subtraction. If the fix is ongoing plugin and app housekeeping, it belongs in a care plan rather than an annual panic, and our guide to website maintenance costs in the UK covers what that involves. If subtraction stops working, the ceiling is the platform itself, and the Next.js vs WordPress comparison is the honest next read.

Do videos and embeds hurt Core Web Vitals?

They can, and on a site built by a creative agency the video is often the single biggest Vitals problem. It is the reason the page looks good and the reason it scores badly. Three specific traps:

• The poster image is usually your LCP element. The still frame behind the play button is the largest thing on screen, so it is what Google times. Compress it, serve it as WebP or AVIF, size it for the slot it sits in, and do not lazy-load it.
• YouTube and Vimeo embeds cost you before anyone presses play. A standard iframe pulls in the player’s own scripts on page load, which adds main-thread work and shows up as poor INP. A facade, meaning a static thumbnail that swaps in the real player on click, removes that cost for every visitor who never watches.
• Unsized embeds shift the layout. Give every video wrapper a fixed aspect ratio so the page does not jump when the iframe resolves. That is a straight CLS fix and takes minutes.

Autoplaying background hero video competes for bandwidth at the exact moment LCP is being measured. If you keep it, use a short, heavily compressed loop with no audio track.

The cheapest fix is often editorial rather than technical, because a shorter cut is a smaller file. Our guide to how long a corporate video should be makes that case on attention alone. And if the film on your homepage is a five-minute conference recap, repurposing that event footage into a 30-second cut serves your viewers and your LCP at once.

FAQ

Are Core Web Vitals a Google ranking factor?

Yes. Core Web Vitals are part of Google’s page experience signals and can influence rankings, especially between pages of similar content quality. They are best treated as a tie-breaker and a conversion lever rather than a primary ranking driver.

What is a good Core Web Vitals score in 2026?

A page passes when 75% of real visits achieve LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. All three metrics must reach “good” for the page to pass overall.

What replaced First Input Delay?

Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital on 12 March 2024. INP measures the responsiveness of every interaction across a visit, not just the first, giving a more accurate picture of how a page feels to use.

How do I test my Core Web Vitals for free?

Use Google’s PageSpeed Insights to test a single URL, or the Core Web Vitals report in Google Search Console to see your whole site grouped into good, needs-improvement and poor pages. Always check the mobile results.

Can Core Web Vitals be fixed without rebuilding my site?

Often, yes — compressing images, reserving space for media, and removing unused third-party scripts fix most issues. If the problem is a bloated platform or theme, though, a rebuild on a modern framework such as Next.js may be the more cost-effective long-term fix.

How long after fixing Core Web Vitals do the scores update?

Allow at least four weeks. Google’s field data is a 28-day rolling window refreshed daily, so a fix deployed today only fully replaces the old measurements once 28 days of traffic have passed through it. Lab tools such as Lighthouse show the improvement immediately, which is why they are the right way to check your work. Search Console can lag further while it revalidates the URLs.

Why does PageSpeed Insights show no field data for my page?

Because too few real Chrome users have visited it. PageSpeed Insights looks for page-level data first, falls back to origin-level data for your whole domain, and shows a No Data message if neither has enough visits. Low-traffic UK small-business sites see this constantly. You are not doing anything wrong; you simply have to work from lab data and fix the obvious causes.

Do YouTube embeds hurt Core Web Vitals?

They can. A standard YouTube or Vimeo iframe loads the player’s own scripts on page load, before anyone clicks play, which adds main-thread work and hurts INP. An unsized embed also causes layout shift and hurts CLS. Use a lightweight facade that shows a static thumbnail and only swaps in the real player on click, and give every video wrapper a fixed aspect ratio.

Does Cloudflare or a CDN fix Core Web Vitals?

Partly. A CDN shortens server response time and serves files from closer to the visitor, which helps LCP, sometimes dramatically on slow shared hosting. It does very little for INP or CLS, because those come from your own scripts and unsized elements rather than from distance. Treat a CDN as one lever of five, not a fix on its own.

Ready to build a faster site?

If your Vitals are in the red — or you’re planning a new build and want them green from day one — we can help. Start a brief with 9495 Creative and we’ll come back with a plan within 5 business days.