SEO · 12 min read

Core Web Vitals 2026: the SEO metric hurting your ranking

48% of mobile sites fail at least one Core Web Vitals metric in 2026. How to audit your site and prioritise a fix that unlocks your Google ranking.

Core Web Vitals 2026: the SEO metric hurting your ranking

Why Google penalises slow sites in 2026

Google confirmed in 2026 that Core Web Vitals remain an active ranking signal. Not the most powerful among hundreds of signals, but the one that tips the SERP when two pieces of content are equivalent. According to the official Google Search Central documentation, a site must pass all three metrics to gain the advantage, with no partial credit.

The logic fits in one sentence: Google does not want to send users to pages that drag. When a competitor publishes an article as good as yours but their site loads in 2 seconds while yours takes 5, Google promotes the competitor. It is mechanical.

Three metrics make up the evaluation, each with a binary good or bad threshold:

2.5s

Largest Contentful Paint max to be considered good

web.dev / Google

200ms

Interaction to Next Paint max (replaced FID in March 2024)

web.dev / Google

0.1

Cumulative Layout Shift max (unitless score)

web.dev / Google

These thresholds are measured at the 75th percentile of your real visitors over the last 28 days. If three out of four visitors see your site load in under 2.5 seconds, you pass LCP. Otherwise, Google records it as a negative signal on all similar pages of your domain.

48% of mobile sites fail: which side is yours on?

The 2025 Web Almanac published by HTTP Archive gives the numerical verdict. Only 48% of mobile sites pass all three metrics, and 56% on desktop. In other words, one site in two pays a silent SEO penalty without realising it.

The breakdown per metric reveals where it breaks:

62%

of mobile sites pass LCP (loading)

HTTP Archive 2025

77%

of mobile sites pass INP (interactivity)

HTTP Archive 2025

81%

of mobile sites pass CLS (visual stability)

HTTP Archive 2025

LCP is the weakest link of the web. On mobile, nearly four sites out of ten fail this single metric, which is enough to disqualify them from all three. The cause is almost always the same: a hero image that is too heavy, or a framework that hydrates its JavaScript before showing visible content. On Next.js and Nuxt, the issue concentrated on INP in 2024-2025, before the maintainers shipped hydration fixes.

If your site belongs to the 52% that fail at least one metric, you are mechanically at a disadvantage against a competitor that passes them all. And that disadvantage compounds article by article, page by page.

What LCP, INP and CLS measure (in plain executive terms)

Each of the three metrics describes a precise, measurable, revenue-costing user frustration. No need to memorise the acronyms: remember what they punish in the real life of a visitor.

01Pilier 1

LCP: how long before the page looks loaded

Measures the time it takes for the largest visible element (typically the hero image or H1) to appear. Past 2.5 seconds, the visitor has already done two things: pressed back, or run a new Google search.
02Pilier 2

INP: how responsive the site feels when you click

Measures the delay between a user action (click, tap, keystroke) and the visible reaction on screen. Past 200 milliseconds, the site feels "slow" or "buggy" even if it works. This is the most violently penalised metric on JavaScript-heavy sites.
03Pilier 3

CLS: how much elements jump during loading

Measures unexpected visual shifts while the page builds (image appearing and pushing text, cookie banner shifting everything, font swaps). Past 0.1, the user loses their reference point and clicks in the wrong place.

Each translates into concrete commercial loss. According to benchmarks compiled by Vercel on the impact of Core Web Vitals on SEO, a site that improves its LCP by 1 second gains on average 10% in conversion rate, and a site that passes the thresholds on all three metrics sees its organic traffic grow by 15 to 25% in 6 to 9 months.

The "100 on PageSpeed" trap: why Google does not look at it

Most executives open PageSpeed Insights, see a Lighthouse score of 95, and conclude that everything is fine. That is exactly the wrong reasoning. Google does not use this score to rank. It looks at the CrUX (Chrome User Experience Report), which aggregates real data from millions of actual Chrome visitors.

The distinction is crucial:

