How to Check Your Website's Core Web Vitals (four Free Tools)

You can check your website's Core Web Vitals for free using Google's own tools: PageSpeed Insights, Google Search Console, the Web Vitals extension for Chrome, and Chrome DevTools. These tools measure user experience metrics that directly impact your site's SEO ranking and visitor retention.

Understanding Core Web Vitals in 2026

Core Web Vitals are a specific set of metrics Google uses to measure a webpage's real-world user experience. They aren't abstract technical goals. They are direct measurements of how quickly your page loads, how fast it responds to clicks, and how much the layout shifts around unexpectedly. In short, they quantify how delightful, or frustrating, your site is to use.

Initially launched in 2020, these metrics became a confirmed Google ranking signal in 2021. Since then, their importance has only grown. Google wants to send its users to websites that provide a good experience, and Core Web Vitals are its primary way of measuring that experience at scale. A poor score tells Google your site might frustrate users, which can harm your visibility in search results.

For your business, this is about more than just SEO. A slow, clunky website drives away customers. A 2025 Deloitte Digital study confirmed that even a 100-millisecond improvement in page load speed can increase conversion rates by up to 8%. Fixing your Core Web Vitals means creating a better, faster experience that keeps users on your site and guides them toward your goals.

The metrics themselves have evolved. In March 2024, Google replaced First Input Delay (FID) with a more comprehensive metric called Interaction to Next Paint (INP). This shift reflects a deeper focus on the total responsiveness of a page, not just the very first interaction.

As of early 2026, the three Core Web Vitals you must focus on are:

• Largest Contentful Paint (LCP): Measures loading performance.
• Interaction to Next Paint (INP): Measures interactivity and responsiveness.
• Cumulative Layout Shift (CLS): Measures visual stability.

Passing the Core Web Vitals assessment means your site meets the “Good” threshold for all three metrics, based on data from real users over the preceding 28 days. Let’s break down what each metric actually means for your website management.

What Is Largest Contentful Paint (LCP)?

Largest Contentful Paint (LCP) measures how long it takes for the largest single image or block of text to become visible within the user's viewport (the part of the screen they can see without scrolling). It’s a direct proxy for perceived loading speed. It answers the user's question: “Is this page actually loading something useful?”

The "largest" element is determined as the page loads. It might be a hero image, the H1 headline, or a large paragraph of introductory text. LCP only considers content above the fold.

What are the LCP score thresholds?

• Good: Under 2.5 seconds
• Needs Improvement: Between 2.5 and 4.0 seconds
• Poor: Over 4.0 seconds

A "Good" LCP score reassures visitors that your page is working and the content they came for is on its way. A "Poor" score is a primary reason for high bounce rates, as users often leave a page they perceive as broken or stalled.

Common causes of a poor LCP score include:

• Slow server response times: The server itself is taking too long to send the first bits of data. This can be due to cheap hosting, unoptimized databases, or a lack of server-side caching.
• Large, unoptimized images: This is the most frequent culprit. A 4MB hero image for a blog post is a guaranteed LCP failure. Images must be compressed and served in modern formats like WebP or AVIF.
• Render-blocking resources: Large CSS and JavaScript files can block the browser from rendering the main content. The browser has to download, parse, and execute these files before it can show the page, delaying the LCP.
• Client-side rendering: Websites built with certain JavaScript frameworks that render the entire page in the user's browser can have terrible LCP scores. The browser receives a nearly empty HTML file and has to run a lot of code before any content appears.

What Is Interaction to Next Paint (INP)?

Interaction to Next Paint (INP) measures the overall responsiveness of your page to user interactions. It calculates the time from when a user clicks, taps, or types until the next visual change (or "paint") happens on the screen. It doesn't just measure one interaction; it observes all interactions during a user's visit and reports the longest one (or one of the longest, for pages with many interactions). This makes it a much better indicator of general sluggishness than its predecessor, FID.

INP answers the user's question: “Did the website register my click?” A low INP means instant feedback. A high INP feels like the page is frozen or broken.

What are the INP score thresholds?

• Good: Under 200 milliseconds
• Needs Improvement: Between 200 and 500 milliseconds
• Poor: Over 500 milliseconds

