— all systems operational
HCWeb Hosting Centre
WordPress

How to speed up a slow WordPress site

Why WordPress sites get slow and the fixes that actually move the needle — in priority order, from quick wins to hosting.

Published 7 min read

A slow site costs you visitors and sales — people leave, and Google’s Core Web Vitals factor speed into rankings. The good news is that most WordPress slowness comes from a short list of fixable causes. Here they are, roughly in order of impact-for-effort.

First, measure (don’t guess)

Run your site through a free tool like Google PageSpeed Insights or GTmetrix before changing anything. It tells you where the time goes — big images, slow server response, render-blocking scripts — so you fix the real bottleneck instead of guessing. Test again after each change so you know what helped.

1. Set up caching

Caching is the highest-impact change for most WordPress sites. Instead of rebuilding every page from the database on every visit, the server stores a ready-made copy and serves that — often several times faster.

  • Use a reputable caching plugin (WP Super Cache, W3 Total Cache, or LiteSpeed Cache if your host runs LiteSpeed).
  • On our Business and above plans, the LiteSpeed web server does server-level caching that’s faster than any plugin-only setup.

2. Optimise your images

Images are the most common cause of slow pages — a single unoptimised photo straight off a phone can be several megabytes.

  • Resize images to the dimensions they’re actually displayed at. A 4000px-wide photo shown at 800px is wasted weight.
  • Compress them (TinyPNG, ShortPixel, or an image-optimisation plugin).
  • Use modern formats like WebP, which are much smaller than JPEG/PNG.
  • Lazy-load images so off-screen ones don’t load until the visitor scrolls to them (WordPress does this by default now).

3. Cut down on plugins

Every active plugin adds code that runs on your pages. The problem is rarely the number so much as a few heavy or poorly built ones.

  • Deactivate and delete plugins you don’t use.
  • Identify the heavy hitters (a tool like Query Monitor shows which plugins add the most load).
  • Replace bloated multi-purpose plugins with lighter, single-purpose ones where you can.

4. Use a lean theme

Some “do everything” themes and page builders load enormous amounts of CSS and JavaScript on every page. A lightweight, well-coded theme can be dramatically faster than a feature-stuffed one. If you’re rebuilding, favour speed.

5. Keep PHP and the database healthy

  • Run a current PHP version. Newer PHP is significantly faster — in the Enhance control panel you can switch any site up to the latest PHP 8.5. (Older versions are there for legacy plugins, but they’re slower.)
  • Tidy the database. Old post revisions, spam comments, and leftover tables from removed plugins bloat it over time. A plugin like WP-Optimize cleans this up.

6. Consider a CDN

A content delivery network stores copies of your static files (images, CSS, scripts) on servers around the world, serving each visitor from a nearby one. If you have an international audience, a CDN like Cloudflare helps. If your audience is almost entirely Australian and your server is in Australia, the benefit is smaller — which brings us to the most overlooked factor.

7. The factor people forget: where your server is

You can optimise everything above and still be slow if your server is physically far from your visitors. Every request to an overseas server makes a longer round trip. For an Australian audience, hosting on Australian servers shortens that trip on every single page load — and no plugin can make up for distance.

The other half of this is the server’s own response speed — “Time to First Byte.” Cheap, overcrowded shared servers respond slowly no matter how lean your site is. Faster storage (NVMe), a performance web server (LiteSpeed), and fewer accounts per machine all cut that number.

When it’s the hosting, not the site

If your site is well-optimised — caching on, images compressed, few plugins — and it’s still slow, especially at busy times of day, you’ve likely outgrown a budget shared plan. Signs include pages that are quick at 2am but sluggish at midday, or occasional “503” errors under load. See understanding resource limits for the full list.

That’s exactly the gap our Business hosting is built for: LiteSpeed, NVMe storage, and fewer neighbours per server. If you want a second opinion on whether it’s your site or your host, open a ticket — we’ll look at your actual numbers before recommending anything.

Tags: wordpress speed slow website page speed caching performance core web vitals
Was this helpful?

Let us know — or open a ticket if you're still stuck.