Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

Page experience · 17 Nov 2026 · 6 min read

Core Web Vitals explained: LCP, INP and CLS

Core Web Vitals are three measurements of how a page feels to use: how fast the main content appears, how quickly it responds, and whether it jumps around.

The short answer

Core Web Vitals are three measures of real user experience. LCP measures how long the biggest visible element takes to load, INP measures how quickly the page responds to taps and clicks, and CLS measures unexpected layout movement. Google lists them as part of page experience, but good content still matters most.

What the three metrics measure

Core Web Vitals are a small set of measurements, defined by Google, that describe what a visit feels like. Each one answers a plain question a visitor would ask.

LCP is the loading measure. It records how long it takes for the biggest piece of content in view, usually a main image, a banner or a large block of text, to appear. A slow LCP feels like staring at a blank or half drawn page.

Interaction to Next Paint, or INP, measures responsiveness. It looks at how long the page takes to react visibly after a tap, click or key press, across the whole visit, and reports a figure close to the slowest. A poor INP feels like pressing a button and wondering whether it worked. INP replaced an older measure called First Input Delay in 2024, so older articles may still mention that one.

Cumulative Layout Shift, or CLS, measures visual stability. It adds up how much visible content moves unexpectedly while the page loads. A poor CLS is the moment you go to tap one button and an advert or image loads above it, pushing the button down so you tap the wrong thing.

Google publishes the pass marks for each metric on web.dev. They are numbers that have been revised before, so look them up there rather than trusting a figure in an article, including this one. The words to look for are good, needs improvement and poor.

Do they matter for ranking?

Google includes page experience signals, among them Core Web Vitals, in its ranking systems, but it also says that good content that matches the search matters more. A fast page with little to say will not beat a useful page that is a little slow. Treat these metrics mostly as a way to protect your visitors from a poor experience, which is what they were designed for.

For a small business, the real cost of a slow or jumpy page is lost visitors. People leave pages that do not load or respond, and those visitors are the ones you paid or worked to attract. That is a good enough reason to look at the scores even if rankings never moved.

Context matters too. Compare your pages with the type of sites you compete with, not with the biggest brands. A local service business with a clean five page site can usually achieve good results without heavy engineering. A store with large photography and many scripts has more to do.

Where to see your scores

There are two kinds of data, and the difference matters. Field data comes from real visitors using real devices. Lab data is a test run in controlled conditions. Field data tells you what people experience; lab data helps you find and fix causes.

  • The Core Web Vitals report in Search Console groups your pages by status, based on field data from Chrome users, and shows which groups need work. Small or new sites may have too little data to appear. Our beginner guide to Search Console shows where to find it.
  • PageSpeed Insights shows field data for a page where enough exists, plus a lab test with suggestions.
  • Chrome developer tools and Lighthouse run lab tests on your own machine.
  • Your hosting or performance monitoring service may report real user data, if it is set up.

Expect the numbers to differ between tools and between days. Lab scores in particular swing with the device and the network used for the test. Look at the pattern across pages, not one score from one run. Template problems show up when a whole group of pages is flagged.

What usually fixes a poor LCP

The biggest element is most often an image, so start there. Look at which element PageSpeed Insights names as the LCP element, then work through these causes in order.

  1. The image is too large in file size. Resize it to the dimensions it is displayed at and use a modern format. Our guide on image alt text, file names and sizes covers how to prepare them.
  2. The image loads late. A main image should not be lazy loaded, since that delays it. Lazy loading suits images further down the page.
  3. The server is slow to respond. Cheap shared hosting, no caching, or a heavy theme can delay everything. Caching and a closer server often help.
  4. Render blocking files hold up the page. Large style sheets and scripts in the head must load before content appears.
  5. Web fonts delay text. Fonts that must download before text shows can slow the biggest text block.

Fix the first item on the list that applies; the work is often smaller than expected.

What usually fixes a poor INP

INP problems are caused by too much work on the browser's main thread, which prevents it from responding to a tap. The causes are usually scripts.

  • Too many plugins and third party scripts, such as chat widgets, trackers, ad tags and social feeds. Remove those you do not use.
  • Large scripts running when the page loads, so the page is busy as soon as the visitor tries to act.
  • Menus, filters or forms built with heavy code, where a tap triggers a lot of calculation.
  • Heavy page structure, with a very large number of elements that the browser must update.

Test on a mid range phone rather than a fast laptop, since that is where the problem shows. Ask your developer to look at the longest tasks in a performance recording. Often a few third party scripts account for most of the delay. If you can only do one thing, audit what each script gives you and remove the ones nobody can justify.

What usually fixes a poor CLS

Layout shifts are mostly caused by elements that arrive without reserved space. The fixes are straightforward.

  • Set width and height, or an aspect ratio, on every image and video, so the browser leaves room before they load.
  • Reserve space for adverts, banners, cookie notices and embeds, instead of inserting them above content that has already appeared.
  • Load fonts in a way that avoids a large jump in text size when the font swaps in.
  • Avoid adding content above what the visitor is reading, such as a promotion bar that pushes the page down after load.
  • Animate with transforms rather than changes to the position or size of elements.

CLS often responds quickly to a few template changes. It is the metric where a developer's afternoon can change the status for a whole group of pages.

A sensible order of work

Begin with the pages that bring most visits or most enquiries, not every page. Run PageSpeed Insights on the home page, one service page and one article. Note which metric fails and which element is responsible. Make one change at a time and test again, so you know what worked.

After changes go live, field data takes weeks to catch up, because it is collected over a rolling period. Do not expect a status in Search Console to change overnight. Use lab tests to confirm the fix, then check field data later.

Other technical checks belong in the same review, such as redirect behaviour and error codes. Our guide to HTTP status codes and the one on internal linking belong on the same list, and so does checking for competing pages, which our guide to keyword cannibalisation describes.

If the fixes are beyond your own site editor, speed and stability work is part of the search engine optimisation service at Liftup Technologies, alongside technical audits.

Related guides

Questions and answers

What do the three Core Web Vitals measure?

LCP measures how long the biggest visible element takes to load. INP measures how quickly the page responds to taps, clicks and key presses. CLS measures how much visible content shifts unexpectedly.

Where do I see my Core Web Vitals scores?

Use the Core Web Vitals report in Search Console for field data on groups of pages, and PageSpeed Insights for a single page. Lighthouse in Chrome gives lab tests. Small sites may lack enough field data to appear.

What usually fixes a poor score?

For LCP, resize and compress the main image and speed up the server. For INP, remove unused scripts and plugins. For CLS, set image dimensions and reserve space for adverts and banners.

Do Core Web Vitals affect rankings?

Google includes them among its page experience signals, but says good content that matches the search still matters most. Treat them mainly as a way to avoid a poor experience for visitors.

Why do my scores differ between tools?

Field data comes from real visitors over a period and lab data is a single test run. Devices, networks and timing differ, so look for patterns across pages rather than a single figure.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote