Here's an uncomfortable number to start with: a big chunk of people will leave a website if it takes more than about three seconds to load. Not "get annoyed." Leave. Hit back, gone, off to a competitor — before they've seen a single thing you offer.

And here's the part that makes it sting: your site is almost certainly slower than you think it is, and you're the last person who'd notice. So let's talk plainly about why sites get slow, how to actually check yours, and the handful of fixes that make the biggest difference — no jargon you need a developer to translate.

Why speed matters more than it seems

Speed isn't a vanity metric or a thing only nerds care about. It hits you in three concrete places.

It costs you visitors directly. Every second of load time bleeds off people who won't wait, and on mobile — where a lot of your traffic is — patience is even shorter. A slow site is a leaky bucket: you can pour all the marketing you want into the top, but if it takes five seconds to load, a big share pours straight out the bottom before they ever arrive.

It costs you money. Those aren't just "visitors," they're potential customers who left before they could contact you, book you, or buy from you. There are well-documented cases where shaving even a fraction of a second off load time measurably lifted sales — speed is a direct conversion lever, not a technical footnote.

And it costs you with Google. Site speed is part of how Google judges your pages, through a set of measures called Core Web Vitals. They influence rankings as a supporting signal — not the single biggest factor (content quality and relevance still lead), but a real one, and notably in its March 2026 core update Google tightened the main loading-speed threshold and made responsiveness a primary ranking signal. Translation: slow sites don't just lose impatient humans, they get quietly ranked below faster competitors.

