How to Check Core Web Vitals in Google Search Console

What is the Core Web Vitals Report in Search Console?

Core Web Vitals are a set of real-world user experience metrics that Google uses to measure how fast, responsive, and stable your website is. Unlike synthetic speed tests that run in a controlled environment, the Core Web Vitals Search Console report relies on actual user data. This data comes from the Chrome User Experience Report (CrUX), which measures how real visitors experience your site over a rolling 28-day period.

When you open this report, you will not see individual page scores. Instead, Google groups similar pages together. This is highly beneficial because most blogs and websites use templates. If your blog post template has a slow-loading image, every single blog post will suffer from the same issue. By grouping these pages, Google helps you fix one template and resolve issues across hundreds of pages at once.

If you are also troubleshooting how Google crawls and indexes these pages, you can read our guide on How to Find and Fix Indexing Errors in Search Console to ensure your technical foundation is strong.

Prerequisites Before You Begin

Before we start analyzing the data, make sure you meet these requirements:

• A Verified Property: Your website must be verified in Google Search Console.
• Sufficient Traffic: Your site needs enough real-world traffic from Chrome users to generate CrUX data. If your site is brand new or has very low traffic, you might see a "Not enough data" message. If you are struggling to get crawled, you can learn How to Submit a Sitemap in Google Search Console to help Google find your pages faster.
• Access Rights: You need at least "Full" or "Owner" permissions in Search Console to start the validation process after fixing issues.

Step 1: Open the Mobile and Desktop Reports

Let us open the reports step by step. Google separates mobile and desktop performance because users experience your site differently on different devices. Mobile networks are often slower, and mobile processors are less powerful than desktop computers.

1. Log in to your Google Search Console dashboard.
2. Look at the left-hand navigation menu. Scroll down to the Experience section.
3. Click on Core Web Vitals.
4. You will see two main charts: one for Mobile and one for Desktop.

Each chart categorizes your URLs into three buckets:

• Poor: These pages offer a highly frustrating user experience and need immediate attention.
• Need Improvement: These pages are decent but do not meet Google's recommended speed thresholds.
• Good: These pages meet all speed and stability standards. Your goal is to get as many URLs into this green bucket as possible.

Always focus on the Mobile report first. Google uses mobile-first indexing, meaning it primarily uses the mobile version of your content for indexing and ranking How Are You Performing on Google?.

Step 2: Understand Field Data and URL Groups

Click on Open Report on either the Mobile or Desktop chart. You will see a list of issues grouped by metric type and status. To understand what you are looking at, let us define the three Core Web Vitals metrics:

• Largest Contentful Paint (LCP): This measures loading performance. It is the time it takes for the main content of a page to load. A good LCP is 2.5 seconds or faster.
• Interaction to Next Paint (INP): This measures responsiveness. It tracks how quickly your page responds when a user clicks a button, taps a link, or interacts with an element. A good INP is 200 milliseconds or less.
• Cumulative Layout Shift (CLS): This measures visual stability. It tracks whether elements on the page jump around unexpectedly while loading. A good CLS score is 0.1 or less.

When you click on a specific issue, such as "LCP issue: longer than 4s (mobile)", Search Console will show you URL Groups. Google groups these pages because they share the same CSS, JavaScript, or theme layout. For example, you might see a group like this:

• example.com/blog/how-to-grow-traffic/
• example.com/blog/seo-tips/
• example.com/blog/wordpress-guide/

This tells you that the issue is not unique to one post. The issue lies within your overall blog post template.

Step 3: Select a Representative URL

You do not need to analyze every single URL in a group. That would take too much time. Instead, you must select one representative URL from the group to run your diagnostics.

Here is how to select and inspect it:

1. Click on the row containing the URL group in Search Console.
2. Look at the list of example URLs provided in the details table.
3. Select one URL that represents the entire group. For instance, if the group consists of blog posts, pick any standard blog post URL.
4. Copy this URL to your clipboard.

If you want to check if Google has indexed this specific URL properly before you run speed tests, you can use the URL Inspection tool URL Inspection Tool. Simply paste the URL into the top search bar of Search Console to see its current index status .

Step 4: Diagnose the Page Template

Now that you have your representative URL, it is time to find out why it is slow or unstable. Because Search Console only provides historical field data, you must use a "lab tool" to get real-time, actionable diagnostics.

We recommend using PageSpeed Insights. It is a free tool provided by Google that analyzes your page and gives you specific recommendations.

