Core Web Vitals for beginners showing LCP, INP and CLS speed gauges with pass marks.

Core Web Vitals for Beginners: LCP, INP and CLS Explained

Quick answer: Core Web Vitals are Google’s three measures of how a page feels to real visitors: LCP for loading, INP for responsiveness, and CLS for visual stability. A page passes when all three are good for at least 75% of real visits: LCP within 2.5 seconds, INP within 200 milliseconds, and CLS at 0.1 or less.

Open your site on your phone and watch what happens. Does the main photo appear quickly, or do you stare at a blank screen? When you tap the menu, does it open at once, or does nothing happen for a second? Does the text jump down just as you go to tap a link? Those three moments are exactly what Core Web Vitals measure. They are Google’s three numbers for real page experience: how fast the main content loads, how quickly the page responds to you, and how still the layout stays while it loads. This guide explains each one in plain English, gives you the pass thresholds, shows you how to check your own numbers free, and tells you which fix to start with. No code needed.

What are Core Web Vitals?

Core Web Vitals are three metrics Google uses to score the loading, interactivity and visual stability of a page for real visitors. They are not a score from a single test. They come from field data, which means measurements from real Chrome users visiting your site, collected by the Chrome User Experience Report (CrUX) over a rolling 28-day window. Google judges your page on that real-visitor data, separately for mobile and desktop. A page passes only when all three metrics are good at the 75th percentile of real visits, which means at least three visits in four hit the good threshold.

The three metrics are Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). They were introduced by the Chrome team in 2020, and the set can change over time. The most recent change matters for this guide: INP replaced First Input Delay (FID) as the responsiveness metric on 12 March 2024. Any guide, tool or report that still teaches FID as a Core Web Vital is out of date, and the top search result for this topic still does exactly that. This guide leads with INP, because that is what Google measures today.

Core Web Vitals are a ranking signal, but they are one signal among many. Relevance and content quality matter far more than a fast page with thin content. Fix your vitals for your visitors first, and the ranking benefit follows.

What are the pass thresholds?

Each metric has three bands: good, needs improvement and poor. The numbers come from Google’s own web.dev guidance. This table is the one to bookmark.

Metric What it measures Good Needs improvement Poor
Largest Contentful Paint (LCP) Loading: when the largest visible element finishes rendering 2.5 seconds or less Over 2.5 up to 4 seconds Over 4 seconds
Interaction to Next Paint (INP) Responsiveness: from a click, tap or key press until the page shows the next frame 200 milliseconds or less Over 200 up to 500 milliseconds Over 500 milliseconds
Cumulative Layout Shift (CLS) Visual stability: how much visible content moves without the visitor asking it to 0.1 or less Over 0.1 up to 0.25 Over 0.25

Remember the 75th percentile rule. A single fast load does not pass you, and a single slow one does not fail you. Google looks at the spread of real visits over 28 days, and at least three in four must be good on every metric. Mobile and desktop are judged separately, so a page can pass on desktop and fail on mobile when its mobile visits are slower. For most small businesses, mobile is the one that fails, because that is where most visitors arrive.

What is LCP, and what slows it down?

Largest Contentful Paint asks one simple question: when does the main content appear? It measures the time until the largest element visible on screen finishes rendering, which is usually the hero image at the top of the page or a big block of headline text. Good is 2.5 seconds or less. Over 4 seconds is poor.

On WordPress, slow LCP usually has the same few causes. A heavy hero image is the most common: a 2 MB photo at the top of the page has to download before the largest element can render. Slow hosting is the next, because every request waits on the server before anything can start. Uncompressed images further down the page and a page that loads too many things at once add to it. The fixes are mostly no-code: compress the hero image before you upload it, use a caching plugin to serve pages faster, and keep your hosting plan honest about the traffic it carries. Our WordPress speed guide works through those fixes in order, quick wins first.

On our own site, the homepage scores well after tuning: mobile performance 95 with LCP at 2.7 seconds, just above the 2.5 second good threshold. That is the honest position most small sites are in, and it is exactly the kind of number this guide helps you move.

