Core Web Vitals – and How to Improve Them

Core Web Vitals are three metrics Google uses to measure how fast, responsive, and visually stable a website is — and they directly affect where your site ranks in search results. This guide explains what each metric is, what Google considers a “good” score, and the specific changes that improve each one.

Important 2024 update: Google replaced the original FID (First Input Delay) metric with INP (Interaction to Next Paint) on 12 March 2024. INP is now the official responsiveness metric inside Core Web Vitals. This post uses the current INP thresholds throughout.

What are Core Web Vitals?

Core Web Vitals are a set of three metrics measuring the user experience of loading and interacting with a webpage: loading speed, responsiveness, and visual stability. Google uses them as a ranking signal alongside mobile-friendliness, HTTPS, and safe browsing.

Why Core Web Vitals matter

There are two reasons to care about Core Web Vitals:

• Search ranking. Sites with good Core Web Vitals scores rank higher than otherwise-comparable sites with poor scores. The effect is stronger in competitive verticals where pages are otherwise similar in quality.
• User experience. Even ignoring ranking, the metrics measure real friction. A site that fails Core Web Vitals feels slow, janky, or unresponsive — and visitors bounce.

Improving Core Web Vitals usually delivers better conversion rates regardless of the SEO impact.

The three Core Web Vitals

The Core Web Vitals are LCP, INP, and CLS — each rated by Google as Good, Needs Improvement, or Poor.

LCP (Largest Contentful Paint)

LCP measures loading performance — specifically the time from page start until the largest visible element (usually the hero image or main heading) finishes rendering.

LCP score	Rating
Under 2.5 seconds	Good
2.5 – 4 seconds	Needs improvement
Over 4 seconds	Poor

LCP is most often hurt by large unoptimised hero images, render-blocking JavaScript, slow servers, or unoptimised fonts. Fix one at a time and re-measure.

INP (Interaction to Next Paint)

INP measures interactivity — how quickly the page responds when a user clicks, taps, or types. It replaced FID in March 2024 because INP captures the full responsiveness picture across the entire visit (FID only measured the first interaction).

INP score	Rating
200 ms or less	Good
200 ms – 500 ms	Needs improvement
Over 500 ms	Poor

INP is usually hurt by heavy JavaScript on the main thread, long event handlers, third-party scripts (chat widgets, analytics tags, marketing pixels), and large React/Vue component trees rendering during interactions. Code-splitting and deferring non-essential scripts are the most common fixes.

CLS (Cumulative Layout Shift)

CLS measures visual stability — how often the layout shifts unexpectedly after the page starts loading.

CLS score	Rating
0.1 or less	Good
0.1 – 0.25	Needs improvement
Over 0.25	Poor

CLS is most often caused by images without width and height attributes, late-loading ads or embeds, web fonts that swap and reflow the text, and content injected above existing content. Reserving space for late-loading elements is the single biggest fix.

Three tools for measuring Core Web Vitals

Before you can improve them, you need to measure them. Several free tools — most from Google — show your current scores.

PageSpeed Insights

PageSpeed Insights gives you a quick, clear breakdown of LCP, INP, and CLS for any URL. It separates field data (real-user metrics from Chrome users over the last 28 days) from lab data (a controlled test run for the current request). Both matter, but Google uses field data for ranking.

Enter your URL, click Analyze, and PageSpeed Insights returns scores plus a prioritised list of fixes. The recommendations are specific — “Eliminate render-blocking resources”, “Reduce unused JavaScript”, “Image elements do not have explicit width and height” — and clicking each one shows which files are affected. Combine with page speed optimisation work for the largest gains.

Chrome UX Report (CrUX)

The Chrome User Experience Report is the underlying dataset for the field metrics PageSpeed Insights uses. You can query it directly through Google’s CrUX dashboard or the CrUX API for time-series data — useful for tracking whether your fixes have moved the field-data needle over weeks and months.

Google Search Console Core Web Vitals report

The Core Web Vitals report inside Google Search Console groups your pages by status (Good / Needs Improvement / Poor) and lets you see exactly which URLs have issues. It uses real-world field data aggregated across your site, separated by mobile and desktop.

For ongoing monitoring, Search Console is the most useful of the three — it gives you a single place to spot regressions and confirm fixes have rolled out across the affected pages.

How to improve Core Web Vitals — the priority order

For most sites, the largest gains come from doing these in order:

1. Optimise images. Use WebP or AVIF. Serve appropriately sized images for each viewport. Set explicit width and height attributes. This single change usually improves both LCP and CLS.
2. Defer or remove non-essential third-party scripts. Chat widgets, analytics tags, marketing pixels, and live-chat tools are the biggest INP killers. Defer them, async-load them, or remove ones you no longer use.
3. Reduce render-blocking CSS and JavaScript. Inline critical CSS for above-the-fold content. Defer the rest. Use code splitting on JavaScript.
4. Reserve space for late-loading content. Set explicit dimensions on images, ads, embeds, and iframes. Use font-display: swap carefully — but with size-adjust fallback metrics to minimise the layout shift when the real font loads.
5. Choose a faster host or CDN. Hosting matters more than most site owners realise. Slow Time to First Byte (TTFB) silently caps how good your LCP can get, no matter what else you optimise.

After every change, re-run PageSpeed Insights and check Search Console field data over the next two to four weeks (field data updates slowly).

Why this matters for SEO

If you want to boost your SEO results and reduce bounce rate, Core Web Vitals are not optional. They directly affect whether Google shows your site to searchers, and they directly affect whether the visitors who do arrive stick around long enough to convert.

The good news: most sites can move from Poor to Good with three or four focused changes. The work is technical but contained, and the impact compounds — better rankings bring more visitors, and better experience converts more of them.

For sites with deeper underlying performance problems, a proper web development audit usually pays back faster than incremental tweaks. Slow themes, bloated page builders, and unoptimised plugins are common root causes that no amount of image optimisation can fully fix.

Frequently asked questions

What happened to FID?

Google replaced FID (First Input Delay) with INP (Interaction to Next Paint) as an official Core Web Vital on 12 March 2024. FID measured only the first interaction on a page; INP measures the slowest interaction across the entire visit, which is a better proxy for how the page actually feels. The new thresholds are 200 ms (Good), 500 ms (Poor) — different from FID’s 100/300 ms thresholds.

How long does it take for Core Web Vitals fixes to affect rankings?

Field data inside PageSpeed Insights and Search Console updates on a rolling 28-day window, so improvements only fully appear after about a month of real-user traffic on the fixed pages. Ranking adjustments typically follow once the field data has stabilised — usually 4 to 8 weeks after fixes ship.

Do Core Web Vitals matter more for mobile or desktop?

Google ranks the mobile version of your site (mobile-first indexing), so mobile Core Web Vitals carry more weight in most cases. Search Console reports mobile and desktop separately so you can prioritise. If you have to choose between fixing one, fix mobile first.

What is the most important Core Web Vital?

LCP and INP usually move the most for typical sites. LCP because slow loading is the most visible failure mode, INP because heavy JavaScript is the most common silent performance killer. CLS matters but is often the easiest of the three to fix once you know about it.

Can I improve Core Web Vitals without a developer?

Some fixes — better images, removing unused plugins, switching to a faster theme, enabling caching — are within reach for any WordPress administrator. JavaScript optimisation, third-party script deferral, and theme-level performance fixes usually need a developer with performance experience. PageSpeed Insights tells you which fixes need code changes versus configuration changes.