Google Launching New Version Of PageSpeed Insights

Google has introduced new PageSpeed Insights features that will improve the user experience and make statistics more understandable.

PageSpeed Insights has been updated by Google, and it now addresses many of the problems that plagued the previous edition

Google Launching New Version Of PageSpeed Insights

Newcomers to PageSpeed Insights may be unfamiliar with the data’s context, making it difficult to know what to do with it. It’s not always easy to tell the difference between lab and field data.

The issue of reading the PageSpeed Insights report has spawned a slew of “how to” blog pieces, owing to the report’s design’s inherent ambiguity.

The current version of PageSpeed Insights on the web is based on 10-year-old code, according to Google, and it’s time for a revamp.

Google expects that the upgrade, which will be released later this year, would make it easier for developers to comprehend the report and act on the information included inside it.

The following are Google’s major priorities for the future PageSpeed Insights revamp:

• Make the user interface more intuitive by distinguishing between lab and field data.
• In the UI, explain how the Core Web Vitals evaluation is calculated.
• Utilize material design to modernize the UI’s appearance and feel.

Here’s what Google has in store for the latest edition of one of its most venerable products.

Updates Coming to Google PageSpeed Insights.

Google will make the following improvements to PageSpeed Insights later this year:

• Field and lab data are being separated, with existing labels for “Field Data” and “Lab Data” being replaced with wording that explains what the data means and how it may assist.
• Google’s Core Web Vitals evaluation is now shown as a single word “passed” or “failed.” The modified evaluation will be shown in its own area, complete with its own symbol.
• Performance labels for mobile and desktop: Google is changing the top navigation menu on the report page to incorporate mobile and desktop options.
• Google is shifting the “Origin” report component under the Field Data section to a new tab called “Origin.”
• Expand view: In the field data area, a new “expand view” feature allows users to see granular information for the Core Web Vitals metrics.
• Page Image: The image of the loaded page is being removed from its present place next to the field data by Google. In the lab data area, both the picture and thumbnails will be displayed.

Finally, Google has included a section at the bottom of each field and lab card that shows the following information on the data sampled:

• Data collection period
• Visit durations
• Devices
• Network connections
• Sample size
• Chrome versions

This extra information should aid users who were previously puzzled about the differences between lab and field data.

Finally, Google has included a section at the bottom of each field and lab card that shows the following information on the data sampled:

The new PageSpeed Insights don’t have a specific release date yet, but Google will provide more information as the day approaches.

The Core Web Vitals assessment result, which formerly appeared in Field Data as a single word “passed” or “failed,” now appears as a separate subheading with a different icon the assessment method for Core Web Vitals has remained unchanged. FID, LCP, and CLS are Core Web Vitals metrics that may be aggregated at the page or origin level.

The aggregation passes the Core Web Vitals evaluation if the 75th percentiles of all three metrics are Good for aggregations with enough data in all three metrics. Otherwise, the aggregate fails the evaluation. If the aggregate lacks inadequate FID data, it will pass the evaluation if both the LCP and CLS 75th percentiles are met.

web.dev/measure web.dev/measure web.dev/measure web.dev/measure we’re also changing the web. dev/measure to use the PageSpeed Insights API directly to eliminate inconsistencies across the many tools in our performance toolkit.

Previously, developers would use the PSI tool and /or measure to produce reports and examine different Lighthouse metrics. One of the key reasons for the variations was that all of the tests were developed in the United States by /measure (due to it previously having a cloud backend that was US-based).

Developers will have a more consistent experience when using PSI and /measure since /measure calls the same API directly as the PSI UI. Based on how users utilize the tool, we’ve made a few changes to /measure. This implies that the /measure signed-in experience will be discontinued, but THE

Today’s PSI #Let’s take a step back and see what the latest PageSpeed Insights report has to offer. Individual tabs in the PSI report provide performance metrics for both mobile and desktop platforms, as well as suggestions for how to enhance a website. In each situation, the essential components of the report are the same and include the following:

The total page performance is summarised by the performance score, which appears at the top of the PSI report. Running Lighthouse to gather and evaluate lab data about the page yields this score. A score of 90 or more is regarded as excellent, 50-90 requires development, and less than 50 is considered bad.