Explainers · Explainer
What Is Core Web Vitals? A Plain Explanation
Short answer
Core Web Vitals are three Google metrics that measure real user experience: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability. A page passes when it meets all three targets for at least 75% of visits. Google uses the scores in its ranking systems, and the data comes from real Chrome users.
Key takeaways
- Core Web Vitals are three metrics: LCP for loading, INP for responsiveness and CLS for stability.
- A page passes only when all three metrics are good for at least 75% of visits.
- INP replaced First Input Delay as the responsiveness metric on March 12, 2024.
- The scores come from real Chrome users through the Chrome User Experience Report.
- Good targets are LCP 2.5 seconds or less, INP 200 milliseconds or less and CLS 0.1 or less.
What are Core Web Vitals?
Core Web Vitals are three Google metrics that measure how real visitors experience a page: loading speed, responsiveness and visual stability.
They are the part of the wider Web Vitals program that applies to every page. Google surfaces them in PageSpeed Insights, Search Console and Chrome DevTools, so you meet the same numbers wherever you look.
Each metric covers one part of the visit. LCP covers loading, INP covers interaction and CLS covers stability. Together they describe whether a page feels fast, responsive and steady.
Google introduced the program because site owners faced too many tools and too many metrics. The idea was to pick a small set of signals that every site owner could understand and act on.
That is why there are only three metrics, and why each one maps to a feeling a visitor can describe: slow to load, slow to respond, or jumping around.
What are the three metrics?
The three metrics are Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.
| Metric | Measures | Good target |
|---|---|---|
| LCP | Loading speed | 2.5 seconds or less |
| INP | Responsiveness | 200 milliseconds or less |
| CLS | Visual stability | 0.1 or less |
All three targets are judged at the 75th percentile of page loads, split by mobile and desktop. That means most of your visitors, not just the average, must have a good experience.
The metrics can change over time. Google moves new metrics through experimental and pending stages before they become stable, and all three current metrics are stable, as of November 2026.
The 75th percentile is not the average. If you sort 100 visits from fastest to slowest, the 75th visit sets the score. That way a few very slow visits do not hide a good experience, and a few very fast visits do not hide a bad one.
What is LCP?
Largest Contentful Paint measures when the largest image, text block or video in view finishes rendering.
It answers a simple question: how soon does the main content appear? A good LCP is 2.5 seconds or less, and a poor one is over 4.0 seconds. Slow servers, large hero images and render-blocking scripts are the usual causes.
On WordPress, the largest element is often a hero image or a headline. Shrinking that image and loading it early usually moves LCP the most. See our guide to serving images in next-gen formats for one way to shrink it.
LCP can change during the load. A page may first report a headline, then report a hero image once it arrives. Only the last entry counts, so a late image can push the score up even when the text appeared early.
What is INP?
Interaction to Next Paint measures how quickly a page responds to clicks, taps and key presses across the whole visit.
Google reports the slowest interaction it sees, ignoring one outlier per 50 interactions. A good INP is 200 milliseconds or less, and anything above 500 milliseconds is poor. Heavy JavaScript and long tasks on the main thread are the main causes.
INP replaced First Input Delay on March 12, 2024. FID only measured the first interaction, while INP watches every interaction from start to finish. Old reports that mention FID are out of date.
An interaction has three parts: the delay before the browser starts work, the time the event handlers run, and the wait until the next frame appears.
Long JavaScript tasks stretch the first part, because the browser cannot start until the main thread is free. Breaking up long tasks is the most direct fix.
What is CLS?
Cumulative Layout Shift measures how much visible content moves without warning while a page loads or is used.
A good CLS is 0.1 or less, and a poor one is above 0.25. Images without sizes, ads with no reserved space and late-loading fonts are the usual causes. Unlike the other two metrics, CLS has no unit: it is a plain number.
Shifts caused by the visitor, such as opening a menu, do not count if they happen within 500 milliseconds of the click. Only movement the visitor did not ask for hurts the score.
How do you check Core Web Vitals on your WordPress site?
Start with PageSpeed Insights and read the field data at the top, which comes from real Chrome users in the Chrome User Experience Report.
Search Console has a Core Web Vitals report that groups every URL on your site into good, needs improvement or poor. It shows mobile and desktop separately, so fix the mobile list first if most of your visitors use phones.
Lab tools such as Lighthouse and Chrome DevTools help you find the cause of a bad score. Field data and lab data often differ, because lab runs load a page once on one machine. Our guide on lab data versus field data explains why the two numbers rarely match.
If your site is new or gets little traffic, field data may be missing. The Chrome User Experience Report only covers pages with enough visits to form a reliable sample. In that case, use Lighthouse and DevTools to find problems, then recheck the field data once traffic grows.
How do you improve Core Web Vitals in WordPress?
Fix the worst metric first, because each one has different causes and different fixes.
- For LCP: use a caching plugin, shrink the hero image and pick a fast host.
- For INP: remove unused JavaScript, delay third-party scripts and keep plugins lean.
- For CLS: add image sizes, reserve space for ads and use font-display: swap.
WordPress's own optimization guide recommends caching first, because it gives the biggest gain for the least work. Deleting unused plugins and keeping PHP and WordPress current also help every metric at once.
Our guide to passing Core Web Vitals in WordPress walks through these fixes in order, starting with the checks that take five minutes.
Do Core Web Vitals affect Google rankings?
Yes, Google's ranking systems use Core Web Vitals, and its page experience guide recommends that site owners reach good scores.
There is no single page experience signal. Google looks at many signals together, and relevance still decides most rankings. A fast page with weak content will not outrank a slower page that answers the query better.
Treat the metrics as a visitor problem first and a ranking factor second. Pages that load fast, respond quickly and stay put keep readers longer, and that is worth fixing on its own.
Page experience also covers HTTPS, mobile display and intrusive interstitials, but only Core Web Vitals feed directly into ranking. The other parts still matter, because a page that is hard to read on a phone will lose visitors even if it ranks well.
If you want a single number to watch, read what a good PageSpeed score means for WordPress next.
Frequently asked questions
Do I need to pass Core Web Vitals on every page?
No, Google judges each page on its own, so a single bad page does not fail your whole site. Fix your most visited pages first, then work through templates such as posts, product pages and category pages, since one template fix can improve hundreds of URLs.
How long does it take for a fix to show in the scores?
Field data covers the last 28 days of real visits, so a fix can take weeks to show in PageSpeed Insights or Search Console. Lab tools such as Lighthouse show the change at once, so use them to confirm the fix and wait for the field data to catch up.
Why do my scores differ on mobile and desktop?
Google measures mobile and desktop separately because phones are slower and often on weaker networks. A page can pass on desktop and fail on mobile, so always check the mobile numbers first, since most WordPress visitors now arrive on phones.
What happened to First Input Delay?
Google replaced First Input Delay with Interaction to Next Paint on March 12, 2024, and FID is now deprecated. FID only measured the first interaction, while INP measures responsiveness across the whole visit, which gives a fairer picture of real use.
Can a caching plugin fix Core Web Vitals on its own?
A caching plugin helps LCP and TTFB by serving pages faster, but it does not fix CLS or INP by itself. Layout shifts need image sizes and reserved space, and slow interactions need leaner JavaScript, so caching is one fix among several.
Sources
- Web Vitals web.dev
- Largest Contentful Paint (LCP) web.dev
- Interaction to Next Paint (INP) web.dev
- Cumulative Layout Shift (CLS) web.dev
- Understanding Core Web Vitals and Google search results Google Search Central
- Optimization WordPress Developer Resources
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