What is INP, and why did it replace FID?

Interaction to Next Paint asks: when you tap something, how long before the page visibly responds? It measures the time from a click, tap or key press until the browser paints the next frame. Good is 200 milliseconds or less. Over 500 milliseconds is poor. It watches every interaction across the whole visit, not just the first one, which is why it is stricter than the metric it replaced.

First Input Delay, or FID, only measured the delay before the browser started handling the first interaction. It said nothing about the rest of the visit, and nothing about how long the visible response took. INP replaced FID as a Core Web Vital on 12 March 2024, and Chrome tools have phased FID out since. If a report still shows FID as the headline responsiveness number, it is showing you a retired metric.

Poor INP on WordPress usually comes from too much JavaScript: heavy page builders, chat widgets, social feeds and third-party scripts that all compete for the browser’s attention. The no-code fixes are to remove what you do not use: deactivate plugins you forgot about, drop widgets that add scripts to every page, and keep only the tools that earn their place. Unlike LCP and CLS, INP cannot be measured in a lab test, because no real user is interacting. That matters for how you check it, which the field data section below explains.

What is CLS, and what makes a page jump?

Cumulative Layout Shift asks: does the layout stay put while the page loads? It measures how much visible content moves without the visitor asking it to. The classic example is going to tap a link and watching it jump further down the page just as your finger lands, so you tap something else instead. CLS is a score, not a time. Good is 0.1 or less, over 0.25 is poor.

The usual causes are images without set dimensions, so the browser does not know how much space to reserve until the image arrives; banners, cookie notices and adverts that load late and push content down; and fonts that swap after the page has already drawn the text. Shifts that happen within 500 milliseconds of a visitor’s input do not count, because the visitor expected something to move when they tapped. Everything else counts.

The fixes are straightforward and need no code on WordPress. Set width and height on your images, or use a theme that does it for you. Reserve space for banners and embeds so they cannot push content around. Keep fonts simple and let them load early. CLS is the easiest of the three to fix, and the one you can verify fastest, which is why it comes first in the fix order below.

Field data vs lab data: which number counts?

There are two kinds of Core Web Vitals data, and confusing them is the most common beginner mistake. Field data comes from real visitors, collected by CrUX over a rolling 28-day window. This is what Google uses for the assessment, and what the Core Web Vitals report in Search Console shows. Lab data comes from a simulated load, usually Lighthouse, on a fixed device and network. It is useful for testing a change, but it is not what Google judges you on.

The practical difference is INP. A lab test has no real user tapping anything, so it cannot measure INP directly. Lighthouse reports Total Blocking Time instead, which correlates with responsiveness problems but is not the same number. LCP and CLS can be tested in the lab, and a Lighthouse run after a fix tells you right away whether it helped. INP improvements need field data to confirm, which means waiting for real visits to accumulate over days and weeks.

That is also why your PageSpeed Insights score and your Search Console report can disagree. PageSpeed Insights shows both: lab data from a fresh simulated test, and field data from the last 28 days of real visits. Search Console shows field data only. When they differ, trust the field data. It is the number Google uses. Our Search Console setup guide shows you where the Core Web Vitals report lives once your property is verified.

How do you check your Core Web Vitals free?

Five Google tools report Core Web Vitals: PageSpeed Insights, the Search Console Core Web Vitals report, Chrome DevTools, Lighthouse and the Chrome UX Report itself. For a small business, the first two are enough. This table shows what each one gives you.

Tool What it shows Best for
PageSpeed Insights (pagespeed.web.dev) Field data for the last 28 days plus a fresh lab test, for one URL at a time Checking a single page right now
Search Console Core Web Vitals report Field data for your whole site, grouped by good, needs improvement and poor Seeing which pages fail, site-wide
Lighthouse (in Chrome DevTools) Lab test with a scored report and specific fix suggestions Testing a change before it goes live

