Page speed is a direct Google ranking factor and has an enormous impact on conversion rates. Research consistently shows that every second of additional load time reduces conversions — for e-commerce sites, the effect can be measured in direct revenue loss.
The good news is that PageSpeed improvements are often among the most straightforward technical SEO wins available. A handful of focused fixes can take a site from a score of 40 to over 80.
Understanding the PageSpeed Score
Google's PageSpeed score (via PageSpeed Insights) is a composite score based on six lab metrics. LCP and Total Blocking Time have the highest weighting. The score is out of 100: - 90-100: Good (green) - 50-89: Needs Improvement (orange) - 0-49: Poor (red)
The score is a useful directional indicator, but remember that Google uses real-user field data (Core Web Vitals) for ranking, not the lab score. Fix the underlying issues, not just the number.
Fix 1: Optimise Images (Typical gain: 8-15 points)
Images are the single biggest contributor to page weight on most sites. To optimise:
Convert to WebP or AVIF — WebP files are typically 25-35% smaller than JPEG at equivalent quality. AVIF is newer and can be 30-50% smaller than WebP. Compress images — Even in modern formats, images often have room for compression. Tools like Squoosh, TinyPNG, or ImageOptim can reduce file sizes by 30-60%. Add explicit dimensions — Setting width and height attributes on every image allows the browser to calculate layout before the image loads, improving CLS and LCP. Lazy load below-fold images — Addloading="lazy" to any image not visible in the initial viewport. Never lazy load your LCP image.
Use responsive images — Use srcset and sizes attributes to serve appropriately sized images for different screen sizes.
Fix 2: Add Image Dimensions (Typical gain: 5-10 points)
This is one of the quickest wins available. For every image element, add explicit width and height:
``html
`
This prevents layout shift as the page loads and significantly improves CLS scores.
Fix 3: Defer Render-Blocking Resources (Typical gain: 10-20 points)
Render-blocking resources are JavaScript and CSS files that prevent the browser from rendering page content until they've fully downloaded and processed.
For JavaScript:
- Add defer attribute to non-critical scripts
- Add async` for scripts that don't depend on DOM order
- Move non-critical scripts to the bottom of the body
For CSS: - Inline critical CSS (the styles needed for above-fold content) - Load non-critical CSS asynchronously
Fix 4: Enable Server-Side Caching (Typical gain: 15-25 points)
Server response time is a fundamental performance bottleneck. If your TTFB (Time to First Byte) is over 600ms, users are waiting over half a second before any content starts loading.
The fastest fix is server-side caching: - WordPress: WP Rocket, W3 Total Cache or LiteSpeed Cache - Generic: Varnish, Redis, or Nginx FastCGI cache - CDN: CloudFlare or Fastly to serve cached content from servers geographically close to users
A well-configured cache can reduce TTFB from 800ms to under 200ms.
Fix 5: Eliminate Unused JavaScript (Typical gain: 5-15 points)
PageSpeed Insights reports how much JavaScript is downloaded but never executed. Common sources of unused JS include: - Analytics tags for services you no longer use - Retired A/B testing scripts - WordPress plugins that load JS sitewide when only needed on specific pages - jQuery loaded by themes but barely used
Use Chrome DevTools Coverage tab to identify exactly which scripts have high unused percentages. Remove what you can; defer or conditionally load the rest.
Fix 6: Use a CDN
A Content Delivery Network serves your static assets (images, CSS, JS) from servers geographically close to each user. For international sites or sites with users spread across a country, a CDN can reduce asset load times by 50-80%.
Most managed hosting providers include CDN options. Cloudflare's free tier is effective for most small to medium sites.
The Compound Effect
These fixes are most powerful in combination. A site that optimises images, fixes render-blocking resources, and enables caching typically sees a 30-50 point improvement in PageSpeed score — and more importantly, a significant reduction in real-user LCP and CLS values that directly affect rankings and conversions.