The Numbers Are Unambiguous
Google's research shows that the probability of a mobile user bouncing increases 32% as load time goes from 1 second to 3 seconds. At 5 seconds, it's 90%. At 10 seconds, it's 123%.
Amazon found that 100ms of additional latency cost them 1% of sales. Google found that slowing search results by 400ms resulted in 8 million fewer searches per day.
Page speed is not a technical nicety. It's a business metric.
Why Page Speed Is an SEO Problem
Core Web Vitals (LCP, CLS, INP) are direct ranking factors - slower sites rank lower, all else being equal.
Crawl budget efficiency - Google allocates a crawl budget to every site. Slow pages consume more of that budget per page, meaning fewer pages get crawled per session. For large sites, this is significant.
Bounce rate and dwell time - slow sites produce higher bounce rates and lower dwell time, both of which are behavioural signals that Google uses to calibrate rankings. A page that users immediately leave signals low quality, regardless of content.
The Most Common Performance Killers
Unoptimised images. Images are typically 50–75% of a page's total byte weight. Serving 2MB JPEG hero images to mobile users is the single most common and most correctable performance problem.
Fix: Convert to WebP or AVIF (typically 30–50% smaller than JPEG at equivalent quality). Implement responsive images with 'srcset'. Use lazy loading for off-screen images.
Render-blocking JavaScript and CSS. Any script or stylesheet in the '<head>' that loads before the page renders is blocking the browser from showing content. Analytics scripts, font loaders, and third-party widgets are frequent offenders.
Fix: Move non-critical scripts to 'defer' or 'async'. Inline critical CSS. Load third-party scripts after the main page content.
No CDN. A server in London serving requests from Singapore adds physical latency that no optimisation can overcome. A Content Delivery Network routes requests to the nearest edge server.
Fix: Use a CDN (Cloudflare, Fastly, AWS CloudFront) for static assets and, where possible, the entire site.
Too many third-party requests. Every third-party script - analytics, chat widgets, A/B testing tools, marketing pixels - adds at least one HTTP request and often blocks rendering. A typical enterprise marketing site has 50+ third-party requests on page load.
Fix: Audit all third-party scripts. Remove any that aren't actively used. Delay non-critical ones (like chat widgets) until after the page is interactive.
No HTTP/2 or HTTP/3. Modern server protocols allow multiple requests to be sent simultaneously over a single connection. Sites still serving over HTTP/1.1 are artificially bottlenecked.
Measuring What Matters
Use Google's PageSpeed Insights for real-user field data and lab diagnostics. Use Chrome DevTools' Network tab to identify the largest and slowest resources. Use Lighthouse for a comprehensive performance report.
Target: LCP under 2.5 seconds, CLS under 0.1, INP under 200ms, Time to Interactive under 3.5 seconds on a mid-range mobile device on 4G.
