How Lighthouse 13.6 May Lift Your PageSpeed Scores Without Changing Code

Google’s PageSpeed Insights now runs on Lighthouse 13.6.0, released on Oct. 27, according to Search Engine Journal. The update tweaks the simulated First Contentful Paint (FCP) and Largest Contentful Paint (LCP), making them more accurate and generally resulting in higher lab scores.

What the Lighthouse 13.6 update actually does

The release notes describe two key simulation tweaks that affect how the tool estimates load performance.

• Lantern now uses Chrome’s render‑blocking label instead of request priority to decide what blocks rendering.
• When the LCP element is text in the same frame as the first content, Lighthouse estimates LCP from the same requests used for FCP, rather than from all preceding requests.

These changes tend to favour sites that rely heavily on JavaScript, including single‑page apps (SPAs). Pollard, a Chrome performance advocate, noted that JavaScript‑heavy sites are more likely to see an impact.

Why scores can jump without any code change

Because the simulated environment is now more realistic, the same page can receive a different PageSpeed Insights score simply due to the new Lighthouse version. The article warns that comparing scores across the version switch without noting the Lighthouse version can be misleading.

The update also modifies Lantern’s handling of fetch priority and render‑blocking labels, which can shift the timing of simulated FCP and LCP. As a result, a page that previously scored low on lab data may see an uplift even though its real‑world performance is unchanged.

Implications for SEO and paid search

However, the article stresses that good lab data does not guarantee better real‑user experiences.

Search Engine Journal points out that field data—real‑user metrics from the Chrome User Experience Report—remains the more reliable indicator of user experience. If field data does not move in step with lab scores, the uplift may be purely methodological.

Practical steps to keep your metrics honest

Treat the Lighthouse update as a signal to audit both lab and field data. Here are concrete actions you can take:

• When you run a PageSpeed Insights report, verify the Lighthouse version displayed next to the device.
• Compare the lab score with the field data (CrUX) for the same period to confirm real‑world performance.
• If the lab score jumps but field data stays flat, note the change as a version effect rather than an optimisation win.
• For JavaScript‑heavy sites, run a lightweight audit of render‑blocking resources, as the new simulation now respects Chrome’s render‑blocking label.
• Document the Lighthouse version in any internal performance dashboards so future score changes can be attributed correctly.

If you need a systematic way to track these metrics and align them with SEO and ad performance, our SEO services can set up automated monitoring, interpret the data, and recommend concrete fixes that keep both lab and field scores moving together.

What to do now

Start with a fresh PageSpeed Insights audit for your most important pages. Record the Lighthouse version shown in the report and capture both the lab and field scores.

Next, bring those numbers into a shared spreadsheet or dashboard. Flag any instances where the lab score improves but the field data does not. Those flags indicate a version‑driven change rather than a genuine performance gain.

Finally, schedule a short review with your development or product team. Discuss whether any render‑blocking resources can be deferred or inlined to turn the simulated gains into real‑world speed improvements. If you prefer a hands‑off approach, reach out to us to build a monitoring solution that surfaces these insights automatically.

Sources

• Search Engine Journal — PageSpeed Insights Scores May Rise After Lighthouse Update