What are Core Web Vitals and why do they matter for SEO?
Core Web Vitals are three user experience metrics (Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift) that Google uses as confirmed ranking signals. A site that passes all three thresholds gets a Page Experience boost in search results. One that fails all three hands that advantage to competitors.
Key takeaways for the impatient reader:
– Core Web Vitals measure real loading speed, interactivity, and visual stability.
– Google has confirmed they are a ranking factor inside the Page Experience signal bundle.
– You can check your scores for free with PageSpeed Insights and the Search Console Core Web Vitals report.
– Passing thresholds are specific and measurable: not vague guidelines but hard cut-offs.
Last updated: September 2026.
Here is the honest version of what Core Web Vitals are and why they matter, without the fluff most guides pad in.
Google's original bet on ranking content by links and keywords alone broke down as the web got heavier. Pages packed with tracking scripts, giant hero images, and unstable ad layouts made technically well-ranked pages miserable to use. Core Web Vitals were Google's answer: instrument the browser, measure real user experience, and fold that measurement into ranking.
They were introduced as ranking signals in June 2021. INP replaced First Input Delay (FID) as the interactivity metric in March 2024, marking the most recent change to the framework. As of September 2026, the three metrics that matter are LCP, INP, and CLS.
For Malaysian website owners, this matters for a concrete reason beyond the generic 'rankings.' Mobile internet penetration in Malaysia is high, and a significant share of that traffic runs on mid-range Android devices over LTE connections that can drop to 3G. A site that scores well on Core Web Vitals on a fast desktop machine may still fail on the device your actual customer is holding. Google measures field data from real users, not just lab data from a simulated connection, which means your Malaysian audience's real experience is what gets graded.
Key takeaway: Core Web Vitals are not a trend or a nice-to-have. They are a confirmed, measurable ranking input that favours sites built for real users over sites built for desktop demos.
What are the three Core Web Vitals metrics and what do they measure?
The three Core Web Vitals are Largest Contentful Paint (LCP), which measures loading speed; Interaction to Next Paint (INP), which measures responsiveness to user input; and Cumulative Layout Shift (CLS), which measures visual stability. Each targets a distinct dimension of the experience a visitor actually has on your page.
Here is what each one is actually measuring under the hood.
Largest Contentful Paint (LCP)
LCP records the time from when the page starts loading to when the largest visible content element, typically your hero image, a large heading, or a banner, finishes rendering in the viewport. It is the closest proxy Google has for 'when does this page feel loaded to the user.' A slow LCP almost always traces back to one of four culprits: a slow server response, render-blocking JavaScript or CSS, slow resource load times (usually a large unoptimised image), or client-side rendering that delays the main content.
Interaction to Next Paint (INP)
INP replaced First Input Delay (FID) in March 2024 and is a stricter, more comprehensive measure. Where FID only measured the delay before the browser started processing the first user interaction, INP measures the full duration of every interaction on the page, including taps, clicks, and key presses, and reports the worst-performing one. A page with a high INP feels sluggish and unresponsive even after it loads visually. On a mid-range phone running a JavaScript-heavy page, INP failures are common.
Cumulative Layout Shift (CLS)
CLS quantifies how much the page's layout shifts unexpectedly during load. The score is calculated from the size of the shifting element and the distance it moves. The classic culprits in Malaysia include late-loading banner ads, fonts swapping in after the page renders, and images without defined width and height attributes. A high CLS score means users tap the wrong button because something shifted just before their finger landed.
The table below summarises what each metric measures and what typically causes it to fail.
| Metric | What it measures | Common causes of failure |
|---|---|---|
| LCP | Time to largest visible element rendered | Unoptimised hero images, slow hosting, render-blocking scripts |
| INP | Worst-case full interaction duration | Heavy JavaScript, long main-thread tasks, excessive third-party scripts |
| CLS | Cumulative unexpected layout movement | Ads without reserved space, unsized images, late-loading web fonts |
Caption: Summary of Core Web Vitals metrics, what each measures, and common causes of failure. A general reference framework; your site's specific causes will vary and should be diagnosed via PageSpeed Insights.
Key takeaway: Each metric targets a different failure mode. Improving LCP does nothing for your INP score. You need to diagnose and fix all three independently.
What are the passing thresholds for LCP, INP, and CLS?
Google defines three tiers for each metric: Good, Needs Improvement, and Poor. To pass, a URL must hit the Good threshold at the 75th percentile of real user sessions. The passing thresholds are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1.
These are not averages. They apply at the 75th percentile, meaning at least three quarters of your visitors must hit the Good tier for your page to be considered passing. That distinction is what catches most site owners off guard. A page that loads fast on a fibre connection in an office but lags on a mid-range phone on LTE is likely failing at the 75th percentile even if the lab score looks fine.
The full threshold breakdown:
| Metric | Good (Pass) | Needs Improvement | Poor (Fail) |
|---|---|---|---|
| LCP | Under 2.5 s | 2.5 s to 4.0 s | Over 4.0 s |
| INP | Under 200 ms | 200 ms to 500 ms | Over 500 ms |
| CLS | Under 0.1 | 0.1 to 0.25 | Over 0.25 |
Caption: Core Web Vitals passing thresholds as defined by Google. These apply at the 75th percentile of real-user field data, not lab averages. Source: web.dev/articles/vitals (Google).
One practical note for Malaysia: Search Console's Core Web Vitals report groups your URLs and flags entire groups as Failing, Needs Improvement, or Good. A single high-traffic URL dragging down a group can make the report look worse than your overall site health actually is. Always drill into the report at the individual URL level before drawing conclusions.
The INP threshold of 200 ms deserves special attention because it is tighter than most developers expect. Browser event handling, JavaScript execution, and layout recalculation all eat into that 200 ms window. Sites with heavy analytics stacks, multiple chat widgets, and cookie consent scripts commonly fail INP even after their LCP looks healthy.
Key takeaway: Know the exact numbers, apply them at the 75th percentile, and use field data from Search Console rather than relying solely on lab scores from PageSpeed Insights.
How do Core Web Vitals affect Google search rankings?
Core Web Vitals are a confirmed Google ranking signal, bundled inside the Page Experience signal group alongside mobile-friendliness and HTTPS. They act as a tiebreaker at the margin: when two pages are equally relevant for a query, the one with better page experience will tend to rank higher. They do not override content relevance, but for competitive queries, the margin is where rankings are won.
Google has published documentation confirming that Page Experience signals, including Core Web Vitals, are used in ranking. The mechanism is a ranking signal applied at the individual URL level based on field data aggregated from Chrome users (the Chrome User Experience Report, or CrUX). If a URL has insufficient field data, Google falls back to domain-level aggregation, and if that is also insufficient, Core Web Vitals may not influence that URL's ranking at all.
This creates a common misconception: site owners with newer or lower-traffic sites sometimes see little movement from CWV improvements because Google has no reliable field data for their pages yet. For high-traffic Malaysian sites with strong CrUX data, the signal is live and active.
Where Core Web Vitals have the clearest documented impact:
– Google Search on mobile: Page Experience signals were introduced specifically for the mobile index. Mobile-first indexing means your mobile CWV scores are the primary ones that matter.
– Google Discover: A good Page Experience is one of the listed eligibility requirements for Discover placement, which can be a significant traffic source for Malaysian news and lifestyle publishers.
– Top Stories carousel: AMP is no longer required, but a good Page Experience (including Core Web Vitals) is listed as a ranking consideration for Top Stories.
What Core Web Vitals do not do: they do not create a binary pass/fail ranking penalty in the way a manual action does. A site failing all three metrics does not disappear from search results. The effect is a relative boost to passing competitors, not a cliff edge for failing sites. This nuance matters because it sets realistic expectations. Core Web Vitals are one signal among hundreds, but one you can directly control and measure, which is rare.
For site owners asking how to track the SEO impact of Core Web Vitals improvements, the practical answer is to monitor organic click-through rates and average position in Search Console before and after fixes, segmented by the URLs you improved, and allow at least six to eight weeks for CrUX data to refresh and for ranking changes to stabilise.
Key takeaway: Core Web Vitals influence rankings as a tiebreaker signal, matter most on mobile, and gate access to Discover and Top Stories. They are one of the few ranking signals you can directly engineer, which is exactly why fixing them is worth the effort.
How do I check and fix my website's Core Web Vitals scores?
Use two tools in combination. PageSpeed Insights (pagespeed.web.dev) gives you both lab and field data for individual URLs instantly. Google Search Console's Core Web Vitals report gives you a site-wide view of which URL groups are failing, using real Chrome user data. Start with Search Console to find the worst-performing groups, then use PageSpeed Insights to diagnose the specific causes. Core Web Vitals are one of several checks in a technical SEO audit.
Step 1: Audit with Search Console
Open Search Console, navigate to Experience, then Core Web Vitals. You will see separate mobile and desktop reports. Download the failing URL groups and sort by traffic volume. Fix high-traffic pages first, since they contribute the most CrUX data and have the highest ranking impact.
Step 2: Diagnose with PageSpeed Insights
Paste the failing URL into PageSpeed Insights. The report separates Field Data (real users, CrUX) from Lab Data (simulated). Always read the field data first for ranking purposes. The Diagnostics section gives you specific, actionable items: which images are unoptimised, which scripts are blocking render, which elements are shifting.
Step 3: Fix by metric
For LCP: Serve images in next-gen formats (WebP or AVIF), add width and height attributes to all images, enable server-side caching, consider a CDN if your server is hosted outside Malaysia (a Kuala Lumpur-based CDN node will reduce latency meaningfully for local users), and defer non-critical JavaScript.
For INP: Audit your JavaScript bundle. Remove or defer third-party scripts you are not actively using. Analytics tools, heatmap scripts, live chat widgets, and cookie consent managers all add to main-thread work. Use the Performance tab in Chrome DevTools to identify long tasks, meaning tasks over 50 ms that block the main thread.
For CLS: Add explicit width and height to every image and embed. Reserve space for ad slots with CSS min-height. Preload your primary web font and use font-display: optional or swap with a matching fallback to prevent layout shifts on font load.
For Malaysian WordPress sites specifically: the combination of a slow shared hosting plan, an unoptimised page builder (Elementor or Divi with every feature active), and a stack of overlapping caching plugins is the most common root cause of all three failures at once. Address hosting quality before optimising assets. A fast CDN cannot fully compensate for a 700 ms server response time.
Step 4: Validate and monitor
After deploying fixes, re-run PageSpeed Insights. Then wait. CrUX data updates on a rolling 28-day window, and Search Console reflects that lag. Set a reminder to check the Search Console Core Web Vitals report four weeks after your fix deployment.
Key takeaway: Audit in Search Console, diagnose in PageSpeed Insights, fix by metric, then wait the full 28-day CrUX window before evaluating whether the changes worked.
Frequently asked questions
Do Core Web Vitals directly impact Google rankings?
Yes. Google has confirmed Core Web Vitals are a ranking signal, bundled within the Page Experience signal group. They function as a tiebreaker: when two pages are comparably relevant, the one passing all three Core Web Vitals thresholds tends to rank higher. They do not override content relevance, but for competitive queries, that margin is where positions are decided.
What is a good Core Web Vitals score for SEO?
A good score means hitting all three passing thresholds at the 75th percentile of real user sessions: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. All three must pass to receive the full Page Experience ranking benefit. Passing two out of three still leaves a gap that competing sites can exploit.
How do I improve my Core Web Vitals to rank higher on Google?
Start with Google Search Console's Core Web Vitals report to find your worst-performing URL groups, then use PageSpeed Insights to diagnose the root cause per metric. For LCP, optimise images and reduce server response time. For INP, remove or defer heavy JavaScript. For CLS, add explicit dimensions to all images and reserve space for ads and embeds.
What is the difference between lab data and field data in Core Web Vitals?
Lab data comes from a simulated test run by a tool like PageSpeed Insights using a fixed device and connection. Field data comes from real Chrome users visiting your site, aggregated in the Chrome User Experience Report (CrUX). Google uses field data for ranking decisions, so a page that scores well in lab conditions can still fail in field data if real user conditions differ.
Does Core Web Vitals apply to desktop as well as mobile?
Yes, Core Web Vitals apply to both desktop and mobile. However, because Google uses mobile-first indexing, your mobile Core Web Vitals scores carry more weight for ranking. Google Search Console provides separate reports for mobile and desktop, and in practice, mobile scores are harder to pass, especially INP on mid-range Android devices common in Malaysia.
How long does it take to see ranking changes after fixing Core Web Vitals?
Allow at least six to eight weeks. CrUX field data updates on a rolling 28-day window, meaning your improved scores take up to four weeks to fully reflect in Google's data. After that, ranking changes take additional time to propagate. Monitor average position and click-through rate in Search Console, segmented by the specific URLs you improved.