Release Notes
Release Notes
Release notes for PageSpeed Insights API and PageSpeed Insights UI
Note: The API is versioned as v5, however the Lighthouse version is independent and updated regularly.
May 10, 2022
Introducing two new experimental field metrics to both the API and UI: Interaction to Next Paint (INP) and Time to First Byte (TTFB). These field metrics are currently experimental, but are now available for users to try out. Experimental metrics may change or disappear.
The UI has a new loading experience as well. Changes include:
Field and lab data load in parallel, so you’ll see results sooner.
PSI will attempt to resolve HTTP redirects before analysis. Before, PSI would send the URL directly to Lighthouse and Lighthouse would handle redirects. Now, PSI will attempt to follow 3XX redirects before handing off that URL to Lighthouse. It is still possible to opt to run with the "original" URL, but this is not usually advised.
The Core Web Vitals (CWV) metrics (LCP, FID, CLS) appear directly underneath the CWV assessment.
We tightened the design, reducing verbosity and vertical space.
Feb 17, 2022
PageSpeed Insights is now using Lighthouse 9.3.0. See the complete 9.3.0 release notes.
Nov 15, 2021
PageSpeed Insights UI has a new look and home. Check it out! See the associated blog post for more information.
Also, as of Nov 13, 2021, PageSpeed Insights is now using Lighthouse 9.0.0. See the complete 9.0.0 release notes and read through the notable changes.
Sept 22, 2021
PageSpeed Insights is now using Lighthouse 8.4.0. See the complete 8.4.0 release notes.
Aug 31, 2021
PageSpeed Insights is now using Lighthouse 8.3.0. See the complete 8.3.0 release notes, along with the 8.2.0 and 8.1.0 release notes.
June 10, 2021
PageSpeed Insights field data is now provided for pages and origins that might have insufficient data for a metric, but sufficient data for other metrics. Previously, field data was only surfaced if all metrics for a page or origin met a threshold of data. Now, any metric that meets the data threshold will be provided. This is reflected in the loadingExperience and originLoadingExperience objects in the API, and also in the frontend. See the docs for how this relates to the Core Web Vitals assessment.
June 1, 2021
PageSpeed Insights is using Lighthouse 8.0.0. See the complete 8.0.0 release notes and read through the Notable changes. If you use the API, consider the Breaking changes for programmatic users.
The CrUX API (which underpins PSI's field data section) has been updated, see their release notes.
May 24, 2021
Pagespeed's underlying Chrome instance was upgraded from Chrome 88 to Chrome 90. This wouldn't be very observable, except for possible impact of a few improvements to CLS that were part of 89 and 90.
April 1, 2021
Lighthouse 7.3.0 was deployed to PageSpeed Insights on April 1, 2021. See the complete 7.3.0 release notes.
March 3, 2021
As of March 3, 2021, PageSpeed Insights uses http/2 to make network requests, if the server supports it. Previously, all requests were made with http/1.1 due to constraints in connectivity infrastructure. With this improvement, you can expect more similarity between Lighthouse results from PSI and from Lighthouse CLI and DevTools (which have always made requests with h2). However, it's important to keep in mind that different environments (hardware & connectivity) will influence measurement, so cross-environment consistency is near impossible.
With this change, network connections are often established quicker. Given your requests are served in h2, you can likely expect metrics and the performance score to improve. In general, performance scores across all PageSpeed Insights runs went up by a few points.
If your page does not support h2, the report will now show an audit that estimates the performance improvement if the page were to support h2.