Core Web Vitals are three measurements Google uses to describe how a page feels to a visitor: how quickly the main content appears, how quickly the page reacts, and how stable it stays while loading. They are often presented with acronyms and charts that make them look more technical than they are. This article explains them in plain language, shows how they are measured and lists the usual causes and fixes.

The three metrics

LCP — Largest Contentful Paint

What it measures: how long it takes for the largest visible element — usually the main image or the main block of text — to appear on screen.

Good result: 2.5 seconds or less.

In plain terms: how long a visitor waits before the page looks loaded.

INP — Interaction to Next Paint

What it measures: how long the page takes to visibly respond after a visitor clicks, taps or types. It looks at interactions throughout the visit, not only the first one.

Good result: 200 milliseconds or less.

In plain terms: whether buttons and menus feel instant or sluggish. INP replaced the older First Input Delay metric as a Core Web Vital in March 2024.

CLS — Cumulative Layout Shift

What it measures: how much the content moves around unexpectedly while the page loads.

Good result: 0.1 or less.

In plain terms: whether a visitor tries to tap a button and hits an advert that jumped into its place.

Field data and lab data

The most common source of confusion is that the same metric can be measured in two different ways.

  • Field data comes from real visitors using real devices and connections. Google collects it from Chrome users who allow it and publishes it as the Chrome User Experience Report. This is what Google uses when it assesses Core Web Vitals. Small sites may not have enough visits to have field data at all.
  • Lab data comes from a test that loads the page once in a controlled environment. It is repeatable and available for any page, which makes it ideal for finding problems and checking fixes — but it is a simulation, not a record of real visits.

One consequence matters in practice: INP cannot be measured in a lab test, because it depends on real people interacting with the page. Lab tools report Total Blocking Time (TBT) instead — the time the browser's main thread is too busy to respond. A high TBT is a strong hint that INP will be poor for real visitors.

Typical causes and fixes

Slow LCP

  • Oversized images. Serve images at the size they are displayed, in modern formats, and compress them.
  • Slow server response. Caching, a better hosting plan or a content delivery network can cut the time before anything starts loading.
  • Render-blocking resources. Stylesheets and scripts in the page head that must load before anything is shown. Defer scripts that are not needed immediately.
  • The main image loaded late. Do not lazy-load the image at the top of the page; it should load first.

Poor INP (high TBT in the lab)

  • Too much JavaScript. Remove unused scripts and plugins. Every chat widget, tracker and slider adds work.
  • Long tasks. Code that runs for a long time without a break blocks the page from responding. Developers can split it into smaller pieces.
  • Third-party scripts. Review which external scripts are truly needed and load the rest later.

High CLS

  • Images and videos without dimensions. Set width and height so the browser reserves space.
  • Adverts and embeds that appear late. Reserve a fixed space for them.
  • Web fonts that swap. Text that changes size when the custom font arrives moves everything below it. Preload key fonts and choose fallback fonts with similar proportions.
  • Banners inserted at the top. Cookie notices and promotions pushed in above content shift the whole page down.

How much do Core Web Vitals matter for rankings?

Google includes Core Web Vitals in its page experience signals, but relevance and content quality matter far more. A fast page that does not answer the question will not outrank a slower page that does. The stronger argument for fixing them is the visitor: a page that loads quickly, responds at once and does not jump around is easier to use and more likely to lead to an enquiry or a sale.

A sensible approach is to fix problems that are clearly poor, focusing on the templates used by many pages — product pages, articles, the home page — rather than chasing perfect scores on every URL.

How to check your pages in SEO Melody

Speedtest runs a lab measurement of a page and shows Largest Contentful Paint, Cumulative Layout Shift, Total Blocking Time, First Contentful Paint, Speed Index and Time to Interactive. It then explains the results in plain language with AI and suggests what to fix first. Because it is a lab test, it does not report INP; use Total Blocking Time as the lab proxy, and treat field data from real visitors as the final word.

Speed & Compare puts your page next to a competitor's page on the same measurements. This is useful when deciding whether speed is a realistic advantage in your market or whether competitors are already faster.

Site Audit adds the structural side: page weight, compression and the viewport setting needed for mobile display are part of its 41 checks.

A short checklist

  1. Test your key page templates, not just the home page.
  2. Fix the largest image and the slowest server responses first.
  3. Remove scripts and plugins you no longer use.
  4. Give every image, video and embed fixed dimensions.
  5. Re-test after each change and keep the results, so you know what helped.

Summary

Core Web Vitals describe three things any visitor notices: waiting, lag and jumping content. Lab tests help you find and fix problems; field data shows what real visitors experience. Fix what is clearly poor on the pages that matter, and measure again to confirm the change worked.