19 Best Core Web Vitals Testing Tools (2026 Guide)

Google doesn't just look at your content anymore — it looks at how your page feels to use. Does it load fast? Does it respond the moment someone taps a button? Does the layout stay put instead of jumping around while images and ads load in? Those three questions are exactly what Core Web Vitals measure, and they've been a confirmed part of Google's ranking systems since the Page Experience update. If your Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) scores are sitting in the red, you're leaving both rankings and conversions on the table.

The problem is that "testing Core Web Vitals" isn't a single action — it's a mix of lab data (simulated tests on a controlled connection) and field data (real visitors on real devices and networks), and no single tool gives you the complete picture. Some tools are built for a five-second gut check before you ship a page. Others are built to sit in your CI/CD pipeline and fail a build the moment LCP regresses. Others exist purely to turn raw millisecond numbers into a prioritized fix-it list a non-developer can act on.

This guide breaks down the 19 best Core Web Vitals testing tools available today — what each one actually measures, who it's built for, and where it fits in a realistic performance workflow. Whether you're a solo blogger running one audit before publishing or an in-house SEO team monitoring hundreds of URLs, there's a tool (or combination of tools) on this list for you.

Before diving in, it helps to run your own numbers through a broader Website SEO Score Checker so you can see how performance sits alongside your other on-page SEO signals, not in isolation.

Quick Refresher: What Are Core Web Vitals?

Google currently tracks three Core Web Vitals metrics, each scored on a "Good / Needs Improvement / Poor" scale based on the 75th percentile of real user sessions:

• Largest Contentful Paint (LCP) — how long it takes for the largest visible element (usually a hero image or headline) to render. Good: under 2.5 seconds.
• Interaction to Next Paint (INP) — how quickly the page responds to a click, tap, or keypress, measured across the entire page visit. Good: under 200 milliseconds. INP officially replaced First Input Delay (FID) as a Core Web Vital in March 2024.
• Cumulative Layout Shift (CLS) — how much visible content shifts unexpectedly during load. Good: under 0.1.

A fourth metric, Time to First Byte (TTFB), isn't a Core Web Vital itself but heavily influences LCP, since a slow server response delays everything downstream. Most of the tools below report on it anyway.

1. Google PageSpeed Insights (PSI)

Best for: A free, instant snapshot that blends lab and field data in one report.

PageSpeed Insights is the natural starting point for almost every performance audit. Paste in a URL and it returns two distinct data sets side by side: a Lighthouse-powered lab test (simulated, repeatable, great for diagnosing why something is slow) and, where available, real Chrome User Experience Report (CrUX) field data pulled from actual Chrome users who visited that page or origin over the past 28 days. It scores each Core Web Vital individually and lists specific, prioritized opportunities — like "reduce unused JavaScript" or "serve images in next-gen formats" — with the estimated time savings for each fix.

The catch: PSI only shows field data if your page or domain gets enough Chrome traffic to be included in CrUX. Low-traffic pages will only show the lab score, which won't always match what real visitors experience.

2. Google Search Console — Core Web Vitals Report

Best for: Free, site-wide monitoring of real-user data across every indexed URL.

Where PageSpeed Insights checks one URL at a time, Search Console's Core Web Vitals report aggregates CrUX field data across your entire site and groups pages by URL pattern (e.g., all product pages, all blog posts) so you can spot systemic issues rather than one-off outliers. It flags pages as "Poor," "Needs Improvement," or "Good," and lets you request validation once you've shipped a fix — Google will re-crawl affected URLs and confirm whether the issue is actually resolved. It's the closest thing to a free real-user monitoring (RUM) dashboard that Google offers directly, and it's essential if you're managing more than a handful of pages. Pair it with our own Website SEO Score Checker for a fuller technical health check alongside your Vitals data.

3. Chrome DevTools (Lighthouse + Performance Panel)

Best for: Developers debugging exactly what is causing a slow LCP or layout shift, right in the browser.

Every Chrome install ships with two built-in performance tools. The Lighthouse panel runs the same audit as PageSpeed Insights, but locally, with no rate limits — useful when you're iterating on a fix and want instant feedback. The Performance panel goes deeper: it records a full timeline of the page load, showing exactly which script, font, or image caused a layout shift or delayed the largest contentful paint, down to the millisecond and the line of code. There's also a dedicated Web Vitals overlay you can enable via the Lighthouse or Performance Insights panel that shows LCP, INP, and CLS live as you interact with the page, which is invaluable for catching interaction-related INP problems that only show up when you actually click something.

4. WebPageTest

Best for: Deep, multi-location, multi-device lab testing with a filmstrip and waterfall view.

