Add to Preferred Sources
Core Web Vitals South Africa site owners need to pass are three measures of real visitor experience — Largest Contentful Paint (how fast the main content loads, good at 2.5 seconds or less), Interaction to Next Paint (how quickly the page responds to a tap, good at 200 milliseconds or less) and Cumulative Layout Shift (how much the page jumps around, good at 0.1 or less).
Google uses them as part of its page experience signals, and they matter more here than in many markets because most South African visitors browse on mid-range phones over mobile data. This guide explains each metric, how to check your real data, and the fixes that work. For the wider picture, see our technical SEO guide and the free SEO audit checklist.
Quick Answer
Pass Core Web Vitals by keeping LCP at 2.5 seconds or less, INP at 200 milliseconds or less and CLS at 0.1 or less for at least 75% of real visits. Check field data in Search Console and PageSpeed Insights, then fix the biggest causes: heavy images, slow hosting, too many scripts and elements that load without reserved space.
Want to know which pages fail and why? We will check your Core Web Vitals and send you a prioritised fix list — free.
Get a Free Speed CheckThe Three Metrics Explained
Core Web Vitals are three metrics that measure loading, responsiveness and visual stability from real visitors' devices, and a page passes only when all three meet Google's thresholds for most visits.
| Metric | What it measures | Good | Poor | Common cause of failure |
|---|---|---|---|---|
| Largest Contentful Paint (LCP) | Time until the main image or text block appears | 2.5 s or less | Over 4 s | Large hero images, slow hosting, render-blocking CSS |
| Interaction to Next Paint (INP) | Delay between a tap or click and the page responding | 200 ms or less | Over 500 ms | Heavy JavaScript, chat widgets, tracking scripts |
| Cumulative Layout Shift (CLS) | How much content moves while loading | 0.1 or less | Over 0.25 | Images without sizes, late-loading banners and ads |
According to Google's web.dev guidance, the thresholds are measured at the 75th percentile of page loads — meaning three out of four real visits must meet them for the page to pass.
Core Web Vitals South Africa: Why They Matter More Here
Core Web Vitals matter more in South Africa because most visitors use mid-range Android phones on mobile data, so a page that feels fast on an office laptop can fail badly for the customers you actually serve. Speed is just part of a wider picture, and our complete SEO guide for South Africa explains how page experience fits into search for SA businesses.
A slower processor makes heavy JavaScript take longer to run, which hurts INP. Variable mobile connections make large images and fonts slower to arrive, which hurts LCP. And the business cost is direct: 53% of mobile visitors leave a page that takes longer than three seconds to load. Hosting location matters too — a site hosted overseas without a content delivery network (CDN) adds delay for every South African visitor.
Key Takeaway
Test on the phone your customers use, not the one you use. A mid-range Android on mobile data is the realistic benchmark for most South African sites, and it is where Core Web Vitals failures cost the most sales.
How to Check Your Real-Visitor Data
The most reliable Core Web Vitals data is field data — measurements from real Chrome users — which you can see in Google Search Console's Core Web Vitals report and at the top of PageSpeed Insights.
| Tool | What it shows | Best for |
|---|---|---|
| Search Console → Core Web Vitals | Groups of URLs rated good, needs improvement or poor from real visits | Seeing which templates fail site-wide |
| PageSpeed Insights (field section) | Real-user data for one URL or the whole origin | Checking a specific page |
| PageSpeed Insights (lab section) | A simulated test with a list of fixes | Diagnosing causes |
Lab scores (the 0–100 number) are useful for diagnosis but are not what Google uses for rankings. Small sites may not have enough visits for field data; in that case, use the lab results as a guide and keep checking as traffic grows.
Search Console showing "poor" URLs and not sure where to start? We will read the report with you and rank the fixes.
Get a Free Core Web Vitals ReviewFixes That Work for Each Metric
Most Core Web Vitals problems come from a short list of causes, so fixing the biggest one for each metric usually moves a site from "poor" to "good" without a full rebuild.
Improving LCP
Compress and resize the main image, serve it in WebP, preload it, avoid sliders and background videos above the fold, use good hosting with a CDN such as Cloudflare, and enable page caching.
Improving INP
Remove unused plugins and apps, delay non-essential scripts such as chat widgets until after interaction, limit tracking tags to what you actually use, and avoid heavy page builders on key templates.
Improving CLS
Set width and height on images and embeds, reserve space for banners and cookie notices, load fonts properly, and avoid inserting content above what the visitor is already reading.
Quick wins: compress the hero image, remove two or three unused plugins, delay the chat widget and add image dimensions. On many small business sites these four changes alone move pages into the "good" range.
False fixes: installing yet another speed plugin on top of a heavy theme, chasing a perfect 100 lab score, or testing only on desktop.
Core Web Vitals and Rankings: Keeping It in Perspective
Core Web Vitals are a ranking factor but not a dominant one — relevant, helpful content still matters more — yet they strongly affect whether visitors stay long enough to convert.
Passing Core Web Vitals will not rank a weak page, and failing them will not sink a page that is clearly the best answer. The bigger payoff is commercial: faster, more stable pages lose fewer visitors and turn more of them into enquiries and sales. Treat Core Web Vitals South Africa work as conversion work that also helps SEO. Our guide to UX design covers the conversion side.
Speed Is a Conversion Lever
Fix Core Web Vitals for your customers first and Google second. The rankings benefit is modest; the benefit of fewer visitors abandoning a slow page is immediate and measurable.
Platform-Specific Fixes: WordPress, Shopify and Wix
The most effective speed fixes depend on the platform your site runs on, because WordPress gives you almost full control over code and hosting, Shopify controls the hosting but not your theme and apps, and builders such as Wix and Squarespace limit what you can change at all. Whatever your platform, our technical SEO service starts with a free SEO audit, and technical work is a core part of the flat monthly retainer.
| Platform | Usual causes of poor scores | Most effective fixes | Best for |
|---|---|---|---|
| WordPress | Heavy page builders, too many plugins, slow shared hosting, uncompressed images | Quality hosting, page caching, image optimisation plugin, removing unused plugins, lighter theme | Sites where you want full control and can maintain it |
| Shopify | Too many apps, heavy themes, large hero videos and sliders | Remove unused apps and their leftover code, choose a lean theme, compress images before upload | Stores that want reliable hosting without server management |
| Wix and Squarespace | Animation-heavy templates, large galleries, embedded widgets | Simplify pages, reduce animations and embeds, use the platform's own image tools | Small brochure sites with modest traffic |
On WordPress, a common pattern is a site built with a visual page builder plus 30 or more plugins on budget shared hosting. Each piece seems harmless, but together they load hundreds of files on every page. Removing plugins that are inactive or duplicated, and moving to better hosting, often fixes more than any single optimisation plugin can. On Shopify, apps are the main culprit — see our guide to Shopify website design for how to keep a store lean from the start.
On Wix and Squarespace, you cannot change hosting or caching, so the work is about what you put on the page. Replace autoplay background videos with a still image, limit galleries to the photos that matter, remove animations that trigger as visitors scroll, and avoid stacking several embedded widgets on one page. If a site still fails after that and speed matters to your business, it may be a sign that the platform has been outgrown rather than that more tweaking will help.
Third-Party Scripts: The Hidden Cost
Third-party scripts — chat widgets, advertising pixels, analytics and heatmap tools, social feeds and embedded videos — are among the most common causes of poor responsiveness scores, because each one adds code that competes with your own page for the phone's processing power.
A typical business site might load Google Analytics, a Meta pixel, a TikTok pixel, a live chat widget, a WhatsApp button plugin, a cookie banner, a reviews widget and an embedded YouTube video. Each is small on its own, but together they can add seconds of processing on a mid-range phone and push interaction delays well past Google's 200-millisecond threshold for good INP.
- Audit what is loaded. List every script on your key pages and ask whether it is still used. Old pixels from past campaigns are often still firing.
- Load only where needed. A booking widget belongs on the booking page, not on every blog post.
- Delay non-essential scripts. Chat widgets and heatmaps can load after the page is interactive or after the first scroll.
- Use lightweight embeds. Show a thumbnail image for YouTube videos and load the player only when someone clicks play.
- Manage tags centrally. Google Tag Manager makes it easier to see and control what fires, but it can also make it easier to keep adding tags — review it quarterly.
Key takeaway: Many sites fail Core Web Vitals not because of their own design, but because of the marketing tools added to them over time. A quarterly review of every third-party script, removing or delaying anything not essential, is one of the cheapest speed improvements available.
Hosting, CDNs and Server Response Time
Hosting affects Core Web Vitals through server response time — how long the server takes to start sending a page — and for a mainly South African audience, a server or content delivery network with a presence in South Africa usually responds faster than budget hosting overseas.
If every page takes a second or more before anything starts to load, no amount of image compression will get LCP comfortably under 2.5 seconds. Check server response time (often shown as TTFB, time to first byte) in PageSpeed Insights. Budget shared hosting in another continent, overloaded servers and sites with no page caching are the usual causes.
Hosting in Johannesburg or Cape Town data centres, or using a content delivery network with local points of presence, shortens the distance data travels. Caching — storing ready-made copies of pages so the server does not rebuild them for every visitor — often makes the biggest single difference on WordPress sites. Our guide to website hosting in South Africa compares the main options.
Keeping Scores Healthy After the Fixes
Core Web Vitals need ongoing attention, because new plugins, apps, images, tracking scripts and theme updates can undo months of speed work within weeks.
Check the Core Web Vitals report in Search Console once a month. Because Google's field data is based on a rolling 28-day window of real visitors, problems show up there with a delay, so also run PageSpeed Insights on your key pages after any significant change. Agree a few simple rules with whoever updates the site: images compressed before upload, no new plugin or app without checking its impact, and no autoplay videos above the fold. Some teams set a "performance budget" — for example, a maximum page weight or number of scripts — and treat anything that breaks it as a problem to fix before launch rather than after.
What to avoid: a site passes all three metrics after a speed project, then marketing adds a new pop-up tool, a second analytics platform and a homepage video over the following months. Nobody checks, and six months later the site is failing again with nobody sure why.
How Growth Pulse Media Fixes Site Speed
Growth Pulse Media handles Core Web Vitals South Africa sites struggle with on WordPress and Shopify — image optimisation, script clean-up, caching and Cloudflare setup, and template fixes — measured against Search Console field data.
We prioritise the templates that carry the most traffic and revenue, and we check results on real mid-range phones. See our web design services.
Who This Is NOT For
Deep speed work is the wrong priority in four situations.
Your pages already pass in Search Console: spend the effort on content and conversion instead.
The site needs a rebuild anyway: fix speed as part of the redesign rather than patching a platform you are leaving.
You have almost no traffic: focus on getting found first; speed fixes pay off once visitors arrive.
You want a perfect lab score: the goal is passing field data for real visitors, not a number on a test.
Want your key templates moved into the "good" range? We will scope the fixes and give you a fixed quote — free.
Get a Free Speed Fix QuoteFrequently Asked Questions
What are Core Web Vitals?
Core Web Vitals are three Google metrics that measure real visitor experience: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness and Cumulative Layout Shift for visual stability.
What are good Core Web Vitals scores?
LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, measured at the 75th percentile of real page visits.
Do Core Web Vitals affect Google rankings?
Yes, as part of page experience signals, but content relevance and quality matter more. The larger benefit is fewer visitors leaving slow or unstable pages.
How do I check Core Web Vitals for my website?
Use the Core Web Vitals report in Google Search Console for site-wide field data, and PageSpeed Insights for individual pages, including a list of suggested fixes.
How long do Core Web Vitals fixes take to show in Search Console?
Field data is based on the previous 28 days of real visits, so improvements usually take about four weeks to show fully in Search Console after the fixes go live. You can confirm the change sooner in PageSpeed Insights lab tests.
Why does my site pass on desktop but fail on mobile?
Mobile devices have slower processors and connections, so heavy images and scripts take longer. Most South African visitors are on mobile, so the mobile result is the one to prioritise.
Does my hosting affect Core Web Vitals?
Yes. Slow hosting increases server response time, which delays everything else and makes a good LCP hard to achieve. For a mainly South African audience, hosting in a local data centre or using a CDN with South African points of presence, plus page caching, usually helps.
Do chat widgets and tracking pixels affect Core Web Vitals?
They often do, especially INP, because each third-party script adds work for the visitor's browser. Remove scripts you no longer use, load others only on the pages that need them, and delay non-essential tools until after the page is interactive.
Make Your Site Fast for Real Visitors
Growth Pulse Media fixes Core Web Vitals for South African WordPress and Shopify sites — image and script optimisation, caching, Cloudflare CDN setup and template fixes, measured with Search Console field data. No obligation — we will get back to you within 24 hours.
Get Your Free Speed Consultation