Core Web Vitals are Google’s three measures of how a page feels to real visitors: how fast the main content appears (LCP), how quickly the page responds to a tap (INP) and how much the layout jumps (CLS). A page passes when 75% of real visits, over 28 days, see LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less. They count towards rankings, but far less than relevance; their bigger effect is on how many visitors stay and enquire.
Below: what each number means, where to find yours, what we found when we tested our own site, and the fixes that move each metric on a typical South African WordPress or Shopify site.

The three Core Web Vitals and their thresholds
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP, Largest Contentful Paint | When the biggest image, video or text block finishes appearing | 2.5 s or less | 2.5 to 4 s | Over 4 s |
| INP, Interaction to Next Paint | The delay between a tap or click and the screen responding | 200 ms or less | 200 to 500 ms | Over 500 ms |
| CLS, Cumulative Layout Shift | How much visible content moves unexpectedly | 0.1 or less | 0.1 to 0.25 | Over 0.25 |
Two details matter. First, each metric is judged at the 75th percentile of real page loads, separately for mobile and desktop, so a page that is fast on your office fibre can still fail if a quarter of your visitors are on slower phones. Second, the thresholds have not changed. Claims in 2026 that Google tightened LCP to 2.0 seconds are false. INP replaced the older FID metric in 2024, so any guide or audit still scoring you on FID is out of date.
How much Core Web Vitals affect rankings
Google’s documentation says Core Web Vitals are used by its ranking systems, and recommends good scores “for success with Search”. It also says Google “always seeks to show the most relevant content, even if the page experience is sub-par”, and that page experience helps most where many pages are equally helpful. In practice that means:
- A fast page with nothing useful on it will not outrank a slower page that answers the question.
- Where you and a competitor are close, a better experience can be the difference.
- A green Search Console report does not guarantee rankings, as Google says itself.
The stronger business case is conversions. A slow, jumpy page loses people from every source, including paid ones. If you run Google Ads, landing page experience is one of the three components of Quality Score, Google’s measure of how relevant and useful your ads and landing pages are compared with other advertisers.
How to check your own scores
Search Console’s Core Web Vitals report
Find it under Experience in Search Console. It groups similar URLs and labels each group Good, Needs improvement or Poor for mobile and desktop, using real Chrome user data from the last 28 days. Start here because it shows which problem affects the most pages. Our Search Console tutorial shows where everything is.
If the report says “No data available”, your site does not yet have enough Chrome traffic in Google’s Chrome UX Report. That is common for small South African business sites. Use the lab tools below instead.
PageSpeed Insights and Lighthouse for a single page
PageSpeed Insights shows real-user field data at the top when Google has enough of it, and a Lighthouse lab test below. When the two disagree, the field data is what Google uses; the lab test is for finding causes. Lab tests cannot measure INP directly, because there is no real person tapping. Total Blocking Time is the lab stand-in: a high figure points to the same heavy scripts that cause poor INP.

What we found when we tested our own site
On 20 November 2026 we ran Lighthouse (version 13.4, standard simulated mobile settings) on two of our own pages. These are lab figures, not the field data Google uses, but they show how quickly problems pile up on a normal business site:
| Page | Lab LCP | CLS | Total Blocking Time | Page weight | What the largest element was |
|---|---|---|---|---|---|
| Searchly homepage | 6.7 s | 0.035 | 440 ms | 3.6 MB | An autoplaying mascot video |
| An older blog post | 3.6 s | 0.083 | 570 ms | 2.4 MB | The featured image |
What the reports showed:
- The homepage’s largest element is a video. Two animation files of roughly 0.5 MB each downloaded on a mobile test, and the video was the element LCP waited for. A static poster image for mobile would fix most of it.
- Third-party scripts outweigh the content on the blog post. Eight outside services loaded, including tag management, an ad pixel, session recording, an email pop-up tool and a live-chat widget. The chat widget alone made 37 requests, nine of them font files, and accounted for about 1.2 MB of the page’s 2.4 MB.
- Layout shift was fine on both, because images carry width and height.
These are our own fixes to make, and they are typical of what we find on client sites: a heavy hero, a growing pile of tags nobody reviews, and a theme that loads fonts and styles before anything else.
The usual causes on South African sites, and the fix for each

LCP: the main content appears late
- Oversized hero images and videos. Resize images to the size they are shown at, use WebP or AVIF, and do not autoplay video as the main element on mobile.
- Lazy-loading the hero. Lazy-load images further down the page, never the main one. Give the hero image a high fetch priority.
- Slow server response. If the server takes a long time to send the first byte, nothing on the front end can make up for it. Use page caching and a CDN, and check where your hosting is and how quickly it answers.
- Render-blocking fonts and CSS. Load fewer font weights and only the CSS a page needs.
INP: the page is slow to respond
- Too many third-party tags. Every pixel, chat widget, heatmap and pop-up in Google Tag Manager runs on your visitor’s phone. List them twice a year and remove any nobody uses.
- Heavy page builders and plugins. Pages with thousands of nested elements are slow to update after a tap. Sometimes the honest fix is a lighter template.
- Scripts that run on load but are needed later. Delay chat, reviews widgets and video players until someone scrolls or taps.
CLS: things jump around
- Images, embeds and ads without dimensions. Set width and height, or an aspect ratio, on every one.
- Late banners. Cookie notices, promo bars and pop-ups that push content down. Reserve their space or overlay them.
- Web fonts swapping in. Preload the main font and match the fallback’s size.
Core Web Vitals on WordPress and Shopify
On WordPress, page caching, image compression, removing unused plugins and delaying non-essential scripts usually move LCP and CLS. INP is harder when the theme or builder outputs a lot of code. Our guide to speeding up a WordPress website goes through it step by step.
On Shopify you control less of the server, so the work is in the theme and the apps. Every app that adds a script to the storefront costs something; removing an app does not always remove its code, so check the theme files afterwards. For stores, see our ecommerce SEO services.
How long until the fix shows
Field data is a rolling 28-day window, so after a fix goes live it takes up to four weeks to show fully. In Search Console, open the issue and click to start validation; Google monitors the affected URLs for 28 days and marks the issue fixed if it does not recur. Lab tests show the change immediately, which is useful for checking the fix worked before the field data catches up.
Other questions owners ask
Do I need a PageSpeed score of 100?
No. The score is a lab measure. What counts is passing the three Core Web Vitals for real visitors. Chasing 100 often means removing things that help people buy or enquire.
Is desktop or mobile more important?
Both are reported separately, and Google indexes the mobile version of your site. For most South African businesses mobile is where the problems are, because phones have less processing power for heavy scripts.
Should I change hosting to fix Core Web Vitals?
Only if the server is slow to respond. Measure time to first byte first. If it is fast, the problem is on the page, and new hosting will not fix it.
Where to go from here
Core Web Vitals are one part of a full site check. Our technical SEO audit tests your templates, lists every script and image slowing them down, and ranks the fixes by what they cost you. If you would like us to look at yours, get in touch.

