Kev Quirk

How To Speed Up WordPress

17 Mar 2021 | ~8 minute read

WordPress has a reputation for being really slow, but that isn't true. This post talks about how I speed up my WordPress site to get a perfect 100 on Google's PageSpeed Insights & Lighthouse speed metrics.

Honestly, there no magic involved here. Speeding up a WordPress site is really simple, it just requires a little bit of forethought and a few quid invested from your wallet.

Why is WordPress slow?

Before we look at ways to speed up WordPress, it's important to understand the problem we're trying to fix. The fact of the matter is, WordPress is not inherently slow; while slowness can come from multiple sources, it's usually caused by one (or both) of the following issues:

  1. Rubbish hosting.
  2. Bad code.

That's really all it boils down to, folks. If you're hosting your site with a shitty shared host, like BlueHost or HostGator, then you're going to have problems.

Conversely, if you have bundled 20+ plugins into your WordPress site so that it does everything except cook your breakfast, then again, you're going to have performance problems.

Same goes for themes. If you have a theme that tries to cater for every possible design permutation possible, there's going to be a tonne of wasted code you're not using.

A typical "multi-purpose" WordPress theme
A typical "multi-purpose" WordPress theme

How fast should a site be?

It's all well and good talking about speeding up WordPress, but what constitutes a fast site? Is a 10 second load time ok? What about 5 seconds? That's pretty quick, right? 3 seconds? Now we're talking, surely?

Well, some clever boffins did some research and established that if your site takes more than 3 seconds to load, 57% of visitors will leave before it's done loading (source).

So the answer is a MAXIMUM of 3 seconds, but make it as quick as possible. For example, this site is running WordPress and according to GTMetrix it loads in 0.6 seconds. I'm happy with that.

Speeding up WordPress

So now we have an idea of what causes WordPress to be slow, let's look at some solutions, shall we? My recommendations for speeding up a WordPress site are 7 fold:

  1. Choose a high quality host.
  2. Pick a theme that doesn't try to do everything.
  3. Be picky with the plugins you install.
  4. Cache all the things.
  5. Use a Content Delivery Network (CDN).
  6. Limit web fonts.
  7. Optimise your images.

1. High quality hosting

As I mentioned earlier, $5/month shared hosting providers are utterly useless. I can't stress this enough, folks. DO NOT USE SHARED HOSTING. They're generally over-subscribed - meaning too many customers share a single server - which directly impacts the performance of all sites using that server.

Instead, get a Virtual Private Server (VPS). These are servers that are much more powerful than shared hosting because they have a minimum guaranteed amount of resources that no-one else can hog.

I personally recommend Ionos which is who I use to host this website. What I love about Ionos is that they offer a free Plesk license with all their VPS packages, so it's just as easy to manage as one of those shitty shared hosts running cPanel.

I'm using the Medium VPS package from Ionos, which costs just £6/month (~$8.50/month). Considering that BlueHosts basic shared hosting package is £6.44/month ($9/month), the Ionos VPS is actually a lot more power for less money.

2. Consider your theme

I'm going to keep this high level as there are literally thousands of themes out there that you can use. If you're running a simple blog like me, you probably don't need a great deal of functionality, so is it worth buying an all-singing, all-dancing theme? Probably not.

I run a slightly customised version of WordPress' default Twenty Twenty-One theme. It's simple, looks good and doesn't have any extra functionality that I don't need.

The best advice I can give you is to stay away from page builders and "multi-purpose" themes. They try to cater for too many uses and end up being incredibly bloated as a result.

3. Be picky with plugins

I have 11 plugins on this site, all of which add something that I need for this site to function. For example, my plugins add functionality like 2 factor authentication, backups and advanced SEO features.

I do not have plugins that add front-end "features" like lightbox on images, or social sharing buttons. It's all just extra code that isn't really needed and is unlikely to be used by most visitors.

By reducing the amount of plugins you have installed, you're literally reducing the number of lines of code your site needs to run. Therefore your site is smaller and quicker to load. Poorly coded plugins can also introduce security vulnerabilities, so please be really picky about which plugins you install.

4. Cache all the things

The single biggest impact you can have on speeding up a WordPress site, aside from hosting, is caching. It's massively important.

I compared a number of common caching plugins recently and while they all had a positive impact on my website's performance, I chose to go with WP Rocket.

WP Rocket is superb. I've been using it for a little over a year and a half now and I'm very happy with it. There are other caching plugins available, obviously. If you don't want to pay for WP Rocket, I'd recommend taking a look at my comparison post and picking a free alternative.