Start with PageSpeed Insights. Paste in your homepage address and run it. Read the field data first, not the big score at the top. The big number is a Lighthouse lab score: 90 to 100 is good, 50 to 89 needs improvement, 0 to 49 is poor. It is useful, but it is not your Core Web Vitals result. Scroll to the field data section and read your LCP, INP and CLS there, mobile first. Then run a typical inner page the same way. If your site has little traffic, field data may be missing for some pages, which is normal: Google needs enough real visits to report on, and a quiet page simply has none yet.

Which metric should you fix first?

Fix in this order: CLS first, then LCP, then INP. CLS is quickest to fix and quickest to verify in a lab test. LCP is next, because image and caching fixes show up in a lab test right away. INP comes last, because it usually needs the most work and its improvements only show in field data over time. This table gives you the first fix for each metric, all without code.

Metric First fix (no code) How you confirm it
CLS Set image dimensions and reserve space for banners and embeds Lighthouse lab test, same day
LCP Compress the hero image and turn on caching Lighthouse lab test, same day
INP Remove unused plugins and third-party widgets that load JavaScript on every page Field data over the next 28 days

For the full fix process, our WordPress speed guide covers hosting, caching and image optimisation in order, and our technical SEO audit guide has speed and Core Web Vitals as Step 3, with the rest of the audit around it. Fix one thing, measure again, then move to the next. Changing five things at once tells you nothing about which one worked.

How common are good Core Web Vitals?

Most sites do not pass all three, which should reassure you if yours does not either. According to the 2025 Web Almanac, which analyses CrUX data, the share of mobile sites rated good is 62% for LCP, 77% for INP and 81% for CLS. LCP is the metric most sites fail, and CLS is the one most sites pass. Among the top 1,000 mobile sites, only 63% had good INP in July 2025, against 77% of all mobile sites. In other words, even the biggest sites struggle with responsiveness. A small business that fixes CLS, then LCP, is already ahead of most of the web.

Frequently Asked Questions

What is a good LCP score?

2.5 seconds or less at the 75th percentile of real visits. Between 2.5 and 4 seconds needs improvement, and over 4 seconds is poor. The largest element is usually the hero image or the main headline, so compress that image first.

Is FID still used?

No. First Input Delay was retired as a Core Web Vital on 12 March 2024, when Interaction to Next Paint replaced it. FID only measured the delay before the first interaction started. INP measures the full time until the screen responds, for every interaction in the visit.

Why does my PageSpeed score differ from Search Console?

PageSpeed Insights shows a fresh lab test plus 28 days of field data, while Search Console shows field data only. The lab test is a single simulated load. The field data is what real visitors experienced. When they disagree, the field data is the number Google uses.

How long before my fixes show in Search Console?

Weeks, not hours. The Core Web Vitals report uses a rolling 28-day window of real visits, so a fix only shows once enough new visits have happened after it. Lab tests in Lighthouse or PageSpeed Insights confirm a fix the same day, but the Search Console report needs patience.

Do I need a developer to fix Core Web Vitals?

Usually not. On WordPress, the biggest wins need no code: compress images, set image dimensions, turn on caching, remove unused plugins and drop third-party widgets that load on every page. A developer is only needed when the theme itself is the problem, or when a custom feature keeps dragging INP down.

Do Core Web Vitals decide my rankings?

They are a ranking signal, but only one of many. A fast page with thin content will not outrank a slower page with genuinely better content. Fix your vitals because visitors deserve a fast, stable page, and treat any ranking benefit as a bonus, not the goal.

Check your three numbers today

Core Web Vitals sound technical, but they ask three human questions: does the main content appear quickly, does the page respond when you tap it, and does the layout stay still? The pass marks are simple: LCP within 2.5 seconds, INP within 200 milliseconds, CLS at 0.1 or less, for at least three visits in four. Run your homepage through PageSpeed Insights, read the field data, and fix CLS first. If the report points to speed problems, start with our WordPress speed guide, and if you want the full picture, run our technical SEO audit and our on-page SEO checklist. The numbers are free to check. The only cost is the afternoon you spend fixing them.

Related Posts