Speed is the one part of a website that nobody notices when it is good and everybody abandons when it is bad. A visitor does not think "this page has a 4.2 second Largest Contentful Paint". They think "this business feels amateur" and press back.
What is actually being measured
Google's Core Web Vitals are three numbers, each with a published threshold:
- Largest Contentful Paint (LCP) — how long until the main content is visible. Good is 2.5 seconds or less. This is usually the hero image or the headline.
- Interaction to Next Paint (INP) — how quickly the page responds when someone taps or clicks. Good is 200 milliseconds or less.
- Cumulative Layout Shift (CLS) — how much the page jumps around while loading. Good is 0.1 or less.
Two of those three have nothing to do with server speed. They are about what the browser is asked to download, parse and execute before the page becomes usable.
Why it matters more in South Africa
A page that feels instant on office fibre can feel broken on a mid-range Android phone on mobile data — which is how a large share of local traffic actually arrives. The gap between a lean page and a heavy one widens dramatically on slower connections and weaker devices. A site that is "fine" in the boardroom is often unusable in the taxi.
Add data cost to the equation. A theme that ships a few megabytes of images and animation is not just slow; on a metered connection it is expensive for the visitor.
The five fixes that actually move the number
- Stop shipping animation libraries for decoration. A scroll-smoothing library, a custom cursor and an entry preloader can easily account for hundreds of kilobytes of JavaScript whose only job is ornament. Removing them is usually the single biggest win available.
- Resize and serve modern image formats. A 4000-pixel photograph in a 400-pixel slot is one of the most common causes of a bad LCP. Serve WebP or AVIF at the size actually displayed.
- Declare image dimensions. Adding width and height attributes costs nothing and eliminates most layout shift.
- Lazy-load below the fold, and never the hero. The hero image should load eagerly with high priority; everything else should wait until it is needed.
- Cut unused CSS and fonts. A theme stylesheet carrying shop, careers and pricing sections you never use is dead weight. Unused web fonts are worse: they block text rendering.
How to check your own site
Run a single page through PageSpeed Insights, in mobile mode, on a real page rather than the home page. Ignore the headline score and look at the three Core Web Vitals. If LCP is above four seconds, there is almost always a large, easily-found cause: an oversized hero image or a render-blocking script.
Fixing those two things is rarely a redesign. It is usually a day of focused work.