What Is Core Web Vitals and Why Does Google Care?



What Is Core Web Vitals and Why Does Google Care?

Direct answer: Core Web Vitals are three measurements Google uses to judge how a real visitor experiences your page: how fast the main content appears, how quickly the page reacts when someone taps or clicks, and whether the layout stays still while it loads. A page passes when Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less, and Cumulative Layout Shift is 0.1 or less — measured at the 75th percentile of real visits. Google cares because slow, jumpy pages lose visitors, and the metrics are a ranking signal. On WordPress, most failures come from unoptimized images, heavy themes, and too many plugins — all fixable without a developer.

What are the three Core Web Vitals?

Core Web Vitals describe three moments in a visit, and each one maps to a frustration every web user knows. Google introduced them because page speed alone does not capture how a page feels: a page can load its code quickly and still feel broken if the main content appears late, the buttons ignore your taps, or the text jumps just as you try to click it.

Largest Contentful Paint (LCP) measures loading: how long it takes for the biggest visible element — usually the hero image or the main headline — to appear on screen. If LCP is slow, the visitor stares at a blank or half-built page and wonders whether the site is working at all.

Interaction to Next Paint (INP) measures responsiveness: the delay between a tap, click, or keypress and the next visual update on screen, across the whole visit. If INP is slow, the visitor taps a menu button and nothing happens — so they tap again, and then the menu opens twice, or the page jumps somewhere they did not intend. INP replaced the older First Input Delay metric in March 2024, because FID only measured the first interaction; a site could pass FID while its enquiry form, menu, or filter felt sluggish for the rest of the visit.

Cumulative Layout Shift (CLS) measures visual stability: how much the page’s content moves unexpectedly while it loads. If CLS is bad, you are reading a paragraph and it suddenly jumps down because an image or an ad loaded above it — and you click the wrong link. CLS is a score, not a time: it measures how far things move and how much of the screen is affected.

Together the three metrics cover the whole visit: loading, interaction, and stability. A page has to pass all three to pass Core Web Vitals at all.

What counts as a good score?

Google publishes clear thresholds for each metric, and they have been stable since INP replaced FID in March 2024. The scores are judged at the 75th percentile of real page loads, separately for mobile and desktop — meaning at least 75% of visits must meet the threshold, not just the average visit. Averages hide the slow experiences; the 75th percentile does not.

Metric What it measures Good Needs improvement Poor
LCP Loading 2.5 s or less 2.5–4.0 s Over 4.0 s
INP Responsiveness 200 ms or less 200–500 ms Over 500 ms
CLS Visual stability 0.1 or less 0.1–0.25 Over 0.25

A page passes only when all three are good at the 75th percentile. A perfect LCP does not rescue a page with a poor INP. That all-or-nothing rule is why so many sites fail: the Chrome User Experience Report data for July 2026 showed 68.3% of origins had a good LCP, 81.6% a good CLS, and 85.7% a good INP — but only 55.7% passed all three. The single failing metric is usually the one nobody looked at.

One more thing worth knowing: since Safari 26.2 (December 2025), every major browser can measure LCP and INP, so the data now reflects iPhone users too. Sites that looked fine in Chrome-only data have discovered problems they never saw before.

Why does Google care about them?

Google cares for two reasons, and only one of them is rankings. The first is user behaviour: slow pages lose visitors. People abandon pages that take too long, and they do not come back. The best-documented example is Vodafone Italy’s A/B test, published by Google, where improving LCP by 31% on otherwise identical landing pages produced 8% more sales. Speed is not a vanity metric; it is money, especially on mobile, where most visitors now arrive.

The second reason is rankings. Core Web Vitals are a ranking signal — one of many, and not the largest. Google has said repeatedly that great content can outrank a faster page, and that is true. But when two pages offer equally useful content, the faster, more stable one has the edge. More importantly, the metrics shape how Google understands your site: a site that fails Core Web Vitals on most URLs is telling Google that its visitors have a poor experience, and that feeds into how the site is treated across the board. Our guide to speeding up a slow WordPress site covers the practical fixes; this article explains what the numbers mean and why they matter.

