Why does Search Console show Core Web Vitals problems that PageSpeed does not?

Website owners frequently observe a discrepancy: Google Search Console reports Core Web Vitals problems, yet PageSpeed Insights shows a “Good” status. This situation indicates a fundamental difference in data sources and aggregation methods. Search Console relies on real user data collected over a 28-day period, reflecting actual user experiences. PageSpeed Insights primarily provides a snapshot from a simulated lab environment. Therefore, the root cause lies in the distinct methodologies. To address this, understand the data sources, prioritize field data, and use lab tools for specific diagnostics. Our FAQ knowledge base offers further insights into such technical challenges. This article clarifies why your Search Console core metrics might not be showing alignment with PageSpeed Insights results.

Technical Background

Google Search Console sources its Core Web Vitals data exclusively from the Chrome User Experience Report (CrUX). CrUX aggregates anonymized field data from actual Chrome users globally. This dataset represents how real users experience a website across diverse network conditions and devices. Search Console specifically reports on a rolling 28-day average of this CrUX data. A URL or group of URLs is classified as “Good,” “Needs Improvement,” or “Poor” based on these aggregated field metrics. For instance, a Cumulative Layout Shift (CLS) score below 0.1 is considered “Good.” However, PageSpeed Insights primarily utilizes Lighthouse, a lab-based tool. Lighthouse simulates a page load under controlled conditions, typically on a throttled mobile network. This provides immediate, reproducible diagnostic data for a single page. While PageSpeed Insights can display CrUX field data if available for the specific URL, its primary analysis is lab-generated. Consequently, the differing data collection methods and timeframes lead to varied reports. Search Console’s data reflects a broad user base over nearly a month, while Lighthouse offers a single-point measurement.

Root Causes and Diagnosis

Several factors contribute to the observed discrepancies. Firstly, the primary data source differs. Search Console reports on actual user experiences via CrUX. PageSpeed Insights often defaults to Lighthouse lab data, a simulated environment. Secondly, Search Console aggregates 28 days of CrUX data. Therefore, recent performance improvements may not immediately reflect in Search Console’s reports. PageSpeed Insights, however, provides a current snapshot. Thirdly, Search Console groups similar URLs. A problem affecting a few pages within a group can flag the entire group, even if individual pages perform well in a PageSpeed Insights lab test. Fourthly, CrUX captures a wide range of device types and network speeds. Lighthouse typically simulates a specific mobile device on a 4G connection. This fixed environment might not represent the average user experience. Lastly, low-traffic pages might lack sufficient CrUX data for Search Console, yet PageSpeed Insights can still run a lab test. To diagnose, always check the “Field Data” section in PageSpeed Insights, if present, and compare it directly to Search Console’s report. Google’s official documentation provides further details on Core Web Vitals metrics.

Solution

Addressing these discrepancies requires a systematic approach. First, always prioritize the Core Web Vitals report within Google Search Console. This report reflects actual user experience. It indicates the real impact on your audience. Second, use PageSpeed Insights as a diagnostic tool. When Search Console flags an issue, run PageSpeed Insights on the specific problematic URLs. Focus on the “Diagnostics” and “Opportunities” sections. These provide actionable insights for code-level optimizations. Third, segment your Search Console data. Filter the Core Web Vitals report by device type (mobile or desktop). This helps pinpoint issues specific to certain user segments. Fourth, implement targeted optimizations. For instance, if CLS is poor, analyze layout shifts in PageSpeed Insights. Identify the elements causing shifts and apply CSS fixes. Fifth, monitor the impact. After implementing changes, continue to run PageSpeed Insights for immediate lab data feedback. However, understand that Search Console will require approximately 28 days to reflect these improvements in its field data.

When analyzing PageSpeed Insights, always check if “Field Data” is available. If it is, this data directly corresponds to the CrUX data Search Console uses, offering a more direct comparison than lab data alone.

Conclusion

The core difference between Search Console and PageSpeed Insights lies in their data sources: aggregated real user data versus simulated lab data. Understanding this distinction is crucial for effective website optimization. Prioritize Search Console’s field data as the definitive measure of user experience. For comprehensive analysis and implementation, consider our Google Search Console consulting services. We can help refine your SEO optimization strategy based on these insights.