Page Speed SEO Checklist: The South African Priority Guide (2026)

A page speed SEO checklist is a prioritised set of technical fixes that improve how fast your website loads and, as a direct result, how well Google ranks it. If your site is taking more than three seconds to load on a mobile connection, you are already losing more than half your visitors before they read a single word — research from Think with Google puts mobile abandonment at 53% at that threshold. South Africa's SEO landscape makes this more urgent, not less: with 50.8 million internet users and a country where mobile browsing dominates, slow pages cost you traffic, leads, and revenue simultaneously.

Google has confirmed that Core Web Vitals — its three-metric framework for loading, interactivity, and visual stability — are used by its ranking systems. When two pages compete for the same query with equally relevant content, the faster page wins. What most generic speed guides miss is that not all fixes move rankings equally. This checklist is organised by impact: the highest-value changes first, so you spend your development budget where it matters most, and skip the low-return tweaks until the priorities are clean.

How Page Speed Affects Your Google Rankings

Google's page experience documentation confirms it plainly: "Core Web Vitals are used by our ranking systems." This is not a rumour or an SEO industry assumption — it is Google's stated position. The nuance is that speed operates as a tiebreaker: for any query where multiple pages offer equally helpful, relevant content, page experience — led by Core Web Vitals — is the factor that separates position three from position one.

The standard that counts is real-user data, not a lab simulation. Google measures your site through the Chrome User Experience Report (CrUX), which collects actual load times from Chrome users visiting your pages. For the full ranking benefit, 75% of those real visits must hit "Good" across all three metrics. Running a PageSpeed Insights audit and seeing a score of 90 does not guarantee you pass — if your field data (the real-user section at the top of PageSpeed Insights) shows "Needs Improvement" for LCP, that is the number Google uses.

Source: web.dev — Core Web Vitals. Thresholds are measured at the 75th percentile of real Chrome users over a 28-day rolling window.

Why SA Websites Face a Tougher Speed Challenge

South Africa's internet context creates conditions where page speed issues hit harder than in most markets. According to DataReportal's Digital 2025 South Africa report, 50.8 million South Africans are online — 78.9% of the population — with the majority browsing on mobile cellular connections. The median mobile download speed is 51.43 Mbps, which sounds healthy, but South Africa's average real-world latency sits at 99 milliseconds, placing it 74th of 119 countries measured. That latency gap means every uncached server request costs your users roughly four to five times the round-trip time of a user in the Netherlands or the US.

Load shedding compounds the problem. When Eskom cuts power, mobile tower backup batteries start draining. Extended outages push some towers to reduced capacity or offline entirely, forcing connected users onto weaker signals. A page that loads adequately on a strong 4G connection becomes frustratingly slow — or does not load at all — on a degraded signal. Pages optimised to load under two seconds on a 4G connection are the ones that survive those windows.

Hosting location matters more here than in markets with low latency. A website hosted on a European or North American server adds a round-trip overhead for every South African visitor. Local data centres in Johannesburg and Cape Town, by contrast, put your server geographically close to the majority of your users, reducing that latency overhead significantly. If your analytics show a South African audience and your hosting is in Frankfurt or Virginia, moving to local hosting is one of the faster wins on this checklist.

Priority 1 — Core Web Vitals

Core Web Vitals are the right place to start your page speed SEO checklist because they are the metrics Google directly links to search rankings. Improving all three puts you in a measurably better position than a competitor whose content is similar but whose experience scores are poor. Pages that pass Core Web Vitals thresholds see visitors who are 24% less likely to abandon the page during loading — a compounding benefit for both rankings and conversions.

Largest Contentful Paint (LCP) — target: under 2.5 seconds

LCP measures how long it takes for the largest visible element on your page — usually a hero image, a product photo, or a large heading — to fully render. It is the metric most commonly responsible for failing Core Web Vitals on South African sites, and the fixes are largely within reach without major development work.

What causes slow LCP:

