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.
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.
March 2, 2021
As of March 2, 2021, the max timeout of the PSI API was raised from 60s to 120s. Complex and heavy web pages can take longer to analyze, and many would time out. We've relaxed our timeouts to give these heavyweight pages a better chance of getting results.
February 19, 2021
As of February 19, 2021, PageSpeed Insights is using Lighthouse 7.1.0. See the complete 7.0.0 release notes and read through the Notable changes. If you use the API, consider the Breaking changes for programmatic users. As this is an upgrade since 6.3.0, it includes the major v7 release, along with 6.4.0, 6.5.0 and 7.1.0 releases. You may see runs taking slightly longer for heavy pages. You shouldn't expect significantly different performance scores, though small metric adjustments are due to bug fixes in the analysis and metric implementations.
December 3, 2020
As of December 3, 2020, PageSpeed Insights is using the Chrome User Experience Report (CrUX) API to get field data. In the API, this affects the
originLoadingExperience objects. More information on the change can be found here.
Sept 8, 2020
Lighthouse 6.3.0 was deployed to PageSpeed Insights on Sept 8, 2020.
May 27, 2020
Lighthouse 6.0.0 was deployed to PageSpeed Insights on May 27, 2020.
May 7, 2019
Lighthouse released 5.0 on May 7, 2019. Information on changes can be found here: Lighthouse 5.0 + PSI Release Notes
January 31, 2019
Lighthouse (which powers PageSpeed Insights) released v4.1 on January 31, 2019. Information on changes can be found here: Lighthouse 4.1 Release Notes
v5 of the PageSpeed Insights API was released in November 2018. It now uses Lighthouse as its analysis engine and also incorporates field data provided by the Chrome User Experience Report (CrUX). v5 of the API will now provide CrUX data and all of the Lighthouse audits. Previous versions of the PSI API will be deprecated in six months.
Historical API Versions
v4 of the PageSpeed Insights API was released in January 2018. It adds a speed score based on Chrome User Experience Report and refines the original PSI score as a new optimization score which mainly focuses on the relative headroom to improve.
v2 of the PageSpeed Insights API was released in January 2015. It adds support for rule groups, such as 'SPEED' or 'USABILITY'.
Updates after release:
- Result category was added on May 12th, 2017.
- Render engine was switched from Webkit to Blink on February 2nd, 2017.
- Image optimization library was switched to use the one in mod_pagespeed on December 12th, 2016.
- The app-install interstitial rule was removed from score compuation in both API versions on August 23th, 2016. The rule was removed completely on November 1st, 2016.
Deprecated. Will close on Jun 2018.
The initial version of the API. This release includes support for localization in 40 languages.
On October 29, 2013, the
ruleScore field, which has been deprecated in PageSpeed Insights for over a year, was removed from the API. We recommend that clients use the
ruleImpact field instead.