How to Check Core Web Vitals: 6 Free Tools & Methods (2025)

Knowing how to check your Core Web Vitals is essential for maintaining good SEO performance. Google uses these metrics as ranking factors, and poor scores can hold back your organic traffic.

In this guide, I’ll walk you through 6 different ways to check Core Web Vitals—from quick spot-checks to deep debugging—so you can find issues and fix them fast.

Quick Answer: The Easiest Ways to Check Core Web Vitals

Tool	Best For	Data Type	Time Needed
Google Search Console	Site-wide overview	Field (real users)	2 minutes
PageSpeed Insights	Single URL check	Both	1 minute
Rankture	SEO-focused audit	Lab	2 minutes
Chrome DevTools	Debugging issues	Lab	5+ minutes
Web Vitals Extension	Quick spot-check	Lab	Instant
CrUX Dashboard	Historical trends	Field	5 minutes

---

1. Google Search Console (Best for Site-Wide Data)

Google Search Console provides the most authoritative Core Web Vitals data because it comes directly from Google’s ranking systems.

How to Check Core Web Vitals in Search Console

1. Go to Google Search Console
2. Select your property
3. Navigate to Experience → Core Web Vitals
4. Choose Mobile or Desktop report

What You’ll See

Search Console groups your URLs into three categories:

• Good ✅ - Meeting all Core Web Vitals thresholds
• Needs Improvement ⚠️ - Some metrics falling short
• Poor ❌ - Failing one or more metrics

You’ll also see which specific metric is causing issues:

• LCP issues (loading)
• INP issues (interactivity)
• CLS issues (visual stability)

Pros and Cons

Pros:

• Uses real user data (field data)
• Shows trends over time
• Groups similar pages together
• Free and authoritative

Cons:

• Requires site verification
• 28-day rolling average (slow to show changes)
• Needs sufficient traffic for data
• No single-page testing

Pro Tip

Click on any issue to see which URL groups are affected. Search Console groups similar pages together (like all blog posts or all product pages), making it easier to prioritize fixes.

---

2. PageSpeed Insights (Best for Single URLs)

PageSpeed Insights is the quickest way to check Core Web Vitals for any specific URL.

How to Use PageSpeed Insights

1. Go to pagespeed.web.dev
2. Enter your URL
3. Click Analyze
4. Wait 10-30 seconds for results

Understanding the Results

PageSpeed Insights shows two types of data:

Field Data (What Real Users Experience)

• Pulled from the Chrome User Experience Report (CrUX)
• Shows actual LCP, INP, CLS scores from real visitors
• Only available for pages with enough traffic
• This is what Google uses for rankings

Lab Data (Simulated Test)

• Generated by Lighthouse in a controlled environment
• Available for any URL
• Useful for debugging and testing changes
• May differ from real-world performance

Reading the Scores

For each Core Web Vital, you’ll see:

• The actual metric value (e.g., “2.1s” for LCP)
• A color indicator (green/amber/red)
• The percentile of your score (e.g., “75th percentile”)

Pros and Cons

Pros:

• Test any URL instantly
• Shows both field and lab data
• Detailed diagnostic information
• Free and easy to use

Cons:

• Only tests one URL at a time
• Lab data may not reflect real conditions
• Can’t track historical data
• No batch testing

---

3. Rankture Free SEO Audit (Best for SEO Context)

Our free SEO audit tool checks Core Web Vitals as part of a comprehensive SEO analysis.

Why Use Rankture for Core Web Vitals

Unlike tools that only measure performance, Rankture puts Core Web Vitals in SEO context:

• Mobile-first testing - Tests mobile performance by default (what Google prioritizes)
• SEO scoring - See how Core Web Vitals impact your overall SEO health
• 20+ other checks - Meta tags, content quality, technical SEO, and more
• Actionable recommendations - Know exactly what to fix first

How to Check Core Web Vitals with Rankture

1. Go to rankture.com/free-seo-audit
2. Enter your website URL
3. Get your full report in under 60 seconds
4. Review Core Web Vitals in the Technical SEO section

What Makes It Different

While other tools give you raw metrics, Rankture prioritizes findings by SEO impact. If your LCP is slightly slow but your title tags are missing, we’ll tell you to fix the title tags first—because that’s the bigger SEO issue.

---

4. Chrome DevTools (Best for Debugging)

Chrome DevTools is the most powerful option for debugging specific Core Web Vitals issues.

How to Access Core Web Vitals in DevTools

1. Open Chrome and navigate to your page
2. Press F12 (or Cmd+Option+I on Mac)
3. Go to the Performance tab
4. Click the Reload button (circular arrow) to record a page load

Finding LCP Issues

After recording:

1. Look for the LCP marker in the timeline
2. Hover over it to see which element was the LCP
3. Check the Summary tab for timing breakdown

Common findings:

• Large images loading late
• Slow server response (long TTFB)
• Render-blocking resources

Finding INP Issues

1. Go to the Performance tab
2. Interact with the page (click buttons, type in forms)
3. Stop recording
4. Look for long tasks (red-flagged) in the main thread
5. Click on tasks to see what JavaScript is causing delays

Finding CLS Issues

1. Enable “Core Web Vitals” in DevTools settings
2. Reload the page
3. Watch for red overlay boxes showing layout shifts
4. Check the Experience section in the Performance panel

Alternatively, use this console command:

new PerformanceObserver((list) => {
  for (const entry of list.getEntries()) {
    console.log('Layout Shift:', entry);
  }
}).observe({ type: 'layout-shift', buffered: true });

Pros and Cons

Pros:

• Most detailed debugging information
• Can simulate different devices/networks
• Identify specific elements causing issues
• Free and built into Chrome

Cons:

• Steep learning curve
• Only lab data
• Manual process
• Requires technical knowledge

---

5. Web Vitals Chrome Extension (Best for Quick Checks)

The Web Vitals extension shows Core Web Vitals data in real-time as you browse.

How to Use the Extension

1. Install from the Chrome Web Store
2. Click the extension icon in your toolbar
3. Visit any page
4. See live Core Web Vitals metrics in the popup

What You’ll See

The extension shows:

• LCP - Updates as the largest content paints
• INP - Updates as you interact with the page
• CLS - Updates as layout shifts occur

Color coding matches Google’s thresholds:

• 🟢 Green = Good
• 🟡 Amber = Needs Improvement
• 🔴 Red = Poor

Pros and Cons

Pros:

• Instant, real-time data
• No setup required
• Works on any website
• See metrics as you browse

Cons:

• Only shows your device’s performance
• No historical data
• Basic information only
• Lab data only

---

6. CrUX Dashboard (Best for Historical Trends)

The Chrome User Experience Report (CrUX) Dashboard shows historical Core Web Vitals data from real users.

How to Access the CrUX Dashboard

1. Go to CrUX Dashboard
2. Click “Access the Dashboard”
3. Enter your website’s origin (e.g., https://example.com)
4. View historical data and trends

What You’ll See

The dashboard shows:

• Monthly Core Web Vitals trends
• Distribution of good/needs improvement/poor experiences
• Breakdown by device type (phone, tablet, desktop)
• Comparison to other origins

Pros and Cons

Pros:

• Historical trends over time
• Real user data (field data)
• Free Google Data Studio report
• Compare multiple origins

Cons:

• Only shows origin-level data (not individual pages)
• Monthly updates (not real-time)
• Requires sufficient traffic
• Limited to CrUX dataset

---

Field Data vs. Lab Data: Which Matters More?

When checking Core Web Vitals, you’ll encounter two types of data:

Field Data (Real User Monitoring)

What it is: Aggregated data from real Chrome users visiting your site.

Where to find it:

• Google Search Console
• PageSpeed Insights (top section)
• CrUX Dashboard

Why it matters: This is what Google actually uses for rankings. Field data reflects real-world conditions—various devices, network speeds, and user behaviors.

Lab Data (Synthetic Testing)

What it is: Simulated tests run in controlled environments.

Where to find it:

• PageSpeed Insights (Lighthouse section)
• Chrome DevTools
• Web Vitals extension

Why it matters: Lab data is instant and consistent, making it ideal for testing changes before pushing to production.

The Bottom Line

Use field data to understand your actual ranking impact and real user experience.

Use lab data for debugging issues and testing fixes before deployment.

If your field data and lab data differ significantly, it usually means:

• Your users have slower devices/connections than the lab simulation
• Third-party scripts behave differently in production
• User behavior (scrolling, clicking) triggers issues not caught in lab tests

---

How Often Should You Check Core Web Vitals?

Here’s a practical checking schedule:

Frequency	Tool	Purpose
Weekly	Search Console	Monitor site-wide trends
Before/after changes	PageSpeed Insights	Verify optimizations
During development	Chrome DevTools	Debug specific issues
Monthly	CrUX Dashboard	Track long-term trends
As needed	Rankture	Full SEO health check

---

Common Core Web Vitals Issues & Quick Fixes

LCP Issues (Loading)

Symptoms: “LCP issue: longer than 2.5s”

Quick fixes:

• Compress and convert images to WebP
• Add fetchpriority="high" to hero images
• Preload critical fonts
• Enable browser caching
• Use a CDN

INP Issues (Interactivity)

Symptoms: “INP issue: longer than 200ms”

Quick fixes:

• Break up long JavaScript tasks
• Defer non-critical scripts
• Reduce DOM size
• Use web workers for heavy computation
• Debounce input handlers

CLS Issues (Visual Stability)

Symptoms: “CLS issue: more than 0.1”

Quick fixes:

• Add width/height to all images
• Reserve space for ads/embeds
• Preload fonts with font-display: optional
• Don’t inject content above existing content
• Use CSS transforms instead of layout properties

---

FAQs About Checking Core Web Vitals

How long does it take for Core Web Vitals changes to show in Search Console?

Search Console uses a 28-day rolling average, so expect 2-4 weeks before seeing the full impact of your changes. However, you’ll start seeing gradual improvement as new data replaces old data in the average.

Why do my Core Web Vitals scores differ between tools?

Different tools use different testing methods:

• Field data tools show real user data (varies by actual visitors)
• Lab data tools simulate controlled conditions (consistent but may not reflect reality)
• Network conditions affect results (especially for LCP)
• Testing location matters (server distance affects response times)

Do I need to check Core Web Vitals for every page?

Focus on your most important pages first:

1. Homepage
2. Top landing pages (check in Analytics)
3. Key conversion pages
4. Template pages (fixing one fixes all pages using that template)

Search Console groups similar pages together, making it easier to identify patterns.

Can I check Core Web Vitals for competitor sites?

Yes! Use PageSpeed Insights or the Web Vitals extension on any public URL. This is useful for benchmarking your performance against competitors.

---

Start Checking Your Core Web Vitals Today

Now you know 6 different ways to check Core Web Vitals—from quick spot-checks to deep debugging sessions. The key is using the right tool for your situation:

• Site-wide monitoring: Google Search Console
• Single page testing: PageSpeed Insights
• SEO-focused analysis: Rankture
• Debugging issues: Chrome DevTools
• Quick spot-checks: Web Vitals extension
• Historical trends: CrUX Dashboard

Ready to check your Core Web Vitals right now? Run a free SEO audit to see your performance scores alongside 20+ other SEO factors. You’ll get actionable recommendations prioritized by impact, so you know exactly what to fix first.