Skip to main content

Guides

Understanding Core Web Vitals

Core Web Vitals measure how fast, responsive and stable your pages feel to real users. This guide explains LCP, INP and CLS and how to improve each one.

Published
Updated
Reading time
7 min read
LCP in good rangeFaster pages

Core Web Vitals are a set of metrics defined by Google to describe how a web page feels to the people using it: how quickly the main content appears, how quickly the page responds when someone interacts with it, and how stable the layout is while it loads. They are measured from real visits in real browsers, which makes them a useful reflection of actual user experience rather than a lab score.

For businesses, Core Web Vitals matter for two reasons. First, they track things that genuinely affect visitors – slow, jumpy, unresponsive pages frustrate people and can reduce enquiries and sales. Second, they form part of the page experience signals Google uses in search. Google has been clear that relevant, helpful content remains the priority, so good Core Web Vitals will not guarantee rankings, but poor page experience is a disadvantage that is worth fixing.

This guide explains each metric in plain English, sets out Google's published thresholds, describes where the data comes from and outlines practical ways to improve each score.

The three Core Web Vitals at a glance

There are currently three Core Web Vitals. Interaction to Next Paint (INP) replaced First Input Delay (FID) as the responsiveness metric in March 2024.

MetricWhat it measuresGoodNeeds improvementPoor
Largest Contentful Paint (LCP)Loading – when the largest visible content element is rendered2.5 s or lessOver 2.5 s up to 4 sOver 4 s
Interaction to Next Paint (INP)Responsiveness – delay between user interactions and the next visual update200 ms or lessOver 200 ms up to 500 msOver 500 ms
Cumulative Layout Shift (CLS)Visual stability – how much visible content unexpectedly moves0.1 or lessOver 0.1 up to 0.25Over 0.25

Google assesses each metric at the 75th percentile of page visits, split by mobile and desktop. In practice, that means at least three-quarters of your visitors' experiences need to fall within the "good" threshold for a page to pass that metric. A fast experience on your office broadband does not count for much if most of your customers browse on mid-range phones over mobile data.

Largest Contentful Paint (LCP)

What it measures

LCP records when the largest image, video poster or block of text in the visible part of the page finishes rendering. On most business sites this is a hero image, a banner, a product photo or a large heading. It is a proxy for "when does this page look like it has loaded?"

Common causes of poor LCP

  • Slow server response (high Time to First Byte) caused by no page caching, an overloaded server or slow database queries.
  • Large, uncompressed hero images, or images served at desktop size to mobile devices.
  • The LCP image being lazy-loaded, or only discovered late because it is set via CSS or injected by JavaScript.
  • Render-blocking CSS and JavaScript in the page head.
  • Web fonts delaying the display of large text blocks.

How to improve LCP

  1. Reduce server response time with page caching, a CDN and an appropriately resourced server.
  2. Serve the LCP image in a modern format such as WebP or AVIF, compressed and sized correctly for each device using responsive image markup.
  3. Do not lazy-load the LCP image; instead, consider giving it a high fetch priority or preloading it.
  4. Inline critical CSS and defer non-critical CSS and JavaScript.
  5. Use font-display settings that allow text to appear before custom fonts finish loading.

Interaction to Next Paint (INP)

What it measures

INP observes the latency of clicks, taps and key presses throughout a visit and reports a value close to the worst interaction a user experienced. It measures the time from the interaction to the moment the browser can paint the next frame showing a response. If someone taps "Add to basket" and nothing visibly happens for half a second, that is a poor INP.

Common causes of poor INP

  • Long JavaScript tasks that block the browser's main thread, preventing it from responding.
  • Heavy third-party scripts: tag managers loaded with many tags, chat widgets, advertising and A/B testing tools.
  • Page builders and themes that ship large amounts of JavaScript to every page.
  • Event handlers that do too much work synchronously, such as re-rendering large parts of the page.
  • Very large DOM sizes that make each update expensive.

How to improve INP

  • Audit third-party scripts and remove those that no longer earn their place.
  • Load non-essential scripts after the page is interactive, or only on pages that need them.
  • Break long tasks into smaller chunks so the browser can respond between them.
  • Provide immediate visual feedback on interaction (for example a loading state) and do heavier work afterwards.
  • Reduce DOM size by simplifying page structure and avoiding unnecessarily nested layout elements.

INP is often the hardest metric to improve on sites built with heavy page builders, because the JavaScript cost is spread across many components. It is usually a case of steady reduction rather than a single fix.

Cumulative Layout Shift (CLS)

What it measures

CLS measures how much visible content unexpectedly moves around while the page is being used. A familiar example is going to tap a link just as an advert loads above it, pushing the link down so you tap something else. Shifts that happen immediately after a user interaction, such as opening an accordion, are not counted.