• Unoptimised hero images (large file sizes, wrong format)
• Render-blocking CSS or JavaScript that delays page rendering
• Slow server response times (Time to First Byte over 600ms)
• No preloading of the LCP image

Fixes in priority order:

• Convert your hero or above-fold image to WebP format — this format consistently delivers 25–35% smaller files than JPEG at equivalent quality
• Add fetchpriority="high" and a preload hint (<link rel="preload">) for the LCP image so the browser loads it before anything else
• Eliminate render-blocking resources that delay the browser from starting to render the page
• Ensure your hosting responds to the first byte (TTFB) in under 600ms — if it does not, server performance or geographic distance is the root issue

Interaction to Next Paint (INP) — target: under 200 milliseconds

INP replaced First Input Delay (FID) in March 2024 as Google's measure of page responsiveness. Where FID only measured the delay to the first interaction, INP measures the full lifecycle of every interaction — click, tap, keystroke — and reports the worst-performing one. A page with a slow INP feels sluggish and unresponsive even if it loads quickly.

What causes high INP:

• Heavy JavaScript executing on the main thread while the user tries to interact
• Third-party scripts (chat widgets, analytics, ad tags) blocking interaction
• Large DOM size — pages with thousands of elements take longer to update

Fixes in priority order:

• Audit and remove unused third-party scripts — chat tools, pop-up scripts, and unused analytics tags are frequent INP culprits
• Defer non-critical JavaScript so it runs after the user can interact with the page
• Break up long tasks (any script taking more than 50ms on the main thread) using async patterns

Cumulative Layout Shift (CLS) — target: under 0.1

CLS measures how much your page layout shifts unexpectedly while loading — a banner that drops the content down, an image that pops in and moves the text, a cookie notice that reshuffles the page. It is often the easiest of the three metrics to fix because the causes are predictable. If fixing layout shift and the other Core Web Vitals is beyond your in-house team, our technical SEO services in SA begin with a free audit before any retainer is agreed.

Common causes and fixes:

• Images without explicit width and height attributes — set them on every image so the browser reserves space before the image loads
• Embedded iframes (maps, YouTube videos) without reserved dimensions — wrap them in a fixed aspect-ratio container
• Web fonts that cause text to reflow when they load — use font-display: optional or font-display: swap with a close fallback font
• Dynamically injected banners or cookie consent bars that push content down — position them as overlays, not in-flow elements

Priority 2 — Image Optimisation

For most South African WordPress and Shopify sites, images account for the largest share of page weight and the most straightforward performance gains. Image optimisation is Priority 2 on this page speed SEO checklist because it directly reduces LCP — often by enough to move a "Needs Improvement" score to "Good" without touching a single line of JavaScript.

A practical rule: never upload an image to your site that has not been compressed and converted to WebP. Tools like Squoosh (free, browser-based) handle both steps in under a minute. For WordPress, plugins such as ShortPixel or Imagify automate the conversion on existing libraries. For Shopify, the platform automatically serves WebP where supported, but original file size still matters — a 4MB source file becomes a large WebP, not a fast one.

Priority 3 — Hosting, Server and Caching

Server configuration is Priority 3 because it affects every page on your site simultaneously — a single fix here improves load times globally, not just on pages you have individually optimised. For South African sites, the hosting conversation has a local dimension: a server in Johannesburg or Cape Town returns responses to local users with far less round-trip delay than one in Frankfurt or Virginia.

Server-side checklist:

• Enable GZIP or Brotli compression — Brotli is the more efficient option and is supported by all modern browsers. It compresses HTML, CSS, and JavaScript files before sending them to the browser, meaningfully reducing transfer size for text-based assets. Check that your server has compression enabled via PageSpeed Insights — it will flag "Enable text compression" if it is missing.
• Set appropriate browser caching headers — static assets (images, fonts, CSS, JS) should be served with long cache lifetimes (a year is typical for versioned files). This means returning visitors load your site from their local cache rather than re-downloading everything. Most caching plugins for WordPress handle this automatically; on Shopify, CDN-level caching is managed by the platform.
• Use a Content Delivery Network (CDN) — a CDN stores copies of your static assets on servers distributed globally, serving each user from the nearest node. For a South African site with some international traffic, a CDN is particularly valuable; for a purely local audience, local hosting often provides comparable benefits without the complexity.
• Consider local SA hosting if your audience is primarily South African — providers like Xneelo host from local data centres with generator-backed infrastructure, giving South African visitors lower latency than internationally-hosted alternatives.

Priority 4 — JavaScript and CSS

JavaScript and CSS clean-up is last on the main checklist not because it matters least, but because it typically requires the most development effort for the least predictable gain on smaller sites. On larger sites — those with multiple third-party tools, accumulated theme CSS, and custom scripts — this work can produce significant LCP and INP improvements once the higher priorities are already addressed.

For a complete technical walkthrough, our guide on improving crawlability and technical site health covers related considerations. The technical SEO checklist for South African websites is a useful companion if you are working through a broader audit.

JavaScript and CSS checklist:

• Identify and remove render-blocking resources — any script or stylesheet loaded in the <head> that is not critical to above-fold rendering delays the browser from painting the page. Move non-critical scripts to the bottom of the <body>, or use defer or async attributes on script tags.
• Minify JavaScript and CSS — minification removes whitespace, comments, and redundant characters without changing functionality. Most build tools (Webpack, Vite) and hosting platforms (Cloudflare, Vercel) offer this automatically; WordPress users can use a caching plugin's minification feature.
• Remove unused CSS — many themes, particularly WordPress themes built on large frameworks, load CSS rules for hundreds of components your site never uses. Tools like PurgeCSS or a coverage report in Chrome DevTools show exactly how much dead CSS your pages are loading. Cutting unused CSS can improve LCP measurably when the CSS file is large.
• Audit third-party scripts — chat widgets, pop-up tools, review platforms, and social sharing buttons all add JavaScript weight and frequently contribute to poor INP. Audit each one: if it is not actively driving business value, remove it. If it is essential, look for a lighter alternative or load it only on pages that need it.

How to Measure Your Page Speed for Free

Running your page speed SEO checklist starts with baseline data. These three free tools give you everything you need:

• PageSpeed Insights (pagespeed.web.dev) — Google's own tool. The "Field Data" section at the top shows your real-user Core Web Vitals from the CrUX database. The "Lab Data" and "Diagnostics" sections below identify the specific issues to fix. Always start with Field Data; if it shows no data (because your page has insufficient Chrome traffic), the lab data is your next best proxy.
• Google Search Console — Core Web Vitals report — shows you which pages on your site are passing, needing improvement, or failing across both mobile and desktop. Unlike PageSpeed Insights (which tests one URL at a time), Search Console gives you a site-wide view grouped by issue. This is where you prioritise — fix the issues affecting the most pages first.
• Web Vitals Chrome Extension — a browser extension that displays live Core Web Vitals as you browse any page. Useful for quickly testing pages that are not yet indexed or do not have CrUX field data, without opening a separate tool.

