What Is Page Speed?
Page speed refers to how quickly a web page loads for a user. It is typically understood as the total time from a user requesting a URL to the page being fully interactive, though in practice it is measured using a set of specific metrics rather than a single number. Google uses page speed as a ranking signal, meaning slower pages may rank lower than faster competitors with otherwise similar content and authority.
The primary metrics used to assess page speed include: Time to First Byte (TTFB), which measures how long the browser waits before receiving the first byte of data from the server; First Contentful Paint (FCP), which marks when the first content is painted on screen; Largest Contentful Paint (LCP), which measures when the main content element loads; and the three Core Web Vitals (LCP, Interaction to Next Paint, and Cumulative Layout Shift). Google's PageSpeed Insights tool reports on all of these and provides specific recommendations for improvement.
Google first confirmed page speed as a ranking factor for desktop in 2010, and extended it to mobile searches in 2018 with the Speed Update. The 2021 Page Experience update further formalised the importance of Core Web Vitals, which are real-user measurements of page speed and experience collected via Chrome. This means your speed score is based on how actual visitors experience your site, not just how it performs in a lab test.
For South African businesses, page speed carries additional weight because a large proportion of web traffic arrives on mobile devices over 4G or LTE connections, which are faster than 3G but still more variable than fixed-line broadband. A technical SEO audit that includes page speed assessment is an important first step for any business looking to improve its organic rankings and on-site conversion rates.
Page Speed In Practice
The scenario below is an illustrative example, not a Juicy Designs client result. The figures indicate the scale of effect that page speed work typically produces, so treat them as indicative rather than measured.
Picture a typical South African small business website scoring around 45 out of 100 on PageSpeed Insights for mobile. The diagnostic breakdown would commonly show the same cluster of issues: an uncompressed hero image served as a JPEG rather than WebP, render-blocking CSS and JavaScript in the document head, no browser caching configured on the server, and several third-party scripts (analytics, a chat widget, a social proof popup) loading synchronously.
Addressing these issues in order of impact could plausibly bring the score to 70 or higher without a complete rebuild. Converting images to WebP typically reduces their file size by something in the region of 25 to 35 percent. Moving render-blocking resources to load asynchronously, or deferring them until after the page has painted visible content, would typically improve FCP and LCP scores. Setting cache-control headers on static assets means returning visitors do not re-download unchanged files on every page visit.
Hosting infrastructure is the factor most often overlooked. A shared hosting plan with a server physically located in Europe adds latency to every request from South African users. Switching to a managed WordPress host with infrastructure on the African continent, or serving through a CDN with South African edge nodes, could plausibly reduce TTFB by several hundred milliseconds. That single change might move a page from the "needs improvement" band into "good" on some metrics without any other code changes.
The metrics that matter, and what they measure
| Metric | Measures | Good |
|---|---|---|
| Largest Contentful Paint (LCP) | When the main content appears | Under 2.5 seconds |
| Interaction to Next Paint (INP) | Responsiveness to taps and clicks | Under 200 ms |
| Cumulative Layout Shift (CLS) | Visual stability while loading | Under 0.1 |
These are the Core Web Vitals, and they are measured on real users rather than in a lab. A perfect lab score with poor field data means your test conditions were not your visitors' conditions.
Why speed matters more in South Africa
Most local traffic is mobile, much of it on prepaid data and variable network quality. A heavy page does not just load slowly here, it costs the visitor money to load. That changes the economics of every extra script.
The fixes that produce most of the gain, in order:
- Images. Correctly sized, modern formats, lazy-loaded below the fold, with width and height set to prevent layout shift.
- Third-party scripts. Chat widgets, tag managers and tracking pixels are usually the single largest cost. Audit what is actually used.
- Fonts. Preload the ones you need, subset them, and avoid loading weights nothing uses.
- Hosting and caching. A CDN and sensible cache headers matter more for a South African audience served from overseas origins.
See our Core Web Vitals guide and technical SEO service.
FAQ
How does page speed affect SEO in South Africa?
Page speed is a direct Google ranking factor, particularly on mobile. Slow pages also increase bounce rates, which means fewer engaged sessions and fewer conversion opportunities. For South African businesses serving mobile users on variable data connections, even a one-second improvement in load time can measurably increase enquiries and sales.
What are the fastest ways to improve page speed?
The highest-impact improvements are compressing and converting images to WebP format, enabling browser caching and server-side gzip compression, removing unused JavaScript and CSS, switching to faster hosting, and using a CDN. Running PageSpeed Insights on your key landing pages will identify the specific issues worth addressing first.
Is page speed a Google ranking factor?
Yes, through the Core Web Vitals as part of page experience signals, though relevance still outweighs speed. The larger commercial effect is on conversion: slow mobile pages lose visitors before they see the offer, particularly on metered data.
What is a good page load time?
Aim for Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1, measured on real mobile users rather than a desktop lab test.