Common causes of poor CLS

  • Images, videos and iframes without width and height attributes, so the browser cannot reserve space.
  • Adverts, embeds and cookie banners injected above existing content.
  • Web fonts that swap in with noticeably different sizes from the fallback font.
  • Content inserted dynamically by JavaScript, such as promotional bars or late-loading reviews.

How to improve CLS

  1. Always set width and height (or an aspect ratio) on images, videos and embeds.
  2. Reserve space for adverts, banners and dynamic content with fixed-size containers.
  3. Display cookie consent and notification bars as overlays rather than inserting them at the top of the page.
  4. Choose fallback fonts that closely match the size of your custom fonts, or use font metric overrides.

Field data versus lab data

One of the most common points of confusion is that different tools show different numbers. That is because there are two kinds of data:

  • Field data comes from real Chrome users visiting your site, collected in the Chrome User Experience Report (CrUX). It reflects real devices and networks and is reported over a rolling 28-day period. This is the data Google uses for Core Web Vitals assessment. You will see it in Google Search Console and at the top of PageSpeed Insights, when there is enough traffic.
  • Lab data comes from a single simulated test, such as Lighthouse, under fixed conditions. It is excellent for diagnosis and for testing changes, but it does not represent your real audience. Lab tools cannot measure INP directly, because there is no real user interacting; Total Blocking Time is often used as a lab proxy.

Because field data is a 28-day rolling window, improvements you make today will take several weeks to be fully reflected in Search Console. Lab data responds immediately and is the right tool for confirming that a change has helped.

How to check your Core Web Vitals

  • Google Search Console – the Core Web Vitals report groups URLs with similar issues across your site, split by mobile and desktop. Start here for a site-wide view.
  • PageSpeed Insights – shows field data for an individual URL (or the whole origin) alongside a Lighthouse lab test with specific recommendations.
  • Chrome DevTools – the Performance panel helps identify long tasks, layout shifts and the LCP element on a specific page.
  • Real user monitoring – collecting Core Web Vitals from your own visitors gives faster feedback than CrUX and covers pages with too little traffic to appear in public data.

Prioritising improvements

Not every page needs the same attention. A sensible order of work is:

  1. Fix issues that affect templates used across many URLs – for example a product page template or the blog post template – because one fix improves many pages.
  2. Prioritise pages that matter commercially: landing pages, category and product pages, booking and checkout flows.
  3. Focus on mobile first, since that is usually where scores are weakest.
  4. Address server response time early, because it affects LCP on every page.
  5. Re-test after each change and record the results so progress is measurable.

Keeping Core Web Vitals healthy over time

Core Web Vitals are not a one-off project. New plugins, marketing tags, content and design changes can undo improvements quietly. Making Core Web Vitals part of routine maintenance – reviewing Search Console monthly, testing key templates after updates and reviewing third-party scripts regularly – helps keep scores stable. Our website maintenance checklist includes these checks, and if scores have dropped suddenly, why your website is suddenly slow covers the most common causes.

Conclusion

Core Web Vitals give you three clear, user-focused measures of page experience: LCP for loading, INP for responsiveness and CLS for visual stability. Understanding what each one measures, where the data comes from and what typically causes poor scores makes it much easier to decide what to fix first. Good scores will not replace good content, but they help ensure that your content is delivered in a way visitors find fast and reliable.

SupportSafe's Core Web Vitals optimisation service diagnoses issues at template and server level and makes changes with before-and-after measurement, while website performance monitoring keeps an eye on scores over time. To see where your site stands, request a free website health check.

Frequently asked questions

Do Core Web Vitals affect Google rankings?
They are part of the page experience signals Google uses, but relevant, helpful content remains far more important. Good Core Web Vitals cannot guarantee rankings; poor scores are simply a disadvantage worth addressing.
Why do PageSpeed Insights and Search Console show different results?
Search Console and the top of PageSpeed Insights show field data from real users over 28 days, while the Lighthouse score is a single simulated lab test. They measure under different conditions, so the numbers often differ.
How long does it take for Core Web Vitals improvements to show?
Lab tests reflect changes immediately, but field data is based on a rolling 28-day window, so it can take several weeks for improvements to be fully reflected in Search Console.
What happened to First Input Delay?
First Input Delay (FID) was replaced by Interaction to Next Paint (INP) as a Core Web Vital in March 2024. INP considers interactions across the whole visit, not just the first one.
Why does my page have no Core Web Vitals data?
Field data is only published when a page or site has enough real Chrome user visits. Low-traffic pages may show only lab data, or data aggregated at the whole-site level.

SupportSafe Engineering Team

Maintenance, infrastructure and security engineers

Articles are written and technically reviewed by the SupportSafe engineers who carry out website, application and server maintenance for our clients. Each article is reviewed for accuracy before publication and updated when practices change.

Let's take responsibility for your technology.

Tell us what you run and what keeps you up at night. We'll assess it and recommend a maintenance plan that fits – with no obligation.