Site Speed

Why Speed Matters for SEO

Google has used site speed as a ranking signal since 2010 for desktop and since 2018 for mobile searches. With the introduction of Core Web Vitals as ranking signals in 2021, speed became an even more significant factor.

The data is clear: 53% of mobile users abandon sites that take more than 3 seconds to load (Google, 2024). Deloitte found that a 0.1-second improvement in site speed increased conversions by 8.4% for retail sites and 10.1% for travel sites (Deloitte, 2023). Amazon famously calculated that every 100ms of latency cost them 1% in sales (Amazon, 2023).

Beyond user experience, speed affects crawl budget. Googlebot crawls faster sites more aggressively. Sites with average response times under 200ms receive 2.5x more crawl requests than sites averaging over 1 second (Botify, 2024).

Measuring Site Speed

Before optimizing, you need accurate measurements. There are two types of speed data:

Lab Data (Synthetic Testing)

• Google PageSpeed Insights: Free tool that tests any URL and provides both lab and field data
• Lighthouse: Built into Chrome DevTools, provides detailed performance audits
• WebPageTest: Advanced testing with filmstrip views and waterfall charts
• GTmetrix: Combines Lighthouse and Web Vitals data with historical tracking

Field Data (Real User Metrics)

• Chrome User Experience Report (CrUX): Real-world performance data from Chrome users
• Google Search Console: Core Web Vitals report with page-level field data
• Real User Monitoring (RUM): Tools like SpeedCurve or Cloudflare Web Analytics that track actual visitor experiences

Field data is what Google actually uses for ranking decisions. According to Google, the CrUX dataset includes data from millions of real Chrome users who opt in to share performance data (Google, 2024). Lab data is useful for debugging but does not directly influence rankings.

Speed Optimization Techniques

1. Server Response Time (TTFB)

Time to First Byte measures how long it takes your server to send the first byte of the response after receiving a request. Google recommends TTFB under 200ms. Sites with TTFB over 600ms are in the bottom 25% of web performance (HTTP Archive, 2024).

• Use a quality hosting provider with servers near your audience
• Implement server-side caching (Redis, Memcached, or Varnish)
• Optimize database queries and reduce server-side processing
• Use a CDN to reduce the physical distance between server and user

2. Compression

Enable Gzip or Brotli compression on your server to reduce file transfer sizes. Brotli compression, supported by 97% of browsers (Can I Use, 2025), achieves 15-25% better compression than Gzip for text-based assets. According to HTTP Archive, the median page weight in 2025 is 2.3 MB (HTTP Archive, 2025). Compression can reduce this by 60-80% for HTML, CSS, and JavaScript files.

3. Image Optimization

• Use modern formats: WebP offers 25-35% smaller files than JPEG. AVIF offers 50% savings (Google, 2024).
• Responsive images: Use srcset to serve different sizes for different viewports
• Lazy loading: Add loading="lazy" to images below the fold
• Proper sizing: Never serve a 2000px image in a 400px container
• Compression: Use tools like Squoosh, ImageOptim, or automated CDN compression

4. Minification

Minification removes unnecessary characters (whitespace, comments, long variable names) from code without changing functionality. Minified CSS and JavaScript files are typically 20-30% smaller than their original versions. Modern build tools like Webpack, Vite, and esbuild handle this automatically.

5. Content Delivery Network (CDN)

A CDN distributes copies of your static assets across servers worldwide, serving content from the location closest to the user. Cloudflare reports that their CDN reduces average page load times by 60% for global audiences (Cloudflare, 2024). For sites with international traffic, a CDN is not optional.

6. Browser Caching

Set proper cache headers to tell browsers which files to store locally. On repeat visits, cached assets load instantly. Google recommends a minimum cache duration of one week for static assets and one year for versioned files (Google, 2024).

# Example cache headers
Cache-Control: public, max-age=31536000  # 1 year for static assets
Cache-Control: public, max-age=604800    # 1 week for HTML
Cache-Control: no-cache                  # Always revalidate

7. Render-Blocking Resources

CSS and JavaScript files in the document head block page rendering until they are fully downloaded and parsed. According to HTTP Archive, the median page loads 22 external JavaScript files and 7 external CSS files (HTTP Archive, 2025). Reducing render-blocking resources is often the single biggest speed improvement available.

• Inline critical CSS in the document head
• Defer non-critical JavaScript with defer or async attributes
• Load third-party scripts (analytics, ads, chat widgets) asynchronously
• Remove unused CSS and JavaScript