Page speed is one of the few digital marketing investments that simultaneously improves SEO rankings, conversion rates, and user satisfaction. A faster site ranks higher, converts more visitors, and creates a better customer experience — all from the same underlying technical work. Yet most business websites perform well below what's achievable, with avoidable speed problems that have been present since the site was built.
This guide explains what actually makes websites slow, which fixes have the highest impact, and how to measure whether speed improvements are delivering business results.
The business case: what slow pages actually cost
Amazon measured that each 100ms of latency cost 1% in revenue
Google research shows a 1-second delay in mobile load time reduces conversion by 20%
53% of mobile visitors abandon a page that takes more than 3 seconds to load
A 0.1-second speed improvement improves conversion rates by 8% for retail sites
These numbers aren't abstract. For a business website that generates 1,000 monthly leads, moving from a 5-second load time to a 2-second load time could add 100–200 additional monthly leads from the same traffic — purely from improved conversion rate. Add the SEO ranking uplift from passing Core Web Vitals thresholds, and the ROI from speed optimisation is often faster and larger than from equivalent investment in content or link building.
What actually makes websites slow
The causes of slow website speed are mostly predictable and mostly fixable. In order of frequency and impact:
- Unoptimised images: the single most common cause of slow load times. Full-resolution JPEGs uploaded directly from a camera, not compressed or converted to modern formats. The fix: convert all images to WebP format, compress to the minimum acceptable quality (usually 80–85%), and serve responsive images at the correct size for each device.
- Render-blocking JavaScript: scripts that load in the <head> of your HTML block the page from rendering until they've finished loading. The fix: defer non-critical JavaScript (analytics, chat widgets, social sharing buttons) to load after the main page content.
- No browser caching: without cache-control headers, browsers re-download the same files on every visit. The fix: configure cache-control headers with appropriate max-age values for static assets (CSS, JavaScript, images).
- No Content Delivery Network (CDN): serving all assets from a single server location means users far from that server experience higher latency. The fix: use a CDN (Cloudflare, AWS CloudFront, etc.) to serve static assets from servers geographically close to each user.
- Too many third-party scripts: each tracking pixel, chat widget, analytics tool, and social media button adds network requests and JavaScript execution time. Audit every third-party script and remove those that don't justify their performance cost.
- Unoptimised database queries (for CMS sites): WordPress sites with poorly configured databases, too many plugins, or no server-side caching can be slow regardless of asset optimisation. Server-side caching (WP Rocket, W3 Total Cache) and query optimisation address this layer.
Core Web Vitals: the Google ranking signal
Google's Core Web Vitals are three specific speed metrics that affect search rankings: Largest Contentful Paint (LCP — time until the largest visible content element loads, target under 2.5 seconds), Interaction to Next Paint (INP — responsiveness to user interaction, target under 200ms), and Cumulative Layout Shift (CLS — visual stability, target under 0.1).
Pages failing these thresholds have a confirmed ranking disadvantage in competitive SERPs. The Google Search Console Core Web Vitals report shows which pages have 'Poor' or 'Needs Improvement' status — these are the highest-priority pages for speed work.
How to measure and monitor speed
Use three tools in combination. Google PageSpeed Insights (pagespeed.web.dev) provides field data from real users alongside lab data, with specific improvement recommendations. Google Search Console Core Web Vitals report shows performance at the page group level using real-world Chrome data. WebPageTest.org provides detailed waterfall analysis showing exactly which assets are creating bottlenecks. Set a baseline measurement before starting speed work, and re-measure after each significant change.
Speed optimisation is included in every website we build and is available as a standalone service for existing sites. A typical small business website can achieve 40–60% load time reduction through image optimisation, caching configuration, and script deferral alone — without touching design or content.
Build my proposal