Web Performance

Core Web Vitals: A Complete Guide for 2026

Google uses three performance metrics to judge page experience: Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. Here is what each one measures, why it matters, and where to start fixing it.

What are Core Web Vitals?

Core Web Vitals are a set of real-world performance metrics that Google uses as ranking signals. They were introduced to give site owners measurable, user-centred targets rather than abstract technical benchmarks. Unlike older speed metrics such as Time to First Byte, Core Web Vitals are measured from the user’s perspective: they capture what a visitor actually experiences, not what a server reports.

There are three metrics in the current set, each covering a different dimension of experience: loading speed, interactivity, and visual stability.

LCP: Largest Contentful Paint

LCP measures how long it takes for the largest visible element on the page to fully render. For most pages, that element is a hero image or a large heading. Google considers an LCP under 2.5 seconds good, 2.5 to 4 seconds needs improvement, and above 4 seconds poor.

The highest-impact LCP fixes are:

  • Preload the LCP image. Add a <link rel="preload"> tag for the hero image so the browser fetches it before it discovers it in the HTML or CSS.
  • Use modern image formats. WebP and AVIF are significantly smaller than JPEG or PNG at equivalent quality, reducing the time the browser spends downloading the image.
  • Set explicit dimensions. Width and height attributes on images let the browser reserve space before the image loads, preventing layout shifts and improving LCP timing.
  • Host on a fast CDN. Serving images from a content delivery network close to the user reduces latency, which is the single biggest lever for LCP on image-heavy pages.

INP: Interaction to Next Paint

INP replaced First Input Delay as the interactivity metric in March 2024. It measures the delay between a user’s input (a click, tap, or key press) and the moment the browser finishes rendering the resulting visual update. A good INP is under 200 milliseconds; above 500 milliseconds is poor.

Common causes of a poor INP score:

  • Long JavaScript tasks blocking the main thread. Any task that runs for more than 50 milliseconds can delay input processing.
  • Third-party scripts (chat widgets, analytics, ad tech) adding uncontrolled execution time.
  • Rendering large DOM trees on each interaction, which forces the browser to recalculate layout.

The primary fix is breaking long tasks into smaller chunks using scheduler.yield() or requestIdleCallback(), and deferring non-critical third-party scripts until after the page is interactive.

CLS: Cumulative Layout Shift

CLS measures how much page content shifts unexpectedly during load. A layout shift happens when an element moves from one position to another after the user has already seen the page. The score is a unitless number; Google considers a CLS below 0.1 good and above 0.25 poor.

The most common causes of high CLS:

  • Images without explicit width and height attributes. The browser cannot reserve space for them, so they push surrounding content down when they load.
  • Web fonts loading late and causing text to reflow. Use font-display: optional or preload critical fonts to reduce the swap period.
  • Late-loading banners or ads injected above existing content.

How to measure Core Web Vitals

There are two categories of data: lab data and field data. Lab data comes from tools like Lighthouse or WebPageTest, which simulate a page load in a controlled environment. Field data comes from real users and is collected by the Chrome User Experience Report (CrUX).

Google’s ranking signals use field data, not lab data. A site can score green in Lighthouse and still have poor CrUX scores if real users on slow connections or low-end devices have a different experience. Use both: lab tools for diagnosis and iteration, field data for the final verdict on whether a fix worked.

Related reading