What are Google Core Web Vitals?
Google Core Web Vitals (CWV) are a specific set of three performance metrics that measure how a user experiences a webpage: how quickly it loads (LCP), how responsive it is to interactions (INP), and how visually stable it remains while loading (CLS). Because Google's primary goal is delivering a great experience to its searchers, they made passing these three metrics a confirmed organic ranking factor.
Why CWV Matters for South African Sites
In South Africa, where mobile networks can be inconsistent and data costs matter to users, CWV is critical for two reasons:
- SEO Impact: A site that passes CWV gets a slight ranking boost over competitors with identical content but failing scores. It acts as a tiebreaker.
- Conversion Impact: Amazon famously found that every 100ms of latency cost them 1% in sales. A slow, shifting, unresponsive site kills your conversion rate long before it hurts your SEO.
To review performance alongside broader technical issues, use our SEO Audit Tool.
The Three Core Metrics
Let's break down each metric without the developer jargon.
1. LCP (Largest Contentful Paint)
What it measures: Loading speed. Specifically, how long it takes for the largest piece of content on the screen (usually a hero image, a video, or a large block of text) to become fully visible.
The threshold: - Good (Pass): Under 2.5 seconds - Needs Improvement: 2.5 to 4.0 seconds - Poor (Fail): Over 4.0 seconds
Common causes of failure: - Huge, uncompressed images at the top of the page. - Slow server response times (cheap hosting). - Render-blocking resources (massive CSS or JavaScript files that must load before the image can appear).
2. INP (Interaction to Next Paint)
Note: INP replaced FID (First Input Delay) in March 2024.
What it measures: Responsiveness. When a user clicks a button, taps a link, or opens a menu, how long does it take for the page to visually acknowledge that interaction?
The threshold: - Good (Pass): Under 200 milliseconds - Needs Improvement: 200 to 500 milliseconds - Poor (Fail): Over 500 milliseconds
Common causes of failure: - Heavy JavaScript execution freezing the browser's main thread. - Too many third-party scripts (analytics, chat widgets, marketing pixels) firing simultaneously. - Complex animations that the device struggles to render.
3. CLS (Cumulative Layout Shift)
What it measures: Visual stability. Have you ever gone to click a link on your phone, and right before your finger touches the screen, an ad loads, the whole page jumps down, and you click the wrong thing? That is a layout shift. CLS measures how much the page physically moves around while rendering.
The threshold: - Good (Pass): Under 0.1 - Needs Improvement: 0.1 to 0.25 - Poor (Fail): Over 0.25
Common causes of failure: - Images or videos without specified width and height dimensions in the code. - Ads or embeds resizing themselves dynamically. - Web fonts loading late and swapping with system fonts (causing text to expand or contract).
How to Test Your Core Web Vitals
There are two ways Google measures these metrics: Lab Data and Field Data.
Lab Data (Simulated)
This is a simulation of a page load under specific, controlled conditions. It is useful for debugging issues while developing a site. Tools like Google Lighthouse or our SEO audit tool use Lab Data.
Field Data (Crux - Chrome User Experience Report)
This is the data that actually counts for SEO. It is gathered from real Google Chrome users over the last 28 days. If your Lab Data says your site is fast, but your real users are on slow 3G connections and failing the metrics, Google uses the failing Field Data for rankings.
Where to find your CWV scores:
- Google Search Console > Core Web Vitals: The clearest source for how Google views your site across indexed pages.
- PageSpeed Insights: Enter a specific URL to see both Field Data (what real users experience) and Lab Data (simulated diagnostics).
5 Practical Fixes for Failing CWVs
Fixing CWV requires technical knowledge, but understanding the solutions helps you instruct your developer or agency effectively.
1. Optimise Images (The Biggest Win)
Images are the #1 cause of LCP failures. - Compress images before uploading (use tools like TinyPNG). - Convert standard JPEGs to next-gen formats like WebP or AVIF. - Ensure images are sized correctly (don't serve a 4000px wide image into a 400px wide space).
2. Implement Lazy Loading
Lazy loading tells the browser to only render images when the user scrolls down to see them. This prioritises the loading of the content immediately visible at the top of the screen (improving LCP).
3. Declare Image Dimensions
To fix CLS (layout shifts), every image and video tag in your code must include exact width and height attributes: <img src="image.webp" width="800" height="600">. This tells the browser exactly how much blank space to reserve before the image even loads.
4. Audit Third-Party Scripts
Every tracking pixel, chat widget, and social media feed you add to a site slows down INP and LCP. Remove unused scripts. For critical scripts (like Google Analytics), ensure they load asynchronously so they don't block the rest of the page.
5. Upgrade Your Hosting
If your server response time (TTFB - Time to First Byte) is over 600ms, your LCP will usually struggle. Shared hosting located outside South Africa can make Core Web Vitals much harder to pass. Use SA-based hosting or a high-quality global CDN (Content Delivery Network).
A practical CWV triage table
| Symptom | Usual cause | First fix to test |
|---|---|---|
| Slow hero load | heavy images or slow hosting | compress media and review TTFB |
| Laggy buttons | too much JavaScript | remove or defer non-essential scripts |
| Layout jumping | missing media dimensions | reserve image and embed space explicitly |
This is usually enough to identify the first high-impact fix before the deeper technical work starts.
FAQs
Does passing CWV guarantee page one rankings?
No. Content relevance and high-quality backlinks remain significantly more important than speed. CWV is a tie-breaker. If two sites have equally great content, the faster, more stable one will rank higher.
Why does my Desktop pass but Mobile fails?
Google tests mobile speed using simulated 4G connections on mid-tier devices to reflect average global users. Desktop processors are faster and run on Wi-Fi or fibre. Because Google uses Mobile-First Indexing, your mobile score is the one that actually matters for rankings.
Do I need a developer to fix Core Web Vitals?
Usually, yes. While you can compress images easily, fixing render-blocking CSS, optimising JavaScript execution, and managing CLS shifts requires altering the website's code or server configuration. See our technical SEO checklist for a deeper technical breakdown.
How often does Google update CWV scores?
Field data in Google Search Console is based on a rolling 28-day average. If you drastically speed up your website today, you will not see the "Pass" status in Search Console until 28 days of new data have overwritten the old data.
Is 100/100 on PageSpeed Insights necessary?
No. Chasing a perfect 100 often leads to removing essential functionality (like analytics or chat) for diminishing marginal returns. The goal is simply to be in the "Good" (green) threshold across all three metrics.
Conclusion
Core Web Vitals removed the mystery from "site speed." Google has provided exact targets: load the main visual in under 2.5 seconds (LCP), react to clicks in under 200ms (INP), and don't physically shift the page while the user is reading (CLS).
While fixing these issues requires technical implementation, the ROI is massive. Passing CWV not only provides a highly confirmed SEO ranking benefit against slower competitors, but it directly protects your conversion rates by preventing users from abandoning a frustrating, slow-loading experience.