WebPageTest has been the go-to advanced testing tool for performance engineers for over a decade, and it's still unmatched for granular control. You can test from more than 40 real-world locations, on real device profiles, over throttled 3G or 4G connections, and get back a full waterfall chart, a frame-by-frame filmstrip of the page loading, and a video comparison against a previous test run. It supports scripting for logged-in states, multi-step user journeys, and custom metrics — features that make it the tool of choice when a single PageSpeed Insights number isn't enough to explain a performance regression.

5. GTmetrix

Best for: A friendlier, visual alternative to WebPageTest with historical trend tracking.

GTmetrix wraps Lighthouse-based testing in a more approachable interface, complete with a letter grade, waterfall charts, and a video playback of the page load. Its free plan lets you test from a handful of server locations and browsers; paid plans add scheduled monitoring, alerts when a page's score drops below a threshold, and the ability to compare historical test runs side by side — handy for proving a redesign or migration didn't quietly tank your Core Web Vitals.

6. Pingdom Tools (SolarWinds)

Best for: Quick, simple speed checks for teams that want uptime and speed monitoring in one place.

Pingdom's website speed test is a lab-only tool, but it's fast, free for a single test, and pairs naturally with Pingdom's broader uptime and synthetic monitoring suite if you're already using SolarWinds products. It grades your page, shows a waterfall of every request, and lists the biggest opportunities for improvement in plain language — a good fit for marketing teams who need a readable report without a developer translating it for them.

7. DebugBear

Best for: Continuous Core Web Vitals monitoring with CI/CD integration and detailed regression alerts.

DebugBear is purpose-built around Core Web Vitals rather than general page speed. It runs scheduled lab tests, pulls in CrUX field data automatically, and — critically — lets you set alerts that fire the moment a specific metric on a specific page regresses, so you catch problems before they show up in Search Console weeks later. It also integrates directly into GitHub Actions and other CI pipelines, letting you block a deploy if a pull request pushes LCP or CLS past your threshold. For agencies managing Core Web Vitals across dozens of client sites, this kind of automated regression tracking saves hours of manual re-checking.

8. SpeedCurve

Best for: Enterprise-grade performance monitoring that ties Core Web Vitals directly to business metrics.

SpeedCurve combines synthetic (lab) monitoring with real user monitoring and layers in custom business metrics — conversion rate, bounce rate, revenue per session — so you can show stakeholders exactly how a 200-millisecond INP improvement affected checkout completions, not just a technical score. Its dashboards are built for continuous, always-on monitoring rather than one-off checks, which makes it a natural fit for larger e-commerce and SaaS teams where performance work needs to be justified against real business outcomes.

9. Calibre

Best for: Automated performance budgets and Slack/email alerts tied to Core Web Vitals thresholds.

Calibre runs scheduled Lighthouse-based tests against your key pages and lets you set hard performance budgets — for example, "LCP must stay under 2.5s" — that trigger an alert the moment a page crosses the line. It's particularly strong for teams that want performance regressions treated with the same urgency as a broken build, and its reports are readable enough to share with non-technical stakeholders without extra formatting work.

10. Chrome UX Report (CrUX) Dashboard

Best for: Free, historical field-data trends without running a single manual test.

The CrUX Dashboard (built on Looker Studio) visualizes the same real-user data that powers PageSpeed Insights and Search Console, but lets you track trends over months, compare multiple origins side by side, and segment by device type or connection speed. Because it's pulling straight from Google's public dataset, there's zero setup cost — just plug in your domain. It's less about diagnosing why a metric is poor and more about tracking whether your fixes are actually moving the needle at the population level.

11. web-vitals JavaScript Library

Best for: Developers who want to capture real-user Core Web Vitals data directly from their own site's visitors.

Maintained by the Chrome team, the web-vitals npm package is a tiny script you drop into your site to measure LCP, INP, and CLS as your actual visitors experience them, then send that data to your analytics platform of choice (Google Analytics 4, a custom endpoint, or a RUM tool). It's the foundation that most third-party RUM tools build on top of, and if you want full control over how field data is collected and segmented, this is the most direct route. It requires a bit of front-end implementation work, which is the trade-off for having your own first-party dataset instead of relying on aggregate CrUX numbers.

12. Treo

Best for: Dedicated Real User Monitoring with SERP-position correlation.

Treo focuses specifically on Core Web Vitals RUM and layers in a feature most competitors skip: correlating your Vitals scores against your actual search rankings over time, so you can see whether a performance improvement lined up with a ranking gain. It supports budgets, Slack alerts, and public status pages you can share with clients — a nice touch for agencies who need to demonstrate ongoing performance work.

