There\u2019s another metric section, this time for the lab test metrics. You\u2019ll find LCP and CLS here but won\u2019t find the FID or INP metrics from CWV. Those require clicks on the page, which lab testing doesn\u2019t reproduce. Instead, you can use Total Blocking Time (TBT) as a proxy metric to work on improving.<\/p>\nYou can also click the \u201cExpand view\u201d button to get an expanded view that includes definitions for the metrics and links with more details.<\/p>\nThe last section tells you a bit about where this data comes\u00a0from.<\/p>\nIf you hover over this information, you\u2019ll get even more info on the test conditions. While PageSpeed Insights has traditionally used a Moto G4 as the test device for many years, it looks like that is now a Moto G Power. You can also get data on the location of the test, which will be North America, Europe, or\u00a0Asia.<\/p>\nThere are some snapshots that visually show you how a page loaded over\u00a0time.<\/p>\nIf you click \u201cView Treemap,\u201d you can find the largest files and how much of the code is unused on the\u00a0page.<\/p>\nBy default, you\u2019ll see issues related to all of the metrics. There are buttons where you can filter to issues impacting specific metrics that you may want to improve.<\/p>\nThe \u201cOpportunities\u201d and \u201cDiagnostics\u201d sections will show you issues that can help your page performance.<\/p>\nThe estimated savings and improvements they show aren\u2019t realistic. There can be other blockers so you won\u2019t get the improvements shown or, in some cases, any improvement at all if you fix an issue. Sometimes, you have to fix multiple issues to actually see an improvement.<\/p>\n
You can click to expand any of the elements. You\u2019ll receive some guidance on how to fix each issue. The recommendations can change based on the system that\u2019s being tested. For instance, I tested a page on our WordPress blog, and I saw WordPress-specific guidance.<\/p>\nThe tips are useful for translating some of the issues into terms you may have heard. For instance, the \u201cdefer offscreen elements\u201d issue tells you that you should be lazy loading images. You can then search for a plugin in WordPress that handles lazy loading.<\/p>\n
There is additional information that shows what the LCP image is, what elements are causing CLS, and what elements are blocking the main thread (what you need to reduce to improve FID\/INP). This information can help you target fixes toward these elements.<\/p>\nThere\u2019s also a section for passed audits, showing you where you\u2019re already doing a good job. You may still be able to improve these. But you\u2019re likely better off spending time on other issues.<\/p>\nPageSpeed Insights has a great API. It lets you pull the field data from CrUX and the lab data from the Lighthouse test. You can also get page-level CWV data in bulk that can only be accessed via PageSpeed Insights.<\/p>\n
The problem is that not everyone has the skills to query the data in bulk and store it. But we make it easy for you in Ahrefs\u2019 Site Audit<\/a>. Follow the instructions for setting up CWV in the Crawl settings.<\/p>\nWhen you run a crawl, we\u2019ll pull the data from PageSpeed Insights into the Performance<\/strong> report, and you can drill into problematic pages.<\/p>\nWe also show the data from previous crawls, which you can use to monitor performance over time. Additionally, you can see the distribution of affected pages for each individual metric.<\/p>\nFor evaluation and monitoring, I\u2019d use Ahrefs, as shown above, to see the problematic pages and trends, as well as the Core Web Vitals<\/strong> report in Google Search Console (GSC)<\/a>.\u00a0<\/p>\nThe benefit of GSC is that it buckets similar URLs. For the bucketed pages, you will likely be working in one system or template. And when you fix the issues, you will fix them for all of the pages in that bucket.<\/p>\nOnce you know what pages or templates you need to work on, you can use the guidance from PageSpeed Insights to make improvements. I\u2019d also recommend checking out our guides on LCP<\/a>, FID<\/a>, and CLS<\/a> for how to fix various issues.<\/p>\nTo check the improvements, you can use PageSpeed Insights or run another crawl in Site Audit<\/a> to get the data in bulk. The CWV data will take longer to show the impact of any changes because it is a 28-day average, so use PSI or the PSI data in Ahrefs to check if the changes you made improved the lab test metrics.<\/p>\nIf you have any questions, message me on Twitter<\/a>.<\/p>\n<\/p><\/div>\n