Services Process Experience Skills Cases Blog Contact
🌐 UA·RU·EN
April 28, 2026 · 9 min read

Core Web Vitals: What LCP, INP and CLS Mean and How to Improve Them

Core Web Vitals are three Google metrics that measure user experience on a page: LCP (how fast the main content appears), INP (how fast the page responds to actions) and CLS (how stable the layout is). They are calculated from real Chrome visitors, not from a test. Below: how to read each metric, where to find it, why your site may have no data, and how to improve Core Web Vitals by giving your developer the right brief.

Contents
  1. What are Core Web Vitals
  2. The three metrics and their thresholds
  3. The 75th percentile rule
  4. Field data vs lab data: why the numbers differ
  5. Where to check Core Web Vitals
  6. Why your site has no field data
  7. How much Core Web Vitals affect rankings
  8. Typical causes and how to fix them
  9. What to ask your developer
  10. Core Web Vitals checklist
  11. Frequently asked questions
  12. Summary
  13. How I help with Core Web Vitals

What are Core Web Vitals

Core Web Vitals are a set of three metrics Google uses to measure how comfortable a page is to use. They are part of the broader page experience concept, together with HTTPS, mobile friendliness and the absence of intrusive interstitials.

General speed advice - image compression, caching, CDN, hosting - is covered in my article on website speed. This one focuses on the metrics themselves: how they are calculated, how to read them correctly and how to find the cause of a poor score.

The three metrics and their thresholds

For each metric Google defines three ranges: "good", "needs improvement" and "poor".

MetricWhat it measuresGoodNeeds improvementPoor
LCP (Largest Contentful Paint)When the largest element above the fold appears: a banner, photo or text blockup to 2.5 s2.5-4 sover 4 s
INP (Interaction to Next Paint)How fast the page responds to clicks, taps and typing throughout the visitup to 200 ms200-500 msover 500 ms
CLS (Cumulative Layout Shift)How much elements move around while the page loads and is usedup to 0.10.1-0.25over 0.25

INP replaced FID (First Input Delay) in March 2024. FID only counted the delay of the first interaction, while INP looks at all interactions during a visit and takes one of the slowest. That is why many sites with a "green" FID ran into INP problems after the switch.

The 75th percentile rule

A page passes when at least 75% of visits fall within the "good" threshold. Not the average, but the 75th percentile.

75%

If LCP is 2.1 s in three visits out of four and 5 s in the fourth, the assessment uses the 75th percentile value. Slow visits from budget phones and mobile networks pull the score down directly.

Mobile and desktop data are assessed separately. In most cases the mobile version has worse numbers, so look at it first.

Field data vs lab data: why the numbers differ

The biggest source of confusion with Core Web Vitals is the difference between field and lab data. They are two different measurements and do not have to match.

Field data (CrUX)Lab data (Lighthouse)
SourceReal Chrome users who opted in to share statisticsA single test run on an emulated device
PeriodA rolling window of the last 28 daysThe moment of the test
INPMeasuredNot measured: TBT (Total Blocking Time) is used instead
PurposeThis is the data Google uses for the assessmentDiagnostics: find the cause and verify a fix

The practical rule: a PageSpeed score of 95 does not mean the page passes Core Web Vitals. Only the field data section gives the assessment. The lab test helps you understand what exactly is slow.

Where to check Core Web Vitals

01

Core Web Vitals report in Search Console

Shows the status of the whole site, separately for mobile and desktop. Pages are grouped by similarity, and a group's status is set by its worst metric. After a fix you can click "Validate fix": Google monitors the group for 28 days. Other reports are covered in my guide to Google Search Console.

02

PageSpeed Insights

For a specific URL. At the top: CrUX field data for the page and for the whole origin. Below: the Lighthouse lab report with diagnostics. If the page gets little traffic, PageSpeed shows origin data or says there is not enough data.

03

Chrome DevTools

The Performance panel shows local LCP, CLS and INP values in real time as you click around the page, and points to the element that became LCP or what caused a shift. This is the developer's main tool for finding the cause.

Why your site has no field data

