Site Speed Optimisation

Learn how to improve your website's loading speed for better SEO rankings and user experience. Covers server, image, code, and caching optimisation techniques.

Intermediate10 min readUpdated 04 Mar 2026Bukhosi Moyo

Site speed is a confirmed Google ranking factor and one of the most impactful technical SEO improvements you can make. Faster pages rank higher, convert better, and retain more users. A one-second delay in page load time can reduce conversions by 7% and increase bounce rate by 11%.

Quick Answer
  • Site speed measures how quickly your web pages load and become interactive for users.
  • Google uses page speed as a ranking factor through Core Web Vitals (LCP, INP, CLS).
  • The biggest speed gains come from image optimisation, render-blocking resource elimination, server response time improvement, and caching.
  • Target: LCP under 2.5 seconds, pages fully interactive within 3 seconds.
  • Speed improvements benefit both rankings and conversions — every second matters.

If you want the full breakdown, continue below.

Why Site Speed Matters for SEO

Direct Ranking Factor

Google confirmed site speed as a ranking factor in 2010 (desktop) and 2018 (mobile). Since 2021, Core Web Vitals — which measure real-world speed and responsiveness — are part of Google's page experience ranking signals.

User Experience Impact

Speed directly affects user behaviour:

Load Time Bounce Rate Increase
1–3 seconds +32%
1–5 seconds +90%
1–6 seconds +106%
1–10 seconds +123%

Users expect pages to load within 2 seconds. After 3 seconds, over half will leave.

Crawl Efficiency

Faster sites allow Google to crawl more pages per visit. Slow sites waste crawl budget — Google spends time waiting for pages to load instead of discovering new content.

Measuring Site Speed

Google PageSpeed Insights

The primary tool for measuring site speed. Provides both lab data (simulated) and field data (real user metrics).

URL: pagespeed.web.dev

Key metrics reported:

  • LCP (Largest Contentful Paint) — when the main content finishes loading
  • INP (Interaction to Next Paint) — how quickly the page responds to user input
  • CLS (Cumulative Layout Shift) — how much the page layout moves during loading
  • FCP (First Contentful Paint) — when the first content appears
  • TTFB (Time to First Byte) — server response time

Google Search Console

Core Web Vitals report shows how your pages perform in the real world across your entire site.

Chrome DevTools

The Performance tab provides detailed waterfall charts showing exactly what loads, when, and how long each resource takes.

For detailed metric guidance, see: Core Web Vitals Explained.

Speed Optimisation Techniques

1. Image Optimisation (Biggest Impact)

Images typically account for 50–70% of page weight. Optimisation steps:

  • Compress images — use 75–85% quality for lossy compression (invisible to the eye, 60–80% smaller files)
  • Use modern formats — WebP is 25–35% smaller than JPEG; AVIF is 30–50% smaller
  • Resize to display dimensions — do not serve a 4000px image in a 800px container
  • Implement lazy loading — defer loading images below the fold
  • Specify dimensions — set width and height to prevent layout shifts

For the complete guide, see: Image Optimisation for SEO.

2. Eliminate Render-Blocking Resources

CSS and JavaScript in the <head> block page rendering until they are downloaded and processed.

Solutions:

  • Defer non-critical JavaScript — add defer or async attributes to script tags
  • Inline critical CSS — embed the CSS needed for above-the-fold content directly in the HTML
  • Load non-critical CSS asynchronously — use media="print" or dynamic loading for below-the-fold styles
  • Remove unused CSS/JS — audit for code that is loaded but never executed
  • Code split — load only the JavaScript needed for the current page

3. Server Response Time (TTFB)

Time to First Byte should be under 200ms. Improve with:

  • Better hosting — upgrade from shared hosting to VPS, dedicated, or cloud hosting
  • CDN (Content Delivery Network) — serve static assets from servers geographically close to users
  • Server-side caching — cache rendered pages to avoid regenerating them on every request
  • Database optimisation — optimise queries, add indexes, reduce database calls
  • HTTP/2 or HTTP/3 — modern protocols that load multiple resources simultaneously