13. Rigor (by SolarWinds)

Best for: Combined synthetic monitoring and RUM with a strong focus on e-commerce transaction paths.

Rigor tests full user journeys — not just a homepage load — which matters because Core Web Vitals problems often hide two or three clicks into a checkout or signup flow rather than on the landing page itself. It's built for teams that need to monitor performance across an entire conversion funnel, not just isolated URLs.

14. Screaming Frog SEO Spider

Best for: Crawling an entire site and pulling PageSpeed/Lighthouse data at scale.

Screaming Frog isn't a Core Web Vitals tool by itself, but its PageSpeed Insights integration lets you crawl thousands of URLs and pull back LCP, INP, CLS, and Lighthouse opportunity data for every single one in a spreadsheet-friendly export. For technical SEO audits where you need to find which templates or page types are dragging down site-wide Vitals — not just check one URL — this bulk approach is far faster than testing pages one at a time. Before a full crawl, it's worth running your XML Sitemap Generator to make sure every URL you care about is actually being fed into the crawl and the sitemap Google sees.

15. Sitebulb

Best for: Visual, audit-style reporting on Core Web Vitals alongside broader technical SEO issues.

Sitebulb crawls your site like Screaming Frog but presents findings in a more visual, client-friendly report format, with Core Web Vitals data integrated alongside crawl depth, internal linking, and indexability issues. It's a strong pick for agencies producing audit deliverables where Core Web Vitals need to sit next to — and be prioritized against — other technical SEO fixes rather than presented as a standalone score.

16. Ahrefs Site Audit

Best for: Teams already using Ahrefs who want Core Web Vitals folded into their regular technical SEO crawls.

Ahrefs' Site Audit tool crawls your site on a schedule and reports Core Web Vitals metrics as part of its broader health-score system, flagging pages with poor LCP or CLS alongside issues like broken links, redirect chains, and thin content. Because it's already part of many SEO teams' existing toolkit, it removes the need for a separate standalone Vitals tool for routine monitoring — though for deep diagnostic work, you'll still want to pair it with a dedicated lab tool like WebPageTest.

17. SEMrush Site Audit

Best for: Combining Core Web Vitals thresholds with SEMrush's wider SEO and content tooling.

Similar to Ahrefs, SEMrush's Site Audit module reports on Core Web Vitals as part of its crawl, and lets you set custom thresholds so pages breaching "Good" scores get flagged automatically in future audits. If your team is already using SEMrush for keyword tracking and competitor research, this keeps performance monitoring inside the same dashboard your stakeholders already check.

18. Cloudflare Observatory

Best for: Free Core Web Vitals reporting for any site sitting behind Cloudflare, with built-in fix suggestions.

Cloudflare Observatory (accessible from the Speed tab in any Cloudflare dashboard) runs Lighthouse tests on a schedule and displays trend charts for LCP, INP, and CLS over time, alongside one-click recommendations — like enabling Cloudflare's Polish image optimization or Rocket Loader — that map directly to features already available in your Cloudflare plan. If you're already using Cloudflare for DNS or CDN, this is essentially a free, zero-setup monitoring layer.

19. PageSpeed API (for Custom Dashboards)

Best for: Teams building their own internal Core Web Vitals dashboard at scale.

The PageSpeed Insights API is the same engine behind the public PSI tool, but callable programmatically — meaning you can script it to test hundreds of URLs on a schedule and pipe the results into your own dashboard, spreadsheet, or Slack alert system. It's the go-to option for larger organizations that want Core Web Vitals data integrated into an existing internal reporting tool rather than checking a third-party dashboard separately. It pairs well with a scheduled Website Screenshot Generator run so you have a visual record of what each page actually looked like at the time of each test.

How to Choose the Right Tool (or Combination)

No single tool on this list does everything, and that's by design — lab and field data answer different questions.

• If you only have time for one free check before publishing: use Google PageSpeed Insights.
• If you manage a whole site and want to know which URL groups are struggling: use Google Search Console's Core Web Vitals report.
• If you need to debug exactly what's causing a slow LCP: use Chrome DevTools or WebPageTest.
• If you need ongoing monitoring with alerts before a regression tanks your rankings: use DebugBear, Calibre, or SpeedCurve.
• If you're auditing an entire site's technical SEO, not just speed: use Screaming Frog, Sitebulb, Ahrefs, or SEMrush.