There is also a practical reason to care that has nothing to do with Google at all: the metrics are a diagnostic tool. LCP tells you your images or hosting are too slow. INP tells you your JavaScript is too heavy. CLS tells you your layout is unstable. Fixing them makes the site better for humans, and the ranking benefit follows.

How are they measured — and where do you see yours?

There are two kinds of data, and confusing them is the most common mistake site owners make.

Field data is what real Chrome users actually experienced on your pages over the last 28 days, collected through the Chrome User Experience Report (CrUX). This is the data Google uses for the thresholds and for Search Console. It only exists for pages with enough real traffic, which is why a brand-new page may show no data at all.

Lab data is a single simulated page load — what Lighthouse and PageSpeed Insights run when you test a URL. Lab data is useful for finding problems and testing fixes, but it is one load on one simulated device, not your visitors’ experience. A Lighthouse Performance score is a lab composite under throttling; it is not a substitute for a CrUX pass.

Where to look: PageSpeed Insights (pagespeed.web.dev) shows both — field data at the top, lab data below — for any URL. Google Search Console has a Core Web Vitals report that groups your URLs into good, needs improvement, and poor, separately for mobile and desktop. Lighthouse, built into Chrome DevTools, gives the lab view with specific recommendations. And the Web Vitals extension for Chrome shows the metrics live as you browse your own site. Start with PageSpeed Insights on your homepage and your most visited post; those two URLs tell you most of what you need to know.

How do you fix a slow LCP?

LCP is slow for a small number of reasons, and they are usually the same on WordPress sites. Work through them in order of impact.

First, the LCP element itself. On most WordPress pages, the LCP element is the hero image or the featured image. If that image is a 2 MB JPEG, the page cannot paint it quickly. Compress it, serve it in a modern format like WebP, and size it to the space it actually occupies — a 2400 px wide image in a 800 px slot is wasted bytes. Our guide to making your WordPress site mobile-friendly covers responsive images, which matter here too: the phone should receive a smaller version of the hero, not the desktop one.

Second, render-blocking resources. If the browser has to download and parse a dozen stylesheets and scripts before it can paint anything, LCP suffers. A caching plugin that minifies CSS and JavaScript, and defers non-critical scripts, usually fixes this in one step. Remove the CSS and JavaScript you do not need — and on WordPress, that usually means removing plugins you do not need. Our guide to how many plugins is too many explains how to judge whether a plugin earns its place.

Third, the server. If the server takes a second to respond at all, no amount of image optimization will get LCP under 2.5 seconds. Slow hosting is the floor under everything else. Caching helps — a good caching plugin or a host with server-level caching can cut response time dramatically — but if the host itself is slow, the honest fix is better hosting. Our shared vs. managed hosting comparison explains when an upgrade is worth the money: if your server response time is consistently above 600 ms, it usually is.

Fourth, the theme. A heavy page-builder theme with animations, sliders, and a dozen font files will always be slower than a lean theme. If your LCP element is a slider image that only appears after JavaScript runs, the slider is the problem. A static hero image almost always paints faster than a slideshow.

How do you fix bad INP and CLS?

INP and CLS fail for different reasons, and both are usually cheaper to fix than LCP.

INP is slow because the browser is busy. Every interaction — a tap, a click, a keypress — has to wait for the browser’s main thread to finish whatever JavaScript it is running. On WordPress, the usual culprits are heavy JavaScript from page builders, chat widgets, social sharing buttons, and analytics scripts, all competing for the same thread. The fixes: remove JavaScript you do not need, defer scripts that do not need to run immediately, and avoid loading third-party widgets on every page. A chat widget that loads on every page, including the ones where nobody ever opens it, is a classic INP killer. Delay it until the visitor scrolls or shows intent.

