An Intro to Optimising WordPress

WordPress runs a huge slice of the web because it's flexible and easy to build on. That same flexibility is why it can get slow: every theme, plugin, image, and third-party script you add is more work for the server and the browser. A fast site keeps the visitors you worked hard to earn, ranks better in search, and turns more visits into enquiries and sales. Here's what actually makes a difference in 2026 — and which parts are your host's job versus yours.

First, know what "fast" means now

Google measures real-world speed with three Core Web Vitals: how quickly the main content appears (LCP, 2.5 seconds or less), how quickly the page reacts when someone taps or clicks (INP, 200 milliseconds or less), and whether things jump around while loading (CLS, 0.1 or less). These come from real visitors' browsers, not a lab test. For the fuller picture, read our intro to Core Web Vitals.

To check your own site, use Google's free PageSpeed Insights or the Core Web Vitals report in Search Console. Read the "real users" data first; the lab score underneath is a diagnosis, not the verdict.

Start with hosting, caching, and PHP

This is the single biggest lever, and almost none of it lives in your content.

• WordPress-tuned hosting means the server starts sending each page sooner. Cheap shared hosting stacks hundreds of sites on one tired machine, so your pages wait in a queue before they even begin loading.
• Server-level caching stores a ready-made copy of each page so the server hands it over instantly instead of rebuilding it from the database every visit. Done at the server (nginx or LiteSpeed), this is faster and more reliable than a caching plugin bolted on inside WordPress. If your host doesn't do it, WP Rocket or LiteSpeed Cache are solid plugin fallbacks.
• A current PHP version. PHP 8.2 or 8.3 is noticeably faster than the old 7.x releases, which no longer get security fixes. A host still defaulting to PHP 7 is a red flag on its own.
• HTTP/2 or HTTP/3 with a valid SSL certificate. Modern connections load many files at once. Any competent host provides this by default.

On managed hosting all of this is handled for you. On basic hosting you're left configuring and babysitting it yourself.

Keep the theme and plugins lightweight

• Choose a well-coded, lightweight theme. WordPress 6.x ships with the block editor and Site Editor built in, and modern block themes are lean because they only load styles for the blocks a page actually uses. Older, heavy page-builder themes often ship code for features you'll never touch.
• Use fewer plugins. Every active plugin adds code that runs on each page load. Twenty plugins doing a little each can be slower than five doing a lot. Remove anything you're not really using — especially plugins that load scripts on every page for a feature used on one.

This part is mostly yours. A good host can tell you which plugin is slow; only you can decide whether it earns its place.

Optimise your images

Images are usually the heaviest thing on a page, and they're where non-technical owners lose the most speed.

• Right-size them. Don't upload a 4000px photo to display it at 800px.
• Use modern formats like WebP or AVIF. They look the same as a JPEG or PNG at a fraction of the file size, and WordPress can generate WebP automatically on upload.
• Lazy-load below the fold. WordPress does this by default now, so images lower on the page only load as the visitor scrolls. Just make sure your main hero image is not lazy-loaded, or your LCP suffers.

Good tooling and hosting can automate most of this — converting and compressing on upload — so it isn't a chore every time you add a photo.

Use a CDN

A content delivery network keeps copies of your site's files on servers around the world and serves each visitor from the nearest one. It also absorbs traffic spikes and takes load off your origin server. Most managed hosts include one.

Keep everything updated, and watch third-party scripts

• Update WordPress core, themes, and plugins. Updates aren't just security patches — they routinely include performance work. On managed hosting, updates are applied and tested for you.
• Minimise third-party scripts. Chat widgets, analytics tags, embedded videos, and social feeds each call someone else's server, and you don't control how fast it answers. They're the most common cause of a poor INP score. Keep the ones that earn their place; cut the rest.

The short version

The biggest wins — fast hosting, server-level caching, current PHP, a CDN, automatic image handling, and updates — are infrastructure work, not things you tweak in your posts. That's the part a good managed host should be quietly handling for you. What's left on your side is smaller and more visible: a lean theme, fewer plugins, right-sized images, and a firm hand with third-party scripts.