Google’s free tool combining Lighthouse testing with available Chrome user experience data.
PageSpeed Insights is Google’s tool for examining page experience on mobile and desktop. It combines a Lighthouse lab test with available Chrome User Experience Report field data. These are different kinds of evidence: the test describes a controlled run, while the field section summarizes eligible real-user experiences.
The field data covers a previous 28-day collection period and may be available for a URL or a broader origin. Some pages do not have sufficient eligible data for a page-level report. That absence should not be read as a pass or a failure. Likewise, a fresh improvement may be visible in a new lab run before it is reflected across the historical field window.
The report is a starting point for diagnosis, not a complete SEO audit or a promise about revenue. Recommendations should be interpreted against the actual site and its important journeys. A change that improves one score while breaking navigation or hiding useful content is not a satisfactory outcome. Keep the performance work connected to what visitors need to accomplish.
Takeaway: Read the field and lab sections separately and preserve their scope. Use the findings to investigate specific problems instead of treating one overall score as the business’s search performance.
Example
A music school tests its lesson-booking page after simplifying a large image. The new lab run shows the changed loading behavior, while the field section still represents a period containing earlier visits. The owner reports that distinction rather than claiming the historical data has instantly validated the release.
What to check
Test representative page types, not only the homepage. Save the URL, device mode and test date with the result. Review whether field data describes the exact URL or the origin, and ask a developer to explain which diagnostic is likely to matter before making broad changes.
For more detail, see Google PageSpeed Insights documentation.