Why website speed affects rankings: what SA site owners need to know
Yes, website speed affects your search rankings, but not in the way most people expect. Google's Page Experience signal treats Core Web Vitals as a
TL;DR:
TL;DR: Quick Answer
Yes, website speed affects your search rankings, but not in the way most people expect. Google's Page Experience signal treats Core Web Vitals as a
Key takeaways
- Very cheap quotes (under R5,000) almost always exclude copywriting, SEO, custom design and post-launch support
- Professional copywriting can represent 20-35% of a total website project cost, and is worth it for search visibility
- On-page SEO built into the website at launch costs a fraction of what it costs to retrofit after the site is live
- Hosting, SSL, domain and maintenance add R3,000-R10,000 per year on top of build cost
- E-commerce adds significant cost due to payment gateway integrations, product data, security requirements and checkout UX
- Timeline and client responsiveness directly affect cost: slow feedback rounds extend agency hours
TL;DR:
- Website speed influences search rankings primarily as a tiebreaker when content relevance is equal and consistently affects user behaviour. Improving Core Web Vitals on revenue pages can significantly boost conversions and reduce visitor abandonment, especially on mobile devices in South Africa. Prioritising fast-loading, well-optimised pages provides measurable revenue gains and enhances competitive positioning.
Yes, website speed affects your search rankings, but not in the way most people expect. Google's Page Experience signal treats Core Web Vitals as a tiebreaker: when two pages are equally relevant and authoritative, the faster one tends to rank higher. Speed rarely overrides a content quality gap, but it consistently determines who wins in competitive keyword clusters.
The more reliable return on speed work is behavioural. Slow pages drive visitors away before they convert, and every abandoned session is lost revenue. Fix your content and relevance first, then attack the biggest speed problems on the pages that generate leads or sales.
The three Core Web Vitals Google measures:
- LCP (Largest Contentful Paint): how quickly the main content loads. Target: a fast load time within Google's threshold.
- INP (Interaction to Next Paint): how fast the page responds to clicks and taps. Target: a responsive interaction time within Google's threshold.
- CLS (Cumulative Layout Shift): how much the page layout jumps around. Target: minimal unexpected layout shifts according to Google's standards.
Your single best first action: run your most important revenue page through Google PageSpeed Insights. Check the field data section, that is the real-user CrUX data Google uses for ranking decisions, not the lab score at the top.
Pro Tip: If you only have 30 minutes, open PageSpeed Insights, paste your homepage URL, scroll to "Diagnose performance issues," and fix the top image optimisation warning. Unoptimised hero images cause more LCP failures than any other single factor.
What website speed actually means and the metrics that matter
"Website speed" is a shorthand for several distinct measurements. Technically, it refers to how quickly a browser can download, parse, and render a page so a user can see and interact with it. Google groups these measurements under Page Experience, which is broader than speed alone, it also covers HTTPS, mobile-friendliness, and the absence of intrusive interstitials.
The most important distinction for SEO is field data vs lab data.
- Field data (CrUX): real measurements from real users collected by Chrome over a 28-day rolling window. Google reads the 75th percentile of these measurements. This is what drives ranking decisions.
- Lab data (Lighthouse): a simulated test run on a controlled machine. Useful for diagnosing problems, but not the ranking signal itself.
Core Web Vitals are the three field-measured metrics Google officially uses. Here is how they map to published thresholds:
| Metric | What it measures | "Good" threshold | Primary tool |
|---|---|---|---|
| LCP | Time until the largest visible content element loads | ≤ 2.5s | CrUX, PageSpeed Insights |
| INP | Latency from user interaction to next visual response | ≤ 200ms | CrUX, PageSpeed Insights |
| CLS | Total unexpected layout shift during page load | ≤ 0.1 | CrUX, PageSpeed Insights |
| TTFB | Time to first byte from the server | ≤ 800ms | WebPageTest, Lighthouse |
| FCP | Time until first content appears on screen | ≤ 2.5 seconds | Lighthouse, PageSpeed Insights |
Published thresholds from Google confirm that Google reads CrUX at the 75th percentile, meaning 75% of your real visitors must experience a "good" score for your page to pass. A Lighthouse score of 95 means nothing if your actual users on mobile data are experiencing 4-second LCP loads.
Supporting metrics like TTFB and FCP are diagnostic. They help you find where in the loading sequence the problem sits, but Google does not use them directly as ranking inputs.
How Google actually uses speed in ranking decisions
Google's Page Experience signal is confirmed and active, but its weight is deliberately light. Google has been explicit: a page with outstanding content will outrank a faster page with thin content. Speed is the deciding factor when relevance and authority are roughly equal, which, in competitive South African markets, happens more often than you might think.
The mechanism works through CrUX. Google aggregates real Chrome user data for each URL and origin, then reads the 75th percentile over 28 days. If your page passes all three Core Web Vitals at that threshold, it qualifies for the Page Experience ranking boost. If it fails, it does not, regardless of what your Lighthouse score says.
Mobile-first indexing amplifies this. Google indexes and ranks based on the mobile version of your site. If your mobile Core Web Vitals fail while your desktop scores pass, the mobile data determines your ranking outcome. For South African sites where the majority of traffic arrives on mobile devices, this is not a theoretical concern.
The correlation between speed and ranking position is real but modest. A large-scale study found that sites ranking on the first page tend to pass Core Web Vitals more frequently than those on subsequent pages, with the top positions passing at a higher rate. The gap is consistent, not dramatic, which is exactly what you would expect from a tiebreaker signal.
Stat to remember: Pages in the top three positions pass Core Web Vitals 50.8% of the time, compared to 44.2% on the second page of results.
Speed experts frame this well: speed is "table stakes." You need to pass to stay competitive, but passing alone will not carry you from position 8 to position 1.
Pro Tip: Open Google Search Console, navigate to Experience > Core Web Vitals, and sort by "Poor URLs." Fix those pages first, they are the ones where a failing CrUX signal is actively working against you in rankings.
How site speed affects user behaviour, conversions, and revenue
The ranking argument for speed is real but modest. The conversion argument is immediate and significant. Research shows that many mobile visitors leave pages that take longer to load, and delays in load time can significantly reduce conversions.
For a South African e-commerce or lead-generation site, those numbers translate directly into rand value. Consider a business generating R30,000 per month in online revenue. If a slow site causes 20% of visitors to abandon before converting, that is R6,000 per month, R72,000 per year, walking out the door. Fix the speed problem and recover even half that abandonment rate, and the ROI on a technical audit pays for itself within weeks.
The number to share with your team: 53% of mobile visitors leave if a page takes longer than 3 seconds to load.
Beyond direct conversions, slow sites compound losses across the full marketing funnel:
- Higher bounce rates mean Google sees less engagement, which can suppress rankings over time.
- Fewer pages per session reduces the chance a visitor discovers your product range or service offering.
- Cart abandonment spikes on slow checkout pages, particularly on mobile.
- Ad spend efficiency drops when your landing page is slow, Google Ads Quality Scores factor in landing page experience, so a slow page costs you more per click.
- Return visit rates fall when users associate your brand with frustration.
Speed work also returns value through conversion rate optimisation, often before any ranking improvement appears. That is why prioritising speed on revenue-driving pages, not just the homepage, is the correct approach.
What causes slow sites: where to look first
Most slow sites share the same handful of problems. Knowing where to look saves hours of diagnostic work.
- Poor caching configuration, Without proper cache headers, returning visitors re-download assets they have already loaded. Browser caching and server-side caching (via tools like W3 Total Cache for WordPress) eliminate this waste.
Pro Tip: Split your diagnosis into two questions: "Is the server slow?" (check TTFB in WebPageTest) and "Is the client slow?" (check LCP and INP in PageSpeed Insights). A slow TTFB points to hosting or server config. A fast TTFB with slow LCP points to front-end assets.
How to measure speed: tools, what each shows, and the right workflow
Using the right tool for the right question is what separates a useful audit from a wasted afternoon.
The core toolkit:
- Google PageSpeed Insights: combines field data (CrUX) and lab data (Lighthouse) in one report. Shows origin-level and URL-level field scores. Start here.
- Lighthouse: the lab diagnostic engine inside Chrome DevTools and PageSpeed Insights. Identifies specific bottlenecks with fix recommendations. Use it after you know which URLs are failing in field data.
- Google Search Console (Core Web Vitals report): groups URLs by status (Good, Needs Improvement, Poor) using field data. The fastest way to find your worst-performing URL groups at scale.
- WebPageTest: detailed loading waterfall, connection view, and filmstrip. Excellent for diagnosing TTFB, render-blocking resources, and third-party script impact. Allows real-device testing from South African locations.
- GTmetrix: similar waterfall view with historical tracking. Useful for monitoring changes over time after fixes are deployed.
- Cloudflare analytics: if you use Cloudflare as your CDN, its dashboard shows cache hit rates, bandwidth saved, and edge response times, useful for validating CDN configuration.
The correct measurement workflow:
- Open Google Search Console and export all URLs flagged as "Poor" in the Core Web Vitals report. These are your priority targets.
- Run each priority URL through PageSpeed Insights. Note the field data scores (not the lab score) and which specific metric is failing.
- Run the same URLs through Lighthouse or WebPageTest to get the diagnostic detail, which resources are blocking render, which images are oversized, which scripts are delaying INP.
- Implement fixes, then wait. Field data updates on a 28-day rolling window, so expect 4-6 weeks before CrUX scores reflect your changes.
- Verify improvement in Search Console and PageSpeed Insights field data, not just the Lighthouse score.
What to capture during an audit:
- Full URL list segmented by page type (homepage, product pages, blog, checkout)
- Device profile tested (mobile is the priority given mobile-first indexing)
- Network throttling setting used in lab tests (Fast 3G simulates typical South African mobile conditions)
- Baseline field scores for LCP, INP, and CLS before any changes
Prioritised fixes: the order to tackle performance problems
Not all fixes are equal. These are ordered by speed of implementation and business impact.
Quick wins (1-3 hours each)
- Compress and resize hero images, Convert to WebP or AVIF. Serve images at display size, not full camera resolution. Use a plugin like Smush for WordPress or an automated build step for custom sites.
Medium-term fixes (1-3 days)
- Upgrade hosting, Move from shared hosting to a managed VPS or managed WordPress host with a local South African data centre. Expect TTFB to drop from 800ms+ to under 200ms.
Longer-term engineering work (weeks)
- Break up long JavaScript tasks. Tasks over 50ms block the main thread and hurt INP. Refactor or split heavy scripts into smaller chunks using code splitting.
- Adopt server-side rendering (SSR) or static site generation for pages that currently rely on heavy client-side JavaScript frameworks. This moves rendering work off the user's device.
- Implement responsive images with
srcset. Serve different image sizes to different screen widths so mobile users never download a desktop-sized image.
For technical SEO work that goes beyond speed, crawlability, structured data, internal linking, these fixes slot into a broader audit framework. The technical SEO audit checklist covers the full scope.
South Africa: local impact, latency, and what slow sites cost in rand
South African users face a compounding problem. Mobile data is expensive relative to income, and network variability is high. When a page loads slowly, it is not just frustrating, it is literally costing the user airtime. Digital strategists describe this as a "data anxiety" effect: users on metered data are quicker to abandon a slow page than users on uncapped fibre, because every second of waiting has a direct financial cost.
Local context: A South African business generating online revenue and experiencing visitor losses to slow load times is losing a significant amount monthly due to abandonment alone.
Geographic latency is a real factor. Hosting your site on a server in Europe or the US adds 200-400ms to every page request for South African visitors. A local server or a CDN with an edge node in Gauteng reduces that to 20-50ms. The difference is often enough to move LCP from "Needs Improvement" to "Good."
Managed WordPress hosting in South Africa typically costs R300, R800 per month for a quality provider with local infrastructure. That is a fraction of the revenue recovered by reducing abandonment, and it is the single highest-leverage infrastructure change most small and medium businesses can make.
Juicydesigns has worked with South African clients across automotive, retail, and professional services to identify and fix speed bottlenecks. In one dealership engagement, technical improvements contributed to a 312% increase in qualified leads, a result driven by both SEO and conversion improvements working together.
Local configuration checklist:
- Host on a South African data centre or use Cloudflare with an edge node in Johannesburg.
- Test on mobile with Fast 3G throttling in Lighthouse to simulate real conditions.
- Prioritise image compression, mobile users on LTE pay per megabyte.
- Check TTFB first. If it exceeds 800ms, hosting is the bottleneck, not front-end code.
- Use WebPageTest with a South African test location for the most representative results.
How speed work fits into your overall SEO and marketing strategy
Speed is not where you start your SEO work. It is where you go after the foundations are solid.
The correct order is: relevance and content first, technical baseline second, iterative performance polishing third. A site with thin content and no backlinks will not recover rankings by passing Core Web Vitals. But a site with strong content that fails Core Web Vitals on its key pages is leaving ranking positions on the table, and losing conversions in the process.
Technical SEO remains a meaningful differentiator in 2026, particularly for sites in competitive verticals. Speed is one component of that, alongside crawlability, structured data, and internal linking.
Decision flow for teams with limited resources:
- If your Core Web Vitals report shows "Poor" URLs on pages that drive revenue, fix those before anything else.
- If all key pages pass Core Web Vitals but rankings are still flat, the problem is content or authority, not speed.
- If you are running Google Ads to a slow landing page, fix the page before scaling spend. A slow page raises your cost per click and lowers your conversion rate simultaneously.
- If you are planning a site rebuild, build speed requirements into the brief from the start, retrofitting performance is always more expensive than building it in.
On measurement windows: CrUX updates on a 28-day rolling window. After deploying fixes, wait at least 4-6 weeks before evaluating whether field data has improved. Checking PageSpeed Insights the day after a fix and seeing no change does not mean the fix failed. Understanding how long SEO improvements take to show results helps set realistic expectations with stakeholders.
Before commissioning speed work, confirm:
- Which URLs are failing in field data (Search Console Core Web Vitals report)
- What monthly revenue or leads those pages generate
- What a 10-20% conversion improvement on those pages is worth in rand
- Whether the fix is a quick win (hours) or engineering work (weeks), and budget accordingly
Key takeaways
Website speed affects rankings as a confirmed tiebreaker signal, but its most reliable return is conversion uplift, fix failing Core Web Vitals on revenue-driving pages first, using field data from CrUX, not lab scores.
| Point | Details |
|---|---|
| Speed is a tiebreaker, not a primary factor | Core Web Vitals influence rankings when content quality is equal; relevance and authority still set the ceiling. |
| Field data drives ranking decisions | Google reads CrUX at the 75th percentile over 28 days, your Lighthouse score is a diagnostic, not the signal. |
| Conversions suffer more than rankings | 53% of mobile users abandon pages that take more than 3 seconds to load. |
| South African sites face a latency penalty | Cross-border hosting adds 200-400ms; local hosting or a Cloudflare edge node in Gauteng reduces that to 20-50ms. |
| Juicydesigns handles the full audit | Juicydesigns runs field-data-first speed audits for South African businesses, from diagnosis through to implementation and CRO uplift. |
Speed work in practice: what the data actually tells you
Most of the speed advice circulating online focuses on Lighthouse scores. Chase a 100, the advice goes, and your rankings will follow. That framing is wrong, and it wastes real budget.
The 37,036-site study is instructive here. The gap between page-one and page-two Core Web Vitals pass rates is 3.4 percentage points, real, but not dramatic. What that data does not show is how many of those page-one sites got there because of speed, versus how many got there despite mediocre speed because their content was simply better.
The more useful insight from that same study: 67% of failing pages fail on LCP and 60% fail on INP, while only 42% fail on CLS. That tells you where to spend your effort. Image optimisation and server response time fix LCP. Deferring heavy JavaScript fixes INP. Layout shift is a real problem but affects fewer sites.
What I see consistently with South African clients is that the conversion argument lands faster than the ranking argument. When you show a business owner that their R50,000-per-month e-commerce site is losing R10,000 monthly to abandonment on a 4-second load time, the budget for a speed audit materialises quickly. The ranking improvement is a welcome bonus, not the primary justification.
Speed is necessary. It is not sufficient. Build your content and authority first, pass your Core Web Vitals on the pages that matter, and then let the compounding effects of better user behaviour do the rest.
Juicydesigns can run your speed audit and fix what matters
Slow pages cost South African businesses real money, in lost conversions, wasted ad spend, and ranking positions conceded to faster competitors. Juicydesigns offers field-data-first speed audits that identify exactly which URLs are failing, why, and what fixing them is worth in rand.
The engagement model is straightforward: an audit to establish your baseline, targeted implementation of the highest-impact fixes, and optional retainer support for ongoing monitoring and CRO work. No long-term contracts, and direct access to the founders throughout. The dealership case study, 312% more qualified leads, reflects what happens when speed, SEO, and conversion work together rather than in isolation.
If your site is losing visitors to slow load times, request a speed audit from Juicydesigns or explore the full digital marketing services available to South African businesses.
Useful sources and tools for your own checks
Run your own speed checks using these tools, each serves a specific purpose in the measurement workflow:
- Google PageSpeed Insights: field data plus lab diagnostics in one report. Start every audit here.
- Google Search Console Core Web Vitals report:, groups your site's URLs by performance status. The fastest way to find your worst pages at scale.
- Juicydesigns free SEO tools: a set of free tools for South African site owners to check speed and SEO metrics without a paid subscription.
For deeper reading on Core Web Vitals and image optimisation, the Juicydesigns blog covers both with South African examples and practical implementation steps.
FAQ
Does website speed directly affect Google rankings?
Yes. Google confirmed Core Web Vitals as a ranking signal under its Page Experience update. Speed functions as a tiebreaker, it helps determine rank when content quality between competing pages is similar.
What are the Core Web Vitals thresholds I need to pass?
LCP must be 2.5 seconds or under, INP must be 200ms or under, and CLS must be 0.1 or under. Google measures these at the 75th percentile of real user data over 28 days.
How do I check my site's real-user speed data?
Open Google Search Console and go to Experience > Core Web Vitals. This shows field data grouped by URL status. You can also paste any URL into Google PageSpeed Insights and read the "Discover what your real users are experiencing" section.
How long does it take to see ranking improvements after fixing speed?
CrUX field data updates on a 28-day rolling window, so allow 4-6 weeks after deploying fixes before evaluating whether scores have improved in Search Console or PageSpeed Insights.
Can Juicydesigns help with a speed audit for my South African site?
Yes. Juicydesigns runs field-data-first speed audits for South African businesses, identifying failing URLs, diagnosing root causes, and implementing fixes tied to measurable conversion and ranking outcomes. Contact the team via the SEO services page to get started.
What role does page load speed play in lead generation for South African websites with varying internet speeds?
Speed decides how many visitors ever see your offer. South African traffic spans fibre, LTE and constrained mobile data, so a page tuned on a fast desktop connection can be unusable on a phone outside a metro. Every second before the first meaningful paint loses visitors who never reach the form. Optimise the largest image, defer non-essential scripts and test on a throttled mobile connection rather than on office fibre.
Recommended
- Website Speed: Why It Matters & How to Get Faster | Juicy Designs
- Website Speed, Performance and Image Optimisation (2026)
- Redesign Your Website Without Losing SEO Rankings | Juicy Designs
- A CRO Checklist for South African Websites (2026) | Juicy Designs