> ## Content Index > Fetch the complete content index at: https://blog.geosearchleads.com/llms.txt > Use this file to discover other available public pages before exploring further. # Lighthouse 13.6.0 May Change PageSpeed Insights Lab Scores Without Site Changes - URL: https://blog.geosearchleads.com/lighthouse-13-6-pagespeed-insights-lab-score-changes/ - Published: 2026-11-07T16:03:50.000Z - Updated: 2026-11-07T16:03:50.000Z - Description: Lighthouse 13.6.0 updates its Lantern simulation model, which may affect PageSpeed Insights lab results even where a page has not changed. Learn how to separate a measurement shift from evidence of better real-user performance. - Author: GEO Search Leads - Tags: GEO Industry News Lighthouse 13.6.0 introduces changes to the simulation technology behind Lighthouse lab testing. That matters for anyone tracking PageSpeed Insights because a score movement may reflect an updated measurement model, rather than a faster or slower website. The release notes say version 13.6.0 includes Lantern upgrades, including trace engine updates, refinements to network and graph modelling, Application Response Delay (ARD) specification updates, and related diagnostics. The release was expected to reach Chrome DevTools with Chrome 159 and PageSpeed Insights within about a week. [Lighthouse’s v13.6.0 release notes](https://github.com/GoogleChrome/lighthouse/releases/tag/v13.6.0) provide the primary technical record of those changes. For SEO teams, agencies, publishers, and smaller businesses, the practical issue is interpretation. A higher PageSpeed Insights lab score after the update is not, by itself, proof that page delivery or visitor experience improved. ## What Lighthouse 13.6.0 changes Lighthouse is the auditing tool used for PageSpeed Insights lab data. Its results are generated under controlled, simulated conditions, rather than collected from every visitor to a live site. Version 13.6.0 updates Lantern, Lighthouse’s simulation system. Lantern uses information from a page load to model performance under defined testing conditions. Changes to its trace processing, network modelling, dependency graph handling, and ARD-related logic can alter the output of that model. That does not make the new scores invalid. It means they should be compared with appropriate context. If Lighthouse changes how it simulates a page, a before-and-after lab comparison can include two variables: - changes made to the page, server, or third-party resources; - changes in the Lighthouse measurement model. This distinction is especially important for teams that use a single PageSpeed Insights score as a monthly KPI or as evidence of completed optimisation work. ## Why a lab-score increase may not represent a real-world gain Lab data and field data answer different questions. Lab data is repeatable diagnostic output from a controlled test. It is useful for finding performance bottlenecks, testing individual URLs, and understanding opportunities highlighted by Lighthouse. However, it is sensitive to the Lighthouse version, test configuration, and simulation model. Field data is based on real-user experiences. In the PageSpeed Insights context, Chrome User Experience Report (CrUX) data provides aggregated field information where sufficient eligible data exists. Chrome’s CrUX guidance distinguishes simulated lab data from real-user field data and advises using field data for Core Web Vitals assessment when it is available. A Lighthouse update can therefore improve a lab metric while CrUX remains unchanged. The reverse can also happen: real-user conditions may improve or deteriorate because of traffic mix, devices, networks, geography, or backend behaviour without an equivalent movement in a single controlled test. Neither dataset should be treated as a substitute for the other. | Data type | What it represents | Best use | Key limitation | | ------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | | Lighthouse lab data | A simulated performance test run under controlled conditions | Diagnosing page-level issues and validating technical changes | Results can shift when Lighthouse testing and simulation methods change | | CrUX field data | Aggregated performance data from real Chrome users where available | Assessing real-user Core Web Vitals trends | May be unavailable for low-traffic URLs or origins and is not an instant diagnostic signal | ## How to report PageSpeed Insights results after the update The first step is to check the Lighthouse version shown in a PageSpeed Insights report. When comparing reports collected around the rollout, record whether the tests use Lighthouse 13.6.0 or a later version. This makes a potentially material methodology change visible to everyone reviewing the numbers. Next, separate the narrative around lab and field results. For example, a report can state that a lab score increased after a Lighthouse update while noting that CrUX field data has not yet shown a corresponding change. That is more accurate than presenting the lab increase as a confirmed improvement in visitor experience. Where a team made site changes at the same time, the result needs even more care. The work may have helped, but a score difference alone cannot isolate the impact of page changes from the impact of the revised simulation model. Supporting evidence can include implementation records, specific audit changes, [server and frontend measurements](https://blog.geosearchleads.com/n8n-node-automated-geo-scans-reports-ai-search/), and field-data trends. For routine reporting, consider documenting: - the report date and Lighthouse version; - whether the number is lab data or CrUX field data; - the URL or origin being assessed; - relevant releases or optimisation changes made during the period; - the field-data trend over several weeks, rather than one report snapshot. ## What this means for Core Web Vitals and search visibility Core Web Vitals are based on field data, not on a PageSpeed Insights performance score. PageSpeed Insights remains valuable, but its lab score should not be presented as a direct ranking metric or as conclusive evidence of search visibility gains. For organic search work, the more useful question is whether real users are experiencing sustained improvements. CrUX can help answer that question when data is available. Lighthouse can help identify why a page may be slow and what engineers should investigate next. This is also a reminder to avoid overly rigid score targets. A score can be a useful operational indicator, but performance work should focus on user-facing outcomes and technically actionable issues. A site that receives a better score because the testing model changed has not necessarily become easier to use, faster to render, or more competitive in search. If a PageSpeed Insights change has made it harder to explain whether your reported gains reflect implementation work or measurement context, [create a GEO Search Leads account](https://app.geosearchleads.com/pages/register) to begin [assessing your website’s GEO readiness](https://blog.geosearchleads.com/chrome-extension-free-geo-checks-scores-scan-history/) and identify optimisation opportunities. Keeping technical evidence, content accessibility, and visibility signals in view can help teams frame performance updates alongside the wider work involved in being [discoverable in search and AI-generated answers](https://blog.geosearchleads.com/ai-visibility-tool-seo-agencies/). ## Frequently Asked Questions **Did Lighthouse 13.6.0 make websites faster?** No. Lighthouse 13.6.0 changes aspects of Lighthouse’s Lantern simulation and diagnostics. It may change how a page is measured in lab tests, but it does not itself change a website’s code, hosting, or real-user loading experience. **Why did my PageSpeed Insights score rise when I changed nothing?** A Lighthouse version or simulation-model change is one possible explanation. Check the Lighthouse version in the report, then compare the result with prior reports and available CrUX field data before attributing the increase to a site improvement. **Should I ignore PageSpeed Insights lab data?** No. Lab data is useful for controlled testing and diagnostics. It should be interpreted as simulated test output, while CrUX field data is more appropriate for evaluating real-user Core Web Vitals when it is available. **How should agencies explain the change to clients?** State the Lighthouse version and distinguish the lab-score movement from real-user field performance. If a client’s site was also updated, explain that the score change may reflect both site work and the revised measurement model, then monitor CrUX trends over time. --- ## Conclusion Lighthouse 13.6.0 is primarily a measurement update, not evidence that monitored sites suddenly became faster. Teams should retain PageSpeed Insights for diagnostics, but annotate version changes, compare lab findings with CrUX where possible, and base performance conclusions on sustained real-user evidence rather than a single score shift.