Stay organized with collections
Save and categorize content based on your preferences.
Wednesday, January 10, 2018
PageSpeed Insights
provides information about how well a page adheres to a set of best practices. In the past, these
recommendations were presented without the context of how fast the page performed in the real
world, which made it hard to understand when it was appropriate to apply these optimizations.
Today, we're announcing that PageSpeed Insights will use data from the
Chrome User Experience Report
to make better recommendations for developers and the optimization score has been tuned to be more
aligned with the real-world data.
The PSI report now has several different elements:
The Speed score categorizes a page as being Fast, Average, or Slow. This is determined by
looking at the median value of two metrics: First Contentful Paint
(FCP)
and DOM Content Loaded
(DCL).
If both metrics are in the top one-third of their category, the page is considered fast.
The Optimization score categorizes a page as being Good, Medium, or Low by estimating its
performance headroom. The calculation assumes that a developer wants to keep the same appearance
and functionality of the page.
The Page Load Distributions section presents how this page's FCP and DCL events are distributed
in the data set. These events are categorized as Fast (top third), Average (middle third), and
Slow (bottom third) by comparing to all events in the Chrome User Experience Report.
The Page Stats section describes the round trips required to load the page's
render-blocking resources,
the total bytes used by the page, and how it compares to the median number of round trips and
bytes used in the dataset. It can indicate if the page might be faster if the developer modifies
the appearance and functionality of the page.
Optimization Suggestions is a list of
best practices
that could be applied to this page. If the page is fast, these suggestions are hidden by default, as the page is already in the top third of all pages in the data set.
For more details on these changes, see
About PageSpeed Insights.
As always, if you have any questions or feedback, please visit our
forums
and please remember to include the URL that is being evaluated.
Posted by Mushan Yang (杨沐杉) and Xiangyu Luo (罗翔宇), Software Engineers
[[["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 now uses real-world data from the Chrome User Experience Report to provide more accurate optimization recommendations and scoring.\u003c/p\u003e\n"],["\u003cp\u003eThe updated report includes a Speed score, Optimization score, Page Load Distributions, Page Stats, and Optimization Suggestions to help developers understand and improve page performance.\u003c/p\u003e\n"],["\u003cp\u003eA page's Speed score is categorized as Fast, Average, or Slow based on First Contentful Paint (FCP) and DOM Content Loaded (DCL) metrics.\u003c/p\u003e\n"],["\u003cp\u003eOptimization Suggestions, based on best practices, are hidden by default for pages categorized as "Fast".\u003c/p\u003e\n"]]],["PageSpeed Insights now incorporates data from the Chrome User Experience Report to provide tailored recommendations. The report categorizes page speed (Fast, Average, Slow) using First Contentful Paint (FCP) and DOM Content Loaded (DCL) metrics. It also provides an Optimization score (Good, Medium, Low) and visualizes FCP and DCL event distributions. Additionally, the report details page stats, like round trips and byte usage, and offers optimization suggestions that are hidden if the page speed is already top-tier.\n"],null,["# Real-world data in PageSpeed Insights\n\nWednesday, January 10, 2018\n\n\n[PageSpeed Insights](https://pagespeed.web.dev/)\nprovides information about how well a page adheres to a set of best practices. In the past, these\nrecommendations were presented without the context of how fast the page performed in the real\nworld, which made it hard to understand when it was appropriate to apply these optimizations.\nToday, we're announcing that PageSpeed Insights will use data from the\n[Chrome User Experience Report](https://blog.chromium.org/2017/10/introducing-chrome-user-experience-report.html)\nto make better recommendations for developers and the optimization score has been tuned to be more\naligned with the real-world data.\n\nThe PSI report now has several different elements:\n\n- The Speed score categorizes a page as being Fast, Average, or Slow. This is determined by looking at the median value of two metrics: First Contentful Paint ([FCP](/web/updates/2017/06/user-centric-performance-metrics)) and DOM Content Loaded ([DCL](/web/fundamentals/performance/critical-rendering-path/measure-crp)). If both metrics are in the top one-third of their category, the page is considered fast.\n- The Optimization score categorizes a page as being Good, Medium, or Low by estimating its performance headroom. The calculation assumes that a developer wants to keep the same appearance and functionality of the page.\n- The Page Load Distributions section presents how this page's FCP and DCL events are distributed in the data set. These events are categorized as Fast (top third), Average (middle third), and Slow (bottom third) by comparing to all events in the Chrome User Experience Report.\n- The Page Stats section describes the round trips required to load the page's [render-blocking resources](/web/fundamentals/performance/critical-rendering-path), the total bytes used by the page, and how it compares to the median number of round trips and bytes used in the dataset. It can indicate if the page might be faster if the developer modifies the appearance and functionality of the page.\n- Optimization Suggestions is a list of [best practices](/speed/docs/insights/rules) that could be applied to this page. If the page is fast, these suggestions are hidden by default, as the page is already in the top third of all pages in the data set.\n\n\nFor more details on these changes, see\n[About PageSpeed Insights](/speed/docs/insights/about).\nAs always, if you have any questions or feedback, please visit our\n[forums](https://groups.google.com/forum/)\nand please remember to include the URL that is being evaluated.\n\nPosted by [Mushan Yang (杨沐杉)](https://www.linkedin.com/in/mushan) and Xiangyu Luo (罗翔宇), Software Engineers"]]