If Search Console says there is not enough data, it is not an error. CrUX includes a page or origin only when it gets enough visits from Chrome users over 28 days. A small corporate site or a new project often does not reach that threshold.

What to do in that case:

How much Core Web Vitals affect rankings

The honest answer: they matter, but they are not decisive. Google states that Core Web Vitals are used by its ranking systems as part of page experience. At the same time, Google stresses that it shows the most relevant content first, even when the page experience is not ideal, and that good scores do not guarantee high rankings.

In practice: "green" metrics will not push a weak page to the top. But when several sites are equally helpful, a better user experience can be an advantage. And apart from SEO, a slow page that jumps around simply loses customers.

I will review your site's Core Web Vitals

Send me your website - I will check the field data, find the pages with the worst LCP, INP and CLS and tell you what to fix first.

Message me on Telegram

Typical causes and how to fix them

MetricTypical causeHow to fix
LCPHeavy hero image above the foldCompress it, serve WebP/AVIF, add fetchpriority="high", never lazy-load it
LCPSlow server response (high TTFB)Page caching, CDN, database query optimization
LCPRender-blocking CSS and JSInline critical CSS, load the rest asynchronously, use defer for scripts
INPHeavy JavaScript on the main threadSplit the code, load only what the page needs
INPThird-party scripts: chats, widgets, trackersRemove the unnecessary ones, delay the rest until interaction or after load
INPLong tasks (over 50 ms) in click handlersBreak up tasks, yield to the browser, update the interface first
CLSImages and videos without dimensionswidth and height attributes or CSS aspect-ratio
CLSWeb fonts replacing system fontsPreload the main font, font-display, a fallback font with similar metrics
CLSBanners, cookie notices and ads injected above contentReserve space in advance or show them as overlays that do not push content

It also helps to break LCP down into its parts: server response time, resource load delay, resource load duration and element render delay. This shows right away where the seconds are lost.

What to ask your developer

"Get PageSpeed to 90" leads to chasing a score. A better brief is built on field metrics and specific page templates:

Core Web Vitals are only part of a site's technical health. If you suspect other problems, start with a technical SEO audit.

Core Web Vitals checklist

Frequently asked questions

What are Core Web Vitals in simple terms?

They are three Google metrics: how fast the main content appears (LCP), how fast the page responds to actions (INP) and whether the layout jumps (CLS). They are based on data from real Chrome users.

Why does PageSpeed show a high score while Search Console shows poor results?

The PageSpeed score is a lab test on an emulated device. Search Console shows field data from real visitors over 28 days at the 75th percentile. For Google's assessment, field data is what counts.

What happened to FID?

In March 2024 Google replaced FID with INP. INP assesses all interactions during a visit, not just the first one, so it reflects the page's real responsiveness better.

How do I improve Core Web Vitals if rankings dropped?

First check whether Core Web Vitals are actually the cause. They are part of page experience signals, but relevance and content quality matter more. Poor metrics are rarely the only reason for low rankings, though they clearly hurt conversions.

How long until fixes show up?

Field data is collected over a rolling 28 days, so the full result in Search Console and PageSpeed appears about a month after release.

Summary

Core Web Vitals are three numbers that show how a site feels to people: LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1 at the 75th percentile. Watch the field data, use lab data for diagnostics, and brief your developer by templates and metrics, not by PageSpeed score.

How I help with Core Web Vitals

As part of a technical audit, I analyze field and lab data, find the templates with the worst scores and the causes, and then write a brief for your developer: what to change, on which pages and how to verify the result. After release, I monitor the metrics in Search Console. Technical optimization is part of monthly SEO from $450/month; the exact budget depends on the site size and niche. I work remotely, with written communication in English via Telegram or email. The first step is a free express audit.

Get a free express audit

I will check your Core Web Vitals and technical health, show the main problems and a fix plan with a brief for your developer.

Send a request

Leave a request

Describe your task - I will reply within a few hours and suggest where to start in your case.

Thank you, your request has been received. I will get back to you shortly.
DZ

Dmytro Zaichenko

Freelance SEO Specialist · 13+ years of experience · 70+ projects · zaichenko.pro