Think about clicking an “Add to Cart” button, opening an accordion menu on a FAQ page, or submitting a contact form. A high INP means there’s a noticeable, frustrating delay before the user sees the item in their cart, the accordion expand, or a "message sent" confirmation. This friction directly impacts conversions.

Common causes of a poor INP score include:

• Heavy JavaScript execution: The most common cause. If the browser's main thread is busy running a complex script, it can't respond to the user's input. This is often caused by third-party scripts (like analytics, ads, or chat widgets) or inefficient custom code.
• Large DOM size: A webpage with an excessive number of HTML elements (a large Document Object Model) requires more work from the browser to calculate layout and style changes, slowing down rendering after an interaction.
• Complex CSS selectors and animations: Overly complicated CSS can take a long time for the browser to process, delaying the "paint" part of the interaction.
• Input delay: The browser is busy with another task (like parsing a large file) and can't even begin to process the user's click or tap right away.

What Is Cumulative Layout Shift (CLS)?

Cumulative Layout Shift (CLS) measures the visual stability of your page. It quantifies how much your page content unexpectedly moves or shifts around as it loads. A high CLS score means elements are jumping around the page, which is a jarring and frustrating user experience. It often causes users to click on the wrong thing, like accidentally clicking an ad when they meant to tap a navigation link.

CLS answers the user's question: “Can I trust what I’m seeing, or is it going to move?”

What are the CLS score thresholds?

• Good: Under 0.1
• Needs Improvement: Between 0.1 and 0.25
• Poor: Over 0.25

The classic example of bad CLS is reading an article when an ad or a large image suddenly loads above the text, pushing the paragraph you were reading down the page. Another is trying to click a button, only to have a cookie consent banner load in its place at the last second, causing you to accept something you didn't mean to.

Common causes of a poor CLS score include:

• Images or videos without dimensions: If you don't specify the `width` and `height` attributes for an image, the browser doesn't know how much space to save for it. When the image finally loads, it pushes all the other content down.
• Dynamically injected content: Ads, banners, or embeds that are loaded with JavaScript and inserted into the page after the initial content has rendered are a primary source of layout shifts.
• Web fonts causing layout shifts: When a custom web font loads, it can replace a system fallback font. If the two fonts have different sizes or spacing, it can cause a flash of text resizing (known as FOUT or FOIT), which contributes to CLS.
• Animations that trigger layout changes: Using CSS properties like `top` or `margin` to animate elements forces the browser to recalculate the layout of the entire page for each frame of the animation.

The Four Best Free Tools to Measure Core Web Vitals

You don't need expensive software to diagnose your site's performance. Google provides a full suite of free tools that give you all the data you need. The key is knowing which tool to use for which job. They generally fall into two categories: tools that use real-world "field data" and tools that use simulated "lab data."

• Field Data (RUM): Real User Monitoring data is collected from actual Chrome users who have opted in to sharing anonymous usage statistics. This data reflects how your site performs across a wide variety of devices, network conditions, and locations. This is the data Google uses for ranking. It's found in PageSpeed Insights and Search Console.
• Lab Data: Lab data is collected in a controlled, simulated environment with a consistent device and network speed. It's perfect for debugging because the results are repeatable. You can test changes and see their direct impact instantly. This is the data you get from Lighthouse (in Chrome DevTools) and the Web Vitals extension.

A complete website management workflow uses both. You start with field data to see what real users are experiencing, then use lab data to diagnose, fix, and verify the issue.

1. Google PageSpeed Insights

PageSpeed Insights (PSI) is the best all-in-one tool for getting a comprehensive report on your Core Web Vitals. It's the first place you should look. You just enter a URL, and it provides both field data from the last 28 days and a fresh lab test.

How to use it:

1. Go to the PageSpeed Insights website.
2. Enter the full URL of the page you want to analyze and click "Analyze."
3. The report will show two main sections: one for Mobile and one for Desktop. Mobile is the default and is generally more important for SEO, as Google uses mobile-first indexing.
4. At the top, you'll see a verdict: "Core Web Vitals assessment: Passed" or "Failed." This is based on the field data ("Discover what your real users are experiencing").
5. Below that, you'll find the detailed lab test results ("Diagnose performance issues"), which includes a performance score from 0-100 and specific metrics.

