Core Web Vitals (CWV) are three specific metrics that measure how real users experience your web pages. They quantify loading speed, interactivity, and visual stability using field data collected from Chrome users. Google incorporates these signals into its page experience ranking factors, which means improving them can directly affect your search visibility and user retention.
What is Core Web Vitals?
Core Web Vitals consist of three measurements that apply to all web pages. Each metric represents a distinct facet of user experience and relies on real-world usage data rather than simulated tests.
Largest Contentful Paint (LCP) measures loading performance. It tracks the time from when a page starts loading to when the largest content element (typically an image or text block) becomes visible. To provide a good user experience, LCP should occur within 2.5 seconds (web.dev).
Interaction to Next Paint (INP) measures interactivity and responsiveness. It assesses the latency between a user interaction (click, tap, or key press) and the next visual update. A good INP score is 200 milliseconds or less (web.dev). Note that INP replaced First Input Delay (FID) as a Core Web Vital in 2024, as it captures responsiveness throughout the entire user session, not just the first interaction.
Cumulative Layout Shift (CLS) measures visual stability. It quantifies how much page content shifts unexpectedly during loading. A good CLS score is 0.1 or less (web.dev).
Google evaluates these metrics at the 75th percentile of page loads, segmented across mobile and desktop devices (Search Console Help).
Why Core Web Vitals matters
Google announced in 2020 that Core Web Vitals would become part of its ranking algorithm in mid-2021 as part of the Page Experience update (Google Search Central Blog). This means these metrics directly influence search rankings alongside content quality.
-
Search visibility: Pages with good CWV scores align with what Google's core ranking systems seek to reward. When Google must choose between two pages with similar content quality, the one with better page experience signals often ranks higher.
-
User retention: Fast, stable pages reduce frustration. Slow load times and layout shifts increase bounce rates and decrease return visits.
-
Mobile performance: The metrics evaluate mobile and desktop experiences separately. With mobile-first indexing, mobile CWV scores carry significant weight.
-
Competitive differentiation: In competitive SERPs, CWV can be the tiebreaker. If two websites provide similar information, the one that loads faster and responds more quickly typically earns the top position.
How Core Web Vitals works
Google measures Core Web Vitals using the Chrome User Experience Report (CrUX), which collects anonymized performance data from real Chrome users. This field data powers the Core Web Vitals report in Google Search Console.
Thresholds and status
Each metric has three status tiers based on the 75th percentile of user experiences (Search Console Help):
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP | ≤2.5s | ≤4s | >4s |
| INP | ≤200ms | ≤500ms | >500ms |
| CLS | ≤0.1 | ≤0.25 | >0.25 |
A URL group receives the status of its worst-performing metric. For example, if a page group has Good LCP and CLS but Poor INP, the entire group receives a Poor status.
URL grouping
Search Console groups similar URLs together to provide meaningful data while preserving user privacy. If a specific URL lacks sufficient data, Google aggregates it into an origin group (protocol + host + port). For example, if https://example.com/page1 lacks data, it may be grouped under https://example.com (Search Console Help).
Validation timeline
When you fix an issue, you must start a 28-day monitoring period in Search Console to validate the fix. Google monitors CrUX data during this window. If the issue does not reappear in any URL during these 28 days, the issue is marked as fixed (Search Console Help).
Best practices
Optimize images for LCP: Compress images and use modern formats. Use a content delivery network to cache content closer to users. Limit lazy-loading to images below the fold, as overuse can delay the largest contentful paint (Cloudflare).
Reduce JavaScript for INP: Minimize or defer non-critical JavaScript. Break long tasks into smaller chunks so the main thread remains responsive. Remove unnecessary third-party scripts that block interaction (Cloudflare).
Reserve space for CLS: Always include width and height attributes on images and videos. Reserve space for ad slots and embedded content using CSS aspect ratio boxes. This prevents content from jumping when media or ads load (Cloudflare).
Keep pages lightweight: Aim for less than 500KB total page size and limit resources to 50 per page for best mobile performance (Search Console Help).
Monitor mobile specifically: Check mobile and desktop reports separately in Search Console. Mobile performance often differs from desktop due to device capabilities and network conditions.
Use field data: While Lighthouse provides useful diagnostic data during development, Core Web Vitals are based on field data. Prioritize improvements that affect real user experiences as measured by CrUX.
Common mistakes
Checking individual URLs only: The Search Console report groups similar pages. You might fix one URL but miss others in the same group. Always check the URL group view to see all affected pages.
Confusing FID with INP: First Input Delay (FID) measured only the first interaction. Interaction to Next Paint (INP) measures all interactions throughout the session. Ensure your optimization efforts address full-session responsiveness, not just initial load.
Ignoring the 75th percentile: Averages hide performance problems. Google uses the 75th percentile, meaning 25% of your users may experience poor performance even if your average looks good. Optimize for the slowest quartile.
Forgetting the 28-day validation period: After deploying fixes, you must click "Start Tracking" in Search Console and wait 28 days. Changes do not reflect immediately in the report.
Relying on lab tests alone: Lighthouse scores in your local environment often differ from real-world CrUX data. Always verify improvements using Search Console or PageSpeed Insights field data.
Examples
E-commerce product pages Your product pages show Poor LCP in Search Console. Analysis reveals unoptimized hero images loading synchronously. You compress images, implement a CDN, and preload the hero image. After the 28-day validation period, the URL group moves from Poor to Good.
News website with high CLS Articles experience layout shifts when advertisements load after the content. You add fixed-size containers for ad slots using CSS aspect ratio boxes. The CLS score drops from 0.25 to 0.05, moving the status from Needs Improvement to Good.
FAQ
What is the difference between Core Web Vitals and Web Vitals? Web Vitals is the broader initiative that includes Core Web Vitals. Core Web Vitals are the three specific metrics (LCP, INP, CLS) that apply to all web pages and factor into search rankings. Other Web Vitals like Time to First Byte (TTFB) and First Contentful Paint (FCP) are useful for diagnostics but are not part of the Core Web Vitals ranking signals.
How often do Core Web Vitals metrics change? Google commits to stable definitions with changes occurring no more than once per year. Metrics progress through experimental, pending, and stable phases. Any changes are announced in advance through official documentation and changelogs (web.dev).
Why does Google use the 75th percentile instead of averages? The 75th percentile ensures that most users experience good performance. Averages can be skewed by fast connections or powerful devices, masking problems faced by users on slower networks. By targeting the 75th percentile, you optimize for real-world variability.
Can I test Core Web Vitals for a specific page immediately? Yes. While Search Console reports take time to update, you can test individual URLs using PageSpeed Insights or Chrome Lighthouse. However, note that Lighthouse provides lab data (simulated), while Search Console shows field data (real users). For validation after fixes, you must still wait for the 28-day CrUX data collection period.
Do good Core Web Vitals guarantee better rankings? No. Core Web Vitals are one of many ranking factors. Content relevance and quality remain primary. However, when content quality is equal between two pages, better page experience signals can provide a ranking advantage.
What causes "No data available" in Search Console? Either your property is new and CrUX has not yet collected data, or your site lacks sufficient traffic to meet the privacy threshold for reporting. The CrUX database requires a minimum amount of data to display metrics while protecting user anonymity (Search Console Help).