5. Use a CDN

A Content Delivery Network (CDN) basically copies the static parts of your site to servers located all over the world. So if your server is in London, and someone visits from New Zealand, that data needs to be transmitted right around the globe.

With a CDN, there would be a local server, in Australia for example, where your static content will be served from. This means your site would load much quicker.

My CDN traffic plotted on a map
My CDN traffic plotted on a map

I personally use and recommend BunnyCDN. Their service is excellent and they're really cheap. For example, the CDN charges for this site cost me around $1/month.

WP Rocket makes using a CDN very simple, as do many other caching plugins. So teaming up WP Rocket and BunnyCDN will have a dramatic impact on your site's performance.

6. Limit use of web fonts

Web fonts can be used to give your site a unique look. They are served from your server, or a service like Google Fonts. However, font files can be really big, so they add a lot of size (and therefore load time) to your site.

If you still want to use web fonts, I'd recommend using this tool to pull down highly optimised versions of web fonts from Google Fonts. You could serve them direct from Google, but there are privacy implications.

I personally use a single web font on this site, Fira Sans Condensed. This adds around 30kb of site to my page load, but it's a pretty slim site already, so I'm happy to do it.

Alternatively, think about using a local font stack, which is a list of system fonts that most operating systems have installed, so they're loaded immediately from the local computer.

But Kev, I don't want my site to use ugly local fonts. People hate them and it will make my site look rubbish!

- Website owners everywhere

Well, I hate to burst your bubble, dear website owner, but the only person who cares about your custom fonts is you. Question - do the fonts on GitHub or on Google? How about Twitter?

All of the fonts on the sites listed above look fine, right? You may not think “Gosh, these fonts look amazing!” But you don't give it a second thought either, I bet.

Well, all of the sites above use local font stacks!

So stop using services like Google Fonts, and serve up a local font stack instead. Here are some example font stacks you could use:

# Sans-Serif font stack
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif

# Serif font stack
font-family: Constantia, "Lucida Bright", Lucidabright, "Lucida Serif", Lucida, "DejaVu Serif", "Bitstream Vera Serif", "Liberation Serif", Georgia, serif;

# Monospace font stack
font-family: Consolas, "Andale Mono WT", "Andale Mono", "Lucida Console", "Lucida Sans Typewriter", "DejaVu Sans Mono", "Bitstream Vera Sans Mono", "Liberation Mono", "Nimbus Mono L", Monaco, "Courier New", Courier, monospace;

7. Optimise your images

Images are generally the single largest element on a web page. So it's really important to optimise them. For this, I would recommend the ShortPixel image optimiser service.

The ShortPixel plugin will take your images as you upload them to WordPress, and optimise them to reduce their size dramatically.

With ShortPixel you get 100 free optimised images per month, which is fine for most people's usage. If that's not enough though, they also have the option to upgrade to paid plans that are relatively cheap.

They also have the option of buying one-off bulk image credits, which are useful for going back and optimising all the images on your site.

As you can see from the image above, I my image sizes are reduced by an average of 62% using ShortPixel. This has equated to a huge 1.25TB of bandwidth that's been saved!

Optimisating your images is a crucial part of speeding up a WordPress site.


All of my recommendations above are relatively simple to implement and don't require you to be some kind of web dev genius. By implementing some, or all, of the recommendations above, you will speed up your WordPress site significantly.

Now, there's always more you can do and if you're that way inclined, this post probably doesn't cut the mustard for you. But if you're a set it and forget it kind of person that just wants a fast WordPress site that you don't need to worry about, this post should leave you in relatively good shape.

Do you think I've missed something? If so, please let me know and I'll be happy to add it.

Get in touch!

Receiving emails from my readers is my favourite thing, so if you have something to say, feel free to drop me an email or sign my guestbook.

Want more content?

Say no more, dear reader. Here's three random posts from this blog for you to peruse:

How To Self-Host Your Web Fonts
19 Jan 2020

Ban the Spam!
31 Aug 2022

How to Setup a Zimbra Server
30 Jul 2015

← The one before
Getting started With Git - A Simple Beginner's Guide

Up next →
My Thoughts On Richard Stallman's Return To the FSF Board

Want to be informed when I post new articles? Simply enter your email address below and you will get an email whenever new posts are published.

Alternatively, you can subscribe via RSS instead.

Enjoyed this post?

I put a lot of work into maintaining this site and I really enjoy interacting with my readers.

My fuel of choice is coffee, so if you did enjoy this post, or found it in any way useful, I'd appreciate more fuel to keep me going. ❤️

Buy me a coffee