The real power of PSI is in the "Opportunities" and "Diagnostics" sections at the bottom of the lab report. It doesn't just tell you your LCP is slow; it tells you why. It will list the specific render-blocking resource, identify the largest contentful paint element, and show you which images are unoptimized. This makes it an actionable starting point for your content team or developer.

2. Google Search Console

While PageSpeed Insights is for analyzing one page at a time, Google Search Console gives you a site-wide overview of Core Web Vitals performance. It aggregates the field data for all indexed URLs on your site and groups them into "Poor," "Needs Improvement," and "Good."

This is your command center for monitoring your site's health over time. You won't use it for real-time debugging, but you will use it to identify systemic problems.

How to use it:

1. Log in to your Google Search Console account. If you haven't set it up, you'll need to verify ownership of your site first.
2. In the left-hand menu, navigate to the "Experience" section and click on "Core Web Vitals."
3. You'll see two reports, one for Mobile and one for Desktop. Each report shows a chart of your site's URLs over time, categorized by status (Poor, Needs Improvement, Good).
4. Below the chart, you'll see a list of specific issues, like "LCP issue: longer than 4s" or "CLS issue: more than 0.25."
5. Clicking on an issue will show you a list of example URLs that are failing for that reason.

After your developer has fixed an issue on those pages, you can use the "Validate Fix" button in Search Console. This tells Google to start monitoring the affected URLs. If Google confirms the fix is working for real users over the next 28 days, the issue will be cleared from your report.

3. Chrome DevTools

Chrome DevTools is the most powerful tool for real-time, hands-on debugging. It's built right into your Chrome browser and provides a suite of panels for deep analysis, including the "Performance" and "Lighthouse" panels.

This is a developer-centric tool, but marketers and project managers should know its basic functions to better communicate with their technical teams.

How to use it (Lighthouse Panel):

1. On any webpage, right-click and select "Inspect" to open DevTools. Or use the shortcut (Cmd+Option+I on Mac, Ctrl+Shift+I on Windows).
2. Navigate to the "Lighthouse" tab.
3. Select the categories you want to audit (Performance is the key one for CWV), choose the device (Mobile or Desktop), and click "Analyze page load."
4. Lighthouse will run a simulated audit and generate a report nearly identical to the lab data section of PageSpeed Insights, but you can run it on any site, including local development versions that aren't public.

How to use it (Performance Panel):

1. In DevTools, go to the "Performance" tab.
2. Click the record button (a circle) or press Ctrl+E, then reload the page you want to analyze. Once the page is loaded, stop the recording.
3. The panel will show a detailed "flame chart" timeline of everything the browser did to load and render the page. In the "Timings" track, you can see markers for LCP. The "Interactions" track will show you any long-running tasks that would cause a poor INP score. This allows a developer to pinpoint the exact line of code or network request that's causing a bottleneck.

4. Web Vitals Chrome Extension

The Web Vitals extension is the simplest way to get an instant, at-a-glance check on any page you visit. After installing it, the extension icon will give you a simple red, yellow, or green light for the Core Web Vitals of the current page as you browse.

This tool is invaluable for quick checks and for spotting issues as a user would. For example, you can click around your own site and see the INP metric update in real-time. If clicking a specific menu makes the extension icon flash red, you've found an interaction that needs to be optimized.

How to use it:

1. Install the Web Vitals extension from the Chrome Web Store.
2. Browse to any page on your website.
3. Click the extension's icon in your toolbar. It will show a dropdown with the live LCP, INP, and CLS scores for your current session. The icon itself will be green if all metrics are good, yellow if one needs improvement, and red if one is poor.

While it uses lab data from your own machine, it’s the fastest way to get immediate feedback on how your site feels to use. It helps bridge the gap between abstract reports and the actual user experience.

Tool Comparison: Which One Should You Use?

A Practical Workflow for Improving Your Scores

Knowing the tools is one thing; using them effectively is another. A systematic approach to fixing Core Web Vitals will save you time and ensure you're working on the highest-impact issues first.