CLS is bad because content moves after it appears. The usual causes on WordPress are images without width and height attributes (the browser does not know how much space to reserve, so the text jumps when the image loads), web fonts that swap in late and change line heights, and ads or embeds that inject themselves into the page after it renders. The fixes are straightforward: always set width and height on images — WordPress does this automatically for images added through the editor, but page-builder images and theme images sometimes skip it — use font-display: swap so text appears immediately in a fallback font instead of waiting, and reserve fixed space for ads and embeds so they cannot push content down. A CLS of 0.1 is a forgiving target: most sites that fix their images and fonts get there.

The WordPress fix checklist, in order

If you fix Core Web Vitals in the order below, you will spend your time on the things that actually move the numbers:

  1. Measure first. Run your homepage and top three posts through PageSpeed Insights. Write down the three numbers. Do not guess which metric is failing.
  2. Compress and resize images. Convert to WebP, size images to their display size, and lazy-load everything below the fold. Never lazy-load the hero image — it is the LCP element, and delaying it makes LCP worse.
  3. Install or configure a caching plugin. Page caching, minified CSS and JavaScript, and deferred non-critical scripts. One good caching plugin, configured properly, fixes most LCP and INP problems.
  4. Audit your plugins. Deactivate and delete anything you do not use. Each active plugin adds code to every page load. A security plugin and a backup plugin earn their place; a plugin you installed once and forgot does not.
  5. Set image dimensions and font-display. Make sure images carry width and height attributes and your theme uses font-display: swap. This alone often fixes CLS.
  6. Delay third-party widgets. Chat widgets, social feeds, and analytics should load after the page is interactive, not before it. If a widget is not essential on a page, do not load it there.
  7. Check your hosting. If the server response time is above 600 ms, caching will only help so much. A slow host is a ceiling on every other fix.
  8. Re-test and wait. Lab data changes immediately; field data takes up to 28 days to reflect your fixes, because it is a rolling window of real visits. Do not panic if Search Console still shows the old scores a week after you fix everything — the data is catching up, not disagreeing with you.

One final note: do not chase a perfect score. A page with an LCP of 2.4 seconds, an INP of 180 ms, and a CLS of 0.08 passes Core Web Vitals, and the difference between that and a perfect 100 on Lighthouse is invisible to your visitors. Fix the failures, confirm the pass, and spend the remaining time on content — which is what your visitors came for, and what Google ultimately ranks.

Frequently asked questions

What are Core Web Vitals in simple terms?

Three measurements of how a real visitor experiences your page: how fast the main content appears (LCP), how quickly the page reacts to taps and clicks (INP), and whether the layout stays still while loading (CLS). A page passes when LCP is 2.5 seconds or less, INP is 200 milliseconds or less, and CLS is 0.1 or less, at the 75th percentile of real visits.

Do Core Web Vitals affect SEO?

Yes, but they are one ranking signal among many, and not the largest. Great content can outrank a faster page. But when two pages are equally useful, the faster and more stable one has the edge — and slow pages lose visitors regardless of rankings, which costs you traffic either way.

What replaced FID in Core Web Vitals?

Interaction to Next Paint (INP) replaced First Input Delay (FID) in March 2024. FID only measured the first interaction on a page; INP measures responsiveness across the whole visit, so it catches sluggish menus, forms, and filters that FID missed.

How long does it take for Core Web Vitals to improve in Search Console?

Lab results in PageSpeed Insights improve immediately after you fix something. Field data in Search Console can take up to 28 days, because it is a rolling 28-day window of real visitor experiences. Wait at least a few weeks before judging whether a fix worked.

What is a good CLS score?

A CLS of 0.1 or less is good; 0.1 to 0.25 needs improvement; over 0.25 is poor. CLS is a score, not a time — it measures how far content moves and how much of the screen is affected. Fixing image dimensions and font loading usually gets a site under 0.1.

Leave a comment

tf
Trusted seller on ThemeForest since July 2016

We sell 100% legal, original items — every product is our own work. No fakes, no resales.

8,900+Total sales on ThemeForest
4.4★Buyer rating on ThemeForest
2016Selling since
View our portfolio →