Most experienced SEO and dev teams end up running a two- or three-tool stack: one for quick manual checks, one for continuous monitoring, and one for site-wide crawling. Once your Core Web Vitals are healthy, don't stop there — run a full Website SEO Score Checker audit to make sure your on-page and technical SEO are pulling their weight too, check your Mobile-Friendly Test since mobile INP and LCP are usually worse than desktop, and confirm your Meta Tag Analyzer output is clean so a fast page still earns the click in the first place.

Common Core Web Vitals Fixes Worth Knowing

Testing tools only tell you what's wrong — here's what usually causes each metric to fail, and what tends to fix it:

• Poor LCP is most often caused by a slow server response (check with our Check Gzip Compression tool and confirm caching headers via Get HTTP Headers), unoptimized hero images, or render-blocking CSS/JS. Compressing images with our Image Compressor and minifying assets with the CSS Minifier and JavaScript Minifier typically moves the needle fastest.
• Poor INP usually traces back to heavy, unoptimized JavaScript blocking the main thread during user interaction — third-party scripts, chat widgets, and ad tags are frequent culprits.
• Poor CLS is almost always missing width/height attributes on images and embeds, web fonts causing text reflow, or ads/banners injected without reserved space.

Frequently Asked Questions

1. What's the difference between lab data and field data in Core Web Vitals tools? 

Lab data is collected in a controlled, simulated environment (like Lighthouse running on a fixed connection speed) and is fully reproducible, making it ideal for debugging. Field data comes from real visitors on real devices and networks over a rolling 28-day window and reflects what users actually experience, but it can't tell you why a metric is poor the way lab data can. You need both for a complete picture.

2. Which Core Web Vitals testing tool does Google actually use for ranking?

 Google uses its own Chrome UX Report (CrUX) field data — the same dataset that powers PageSpeed Insights' field data panel and the Search Console Core Web Vitals report — as the ranking signal. Lab-only tools like GTmetrix or WebPageTest are diagnostic aids; they don't directly feed the ranking algorithm, though improving your lab scores generally improves your real-world field scores too.

3. Is Google PageSpeed Insights enough on its own? 

For a quick check on a single page, yes — it covers both lab and field data. But it doesn't monitor continuously, doesn't alert you to regressions, and won't show trends over time, which is why most serious performance workflows pair it with a monitoring tool like DebugBear, SpeedCurve, or Search Console.

4. What replaced First Input Delay (FID) as a Core Web Vital?

 Interaction to Next Paint (INP) officially replaced FID as the responsiveness metric in Google's Core Web Vitals in March 2024. INP measures responsiveness across the entire page visit rather than just the first interaction, giving a more complete picture of how a page performs as users keep interacting with it.

5. How often should I test my Core Web Vitals?

 For actively developed sites, continuous monitoring (via a tool like DebugBear or Calibre with CI/CD integration) is ideal so regressions are caught before they ship. For smaller or static sites, a monthly manual check with PageSpeed Insights and a quarterly Search Console review is usually sufficient.

6. Can a fast Lighthouse score still fail Core Web Vitals in Search Console?

 Yes, and this is one of the most common points of confusion. Lighthouse in PageSpeed Insights and Chrome DevTools produces a lab score on a simulated, throttled connection. Search Console reports field data from real users, who may be on slower networks, older devices, or connections your lab test doesn't replicate — so a page can score well in Lighthouse but still show as "Poor" in Search Console.

7. Do Core Web Vitals matter for mobile and desktop separately? 

Yes. Google evaluates Core Web Vitals separately for mobile and desktop experiences, and since mobile-first indexing means Google primarily uses your mobile version for ranking, mobile Core Web Vitals typically carry more weight. Always check both when testing, and use a tool like our Mobile-Friendly Test alongside your Vitals checks.

8. What's a good free tool stack if I can't afford paid monitoring software?

 Google PageSpeed Insights for spot checks, Google Search Console for site-wide field data monitoring, Chrome DevTools for debugging, and the free tier of GTmetrix or the CrUX Dashboard for historical trends — together these cover most of what a paid monitoring platform offers, just with more manual effort.

9. Do third-party scripts (ads, chat widgets, analytics) really affect Core Web Vitals that much? 

Frequently, yes — especially for INP and CLS. Third-party scripts run on the same main thread as your own code and often inject content without reserved space, which is why many teams find that removing or lazy-loading a single unnecessary widget improves Vitals scores more than any code optimization on their own pages.

10. How long does it take for a Core Web Vitals fix to show up in Search Console?

 Because Search Console's report is based on a rolling 28-day window of CrUX field data, it typically takes several weeks after deploying a fix before the report fully reflects the improvement, even though the change is live immediately. Lab tools like PageSpeed Insights or WebPageTest will show the improvement instantly, since they test in real time rather than aggregating historical visits.