Check your Core Web Vitals specifically for your South African site using PageSpeed Insights — run it on your homepage, your top-traffic product or service page, and your slowest-loading page (Search Console's Core Web Vitals report will show you which that is). Those three URLs give you a representative picture without requiring you to audit every page individually.

Why South African Businesses Choose Growth Pulse Media for Page Speed and SEO

Most SEO agencies hand you a report. We work through the list with you. Dirk founded Growth Pulse Media after building and scaling a South African ecommerce business — the kind of business where a slow checkout page has a measurable cost that same day. That experience shapes how we approach technical SEO: we prioritise fixes by revenue impact and ranking impact simultaneously, not by what is easiest to report.

Our SEO services for South African businesses include technical audits that go beyond surface-level PageSpeed scores. We look at your field data (the CrUX numbers Google actually uses), your hosting configuration, your image pipeline, and the third-party scripts you have accumulated over time. We carry a deliberately limited client load — you get senior attention on your account, not handoffs to a junior coordinator after the kickoff call. We are familiar with the platforms SA businesses actually use: Shopify, WooCommerce, WordPress, and local payment gateways like PayFast and Peach Payments.

We are also direct about what speed optimisation alone cannot fix. If your content does not match search intent, a fast page will not save your rankings. If you want to understand the full picture, our website speed optimisation guide for South Africa and our broader indexation improvement guide sit alongside this checklist as part of a coordinated technical approach.

Who This Checklist Is NOT For

Page Speed SEO Checklist: Frequently Asked Questions

Is page speed a confirmed Google ranking factor?

Yes. Google's official page experience documentation states that "Core Web Vitals are used by our ranking systems." Speed operates as a tiebreaker: when two pages offer equally relevant content for a query, the one with better Core Web Vitals scores is more likely to rank higher. Speed alone will not overcome a significant content gap, but it increasingly determines the outcome when content quality is comparable.

What is a good page speed score for SEO purposes?

For SEO, the score that matters is not the PageSpeed Insights number — it is your Core Web Vitals field data. You need 75% of real Chrome users visiting your page to achieve "Good" on LCP (under 2.5s), INP (under 200ms), and CLS (under 0.1). Check the "Field Data" section at the top of a PageSpeed Insights report; if it shows "Good" across all three metrics, your pages are passing Google's page experience signal. The diagnostic score below (0–100) is useful for finding what to fix — but per analysis of how Google's ranking systems use Chrome User Experience Report field data, the lab-based performance score is not the signal applied to rankings.

How long does it take to see SEO results from fixing page speed?

Core Web Vitals field data is collected over a 28-day rolling window, so ranking effects from fixes made today will take at least a month to fully register. Sites that move from "Poor" to "Good" on a widely-crawled, well-linked page can start to see ranking shifts within four to six weeks of the fix. For a broader understanding of organic ranking timelines, our guide on how long SEO takes in South Africa covers what realistic timelines look like across different site types.

Does page speed matter more for mobile users in South Africa?

Yes, and for two compounding reasons. First, as Google has confirmed in its official crawling and indexing documentation, mobile-first indexing means Googlebot evaluates your mobile page content and experience for ranking purposes — your desktop version is secondary. Second, South Africa is a mobile-dominant browsing environment where metered data costs and variable connectivity (including load-shedding-related signal degradation) mean users are more likely to abandon slow pages than in markets with consistently fast broadband. Optimise for mobile field data first.

What is the fastest page speed fix with the biggest SEO impact?

For most South African websites, converting and compressing images to WebP format delivers the largest LCP improvement for the least development effort. Hero images and product photos are frequently the LCP element on a page, and unoptimised JPEGs are commonly two to ten times larger than their WebP equivalents. On WordPress, a plugin like ShortPixel or Imagify automates this at scale; on Shopify, ensure your source images are compressed before upload since the platform handles format delivery.

Do I need a developer to complete this page speed SEO checklist?

Not for all of it. Image conversion, compression, and setting explicit image dimensions are tasks a non-developer can handle with the right tools. Enabling server-side GZIP compression and browser caching is typically a hosting control panel setting or a plugin configuration. JavaScript deferral, removing unused CSS, and fixing complex INP issues require either developer involvement or a well-configured performance plugin (for WordPress). Start with the no-code steps — images, caching, and checking your hosting — before committing development time.

Dirk van Greuning Founder, Growth Pulse Media

Founder of Growth Pulse Media and a specialist in South African search dominance. Dirk translates his experience in scaling South African businesses into high-velocity digital strategies for B2B and retail leaders. He writes about SEO, lead generation, and paid media from an operator's perspective — prioritising pipeline value over impressions.

Connect on LinkedIn