How Can I Check My Site’s Core Web Vitals With Free Google Tools?

Slow, jumpy, and unresponsive pages frustrate visitors and can hold back your search performance. Google measures that real-world experience with a set of signals called Core Web Vitals. The good news is you do not need paid software to check them. Google itself provides free tools that show exactly how your pages perform.

This guide explains each vital in plain language, what a good score looks like, how to check your site with PageSpeed Insights, Search Console, Lighthouse, and the CrUX dashboard, and basic fixes for common failures.

Quick Answer

You can check Core Web Vitals for free with Google PageSpeed Insights for a single page, the Core Web Vitals report in Google Search Console for your whole site, Lighthouse in Chrome for local testing, and the CrUX dashboard for real-user trends. Aim for Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1 on at least 75 percent of visits.

What Are Core Web Vitals?

Core Web Vitals are three measurements of how a page feels to a real visitor: loading speed, responsiveness, and visual stability. Google uses them as page experience signals, and visitors feel them too — they simply leave pages that feel bad.

Largest Contentful Paint, or LCP

LCP measures how long it takes for the largest visible element in the viewport to load. On most pages that element is a hero image, a large heading, or a featured video poster. If your main content appears quickly, visitors feel the page is fast, even if smaller items load later.

Interaction to Next Paint, or INP

INP measures how quickly a page responds when a visitor clicks, taps, or types. It replaced First Input Delay in March 2024. A low INP means buttons and menus react right away. A high INP usually points to heavy JavaScript blocking the browser’s main thread.

Cumulative Layout Shift, or CLS

CLS measures how much visible content moves around while the page loads. You have felt bad CLS when you try to tap a link and an ad or image loads above it, pushing the link down. A low CLS score means the layout is stable and predictable.

The Thresholds You Need to Hit

Google groups each vital into good, needs improvement, and poor. To pass overall, at least 75 percent of real visits should be in the good range for all three.

• LCP: Good is 2.5 seconds or less. Needs improvement is up to 4 seconds. Over 4 seconds is poor.
• INP: Good is 200 milliseconds or less. Needs improvement is up to 500 milliseconds. Over 500 milliseconds is poor.
• CLS: Good is 0.1 or less. Needs improvement is up to 0.25. Over 0.25 is poor.

These numbers use field data — real visits over the last 28 days — not just a lab test. That is why a page can look fast on your office connection and still fail for visitors on slower phones.

Tool 1: PageSpeed Insights for a Single Page

PageSpeed Insights is the fastest way to check one URL. It combines field data from the Chrome User Experience Report, called CrUX, with a lab test run by Lighthouse.

Steps to Check a Page in PageSpeed Insights

1. Open the tool at PageSpeed Insights for testing page speed and Core Web Vitals.
2. Paste the full URL of the page you want to test.
3. Click Analyse and wait for both mobile and desktop results.
4. Read the top section first. It tells you if the page passed or failed Core Web Vitals over the last 28 days.
5. Check each metric and note whether the field data or the lab data looks worse.
6. Scroll to the diagnostics and fix the largest items first, such as a slow hero image or unused JavaScript.

Always look at the mobile result first. Google indexes and ranks mainly based on the mobile version, and most field data comes from phones. A strong desktop score does not make up for a poor mobile score.

If PageSpeed says there is not enough field data, the page does not get enough traffic for CrUX to report. In that case, rely on the lab data as a guide and check the site-level data in Search Console instead.

Tool 2: Search Console Core Web Vitals Report

PageSpeed is for one page. Search Console shows the pattern across your whole website, grouped by similar pages. This is where you find problems that affect templates — for example, every product page failing LCP because of one shared image setting.

Steps to Use the Search Console Report

1. Sign in at Google Search Console for Core Web Vitals reports and select your property.
2. In the left menu, open the Core Web Vitals report under Experience.
3. Review the mobile and desktop charts separately.
4. Click an issue, such as LCP poor or CLS poor, to see example URLs.
5. Open a few examples in PageSpeed Insights to diagnose the cause.
6. Fix the template or shared element, then return and validate the fix in Search Console.

Validation matters. After you fix an issue, Search Console watches real-user data for up to 28 days to confirm the improvement. Do not expect the chart to turn green overnight.