4. Browser Caching

Configure caching headers so returning visitors load resources from their browser cache:

Cache-Control: public, max-age=31536000
  • Static assets (images, CSS, JS) — cache for 1 year (use content hashing for cache busting)
  • HTML pages — cache for shorter periods or use revalidation
  • API responses — cache where appropriate with proper invalidation

5. Minify CSS, JavaScript, and HTML

Minification removes whitespace, comments, and unnecessary characters:

  • CSS: 10–20% smaller after minification
  • JavaScript: 20–30% smaller after minification
  • HTML: 5–10% smaller after minification

Most build tools (Webpack, Vite, Next.js) handle this automatically in production builds.

6. Enable Compression

Configure Gzip or Brotli compression on your server:

  • Brotli — 15–20% better compression than Gzip, now widely supported
  • Gzip — universal fallback, still effective

Text-based resources (HTML, CSS, JS, JSON) compress by 60–80%.

7. Reduce Third-Party Scripts

Third-party scripts (analytics, chat widgets, ad networks, social media embeds) are a major speed killer:

  • Audit every third-party script — is it necessary?
  • Load non-essential scripts asynchronously or after page load
  • Use tag managers to control when scripts execute
  • Prefer lightweight alternatives (e.g., Plausible over Google Analytics for better speed)

8. Font Optimisation

Web fonts add download time and can cause layout shifts:

  • Use system fonts where possible (no download required)
  • Self-host fonts rather than loading from external CDNs
  • Use font-display: swap — show fallback text immediately while fonts load
  • Subset fonts — include only the characters you need
  • Preload critical fonts<link rel="preload" as="font">

Speed Optimisation Priority Order

If you can only do a few things, do them in this order:

  1. Compress and resize images — biggest single impact
  2. Enable Brotli/Gzip compression — server configuration change
  3. Defer non-critical JavaScript — prevents render blocking
  4. Enable browser caching — helps returning visitors
  5. Use a CDN — serves content faster globally
  6. Minify CSS and JS — usually automatic with modern build tools
  7. Audit third-party scripts — remove what you do not need
  8. Optimise fonts — swap display and subset

South African Speed Considerations

Speed optimisation is especially important for South African websites:

  • Mobile dominance — the majority of South African internet users browse on mobile devices with varying connection quality
  • Data costs — South African mobile data is expensive; smaller pages directly benefit users
  • Infrastructure variance — connection speeds vary significantly across the country
  • CDN selection — choose a CDN with edge nodes in or near South Africa (Cloudflare has a Johannesburg PoP)
  • Hosting location — if your audience is primarily South African, hosting in South Africa or nearby (Europe at minimum) reduces latency

Key Takeaways

  • Site speed is a confirmed ranking factor through Core Web Vitals.
  • Image optimisation provides the biggest speed improvement for most websites.
  • Target LCP under 2.5 seconds and full interactivity within 3 seconds.
  • The priority order: images → compression → render-blocking → caching → CDN → third-party audit.
  • South African speed optimisation must account for mobile-dominant usage and varying connection quality.

Quick Speed Optimisation Checklist

  • Images compressed, resized, and served in WebP/AVIF format
  • Lazy loading enabled for below-the-fold images
  • Non-critical JavaScript deferred with async/defer attributes
  • Critical CSS inlined, non-critical CSS loaded asynchronously
  • Brotli or Gzip compression enabled on server
  • Browser caching configured for static assets
  • CDN configured for static asset delivery
  • Third-party scripts audited and non-essential ones removed
  • Fonts self-hosted with font-display: swap
  • Core Web Vitals monitored in Google Search Console

Tools & Resources (Coming Soon)

  • Page Speed Checker (Coming soon)
  • Image Compression Tool (Coming soon)
  • Core Web Vitals Monitor (Coming soon)

Related SEO Documentation

Was this helpful?