Core Web Vitals are Google’s measurable signals for real-world page experience, and they feed into ranking. Passing them is not about chasing a green score for its own sake; it is about a site that loads fast, responds instantly, and does not jump around while people use it. This guide explains the three metrics as they stand in 2026 and, more importantly, the fixes that actually move each one.

TL;DR

  • The three Core Web Vitals are LCP (loading), INP (responsiveness), and CLS (visual stability). INP replaced FID as a Core Web Vital in 2024
  • “Good” thresholds: LCP under 2.5s, INP under 200ms, CLS under 0.1, measured at the 75th percentile of real visits
  • The highest-impact fixes are optimising the largest image or text block, reducing and breaking up JavaScript, and reserving space for images, ads, and embeds
  • Use field data (real users), not just lab tests, because Google ranks on real-world performance

The Three Core Web Vitals (2026)

Largest Contentful Paint (LCP): Loading

LCP measures how long it takes for the largest visible element (usually a hero image, banner, or large text block) to render. Good: under 2.5 seconds.

Interaction to Next Paint (INP): Responsiveness

INP measures how quickly the page responds to user interactions across the whole visit, replacing the older First Input Delay (FID) metric in 2024. It captures the delay between a tap or click and the next visual update. Good: under 200 milliseconds.

Cumulative Layout Shift (CLS): Visual Stability

CLS measures how much the page unexpectedly shifts while loading (the frustrating jump when a late image or ad pushes content down). Good: under 0.1.

Google evaluates these at the 75th percentile of real visits, so you need most of your users, not just the fastest, to have a good experience.

Fixing LCP

  • Optimise the LCP element. Identify it (most tools name it) and make it load fast: compress and correctly size the image, serve modern formats (WebP/AVIF), and avoid lazy-loading the hero image.
  • Serve responsive images with a proper srcset so devices download an appropriately sized file rather than a huge one. (See the guide to dealing with responsive images .)
  • Speed up the server response (TTFB) with caching and a CDN so the document arrives quickly.
  • Preload critical resources (the LCP image, key fonts) and eliminate render-blocking CSS and JavaScript where possible.
  • Use a fast image pipeline. Serving images through an optimised service like Cloudflare image transformations resizes and compresses on the fly.

Fixing INP

  • Reduce JavaScript execution. Heavy scripts block the main thread and delay responses. Ship less JavaScript and remove unused code.
  • Break up long tasks. Split long-running work so the browser can respond to input between chunks.
  • Defer non-critical work until after interaction, and avoid large, synchronous handlers.
  • Audit third-party scripts. Tag managers, chat widgets, and analytics are common INP culprits; load them efficiently or remove what you do not need.

Fixing CLS

  • Always set width and height (or CSS aspect-ratio) on images and video so the browser reserves space.
  • Reserve space for ads, embeds, and iframes so they do not push content when they load.
  • Avoid inserting content above existing content after load.
  • Preload fonts and use font-display sensibly to reduce layout shift from late-loading fonts.

Measure the Right Way

  • Field data over lab data. Google ranks on real-user (field) data such as the Chrome User Experience Report , not just a single lab run. A perfect lab score with poor field data will not pass.
  • Watch the 75th percentile. Improving your median is not enough; the slower quarter of visits is what fails you.
  • Test on real devices and connections, especially mid-range mobile, not just a fast desktop.

Key Takeaways

  • The three Core Web Vitals in 2026 are LCP, INP (which replaced FID), and CLS.
  • Aim for LCP under 2.5s, INP under 200ms, and CLS under 0.1 at the 75th percentile of real visits.
  • The biggest wins: optimise the LCP element and images, cut and split JavaScript for INP, and reserve space to stop layout shift for CLS.
  • Judge success on field data, not just a lab score.

Get a Professional Assessment

Core Web Vitals are one part of technical SEO. A technical SEO audit covers Core Web Vitals alongside crawl budget, indexation, site architecture, JavaScript rendering, and structured data, with a prioritised action plan based on real ranking impact. If speed is your main concern, the guide to speeding up your website with Cloudflare goes deeper on performance.

Frequently Asked Questions (FAQ)

What are the three Core Web Vitals in 2026? Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. INP replaced First Input Delay (FID) as a Core Web Vital in 2024.

What are good Core Web Vitals scores? LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, measured at the 75th percentile of real user visits. You need most visitors, not just the fastest, to hit these.

Do Core Web Vitals affect Google rankings? Yes. They are part of Google’s page experience signals. They are not the only or the strongest ranking factor, but for competitive queries a good page experience is a meaningful advantage, and a bad one holds you back.

Why does my site pass in the lab but fail in Search Console? Because Google uses field data from real users, not a single lab test. Real devices, connections, and the 75th percentile expose problems a fast test machine hides. Optimise for real-world conditions.

What is the fastest way to improve Core Web Vitals? Usually optimising the LCP element (compress and size the largest image, avoid lazy-loading it) and reducing JavaScript. For CLS, set dimensions on images and reserve space for ads and embeds.