Page speed affects both your Google rankings and your conversion rate. Every second of extra load time costs you visitors. Here are 10 fixes that actually move the needle, with the highest-impact ones first.
Google officially uses page speed as a ranking signal for both mobile and desktop search. But beyond rankings, speed directly affects user behavior. Slow pages have higher bounce rates, lower engagement, and fewer conversions.
Images account for 60-70% of a typical page's total file size. WebP images are 25-35% smaller than JPEG and 50-80% smaller than PNG at equivalent visual quality. Convert your images to WebP using a tool like Squoosh, or install an image optimization plugin if you're on WordPress (Smush, ShortPixel). Make sure you also specify width and height attributes on every image tag to prevent CLS.
Browser caching stores static files (images, CSS, fonts) on the user's computer after the first visit. Repeat visitors load these files from their local cache instead of downloading them again, which dramatically reduces load time for returning users. Set cache headers to at least 30 days for images and 7 days for CSS/JS. In Apache, this goes in .htaccess; in Nginx, in the server configuration.
Minification removes whitespace, comments, and line breaks from CSS and JavaScript files without changing how they function. A 150KB CSS file often minifies to under 100KB. Use a build tool like Webpack or esbuild, or a WordPress plugin like WP Rocket. This typically saves 10-20% on CSS/JS file sizes with zero visual or functional impact.
JavaScript that runs before the page renders blocks everything else. Add the defer attribute to any script that doesn't need to run during page load: <script src="analytics.js" defer></script>. Analytics scripts, chat widgets, and marketing pixels are all candidates for deferral. This is one of the most effective ways to reduce TBT (Total Blocking Time).
A CDN stores copies of your static files on servers distributed around the world. When a user in Australia visits your site hosted in New York, they load images and scripts from the nearest CDN node instead of the original server. Cloudflare's free plan covers most small sites and typically reduces TTFB (time to first byte) by 30-50% for geographically distant users.
Time to first byte (TTFB) measures how long your server takes to respond. A TTFB over 600ms delays all page rendering. Main causes: slow hosting, no server-side caching, heavy database queries, or PHP processing time on WordPress. Enable server-side caching (OPcache for PHP, Redis for database queries), or upgrade to a faster hosting tier. A well-tuned VPS consistently outperforms shared hosting here.
Render-blocking resources are CSS and JavaScript files in the <head> that the browser must download and process before displaying anything on screen. Move non-critical CSS to the bottom of the page or load it asynchronously. Use the preload link tag for critical CSS that must load first. The PageSpeed Insights report flags specific render-blocking resources on your pages.
Lazy loading defers loading of images that are not visible on screen until the user scrolls to them. Add loading="lazy" to all image tags except your hero image (which should always load eagerly). This reduces initial page weight significantly on image-heavy pages. Most modern browsers support native lazy loading; no JavaScript library is required.
Each redirect adds an HTTP round-trip, typically 100-300ms per redirect. Redirect chains (A redirects to B, B redirects to C) compound this delay. Audit your redirects using Screaming Frog or a browser tool like the Redirect Path extension. Update any internal links pointing to redirected URLs to point directly to the final destination, and eliminate chains wherever possible.
Server-side compression reduces the size of text-based files (HTML, CSS, JavaScript) before they're sent to the browser. Brotli is 15-20% better than Gzip for most text content. Check if your server has compression enabled using Google's PageSpeed Insights — it will flag "Enable text compression" if not. For Apache, add mod_deflate to your .htaccess. Most managed hosting platforms enable this by default.
Run these tests before making changes and record your scores. Then run them again 24-48 hours after applying fixes.
Focus on the mobile scores. Google primarily uses mobile performance for ranking decisions, and mobile scores are almost always lower than desktop.
A plugin update, a new banner image, or an added tracking script can silently destroy a previously good PageSpeed score. SEO Monitor checks your Core Web Vitals every week and alerts you in your Monday report if scores change. You'll catch performance regressions the week they happen, not months later when you notice a traffic drop.
From $9 per site per month.
Get your free weekly SEO reportWhat's a good PageSpeed Insights score?
Scores are 0-100. Google categorizes 90-100 as "Good", 50-89 as "Needs Improvement", and 0-49 as "Poor". For most sites, a mobile score above 70 is a solid target. Getting from 30 to 70 typically has a meaningful ranking impact. Getting from 80 to 95 has diminishing returns compared to other SEO improvements.
Will improving page speed alone boost my rankings?
Speed is one of many ranking signals. Improving a slow page to a fast page removes a ranking disadvantage. It won't overcome a huge deficit in content quality or backlinks. Think of speed as a prerequisite, not a shortcut.
My PageSpeed score is fine on desktop but terrible on mobile. Why?
Mobile tests simulate a mid-range device on a 4G connection, which is significantly slower than a desktop on broadband. Heavy JavaScript is particularly punishing on mobile because mobile CPUs have less processing power. Focus on deferring JavaScript and compressing images to close the gap.
Does my hosting plan affect page speed significantly?
Yes, significantly. Shared hosting typically produces TTFB values of 800ms to 2 seconds. A VPS or managed WordPress host like Kinsta or WP Engine regularly delivers TTFB under 200ms on the same codebase. If your TTFB is consistently over 600ms and you've already addressed caching, upgrading hosting is often the highest-impact single change available.