The speed fixes that actually matter

You can spend a week chasing a perfect Lighthouse score, or a morning fixing the three things that cause most of the problem on most small business websites. The second is usually the better trade.

Google's Core Web Vitals measure three things a visitor can feel: how quickly the main content appears, how quickly the page responds when tapped, and whether the layout jumps around while loading. Almost every slow small business site fails the same way.

Fix one: your images are far bigger than they need to be

This is the single most common cause, and the easiest to fix. A photo straight from a phone or a stock library can be 4000 pixels wide and several megabytes. Displayed in a 600 pixel column, every one of those extra pixels was downloaded for nothing, and on mobile data it is paid for in seconds.

What to do:

• Resize before uploading. Nothing on a typical site needs to exceed about 2000 pixels wide, and most images need far less.
• Use a modern format. Converting to WebP typically cuts file size by half or more at the same visible quality. On this site it took the photography from roughly 4 MB to 1.6 MB.
• Serve a smaller file to phones using srcset, so a 400 pixel screen is not downloading a desktop-sized image.
• Lazy-load anything below the fold, but never the main hero image, which should load as early as possible.

The related fix: reserve space

If an image has no declared dimensions, the browser does not know how much room to leave, so the text renders first and then jumps down when the image arrives. That jump is what Cumulative Layout Shift measures, and it is infuriating when you have just tapped a link. Give images their width and height, or a fixed aspect ratio in CSS. Same for ad slots and embedded videos.

Fix two: you have too many plugins doing too little

On WordPress, every active plugin can add its own CSS and JavaScript to every page, whether or not that page uses the feature. A slider plugin used once on the homepage often loads its assets everywhere. Thirty plugins is not thirty times worse than one, but it is rarely far off.

A practical audit: list your active plugins and, for each, answer what it does and what would break without it. In most site audits I do, several can simply be deleted, one or two are doing something a few lines of code would do more cheaply, and one is a genuine performance problem all by itself.

Page builders deserve a specific mention. They are wonderful for the person building the page and expensive for everyone visiting it, because the flexibility ships as extra markup and stylesheets on every load. That is a reasonable trade if your team edits pages weekly. It is a poor one if the site has not changed in a year.

Fix three: your fonts are blocking the page

Custom fonts are usually loaded from a third-party server. That means an extra DNS lookup, an extra connection, and a file that must arrive before the browser will paint text. Meanwhile the visitor sees nothing, or sees text appear and then visibly change shape.

What to do:

• Self-host the font files on your own domain, which removes an entire third-party round trip. It is also better for privacy: your visitors are not announced to a font provider.
• Use font-display: swap so text renders immediately in a fallback font rather than staying invisible.
• Preload the one or two faces used above the fold, and no more.
• Cut the number of weights. Every additional weight is another file. Most sites genuinely need two or three.

What matters much less than people think

Once those three are handled, the remaining gains get small quickly:

• Chasing 100 out of 100. The difference between 85 and 100 is rarely perceptible to a visitor. The difference between 35 and 85 is the difference between leaving and staying.
• Switching hosts first. Faster hosting helps, but it will not rescue a page carrying 8 MB of images. Fix the payload, then judge the host.
• Minification alone. Worth doing, and it saves kilobytes where images are wasting megabytes.
• Desktop scores. Google measures the mobile experience, and so do most of your visitors. Test on mobile, throttled.

How to check your own site in ten minutes

1. Run your homepage and one service page through PageSpeed Insights, on mobile.
2. Ignore the score for a moment and read "Opportunities". Look for "Properly size images" and "Serve images in next-gen formats", which are usually the two biggest.
3. Check the Core Web Vitals block: LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1.
4. Open your site on a phone on mobile data, not office Wi-Fi. That is the real test, and it is the one most sites have never been given.

If the biggest opportunity listed is about images, you already know what to do with your morning.