Ce qui ne sert plus

  • Trust the Lighthouse score (the coloured bars in PageSpeed Insights or Chrome DevTools). It is a simulation from a Google datacenter with a fixed connection.
  • Optimise only the homepage and assume the whole site is good. CrUX measures page by page.
  • Run a performance audit before launch and never run it again. CWV shift across releases.
  • Confuse "fast on the dev's fibre" with "fast for real visitors". 60% of your visitors are on degraded 4G or 5G.

À faire à la place

  • Look at the "Origin Summary" section in PageSpeed Insights, which displays the CrUX field data for your domain.
  • Hook up Vercel Speed Insights or an equivalent (DebugBear, SpeedCurve) to measure every real visit continuously.
  • Follow the Core Web Vitals report in Google Search Console, which reflects exactly what Google sees.
  • Audit every page type, not just the homepage: product, article, cart, contact.

The Lighthouse vs CrUX gap explains why so many sites with a "good PageSpeed score" stall in Search Console: Lighthouse is a lab test, CrUX is the field audit. Google ranks exclusively on the second one.

How to audit your site in 5 minutes without a dev

You need zero technical skill to know whether your site passes or fails Core Web Vitals. Four free tools, in order, give a reliable answer in under 10 minutes:

  1. 1

    PageSpeed Insights, Origin Summary section

    2 min
    Paste your site URL on pagespeed.web.dev. Below the Lighthouse score, scroll down to "Discover what your real users are experiencing". That is the CrUX field data. Green = you pass. Orange or red = you fail.
  2. 2

    Google Search Console, Core Web Vitals report

    3 min
    In GSC, "Experience" tab then "Core Web Vitals". The report lists exactly which URLs fail, by group and by metric. It is the official Google source.
  3. 3

    CrUX Vis or CrUX Dashboard

    2 min
    CrUX Vis (Google tool) displays your metrics evolution over 25 months. Lets you see if you are regressing or improving since your last release.
  4. 4

    Vercel Speed Insights or equivalent RUM

    2 min
    If your site is on Vercel, the Speed Insights tab is free up to a certain volume and gives detail per page. Otherwise: DebugBear, SpeedCurve, or the native Web Vitals integrated via the official useReportWebVitals hook.

If the assessment is bad, you will know exactly which metric fails, on which pages, and at which percentile. That is the minimum information to brief a provider.

The levers that bring a site back under the thresholds

Four families of technical actions solve 80% of Core Web Vitals issues. They are not exotic operations, but they need a developer who knows where to look.

01Pilier 1

Preloaded, properly sized hero image

LCP is almost always an image above the fold. AVIF or WebP format, max served width 1,600 px, fetchPriority="high" attribute. On Next.js, the priority prop was replaced by preload in version 16 (see the official next/image docs).
02Pilier 2

Split and non-blocking JavaScript

INP collapses when the main thread is saturated by analytics, chatbot, or tag management JS. Code splitting, deferred third-party scripts, removing unused dependencies. A bundle audit often reveals 200 to 500 kB of JS never used.
03Pilier 3

Fonts and ads with reserved space

CLS almost always comes from web fonts that reflow the layout or ad banners inserted after initial render. font-display: swap, fixed dimensions on iframes, explicit space reservation for banners.
04Pilier 4

Static generation rather than dynamic rendering

On Next.js, a site served via SSG or ISR is CDN-cacheable and delivers a very low LCP. A site flipped into dynamic SSR (often by accident, due to a misplaced cookies() or headers() call in the root layout) loses that benefit and sees its LCP explode in prod. A silent trap we see regularly with clients.

None of these levers requires rebuilding your site. They are surgical optimisations that a competent developer handles in 2 to 5 days, depending on the starting state. For the broader 2026 SEO/GEO challenges beyond Core Web Vitals alone, our dedicated SEO and GEO pillar frames what comes next.

What to ask your technical provider

The most common risk in a poorly scoped CWV audit: a provider who comes back with a Lighthouse score of 100 and declares the job done. The right questions to ask before commissioning the work:

A good provider will answer all five clearly. A bad one will say "we will optimise performance" with no precise commitment. The fifth answer is worth knowing: Google takes at least 28 days to recompute its CrUX report, and 2 to 3 additional months for the SEO benefit to show in rankings. Any provider promising an effect in 2 weeks is wrong or lying.

