GSC Core Web Vitals Report: The Complete 2026 Guide

Master the Google Search Console Core Web Vitals report for diagnosing performance issues, improving LCP/INP/CLS, and optimizing user experience in 2026.

Dilshad Akhtar
Dilshad Akhtar
Published: 29 July 2026
4 min read
TL;DRAI summary
  • The CWV report has two tabs: 'Open issues' pages failing the thresholds and 'Passing' pages meeting the thresholds .
  • Clicking a metric group e.g., 'Poor LCP' shows a list of affected URL groups.
  • CWV is a ranking signal for all search results.
  • Monthly, review the CWV report's 'Open issues' tab.

The Core Web Vitals (CWV) report in Google Search Console shows how your pages perform against Google's three key user experience metrics: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Since March 2024, INP replaced First Input Delay (FID) as...

Report Layout

Illustration for: Report Layout

The CWV report has two tabs: "Open issues" (pages failing the thresholds) and "Passing" (pages meeting the thresholds). Both tabs organize URLs by metric status group: Poor (failing), Needs improvement (borderline), and Good (passing).

The report aggregates field data from real Chrome users (CrUX) over the past 28 days. This is not lab data from Lighthouse, but real-user monitoring data that reflects actual visitor experiences. The 2026 report provides a rolling 28-day window rather than the previous fixed-month reporting period, giving more timely feedback on performance changes.

Understanding the Metrics

Illustration for: Understanding the Metrics

Largest Contentful Paint (LCP)

Illustration for: Largest Contentful Paint (LCP)

Measures perceived load speed: the time from navigation start until the largest content element (image, text block, or video poster) is fully rendered. Thresholds: Good (<2.5s), Needs improvement (2.5-4.0s), Poor (>4.0s). Common causes of poor LCP include slow server response times (TTFB), render-blocking resources, unoptimized images, and client-side rendering delays. The 2026 CrUX data includes LCP sub-parts (LCP-TTFB, LCP-LoadDelay, LCP-LoadTime, LCP-RenderDelay) in the API response, helping pinpoint the exact bottleneck.

Interaction to Next Paint (INP)

Measures responsiveness: the time from a user interaction (click, tap, keypress) until the next frame is painted. Thresholds: Good (<200ms), Needs improvement (200-500ms), Poor (>500ms). INP evaluates the entire interaction lifecycle, not just the first input. Common causes: long main-thread tasks, heavy JavaScript execution, and delayed event handlers. The 2026 CrUX update improved INP granularity by reporting the 75th percentile of all interactions, not just the worst interaction.

Cumulative Layout Shift (CLS)

Measures visual stability: the sum of all unexpected layout shifts during the page's lifespan. Thresholds: Good (<0.1), Needs improvement (0.1-0.25), Poor (>0.25). Common causes: images or embeds without dimensions, dynamically injected content, web fonts causing FOIT/FOUT, and third-party ads shifting layout after initial render.

Drilling into Issues

Clicking a metric group (e.g., "Poor LCP") shows a list of affected URL groups. Google groups similar URLs together (by template or content management system pattern) to avoid listing thousands of individual URLs. Click a group to see:

  • Affected URLs: Representative sample of failing URLs
  • CrUX data distribution: Percentage of users experiencing Good, Needs improvement, and Poor experiences
  • Diagnostic suggestions: Links to web.dev documentation and Lighthouse recommendations

The 2026 report added a "Trend" column showing metric direction over the past 28 days, making it easier to tell if a fix is working before the full reporting window resets.

Connecting CWV to Performance and Rankings

CWV is a ranking signal for all search results. A site with predominantly "Poor" CWV scores across its top pages can expect a ranking disadvantage compared to a site with "Good" scores, all else being equal. The Search Signals report (now merged into the Performance report in 2026) can show correlations between CWV score improvements and organic traffic changes.

Remediation Strategies

LCP

  • Optimize server response times (target TTFB under 800ms)
  • Implement proper image sizing and next-gen formats (WebP, AVIF)
  • Remove render-blocking CSS/JS from above-the-fold content
  • Use fetchpriority="high" on the LCP image element

INP

  • Break up long tasks (each under 50ms) using setTimeout, requestAnimationFrame, or scheduler.yield
  • Defer non-critical JavaScript
  • Minimize DOM size and complexity
  • Use the Performance API to instrument and monitor INP in real-user monitoring

CLS

  • Set explicit width and height attributes on all images and embeds
  • Reserve space for ads and dynamic content
  • Use font-display: optional for web fonts
  • Avoid injecting content above existing content without measuring available space

Audit and Verification

Monthly, review the CWV report's "Open issues" tab. For each metric with "Poor" status affecting more than 1 percent of your URLs, create a performance optimization ticket. After implementing fixes, monitor the 28-day trend for at least 14 days. A shift from "Poor" to "Needs improvement" or "Good" confirms the fix is working. Document the before-and-after CrUX distribution percentages for each URL group. Close the audit only when the "Poor" percentage for each metric is below 1 percent of all URLs in the report.

Ready to Build Your Dream Website?

Let's discuss your project and create something amazing together.