Step 1: Get the Big Picture with Search Console
Start in your Google Search Console Core Web Vitals report. Look at the Mobile tab first. Are most of your URLs "Good," or do you have a large number of "Poor" URLs? Identify which metric (LCP, INP, or CLS) is causing the most failures. This tells you where to focus your efforts. For example, if 90% of your poor URLs are due to CLS, you have a systemic template issue, not just a problem with one page.

Step 2: Analyze a Problem URL with PageSpeed Insights
Go to the list of example URLs in Search Console for a specific issue (e.g., "LCP issue: longer than 2.5s (mobile)"). Copy one of those URLs and paste it into PageSpeed Insights. Run the analysis and look at the "Opportunities" and "Diagnostics" sections. This will give you specific, tactical recommendations. For an LCP issue, it might say "Properly size images," "Eliminate render-blocking resources," or "Reduce initial server response time."

Step 3: Debug and Fix with Chrome DevTools
This is where your developer takes over. Armed with the PSI report, they can use Chrome DevTools to dig deeper. If the issue is a slow server response, they might check database queries or server caching. If it's a render-blocking CSS file, they can use the Performance panel to see exactly how long it's taking to load and decide how to optimize it (e.g., by inlining critical CSS). For an INP issue, they can use the Performance panel to find the specific JavaScript function that is taking too long to run after a click.

Step 4: Verify the Fix in a Lab Environment
After making a change, the developer can immediately re-run the Lighthouse audit in DevTools on their local machine or a staging server. This provides instant feedback. Did the LCP score improve? Is the INP now under 200ms? This lets them iterate quickly without having to wait for field data to update.

Step 5: Validate and Monitor in Search Console
Once the fix is deployed to your live website, go back to the Core Web Vitals report in Search Console. Find the issue you were working on and click "Validate Fix." This tells Google you believe the problem is solved. Google will then monitor users visiting those pages. Over the next few weeks, you should see the number of "Poor" URLs decrease and eventually, the issue will be marked as "Passed."

By following this cycle, you move from high-level monitoring to specific diagnosis, deep debugging, and final validation, using the right tool for each stage of the process.

At WorkspaceCMS, our platform is engineered to be SEO-ready out of the box, with built-in features like automatic image optimization, minification of code, and intelligent caching to help you pass Core Web Vitals without needing a developer for every change. Our all-in-one dashboard simplifies website management, so you can focus on your content pipeline, not on performance tuning.

Core Web Vitals FAQ

What score do I need to pass Core Web Vitals?

To pass, your page must have a "Good" score for all three metrics: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. This is based on the 75th percentile of real-user visits over the last 28 days, meaning at least 75% of your visitors must have a "Good" experience for your page to pass the assessment.

How often should I check my Core Web Vitals?

You should check your Google Search Console report at least once a month for a high-level overview. If you are actively publishing content or making changes to your website (like adding new features or plugins), check more frequently, perhaps weekly. Use PageSpeed Insights or the Web Vitals extension immediately after any major site change to ensure you haven't introduced a new performance issue.

Can I ignore Core Web Vitals if my content is great?

No. While high-quality, relevant content is the most important ranking factor, Google uses page experience signals, including Core Web Vitals, as a tie-breaker. If you and a competitor have equally good content, the site with the better user experience will often rank higher. More importantly, poor vitals directly lead to higher bounce rates and lower conversions, so you're losing customers even if you manage to rank.

Why are my lab data and field data scores different?

They measure different things. Lab data (from Lighthouse, DevTools) is a single test from one location on a specific network and device setting. Field data (from Search Console, PSI) is an average of thousands of real user sessions from all over the world on different devices and networks. Your field data can be worse than your lab data if your real users have slower devices or internet connections than the lab test's simulated environment.

Will using WorkspaceCMS automatically fix my Core Web Vitals?

WorkspaceCMS provides a powerful, performance-optimized foundation. Features like automatic image compression, code minification, and a global CDN give you a significant head start and handle many common causes of poor vitals. However, performance also depends on the content you add. For instance, uploading a massive, uncompressed video file or embedding a dozen slow third-party scripts can still negatively impact your scores. Our platform handles the technical foundation so you can focus on creating great content.