1. Go to the PageSpeed Insights website.
2. Paste your representative URL and click Analyze.
3. Look at the Diagnose Performance Issues section below the scores.

How to Solve Common Metric Failures

Depending on which metric is failing in your Core Web Vitals report, apply these template-level solutions:

• If LCP is Poor: This is usually caused by large images or slow server response times. Optimize your images by converting them to modern formats like WebP. Ensure your hero image (the main image at the top of the page) is not lazyloaded, as lazyloading the main image actually delays LCP.
• If CLS is Poor: This is caused by layout shifts. Ensure all images, ads, and iframes have explicit width and height attributes in the HTML. If you do not set these dimensions, the browser does not know how much space to reserve, causing the content to jump when the element finally loads.
• If INP is Poor: This is caused by heavy JavaScript blocking the main thread. Reduce unused JavaScript, defer non-essential scripts, or use a lightweight caching plugin to optimize how scripts execute on your site.

Step 5: Validate the Fix in Search Console

Once your developer or your caching plugin has implemented the fixes on your live website, you must tell Google to check your work. This is where the validation process begins.

1. Go back to the specific issue details page in your Core Web Vitals Search Console report.
2. Click the grey Validate Fix button at the top of the page.
3. Search Console will perform a quick initial check. If the page is accessible, the validation status will change to Started.

The 28-Day Validation Rule

Do not expect your charts to turn green immediately. Google requires a 28-day monitoring window to collect enough real-world user data to confirm that the speed has actually improved. During this time, Google will monitor the experiences of actual visitors landing on your site.

Validation Status	What It Means	Action Required
Not Started	The issue has been detected but validation has not been requested.	Apply your fixes and click "Validate Fix".
Started	Google is actively collecting 28 days of field data from real users.	Monitor your site performance; do not make major layout changes.
Passed	The field data shows that the URLs now meet the required speed thresholds.	No action needed. Keep maintaining your site speed.
Failed	The URLs still do not meet the speed thresholds after 28 days.	Re-diagnose the template and apply stronger optimizations.

Common Mistakes to Avoid

When working with the Core Web Vitals report, avoid these common traps:

• Treating Search Console as a Live Speed Test: Search Console does not run live tests. If you fix an issue today, the warning will not disappear today. It takes time for the 28-day rolling average to reflect your changes. Use PageSpeed Insights for live testing.
• Fixing Only the Example URL: If you only optimize the single URL you copied, the rest of the URLs in that group will remain slow. You must apply the fix to the theme, template, or global plugin settings so that all pages in the group benefit.
• Starting Validation Too Early: Do not click "Validate Fix" before your changes are fully live and your cache is cleared. If Googlebot checks your site and finds the old, unoptimized code, your validation attempt may fail early.

How to Verify Your Results

To verify if your optimization work was successful, check the validation progress page in Search Console periodically.

Go to the Core Web Vitals section, click on the issue you validated, and look at the progress details. You will see a chart showing how many URLs in the group have moved from "Poor" or "Need Improvement" to "Good".

If the validation status changes to Passed, your template is officially optimized. If it changes to Failed, click on the failed group to see which specific URLs are still causing issues. Run those URLs through PageSpeed Insights again to see if a different element is causing the bottleneck.

Next Steps for Your Website

Now that you know how to monitor and fix your site's speed templates, you should ensure that your pages are also fully optimized for search visibility. Speed is only one part of the puzzle. Once your pages are fast, you must ensure they are indexed correctly. Take a look at our detailed guide on to clean up any remaining technical errors. If you want to drive more organic visitors to your newly optimized pages, read our tutorial on How to Use Search Console Queries to Grow Blog Traffic to learn how to find high-performing search queries.

Frequently Asked Questions

Why does Search Console say 'Not enough data' for my Core Web Vitals?

This happens because your website does not have enough traffic from Chrome users to generate a statistically significant amount of field data. Google requires a minimum threshold of real-world visits over a 28-day period to populate this report. In the meantime, you can use lab tools like Lighthouse or PageSpeed Insights to test your page speed manually.

How long does it take for Core Web Vitals validation to complete?

The validation process in Google Search Console takes exactly 28 days. This is because Google collects a rolling 28-day average of real-world user experience data (field data) to confirm that the speed improvements are consistent and stable for actual visitors.

Will fixing Core Web Vitals instantly boost my search rankings?

While Core Web Vitals are a ranking factor, they are part of a broader set of page experience signals. Improving your scores provides a better user experience and can prevent ranking drops, but it works best when combined with high-quality content, strong on-page SEO, and proper technical indexing.