The 3 Core Web Vitals That Decide Your Rankings
Core Web Vitals (CWV) are the 3 indicators Google uses to measure the technical user experience of your site. They have been officially integrated into ranking factors since June 2021 and reinforced in March 2024 with the replacement of FID by INP. Source: Google Search Central — Core Web Vitals.
The 3 metrics measure 3 concrete things your visitor actually feels:
- LCP — Largest Contentful Paint. How long before the main element of your page (hero image, main heading) appears? Visitor feeling: "Is it loading?"
- INP — Interaction to Next Paint. How long between a user click or tap and the first visible page reaction? Feeling: "Does the button respond, yes or no?"
- CLS — Cumulative Layout Shift. How much do your elements move during loading? A high CLS is the experience of "I click a link, but it shifts at the last moment and I open something else."
Google's 2026 Thresholds (and Why 2.5s Is Not a Marketing Goal)
Google defines 3 tiers: Good (green), Needs Improvement (orange), Poor (red). These are not recommendations: they are the exact thresholds used by the ranking algorithm.
| Metric | Good (green) | Needs Improvement (orange) | Poor (red) |
|---|---|---|---|
| LCP | ≤ 2.5s | 2.5 – 4.0s | > 4.0s |
| INP | ≤ 200ms | 200 – 500ms | > 500ms |
| CLS | ≤ 0.1 | 0.1 – 0.25 | > 0.25 |
Sources: Google — web.dev/vitals · Chrome for Developers
Important: Google uses measurements on real users (Chrome UX Report), not lab tests. Your own computer on gigabit fibre doesn't reflect the experience of your client on 4G in rural Ontario.
According to Deloitte — Milliseconds Make Millions, a 0.1s improvement in LCP increases conversions by an average of 8% in e-commerce and 10% in lead-gen time-on-page. This is not a technical detail — it's a revenue lever.
How to Test Your Site in 2 Minutes (PageSpeed Insights)
You don't need any paid tools to diagnose your Core Web Vitals. Procedure in 4 steps:
- Go to pagespeed.web.dev.
- Paste your homepage URL. Click "Analyze".
- Wait 30–60 seconds.
- Read the 3 numbers in the "Discover what your real users are experiencing" section.
You'll see a mobile card and a desktop card. Focus on mobile: most Canadian web traffic comes from mobile, and Google has used mobile-first indexing since 2020. If your 3 numbers are green on mobile, your site passes the CWV test. If even one is red or orange, you have work to do. Second useful test: run it on your conversion page (contact, audit, quote) — that's often the slowest one.
Diagnosing takes 2 minutes. Prioritizing fixes takes 30 minutes. Applying the fixes takes 2–40 hours depending on technical debt. Want a second opinion?
See Our SEO Services →The 5 Most Common Causes of Slowness on SMB Sites
1. Unoptimized Images
JPG files at 2MB delivered uncompressed, not resized for actual display, loaded above the fold without a fetchpriority attribute. Impact: LCP easily drifts to 4–6s. Fix: Squoosh or TinyPNG, WebP conversion, proper resizing. Cost: $0.
2. Invasive Third-Party Scripts
Facebook Messenger chat, Facebook pixel, Google Analytics, Hotjar, SEO trackers, exit-intent popup plugins. Each third-party script is a black box that can block rendering. According to the HTTP Archive — Web Almanac 2024, third-party scripts represent a median of 45% of a page's loading time. Fix: audit scripts, remove unused ones, add async/defer to non-critical ones.
3. Budget Shared Hosting
A $4/month hosting shared with hundreds of other sites produces a TTFB (time to first byte) of 1–2 seconds, which undermines everything else. Fix: upgrade to VPS or managed hosting (Kinsta, WP Engine, Pressable, Cloudways) starting at $30/month.
4. Heavy Theme or Page Builder
Pagebuilder themes with all options activated can generate several MB of CSS and JS per page. A lightweight theme (GeneratePress, Kadence, Astra) stays well below that. Fix: theme change — a significant project, plan accordingly.
5. Layout Shifts During Loading
Banners, images without fixed dimensions, web fonts loaded late. Impact: high CLS. Fix: declare width and height on all images, preload critical fonts with rel="preload".
The 30-Day Fix Plan
Week 1 — Owner (2 hours)
- Test the homepage and 5 most-visited pages in PageSpeed Insights.
- Note the 3 numbers per page in a simple table.
- Identify which of the 5 causes (images, scripts, hosting, theme, CLS) is the main culprit.
Week 2 — Delegated (developer or agency, 8–12 hours)
- Compress and convert to WebP all images over 200KB.
- Audit third-party scripts, remove those with no real use.
- Add
async/deferto non-critical scripts.
Week 3 — Delegated (4–8 hours)
- Review hosting. If TTFB > 800ms consistently, plan migration.
- Add
width/heightdimensions to all images. - Preload critical fonts.
Week 4 — Owner (1 hour)
- Re-run PageSpeed Insights on the same pages.
- Validate gains. Check impressions and CTR in Search Console.
Typical budget: $800 to $3,500 for a 20–100 page SMB site depending on technical debt. If you're quoted $8,000 or more without being shown your current 3 numbers first, ask for a second quote.
A fast site ranks higher, converts better, and retains visitors. Don't let a slow load time undo months of SEO work.
Get My Free Audit →FAQ — Website Speed for SMBs
Core Web Vitals are 3 Google measurements that evaluate the technical user experience of a web page: LCP (time before main content appears), INP (reaction time after a click), CLS (visual stability during loading). Since 2021 they are an official Google ranking factor, measured on real users via Chrome.
Each PageSpeed Insights test performs a new lab measurement with its own simulated network and CPU context. Variations of 5–15% are normal. What matters to Google is the Field data (CrUX), measured over a rolling 28-day period on your real users — not the lab measurement from a single isolated test.
No. The score out of 100 is a composite grade that includes other metrics (First Contentful Paint, Speed Index, Total Blocking Time). Core Web Vitals are the 3 specific metrics used by Google for ranking: LCP, INP, CLS. A score of 85/100 can coexist with a red LCP.
3.2s is rated "Needs Improvement" by Google (2.5–4s range). It's not "red/poor" but it's below the "Good" threshold (≤2.5s). The impact is a measurable potential loss of organic traffic. Medium priority: fix within 60 days, not within 24 hours.
Yes, with 4 choices: a lightweight theme (GeneratePress, Kadence, Astra), quality hosting (Kinsta, WP Engine, Pressable), a well-configured cache plugin (WP Rocket, LiteSpeed Cache), and WebP-optimized images. These 4 levers combined can achieve an LCP of 1.5–2.2s.
Yes, if your TTFB consistently exceeds 800ms on PageSpeed. Budget shared hosting is structurally incompatible with good Core Web Vitals. Recommended alternatives: Kinsta, WP Engine, Pressable, Cloudways. Budget: $30–100/month depending on traffic.
They're necessary but not sufficient. A good cache plugin addresses a significant portion of WordPress speed issues: cached HTML, GZIP compression, lazy loading. But it can't compensate for a heavy theme, slow hosting, or uncompressed images.
Yes if your audience is spread out (across Canada or internationally). A CDN (Cloudflare, BunnyCDN) serves your static files from servers close to your visitors, reducing TTFB. For a purely local SMB, the impact is smaller, but Cloudflare offers a sufficient free plan.
Yes, significantly. A YouTube iframe loads a large amount of JavaScript even without playback. Solution: use a lite embed (WP Feather plugin, lite-youtube-embed), which shows the thumbnail and only loads YouTube on click. The LCP gain is measurable.
Ideally fewer than 5 total (Google Analytics + 1–2 business tools are enough for most SMBs). Each third-party script adds loading time. Beyond 8 scripts, the site becomes structurally slow. Remove trackers that haven't been used in 6 months.
According to Deloitte Milliseconds Make Millions, a 0.1s improvement increases conversions by an average of 8% in e-commerce and 10% in lead-gen. Going from 4s to 2s represents a significant business performance gain.
Mobile, absolutely. Google has used mobile-first indexing since 2020: your mobile version is what's used for ranking. A slow mobile page penalizes even desktop visitors in Google search results.