Best Core Web Vitals Checker Tools for 2026
A score can look fine in a test and still feel slow on a real phone. The best Core Web Vitals checker for your site depends on whether you need a quick URL test, real-user data or a clear path from finding to fix. Here are five options, starting with HubSEO for site owners who want ranked findings and prompts for an AI coding agent.
Table of Contents
* HubSEO * PageSpeed Insights by Google: a quick live test for individual URLs * GTmetrix: performance monitoring with historical graphs * Core Web Vitals Test and Checker by SpeedVitals: a focused checker * Free Core Web Vitals Test by DebugBear: a free assessment option * Frequently asked questions * Conclusion
1\. HubSEO
HubSEO is a self-serve website audit tool for owners and developers who want to check a live site, act on ranked findings and verify changes after deployment. It checks live-site performance, SEO, AI readability and accessibility, then turns prioritised findings into scoped prompts for external AI coding agents.
!Screenshot of the HubSEO website
For Core Web Vitals work, the useful part is the loop. Run the check, see which issue ranks highest, then give the prompt to your coding agent. After the code goes live, rerun the same checks to see whether the finding remains. HubSEO doesn't make changes to your site. You or your developer review and deploy the suggested fix.
The free tier includes a full ranked check and the first fix prompt. Guests get one check every 30 days; a free registered account gets three checks a month. Free, no card needed. Nothing is installed on your site. If you want the wider audit scope, our free SEO audit report also covers crawlability, page signals and mobile and desktop Lighthouse lab metrics.
HubSEO is a fit if you use tools such as Cursor or Claude Code and want a prompt tied to evidence from your live site. A cleared audit flag is proof that the check no longer finds that issue. It isn't a promise of higher Google rankings, indexing or visibility in AI answers. For the workflow behind AI coding-agent audits, see our guide to using Claude Code and Cursor for SEO audits.
Choose HubSEO when the hand-off from measurement to a scoped coding task matters as much as the test itself. It also checks AI-crawler readiness, which helps surface access issues a speed-only report won't answer.
2\. PageSpeed Insights by Google: a quick live test for individual URLs
PageSpeed Insights by Google lets you run a live performance test on an individual URL. It suits a developer or site owner who needs a quick read on one page without installing software or setting up a monitoring process.
!Screenshot of the PageSpeed Insights by Google website
Paste in a page address and run a test. Check mobile and desktop separately, then compare the results with the page people use most, such as a product or pricing page. A single test can point to a page worth investigating, but it doesn't show whether a problem affects every page on your site.
Field data collected from real users through the Chrome User Experience Report is grouped by similar URLs and reported as Good, Needs improvement or Poor. The group status reflects its weakest metric, and a URL group needs enough data to appear.
That distinction matters. A live test is a snapshot under test conditions; CrUX field data reflects visits from real Chrome users over time. The two can differ. A page may perform well in a lab run but still have slow real visits on mobile, or the reverse. For more on how audit tools fit into a SaaS team's work, compare our website optimisation tools for SaaS companies.
Use PageSpeed Insights to test a specific URL, then use Search Console's report to look for patterns across URL groups when enough field data is available. It is a sound starting point for testing, but it won't turn a finding into a scoped fix prompt or provide the end-to-end workflow HubSEO is built around.
Key Takeaway: A one-page test answers “how did this URL perform now?” Field data helps answer “what do visitors experience over time?”
3\. GTmetrix: performance monitoring with historical graphs
GTmetrix is a monitoring option for teams that want historical performance graphs. It suits a site owner who needs to see how a site's performance changes over time, rather than relying on a single test result.
!Screenshot of the GTmetrix website
Historical graphs give you a way to check whether a change lines up with a shift in performance. For example, if a page slows after a release, the timeline can help you spot when the change began. That is useful context for a developer reviewing a deployment, though a graph alone doesn't tell you which code change caused the result.
Monitoring and a live check serve different jobs. A live check helps investigate a URL at a point in time. A monitoring layer helps you notice movement across time. When you work through a fix, keep a record of the page and the change, then compare the later result against that starting point.
Our SaaS SEO checklist includes checking key templates such as pricing and feature pages. That focus helps keep tracking tied to pages with a clear job, rather than filling a dashboard with every URL. GTmetrix is the better fit when historical graphs are the main need; HubSEO adds ranked findings and prompts for the fix-and-recheck hand-off.
Use a monitoring tool to spot a change, then investigate the affected page with a test that gives you enough detail to act. Don't treat a trend line as a diagnosis.
4\. Core Web Vitals Test and Checker by SpeedVitals: a focused checker
Core Web Vitals Test and Checker by SpeedVitals is a focused option for someone who wants to check Core Web Vitals without starting with a broader SEO audit. It may suit a developer who already has a process for diagnosing and fixing issues, and needs a dedicated checker as one part of that workflow.
!Screenshot of the Core Web Vitals Test and Checker by SpeedVitals website
Keep the question narrow when you use a focused checker: which page are you testing, and what result do you need to follow up? Start with an important URL, then compare the result with the experience you see on the device your customers use. A checker can help surface a performance concern; the next task is to find the cause in the page or its code.
Core Web Vitals are measures of loading, interaction and visual stability. Current guidance uses Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). Older articles may still mention First Input Delay (FID), but INP is the current interaction metric.
For a useful comparison, run the same URL on mobile and desktop. A desktop result won't tell you how the page feels on a phone. If the main content appears late, look at the largest content element. If a button responds slowly, investigate the work triggered by that interaction. If the page jumps while loading, look for content that changes size or arrives late.
A focused checker is a sensible choice if you can interpret the result and make the code change yourself. If you want the audit to rank findings and prepare a scoped prompt for an external coding agent, HubSEO is designed for that next step. Our separate AI crawler readiness checker comparison covers access checks beyond page speed.
5\. Free Core Web Vitals Test by DebugBear: a free assessment option
Free Core Web Vitals Test by DebugBear combines Google CrUX real-user data with an on-demand lab test. It suits teams that want to compare what visitors experience with a controlled test of a page.
!Screenshot of the Free Core Web Vitals Test by DebugBear website
Lab data and field data answer different questions. A lab test runs under set conditions and can help you investigate a page. CrUX field data comes from real Chrome users and reflects a wider mix of visits. DebugBear says its test includes both types of data, with a detailed metric breakdown and performance suggestions.
Its test results can show LCP subparts, which break the time to display the main page content into phases. That can help narrow down whether the delay sits in an earlier loading stage or later rendering work. The test also includes a filmstrip timeline of page loading, so you can see how content appears as the page renders.
What you need to decide| What DebugBear's test helps with| What to do next ---|---|--- Do field results match a fresh test?| Compare CrUX real-user data with lab results.| Check mobile and desktop separately. When does the main content appear?| Review LCP subparts and the loading filmstrip.| Investigate the slow phase before changing code. Is performance changing over time?| Historical CrUX trends can show how results move.| Compare the change with releases and page edits.
DebugBear also describes monitoring and notifications through Slack or email, alongside real-user monitoring. These are useful when you need to follow performance over time. Its free test is an assessment, while an ongoing monitoring setup is a separate consideration. For teams using AI coding agents, HubSEO adds a different step: a ranked live-site finding becomes a scoped prompt, then the same checks can be rerun after deployment.
Pro Tip: Keep a note of the URL, device and test date when you change a page. It makes later comparisons more useful than relying on memory.
Frequently asked questions
What are the three Core Web Vitals?
The three current Core Web Vitals are LCP, INP and CLS. LCP measures when the main content appears. INP measures how quickly a page responds to user interactions, such as a click or keypress. CLS measures unexpected movement in page content. Older articles may name FID, but INP is the current interaction metric.
What is a good Core Web Vitals score?
A good result meets the threshold for each metric: LCP is 2.5 seconds or less, INP is 200 milliseconds or less, and CLS is 0.1 or less. Results can be labelled Good, Needs improvement or Poor. Check the device type too, since mobile and desktop results can differ.
Do Core Web Vitals affect Google rankings?
Core Web Vitals are part of Google's page experience signals, but a passing result doesn't guarantee a ranking, indexing or traffic gain. Google also considers other signals and the needs of the search. Use the metrics to find and fix user experience problems, not as a promise of a search position.
Why can lab and real-user results differ?
Lab results come from a controlled test run, while field data comes from real Chrome users visiting your site. Visitors have different devices, networks and page conditions, so their experience can differ from one test run. Use lab data to investigate a page, then check field data to see how visitors experience it over time.
How often should I check Core Web Vitals?
Check after a meaningful page or code change, then keep an eye on key pages over time if your tool supports monitoring. Field data changes as new visits are recorded, so it won't reflect a deployment instantly. A repeatable check on the same URL and device gives you a clearer comparison than one isolated score.
Conclusion
For UK site owners who want an audit tied to an actionable coding task, start with HubSEO's free check. It includes the ranked findings and first fix prompt, with no card or site installation needed. Run a key URL, review the prompt before using it, deploy your change, then rerun the same check to see what changed.