Why you think your site is fast (and why you're wrong)

This is the trap nearly every business owner falls into. You visit your own site, it loads quickly, you conclude it's fine. But you are the worst possible judge of your own site's speed, for three reasons.

Your browser has it cached. You've been there before, so your computer has saved a lot of the site and serves it up fast. A brand-new visitor's browser has none of that and has to download everything fresh — a completely different, slower experience.

You're probably on good gear and good wifi. You might be on a fast computer with solid internet. A chunk of your visitors are on an older phone, on patchy mobile data, in a parking lot. Your site has to be fast for them, not for you at your desk.

And you're emotionally invested. You want it to feel fast, so it does. That's not a measurement; it's a hope.

The only way to actually know is to test it with a tool that measures the real thing, instead of trusting your own cached, optimistic, desktop impression.

How to check yours (free, takes two minutes)

You don't need to hire anyone to find out where you stand. Google PageSpeed Insights is the standard free tool — it pulls both real-user data and a simulated lab test. Pop your URL in, and it grades your site and flags what's slowing it down.

It'll show you scores for those Core Web Vitals I mentioned. In plain English, the three that matter are:

• Loading (the jargon is "LCP") — how fast the main content actually shows up. Google now wants this under about 2 seconds, tightened from 2.5.
• Responsiveness (the jargon is "INP") — how quickly the page reacts when someone taps or clicks. Good is under 200 milliseconds, and it's the metric most sites actually fail in 2026.
• Visual stability (the jargon is "CLS") — whether things jump around as the page loads (you go to tap a button and it leaps, and you hit an ad instead). Good is under 0.1.

Two things to remember when you test: check the mobile score, not just desktop — mobile is usually worse and usually where most of your visitors are — and don't panic at a scary number. The tool also hands you a prioritized list of what's dragging you down, which is the genuinely useful part.

Why sites get slow in the first place

When PageSpeed flags your site, the cause is almost always one or more of a short list of usual suspects. The good news: they're the same culprits over and over, and most are fixable.

Giant images. This is the number one cause, by a mile. People upload a photo straight off their phone or camera — a massive, multi-megabyte file — and drop it on the page at full size. The browser then has to haul that enormous file down before it can show anything. One oversized hero image can single-handedly tank your load time. Images are usually both the biggest problem and the easiest fix.

Too many plugins. On WordPress especially, every plugin you add can pile on more code the page has to load. A site carrying twenty plugins — half of them forgotten, doing nothing useful — is dragging dead weight on every single visit.

Cheap or overloaded hosting. Rock-bottom shared hosting crams hundreds of sites onto one server. When everyone's busy, everyone's slow. Hosting is the foundation; if it's weak, no amount of tweaking on top fully fixes it.

No caching. Without caching, your site rebuilds itself from scratch for every visitor every time — wasteful and slow. Caching saves a ready-made version and serves it instantly. Most slow WordPress sites simply don't have it set up.

Bloated themes and page builders. Some themes and builders generate heavy, messy code. The site looks fine but it's lugging around far more under the hood than it needs to. (Worth noting: this is exactly the kind of thing a well-built site avoids from the start.)

Third-party clutter. Every tracking script, chat widget, social feed, ad network, and fancy font you bolt on makes a request to someone else's server, and each one adds drag. Five "small" add-ons quietly become a big slowdown — and third-party scripts are a leading cause of that responsiveness metric failing.

No lazy loading. By default, a page may try to load every image at once, even the ones way down at the bottom nobody's scrolled to yet. Lazy loading tells it to load images only as they're about to come into view, so the top of the page appears fast.

The handful of fixes that actually move the needle

You could chase a hundred micro-optimizations, but a small number of fixes deliver most of the gain. In rough order of impact:

1. Fix your images. Compress and resize them before (or as) they go up, serve them in modern formats, and never upload a 4000-pixel photo to display in a 600-pixel space. This one change alone often transforms a site's speed. If you do nothing else, do this.

2. Turn on caching. Add a caching solution (on WordPress, a caching plugin; some good hosts bake it in). It's one of the highest-impact, lowest-effort wins available.

3. Get decent hosting. If you're on the cheapest shared plan and the site's still slow after the easy fixes, better hosting raises the whole floor. It's the foundation everything else sits on.

4. Cut the dead weight. Go through your plugins and third-party scripts and kill anything you're not actually using. Every one you remove is code that no longer has to load. Be ruthless — most sites are carrying junk.

5. Enable lazy loading. Usually a simple setting or small plugin, and it makes the top of your pages appear noticeably faster.

6. Tidy the fonts and extras. Limit yourself to a couple of font weights, and drop the widgets and embeds you don't genuinely need. Each one you remove is a request you're no longer waiting on.

Notice these are mostly fixes, not rebuilds — which means a slow site rarely needs replacing. It needs the drag removed. (Yes, that connects to something I've written about before: most "my site is broken" problems are a handful of fixable things, and speed is squarely one of them.)

The honest caveat: don't chase a perfect score

Here's where I'll talk you down a little, because speed optimization has a rabbit-hole problem.

PageSpeed Insights gives you a score out of 100, and it is genuinely addictive to want a perfect 100. Resist it. The difference between a 75 and a 95 is usually worth chasing; the grind from 95 to 100 often means hours of fiddling for a payoff no human visitor will ever feel. The score is a guide, not a religion. What actually matters is the real experience — does the page show up fast, respond when tapped, and stay still while it loads? A site that loads in two seconds with a score of 85 is beating a site that loads in five with a "better-on-paper" anything.

Don't let a tool's number become the goal. The goal is a site that doesn't make people wait. Get it comfortably fast, make sure it passes the Core Web Vitals thresholds, and then go run your business instead of refreshing the score.

And one more honest note: some of this you can do yourself in an afternoon (compress your images, delete dead plugins). Some of it — diagnosing why a stubborn site is slow when the obvious stuff is already handled — is genuinely fiddly and worth handing to someone who does it all the time. Knowing which bucket you're in saves you a frustrating weekend.

Three speed myths worth dropping

A few beliefs send people in the wrong direction, so let's clear them out.

"I'll just buy a faster, fancier theme." Often backwards. Many of the flashiest premium themes are heavier, not lighter — more features means more code to load. A clean, simple setup usually beats a feature-stuffed one on speed. Switching themes can help, but only if the new one is genuinely lean, not just prettier.

"I'll upgrade my hosting and that'll fix it." Better hosting raises the floor, but it won't rescue a page weighed down by a 6-megabyte image and twenty plugins. If you throw money at a faster server without fixing the actual drag, you've made a slow site slightly less slow at higher cost. Fix the obvious stuff first, then judge whether hosting is the bottleneck.

"It's slow, so I need a whole new site." Almost never true. Speed problems are some of the most fixable problems there are — compress the images, add caching, cut the clutter. You're removing weight from the existing site, not rebuilding it.

What to do this week

If you've never checked, do this: run your homepage and one or two key pages through PageSpeed Insights, on mobile. Write down the score and skim the list of issues it gives you. If giant images are flagged (they almost always are), that's your first and biggest win — handle those before anything else. Then look at caching, then at the plugin and script clutter.

Even just the image fix and caching will, for most slow sites, turn a sluggish experience into a snappy one. You don't have to do everything. You have to do the few things that matter.

The bottom line

Your visitors are deciding whether to stay in about three seconds, and they're making that decision on a fresh, uncached, mobile experience that's almost certainly slower than the one you see at your desk. A slow site quietly leaks the visitors, customers, and search ranking you worked to earn — and the causes are usually a short, fixable list led by oversized images.

So go check. It's free and it takes two minutes. You might find you're in great shape. More likely you'll find a couple of easy fixes standing between you and a site that doesn't send people running before they've even seen it. Either way, you'll know — which beats assuming you're fast because it feels fast to you.