If you don't know the difference between lab and field data, check out the explainer on web.dev. The traditional lab-based performance score, which is currently shown at the top, has been moved down to the Lab data section to avoid ambiguity about the origin of the score. We have also brought the Field data section to the top. Labels for "Field Data" and "Lab data" have been replaced with text that indicates what the data means and how it can help. We have changed the UI to distinctly separate field data from lab data. The fundamental changes to the UI include: Clear separation of field and lab data # The new UI is aimed to be more intuitive and helps developers quickly discover lab and field performance insights for their pages. The PSI UI redesign aims to improve the presentation of the report data and add clarity and granularity to the data available in the report. This post introduces the new features in PSI which will be released later this year. Modernize the look and feel of PSI, leveraging Material Design.Clearly communicate how the Core Web Vitals assessment is calculated in the UI.Make the UI more intuitive by clearly differentiating between data derived from a synthetic environment and data collected from users in the field.We used this as an opportunity to address interface-related issues in PSI which have sometimes made it difficult for users to navigate the report.
#Pagespeed insights code#
Today, we are excited to announce an updated version of PSI! While it is a critical element in our speed tooling suite, the PSI code base was ten years old, contained a lot of legacy code, and was due for a redesign. It integrates information from the Chrome UX Report (CrUX) and Lighthouse diagnostics to provide insights that help improve the performance of your website. Over the years, PageSpeed Insights (PSI) has evolved into a one-stop source for both field and lab data. Labels for mobile and desktop performance.
0 kommentar(er)