Pairing vitals data with a broader check using a tool for checking a website’s overall SEO score gives you both the technical and content picture.

Tool 3: Lighthouse in Chrome

Lighthouse runs a controlled lab test on your own computer. It is built into Chrome DevTools, so there is nothing to install. Because it is a lab test, it does not replace field data, but it is perfect for testing a fix before you publish it.

1. Open the page in Chrome, ideally in an Incognito window to avoid extension interference.
2. Open DevTools and select the Lighthouse tab.
3. Choose Mobile, tick Performance, and run the audit.
4. Read the LCP and CLS estimates and the list of opportunities, such as properly sized images or reduced JavaScript.
5. Make one change at a time and re-run the test to see the effect.

Run Lighthouse two or three times and take the middle result. Scores vary between runs because of network and device load during the test.

Tool 4: The CrUX Dashboard

The CrUX dashboard in Looker Studio shows real-user trends over time. Search for it, enter your domain, and you will see monthly charts for LCP, INP, and CLS by device. It updates monthly, so use it for trends and reporting, not daily debugging.

Basic Fixes for Common Failures

Fixing Poor LCP

• Compress and resize the hero image, and serve a modern format such as WebP or AVIF.
• Preload the hero image on key templates so the browser finds it early.
• Remove render-blocking resources and delay non-critical scripts.
• Use a fast host and a content delivery network if your visitors are spread across countries.
• Avoid sliders above the fold, because each slide change can reset what counts as the largest element.

Fixing Poor INP

• Break up long JavaScript tasks and remove third-party scripts you no longer need.
• Delay chat widgets, trackers, and pop-ups until after the page becomes interactive.
• Keep the page’s HTML size sensible, because a very large document makes every interaction slower.

Fixing Poor CLS

• Always set width and height on images and videos so the browser reserves space.
• Reserve fixed space for ads, banners, and embeds instead of letting them push content down.
• Avoid inserting new content above existing content after load, unless it follows a direct user action.
• Use font display settings that limit the shift when web fonts swap in.

Tips for Checking Core Web Vitals Properly

• Test your money pages first. Homepages get attention, but product, service, and top guide pages drive revenue and rankings.
• Check both field and lab data. Field data tells you what happened, lab data tells you why.
• Group pages by template. Fixing one template in Search Console can resolve hundreds of URLs at once.
• Re-test after every major change. New plugins, themes, and ad tags are the most common cause of sudden failures.
• Keep a simple log. Note the date, the change, and the scores before and after. It makes validation and reporting much easier.

Conclusion

Core Web Vitals are not a mystery metric hidden behind paid tools. With PageSpeed Insights you can diagnose a single page, with Search Console you can find site-wide patterns, with Lighthouse you can test fixes locally, and with the CrUX dashboard you can track real-user trends over time.

Start with Search Console to find your worst template, fix the largest issue first, and validate the change. Steady, measured improvements to LCP, INP, and CLS give visitors a faster, calmer experience — and that is exactly what these tools are there to help you deliver.

Frequently Asked Questions

Are Core Web Vitals a direct ranking factor?

Google uses Core Web Vitals as part of ranking, but content relevance matters more. Good vitals remove a disadvantage and help visitors stay, rather than acting as a shortcut to the top.

Why does PageSpeed show different scores each time I run it?

The lab test runs in real time, so network conditions, server load, and third-party scripts can change between runs. Field data is more stable because it covers 28 days of real visits. Judge progress by field data trends, not by one lab score.

What if my page has no field data in PageSpeed Insights?

That means the page does not have enough Chrome traffic in the last 28 days for CrUX reporting. Use the lab data as guidance, check origin-level data if available, and rely on the Search Console report, which groups similar pages together.

How long does it take for a fix to show as passing?

Search Console validates using a rolling 28-day window of real-user data. Even a perfect fix needs time for enough new visits to replace the old data, so expect several weeks before an issue is marked as fully passed.

Should I focus on mobile or desktop scores?

Focus on mobile first. Most traffic and Google’s indexing are mobile-based, and mobile devices are slower, so problems appear there first. Fix mobile, then confirm desktop, rather than the other way around.