Website Speed Is Killing Your Sales: Here’s How to Fix It
There’s a number I want you to look up right now, before you keep reading.
Go to pagespeed.web.dev, paste in your website, hit analyze, and wait about 30 seconds. Look at the mobile score. Not the desktop one — the mobile one, because that’s where most of your traffic actually lives.
If that number is under 70, you have a real problem, and it’s almost certainly costing you money every month you don’t fix it. If it’s under 50, you’re hemorrhaging.
I’ll explain what the number actually means, why most “speed fixes” don’t work, and what actually moves the needle.
Why speed matters more now than five years ago
A decade ago, site speed was a nice-to-have. In 2026, Google uses it as a ranking signal through Core Web Vitals, mobile users abandon slow sites within seconds, and every major study confirms the same basic math: every additional second of load time kills a significant chunk of your conversion rate.
But here’s the part that doesn’t get talked about enough. Speed doesn’t just affect whether people convert — it affects whether people even see your site in the first place. Google rewards fast sites with better rankings, especially on mobile. A slow site gets buried. A fast site gets surfaced. Compounded over months, that difference in visibility is enormous.
If you’re running ads to your site, speed hits you twice. Google’s ad platform literally scores your landing pages on load time and raises your cost-per-click when they’re slow. I’ve seen businesses cut their ad costs by 25% just by fixing their site speed, without changing a single ad.
What “fast” actually means
The Core Web Vitals that Google cares about are three specific measurements:
LCP (Largest Contentful Paint) — how long it takes for the biggest visible element on the page to show up. Should be under 2.5 seconds. This is usually your hero image or the big headline.
INP (Interaction to Next Paint) — how long it takes the page to respond when a user clicks or taps something. Should be under 200 milliseconds. If your menu stutters or buttons feel sluggish, this is what’s failing.
CLS (Cumulative Layout Shift) — how much the page jumps around as it loads. Should be near zero. You’ve experienced this every time you go to tap something and an ad loads and shifts everything down and you tap the ad instead. That rage you felt? That’s bad CLS.
You don’t need to memorize the numbers. You just need to know that PageSpeed Insights checks all three and tells you which ones are broken.
The five things actually slowing your site down
I’ve diagnosed a lot of slow sites. It’s almost always the same few culprits in different combinations.
Enormous images. This is the #1 issue on about 70% of slow sites I look at. Someone uploaded the original photo straight from their phone or camera — a 4,000 pixel wide, 6MB JPEG — and the site is displaying it at 400 pixels but still loading the full file. Multiply by ten images on the homepage and you’re shipping 60MB of images to every mobile visitor.
The fix is boring but real: images should be resized to actual display dimensions, compressed with a tool like TinyPNG or Squoosh, and ideally served in WebP format. On WordPress, a plugin like ShortPixel or Imagify automates this once you set it up.
Too many plugins, and specifically the wrong ones. WordPress sites collect plugins the way junk drawers collect batteries. Every plugin adds code to your site, and some of them add a lot. Sliders, popup builders, contact form plugins with forty features when you needed one — they all stack up.
Audit your plugin list. Anything you installed and aren’t actively using, deactivate and delete. For the ones that stay, check if they’re known to be heavy. Sliders and popup plugins are the usual offenders.
Cheap hosting. If you’re paying $3.99/month for hosting, you’re sharing a server with two thousand other sites, and your response time from the server itself — before anything even loads — is going to be slow. This is a place where spending an extra $15/month actually makes your site measurably faster.
Good hosts in 2026: SiteGround, Cloudways, Kinsta, WP Engine. Stay away from the brands that spend heavily on affiliate marketing and charge $2.95 for the first year.
No caching. Caching means your site saves pre-built versions of pages instead of rebuilding them from scratch every time someone visits. On WordPress, this is what plugins like WP Rocket, LiteSpeed Cache, or FlyingPress do. A properly caching site can be two to three times faster than an uncached one. This should take a few hours to set up correctly and it will pay off every day forever.
Third-party scripts. Every time you embed something — a YouTube video, a live chat widget, a Facebook Pixel, a tracking script, a fancy font from a sketchy provider — you’re letting someone else’s code slow your site down. The fix isn’t to remove everything. It’s to audit what’s on there and remove what you don’t need, then load what’s left asynchronously so it doesn’t block the rest of the page.
What won’t actually help
I want to flag a few things that sound like speed fixes and aren’t.
Switching themes rarely makes a huge difference unless your current theme is catastrophically bloated. If your theme is from a legitimate developer, the theme isn’t your problem.
“Mobile optimization” as a service is usually code for “we’ll tweak your CSS a little.” Real mobile speed comes from the five things above, not from a separate mobile-specific version of your site.
Paying for a CDN alone won’t fix a slow site. CDNs help with global speed by serving your site from a server closer to the visitor. If your visitors are mostly local and your site is slow because of huge images and too many plugins, a CDN is lipstick on the problem.
The order I’d fix things in
If I were standing next to you right now, this is what we’d do in order:
First, compress and resize every image on the site. You’ll probably cut your page weight in half.
Second, audit your plugins and delete anything you don’t actively use.
Third, install a real caching plugin and configure it properly. Not the free defaults — actually set up the options.
Fourth, if your PageSpeed score is still under 80, look at your hosting and seriously consider moving.
Fifth, only now, worry about fine-tuning CSS, deferring JavaScript, and the smaller stuff.
Most sites I touch jump 30 to 50 PageSpeed points from just the first three steps. If you’re technically comfortable and want to DIY it, that’s genuinely the path. If you’d rather have someone else do it, I handle speed overhauls as a specific service — usually a one-time fix rather than an ongoing engagement.
The business case in one sentence
A site that loads in two seconds instead of five will rank higher, convert better, cost less to advertise against, and feel more professional to every visitor. Nothing else you can do to your website delivers that kind of compound return.
If you’ve got your PageSpeed score in front of you and it’s ugly, I’ll take a look for free and tell you honestly what’s causing it and whether it’s worth fixing yourself or handing off. Send it over here.
