Your WordPress site is slow. Probably this.

A message came in asking if a site could “just be made faster” before a campaign went live. That’s how most wordpress speed optimisation conversations start. No detail, just: it’s slow, can you sort it.

The homepage took nine seconds to load on mobile. Nine. Not mysterious, just that nobody had looked at it yet.

That’s usually what it comes down to. Not a rebuild, not a new plugin stack. Knowing where to check first.

It’s almost always the same three things

Images. Plugins. Hosting. Every slow WordPress site I’ve worked on traces back to at least one of these, usually two.

Images are the biggest culprit by far. Photos uploaded straight from a phone or camera, no compression, 5 to 8MB each. Three of those on a homepage and every visitor is downloading 20MB before the page finishes loading. WordPress resizes for display but won’t compress. A plugin like ShortPixel or Imagify handles that. On image-heavy sites it can cut load time significantly by itself, before anything else is touched.

Plugins stack up quietly. Every active one adds code that runs on every page load. Most sites I look at have 30 to 40 installed, a third of them inactive or only used once during setup. Deactivating isn’t enough either. Some run code even when switched off. Delete what’s not actively in use. The leaner the plugin list, the less there is competing for resources on every single request.

Hosting is the one nobody wants to hear because it costs money to fix. Shared hosting means competing for server resources with hundreds of other sites. When that server’s under load, the site is slow and there’s nothing to be done about it from the site side. Moving to managed WordPress hosting is the biggest single performance improvement available without touching a line of code. It changes the ceiling entirely.

Two things that help and are consistently skipped

A caching plugin and a CDN make a real difference on almost every WordPress site, and both are underused.

Caching serves a saved static version of pages instead of rebuilding them from scratch on every visit. Without it, WordPress runs database queries and PHP processes every time someone loads a page, even if nothing has changed since the last visit. WP Rocket is the paid standard. LiteSpeed Cache is a solid free option. Either one is worth setting up before reaching for anything more complicated.

A CDN stores assets on servers closer to where visitors actually are, so content doesn’t have to travel as far. Cloudflare’s free tier handles this reasonably well and takes about twenty minutes to set up. There’s no good reason most sites aren’t using it.

The score is not the goal

Google PageSpeed Insights gives a number out of 100. That number isn’t the point.

A score of 65 that loads in 2.5 seconds on mobile is better, practically speaking, than a score of 90 that takes 4.5 seconds. I saw this consistently when I audited 10 Aussie websites. Slow load times were one of the most common problems, and most site owners had no idea how bad it was until I showed them the number.

Most WordPress speed problems aren’t mysterious. Images nobody compressed, plugins nobody cleared out, hosting that made sense a few years ago but doesn’t anymore. Finding them doesn’t take a developer. It takes knowing where to look, and then actually looking.