Core Web Vitals • 9 min read

Core Web Vitals: Field Data vs Lab Data Explained

Understand the difference between field data and lab data for Core Web Vitals. Learn why they differ, which one Google uses for rankings, and how to use both.

By Rankture Team
Core Web Vitals: Field Data vs Lab Data Explained

You run your site through Lighthouse and score 95. Then you check Search Console and see “Core Web Vitals: Failed.” What gives?

The answer lies in the difference between lab data and field data—and understanding which one actually matters for SEO.

The Short Answer

If your lab scores are great but field data is poor, your rankings can still be affected.

What Is Lab Data?

Lab data comes from controlled, simulated tests. A tool runs your page through a standardized environment:

Characteristics

Common Lab Tools

What Lab Data Measures

Lab Data Is Great For

Lab Data Is Bad For

What Is Field Data?

Field data comes from real users visiting your site. Chrome collects anonymized performance data from users who have opted in.

Characteristics

Where Field Data Comes From

What Field Data Measures

Field Data Is Great For

Field Data Is Bad For

Why Lab and Field Data Differ

It’s common to have great lab scores and poor field scores—or vice versa. Here’s why:

1. Device Differences

Lab: Tests on a simulated Moto G4 (mid-tier from 2016) or similar.

Field: Your actual users might be on:

2. Network Differences

Lab: Simulated “Fast 4G” (1.6 Mbps down, 150ms RTT).

Field: Real users on:

3. Third-Party Script Behavior

Many third-party scripts detect “bot” traffic and load lighter versions:

Lab: Bots often get minimal ads, no personalization, cached responses.

Field: Real users get:

4. Caching Differences

Lab: Often tests with a “cold cache” (first visit).

Field: Mix of:

5. Interaction Patterns

Lab: TBT measures potential blocking time during load.

Field: INP measures actual interaction responsiveness, which depends on:

Which One Does Google Use?

Google uses field data (CrUX) for ranking decisions.

The Core Web Vitals assessment in Search Console is based on:

Your Lighthouse score doesn’t directly affect rankings. Only the CrUX-based assessment does.

How to Use Both Effectively

Lab and field data serve different purposes. Use them together:

Use Lab Data For:

1. Debugging specific issues When you know LCP is bad, use Lighthouse to identify:

2. Testing before deployment Before pushing changes:

3. Competitive benchmarking Compare your lab scores to competitors:

Use Field Data For:

1. Understanding your actual CWV status This is what Google sees. Check:

2. Identifying real-world problems Field data reveals issues lab misses:

3. Tracking progress over time Field data shows if your optimizations are actually helping real users—not just passing lab tests.

When Field Data Isn’t Available

Low-traffic pages may not have field data in CrUX. In this case:

What Google Does

What You Should Do

  1. Use lab data as a proxy — it’s better than nothing
  2. Implement Real User Monitoring (RUM) — get your own field data
  3. Focus on high-traffic pages first — they have data and matter most

RUM Options

// Basic RUM with web-vitals library
import { onLCP, onINP, onCLS } from 'web-vitals';

function sendToAnalytics({ name, value, id }) {
  // Send to your analytics endpoint
  navigator.sendBeacon('/analytics', JSON.stringify({ name, value, id }));
}

onLCP(sendToAnalytics);
onINP(sendToAnalytics);
onCLS(sendToAnalytics);

Common Scenarios

Scenario 1: Great Lab, Poor Field

Symptoms: Lighthouse 90+, but Search Console shows CWV failing.

Likely causes:

Fix: Profile with real user data, audit third-party scripts, test on slower devices.

Scenario 2: Poor Lab, Good Field

Symptoms: Lighthouse 60, but Search Console shows CWV passing.

Likely causes:

Action: You’re fine for rankings, but lab issues might still affect first-time visitors.

Scenario 3: Both Poor

Symptoms: Everything is red.

Action: Start with lab data to identify and fix fundamental issues. Field data will improve as optimizations reach real users (expect 2-4 week delay).

Scenario 4: Both Good

Symptoms: Everything is green.

Action: Maintain your setup, monitor for regressions, and focus on other SEO factors.

Key Takeaways

  1. Lab data is for debugging; field data is what Google uses
  2. They measure similar things but in very different conditions
  3. It’s normal for them to disagree—understand why
  4. Always prioritize field data for ranking concerns
  5. Use lab data to find and fix issues, field data to verify the fix worked
  6. Low-traffic pages may need RUM for accurate field measurement

Frequently Asked Questions

Why does my Lighthouse score change every time?

Lab tests have some variance due to network simulation, server response variability, and browser differences. A ±5 point fluctuation is normal. Focus on trends, not single tests.

How often does field data update?

CrUX data is collected continuously but aggregated monthly. However, PageSpeed Insights and Search Console may show more recent data as it becomes available. Expect 2-4 weeks to see changes reflected.

Can I improve field data without changing my site?

If your field data is poor but lab is good, the issue is likely third-party scripts, user device/network mix, or real-world conditions. You’ll need to optimize for those scenarios—there’s no shortcut.

What’s the 75th percentile threshold?

Google requires 75% of page views to meet the “Good” threshold. This means the slowest 25% of your users can have a bad experience and you’ll still pass—but if more than 25% have issues, you fail.

Next Steps

Check your current field data status and identify what needs fixing:

Tags:

core web vitals field data lab data page speed crux

Share this article:

Share on X Share on LinkedIn

Ready to improve your SEO?

Get a free SEO audit and see exactly what needs fixing on your site

Start Free Audit