Lighthouse 13.6.0 with better metrics for SPAs

  • Lighthouse

Treo's scheduled tests moved from Lighthouse 13.4.1 to 13.6.0 on November 6th. A "Lighthouse 13.6.0" note marks the step on your charts.

What moves on your charts

The largest change is in simulated throttling. Lighthouse now takes render-blocking from Chrome's own data (#16869), so preloads and fonts that do not block rendering no longer hold back FCP, and a text LCP painted in the same frame as FCP now equals it. Single-page apps with preloads gain the most, as Framer shows on its sites.

On mobile pages FCP and LCP fall and most scores rise, while TBT rises a little. Desktop moves little.

Pages tested through PageSpeed Insights follow Google's own move to 13.6.0, on Google's date.

Clearer failures

A failed run now says what happened: "The page crashed the browser tab", "The page stopped responding", "Chrome closed during the run" or "Lighthouse could not record the trace". A crashed tab or a page that stops responding counts toward the three failures in a row that pause a page, and the other two do not.

See any site's Core Web Vitals from Chrome users

Type a domain to open its free report.