The ROI of a Core Web Vitals audit

On a site doing 5,000 organic visits per month, unlocking Core Web Vitals typically represents 30 to 60 K€ in additional annual revenue in B2B services. The math is simple: a site that moves from "Poor" to "Good" rating sees its organic traffic grow 15 to 25% over 6 to 9 months, and its mobile conversion rate increase 8 to 12%.

For a site already well ranked on its main queries, the gain is more diluted but still measurable: we typically observe a 2 to 5 position improvement on secondary queries, where CWV play their tie-breaker role against equivalent competitors. That is exactly what we observed on the refactor projects we delivered in 2025-2026, and it is what our Performance maintenance pack covers with the monthly CWV audit + CrUX tracking + 4 SEO articles per month.

On the Odyssée home, we went from LCP 18.5s to 9.4s in a single refactor session. The gain cascaded to all child pages within 2 months, and Google indexation accelerated in the wake. The trajectory is nothing exceptional: it is what any well-run CWV audit produces.

Questions fréquentes

What is the difference between Lighthouse score and Core Web Vitals?

The Lighthouse score is a simulation from a Google datacenter that tests your site on a fixed connection and device. It is useful to detect regressions before deployment, but Google does not use it to rank. Core Web Vitals are measured in the field via the CrUX report, which aggregates real Chrome visitor data over 28 days. It is this field data that influences ranking, not the Lighthouse score.

How long for Google to register a Core Web Vitals improvement?

Count at least 28 days for the CrUX report to update after a deployment. The Core Web Vitals report in Search Console reflects this rolling data. For the improvement to concretely impact your ranking, add 2 to 3 months: Google waits to confirm the gain is stable before recalibrating positions. In total, 3 to 4 months between the fix and the visible SEO impact.

My site has a good PageSpeed score (90+), why am I not ranking better?

Because PageSpeed Insights displays the synthetic Lighthouse score by default, not the CrUX field data. Scroll down on the same page to the "Discover what your real users are experiencing" section to see your actual metrics at the 75th percentile. It is very common to have a Lighthouse score of 95 and a failing CrUX, because the simulation reflects neither degraded 4G/5G connections nor production-loaded third-party scripts.

Do you need to rebuild your site to pass Core Web Vitals?

No, in 90% of cases. Four families of optimisations cover the essentials: optimised and preloaded hero image, split and deferred JavaScript, fonts and banners without layout shift, and static rendering (SSG/ISR) rather than dynamic when possible. An experienced developer handles these levers in 2 to 5 days on an existing site. A rebuild is only justified if the technical foundation predates 2020 or the CMS allows no deep optimisation.

Which free tools to monitor Core Web Vitals continuously?

Three tools are enough: Google Search Console ("Core Web Vitals" report) for the official Google view, PageSpeed Insights with the "Origin Summary" section for one-off tests, and CrUX Vis (cruxvis.withgoogle.com) to visualise the evolution over 25 months. If your site is on Vercel, Speed Insights adds per-page detail in near real time. To go further, DebugBear or SpeedCurve offer paid RUM (Real User Monitoring) from 30 €/month.

Is INP really the hardest metric to pass in 2026?

Not in absolute terms: globally, 77% of mobile sites pass INP versus only 62% that pass LCP, according to the 2025 Web Almanac. On the other hand, on sites built with a heavy JavaScript framework (Next.js, Nuxt, Remix with significant client interactivity), INP has become the metric that fails first. The frameworks shipped hydration fixes in 2024-2025, but an upgrade to the latest version is often still needed to benefit.

Do Core Web Vitals impact ranking on ChatGPT Search and Perplexity?

Indirectly, yes. AI engines preferentially cite content already well ranked on Google, and a slow site is less visible there. Beyond ranking, a performant site also signals technical quality to AI crawlers. For a broader view of GEO and showing up in ChatGPT/Perplexity, see our GEO 2026 guide which details the complementary levers.

ShareLinkedInX
#Core Web Vitals#SEO 2026#Performance#Google ranking

Published on

Shall we discuss your project?

30 minutes to scope your needs and tell you exactly what we would do in your position.

Start a project
Chat