On this page
Core Web Vitals are pass/fail for SEO. If you're red, you lose. Here's the 90-minute sequence of fixes we run on every SME site to get to green — in the order that matters most.
- 01CWV is a hard ranking factor — red scores destroy organic potential.
- 02The 3 metrics that matter: LCP (under 2.5s), CLS (under 0.1), INP (under 200ms).
- 0390% of CWV failures come from 3 root causes: images, web fonts, and blocking scripts.
- 04The 90-minute fix, in order: hero image, font loading, third-party scripts.
- 05Measure with real-user monitoring, not PageSpeed Insights alone.
Why Core Web Vitals are non-negotiable
Since 2021, Google has treated Core Web Vitals as a hard ranking signal for mobile search. It's not a tiebreaker — it's a gate. Sites with red CWV scores get systematically outranked by sites with green ones, even when the red site has better content.
For SMEs, this means the whole content and SEO strategy — everything in SEO that actually ranks — gets wasted if the technical foundation is red. The good news: 90% of CWV failures come from three specific root causes, and all three are fixable in under 90 minutes.
The 90-minute fix, in impact order
Fix the biggest thing first. On 80% of SME sites, that's the hero image — it's what Google measures as LCP. Serve it at the right dimensions, compress it aggressively, and add a preload link. LCP usually drops from 3.5s to 1.8s from this one change.
Fix number two is fonts. Most SME sites load 3–5 font weights from Google Fonts with default settings, which blocks render and causes layout shift. Switch to self-hosted, subset, with `font-display: swap` and you've killed both the render block and the CLS.
- 01 · Hero image (30 min) — right dimensions, compress, preload
- 02 · Fonts (20 min) — self-host, subset, font-display: swap
- 03 · Third-party scripts (25 min) — defer, lazy-load, remove what you can
- 04 · Layout stability (15 min) — explicit width/height on images, reserved space for ads
What to measure after the fix
Don't just re-run PageSpeed Insights and declare victory. Install real-user monitoring (web-vitals.js or Cloudflare RUM), let it collect 1,000+ sessions, and look at the 75th percentile scores. That's what Google actually uses for ranking.
If your p75 is under 2.5s LCP, under 0.1 CLS, and under 200ms INP, you're green across the board. Pair this with a proper 45-minute revenue audit and you've closed both the technical and behavioral loops at the same time.
Questions about this topic
01How much does bad Core Web Vitals hurt SEO rankings?
For commercial-intent keywords on mobile, a red CWV page can lose 10–30% of its ranking potential vs. an equivalent green page. Over 90 days, that compounds significantly. For informational keywords, the impact is smaller but still real.
02What tool should I use to measure Core Web Vitals?
Start with PageSpeed Insights for a quick baseline, but always confirm with real-user monitoring (web-vitals.js, Cloudflare RUM, or Chrome UX Report). The real-user data is what Google uses for ranking — not the simulated lab data.
03Do Core Web Vitals matter for desktop as well?
Yes, but less aggressively. Google's ranking impact is heavier on mobile, where most of your traffic is anyway. Fix mobile first, verify desktop comes along for the ride.
Writes about revenue systems, SME conversion, and the unglamorous ops work that compounds.