Start here
Before You Fix It: What This Check Means
Core Web Vitals are user-centric performance outcomes measured from real visitor sessions. In plain terms, this tells you whether users are likely to feel this page as fast, stable, and usable. Scavo queries CrUX p75 metrics for the scanned URL and form factor (with origin fallback when URL-level data is unavailable).
Why this matters in practice: degraded speed here often compounds into lower conversion and weaker user trust.
How to use this result: treat this as directional evidence, not final truth. A single scan cannot reproduce full real-user variance across devices, geographies, and session history. First, confirm the issue in live output: confirm trend direction in field data, not only synthetic runs Then ship one controlled change: **LCP**: reduce TTFB, optimize hero resource path, preload critical assets. Finally, re-scan the same URL to confirm the result improves.
Background sources
TL;DR: Your pages fail Google's Core Web Vitals metrics, which are confirmed ranking factors that directly affect search visibility.
Google officially confirmed on March 12, 2024 that Core Web Vitals are used as a ranking factor (Google Search Central). After the March 2024 core update, sites with poor CWV experienced 20-40% traffic drops while those that improved saw 15-30% gains (BrightVessel). Pages at position 1 are 10% more likely to pass CWV than pages at position 9 (BKND).
What Scavo checks (plain English)
Scavo queries CrUX p75 metrics for the scanned URL and form factor (with origin fallback when URL-level data is unavailable).
Metrics and thresholds in this check:
- LCP good at
<= 2500ms - INP good at
<= 200ms(preferred interaction metric) - FID fallback good at
<= 100mswhen INP unavailable - CLS good at
<= 0.1
How Scavo scores this check
Result behavior:
- Pass: all available metrics are within threshold
- Fail: one or more available metrics exceed threshold
- Info: no CrUX data or no usable metrics
In your scan report, this appears under What failed / What needs attention / What is working for core_web_vitals, followed by Recommended next steps and Technical evidence (for developers) when needed.
- Scan key:
core_web_vitals - Category:
PERFORMANCE
Why fixing this matters
Poor CWV often maps to real friction: slow hero rendering, delayed interactions, unstable layout shifts. That hurts conversion and trust before users read your value proposition.
Because this is field data, improvements can lag after deployment. You need both implementation fixes and trend monitoring discipline.
Common reasons this check fails
- Slow backend/TTFB affecting LCP.
- Heavy JS main-thread work hurting INP/FID.
- Late-loading media/ads/components causing CLS.
- Device/network mix skewing p75 on mobile.
If you are not technical
- Ask for one owner per failing metric (LCP, INP/FID, CLS).
- Prioritize fixes on highest-traffic templates.
- Use field trends over time, not single snapshots.
- Re-scan after releases and review monthly trend direction.
Technical handoff message
Copy and share this with your developer.
Scavo flagged Core Web Vitals (core_web_vitals). Please triage failing p75 metric(s) in CrUX (LCP/INP or FID/CLS), apply template-level fixes, and provide before/after field-data evidence.If you are technical
- LCP: reduce TTFB, optimize hero resource path, preload critical assets.
- INP/FID: reduce long tasks, defer non-critical JS, split bundles.
- CLS: reserve dimensions, stabilize dynamic inserts, avoid layout jumps.
- Validate by form factor and URL vs origin scope.
- Keep lab diagnostics paired with field metrics.
How to verify
- Confirm CrUX p75 values for targeted pages/templates.
- Segment by form factor (phone/desktop/tablet where relevant).
- Compare URL-level vs origin-level scope where fallback is used.
- Re-run Scavo and confirm metric failures reduce.
What this scan cannot confirm
- It does not replace route-level lab profiling for root-cause debugging.
- CrUX requires enough traffic; low-volume pages may stay data-sparse.
- Passing CWV does not guarantee perfect UX across all edge cases.
Owner checklist
- [ ] Assign metric owners for LCP, INP/FID, and CLS.
- [ ] Track p75 trends weekly, not only release day.
- [ ] Keep performance budgets in CI for critical templates.
- [ ] Recheck after major frontend or infrastructure changes.
FAQ
Why do we get info instead of pass/fail sometimes?
CrUX field data may be unavailable at URL level for low-traffic pages; this check then cannot score reliably.
Why can origin and URL results differ?
Origin scope aggregates multiple pages. URL scope is more precise but needs enough traffic.
Is INP always used?
This check uses INP when available and falls back to FID where needed.
How quickly do fixes appear?
Field metrics are rolling-window based, so expect a lag before full trend impact is visible.
Sources
- web.dev: Core Web Vitals
- Chrome UX Report API docs
- Google PageSpeed Insights
- Google Search Central: Page experience
Need a CWV triage plan that maps each failing metric to owners and release gates? Send support your top templates and current p75 metrics.
