The URL is not already a top ranker for targeted keywords with high search volume.
Page copy that is keyword-rich, likely because it was optimized.
For a given targeted keyword: The top rankers’ scores are high, but your URL mapped to the keyword has low Core Web Vitals scores.
Getting started on qualitative analysis for quantitative changes
How to conduct a qualitative analysis for quantitative changes is beyond the scope of this article. But, to get you started, here are the next steps:
Segment the URLs into groupings of shared code (e.g., Category Page, Product Grid Page, Product Detail Page, Article, etc.).
Analyze URLs in each grouping via Google Page Speed Insights and WebPageTest.org. Remember to log in when using WebPageTest.org; it will save all your test results.
If you’re savvy enough to use the CrUX API, getting data at scale will be much easier.
Use these tools to analyze individual URLs and identify improvements that can be applied at scale. This enables you to make quantitative changes across hundreds or thousands of URLs simultaneously.
The key outcome of this analysis is that it will find the “best opportunities” for improving URLs with the biggest lift potential (greatest traffic and revenue increase opportunities).
A few tips for analyzing URLs in Google Page Speed Insights
Confirm that the Core Web Vitals data reported is for the URL, not the origin. This is easily missed by less experienced SEOs and developers, causing them to evaluate origin data rather than URL data.
Determine which metrics need improvement and use the filters to identify recommendations for improving the metric.
Use the treemap to identify unused code.
A few tips for analyzing URLs in WebPageTest.org
WebPageTest.org is a treasure trove of insights for improving the entire page speed experience. Here are just a few tips for using WebPageTest.org for Core Web Vitals.
Don’t wait until the last minute. All tests go in a queue, and at the end of the month and certain times of the day, tests can take some time to run.
The filmstrip view is fantastic for developers. They can see how the page loads visually, and beneath it is a waterfall chart showing what loaded when.
Use the Web Vitals page as a highlights reel for explaining the most important issues to address. It’s a very nice summary page. It does not cover all your opportunities, but it’s a good start for common issues.
The Web Vitals view page allows you to easily see where the CLS issue(s) are. This is great visual for developers to understand the problem quickly.
What’s next?
Begin evaluating Core Web Vitals data differently, prioritizing your attention on URLs with the biggest lift potential.
To get this data, you need to access the CrUX API and curate it into meaningful segments to analyze (using shared code/templates).
Then, start looking for patterns of problems to analyze that will improve Core Web Vitals metrics across many URLs. You often only need to look at a few URLs to spot clear action items.
This was the fourth article in my series recapping my SMX presentation on identifying action items in technical SEO data. You might find Part 1, Part 2 and Part 3 useful, especially for the up-and-coming technical SEOs on your team looking to accelerate their skills.
The next (and final) article in this series will discuss technical SEO use cases and how to use tools for various scenarios to uncover problems.
Contributing authors are invited to create content for Search Engine Land and are chosen for their expertise and contribution to the search community. Our contributors work under the oversight of the editorial staff and contributions are checked for quality and relevance to our readers. The opinions they express are their own.