Stay organized with collections
Save and categorize content based on your preferences.
Monday, November 12, 2018
At Google, we know that
speed matters
and we provide a
variety of tools to
help everyone understand the performance of a page or site. Historically, these tools have used
different analysis engines. Unfortunately, this caused some confusion because the recommendations
from each tool were different. Today, we're happy to announce that Pagespeed Insights (PSI) now
uses
Lighthouse as its analysis engine. This
allows developers to get the same performance audits and recommendations everywhere: on the web,
from the command line, and in Chrome DevTools. PSI also incorporates field data provided by the
Chrome User Experience Report
(CrUX). Version 5 of the PageSpeed Insights API will now provide CrUX data and all of the
Lighthouse audits. Previous versions of the PSI API will be deprecated in six months.
PageSpeed Insights provides the following information:
Lab Data:
PSI fetches and analyzes the page using
Lighthouse, which simulates how a mobile
device loads a page. It computes a set of
performance metrics
for the page (such as First Contentful Paint and Time to Interactive) and summarizes these
metrics with a performance score from 0-100. Scores are categorized into three levels; 90 and up
is considered to be a good score.
Field Data: PSI also displays real-world performance metrics (First Contentful Paint and First
Input Delay) for the page and its
origin.
(As a result, we've also deprecated the origin: query in PSI). Note that not all sites may have
field data available for display. The data set relies on a version of the Chrome User Experience
Report that is updated daily and is aggregated over the previous 28 days. Keep in mind that the
metrics here may be different from the ones in the Lab Data section as they capture a wide
spectrum of real-world network conditions and devices used by Chrome users.
Opportunities: PSI provides suggestions on how to improve the page's
performance metrics. Each suggestion in this section estimates how much faster the page will
load if the improvement is implemented.
Diagnostics: This section provides additional information about how a page
adheres to best practices for web development.
The
PSI v5 API
now returns this new analysis together with CrUX data, and all Lighthouse category data
(Performance, Progressive Web App, Accessibility, Best Practices, and SEO) for a given URL.
We have more information about the changes in our
FAQ.
If you have a specific, answerable question about using PageSpeed Insights, ask the question in
English on
Stack Overflow.
For general questions, feedback, and discussion, start a thread in the
mailing list.
Posted by Rui Chen and Paul Irish, PageSpeed Insights and Lighthouse teams
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["\u003cp\u003ePageSpeed Insights (PSI) now utilizes Lighthouse as its analysis engine, providing consistent performance audits and recommendations across various platforms.\u003c/p\u003e\n"],["\u003cp\u003ePSI incorporates both Lab Data (simulated mobile loading) and Field Data (real-world user experience) to offer a comprehensive performance overview.\u003c/p\u003e\n"],["\u003cp\u003eThe updated PSI provides opportunities for performance improvement and diagnostic information related to web development best practices.\u003c/p\u003e\n"],["\u003cp\u003eThe PSI v5 API integrates CrUX data and all Lighthouse category data for a given URL, with previous versions being deprecated in six months.\u003c/p\u003e\n"],["\u003cp\u003eUsers can find support through FAQs, Stack Overflow for specific questions, and a mailing list for general inquiries and discussions.\u003c/p\u003e\n"]]],["PageSpeed Insights (PSI) now utilizes Lighthouse as its analysis engine, ensuring consistent performance audits across various platforms. PSI offers lab data, simulating mobile device page loads, and field data, displaying real-world performance metrics from the Chrome User Experience Report (CrUX). It also provides improvement suggestions (Opportunities) and adherence to web development best practices (Diagnostics). The PSI v5 API now includes both this analysis and all Lighthouse category data, while previous versions will be phased out.\n"],null,["# PageSpeed Insights, now powered by Lighthouse\n\nMonday, November 12, 2018\n\n\nAt Google, we know that\n[speed matters](/web/fundamentals/performance/why-performance-matters)\nand we provide a\n[variety of tools](/web/fundamentals/performance/speed-tools) to\nhelp everyone understand the performance of a page or site. Historically, these tools have used\ndifferent analysis engines. Unfortunately, this caused some confusion because the recommendations\nfrom each tool were different. Today, we're happy to announce that Pagespeed Insights (PSI) now\nuses\n[Lighthouse](/web/tools/lighthouse) as its analysis engine. This\nallows developers to get the same performance audits and recommendations everywhere: on the web,\nfrom the command line, and in Chrome DevTools. PSI also incorporates field data provided by the\n[Chrome User Experience Report](/web/tools/chrome-user-experience-report)\n(CrUX). Version 5 of the PageSpeed Insights API will now provide CrUX data and all of the\nLighthouse audits. Previous versions of the PSI API will be deprecated in six months.\n\n\nPageSpeed Insights provides the following information:\n\n- **[Lab Data](/web/fundamentals/performance/speed-tools#lab_data)** : PSI fetches and analyzes the page using [Lighthouse](/web/tools/lighthouse), which simulates how a mobile device loads a page. It computes a set of [performance metrics](/web/fundamentals/performance/user-centric-performance-metrics) for the page (such as First Contentful Paint and Time to Interactive) and summarizes these metrics with a performance score from 0-100. Scores are categorized into three levels; 90 and up is considered to be a good score.\n- **[Field Data](/web/fundamentals/performance/speed-tools#field_data)** : PSI also displays real-world performance metrics (First Contentful Paint and First Input Delay) for the page and its [origin](https://developer.mozilla.org/en-US/docs/Glossary/Origin). (As a result, we've also deprecated the origin: query in PSI). Note that not all sites may have field data available for display. The data set relies on a version of the Chrome User Experience Report that is updated daily and is aggregated over the previous 28 days. Keep in mind that the metrics here may be different from the ones in the Lab Data section as they capture a wide spectrum of real-world network conditions and devices used by Chrome users.\n- **Opportunities**: PSI provides suggestions on how to improve the page's performance metrics. Each suggestion in this section estimates how much faster the page will load if the improvement is implemented.\n- **Diagnostics**: This section provides additional information about how a page adheres to best practices for web development.\n\n\nThe\n[PSI v5 API](/speed/docs/insights/v5/get-started)\nnow returns this new analysis together with CrUX data, and all Lighthouse category data\n(Performance, Progressive Web App, Accessibility, Best Practices, and SEO) for a given URL.\n\n\nWe have more information about the changes in our\n[FAQ](/speed/docs/insights/v5/about#faq).\nIf you have a specific, answerable question about using PageSpeed Insights, ask the question in\nEnglish on\n[Stack Overflow](https://stackoverflow.com/questions/tagged/pagespeed-insights).\nFor general questions, feedback, and discussion, start a thread in the\n[mailing list](https://groups.google.com/forum/#!forum/pagespeed-insights-discuss).\n\n\nPosted by Rui Chen and Paul Irish, PageSpeed Insights and Lighthouse teams"]]
