Doubling WordPress speed in an hour

I have recently had to start considering website performance. My main job the new wordpress multisite install has been great but really slow. As a result I had to do lots of research and trial and error in an attempt to speed up the site.

I learnt a lot through that process and I thought that I could apply what I learnt to the Clyde Street blog and outline the tools I used.

1. Test the current speed

First things first, if you want to improve the performance of your site you need to take benchmarks of what the current performance is. I used three tools to achieve this:

  • YSlow plugin for Firebug on Firefox: This tool gives useful feedback about the areas that are slowing down your site and also gives you a grade and a mark out of 100.
  • Google PageSpeed Insights: Part of the Google search algorithm is how fast your page loads. Google allows you to see how well your page does in this speed test. The result is marked out of 100.
  • P3 – Plugin Performance Profiler: On WordPress it can often be the plugins that you have installed that are slowing your site down, this plugin allows you to run a report and find what plugins are taking up the most resources.

After running these three tools I found that although the plugins were not slowing down the site too much the results of the site were very poor:

Clyde Street Yslow (before) Clyde Street Page Insights Desktop (before) Clyde Street Page Insights Mobile (before)


2. Fixes using Plugins


This is an area I have ignored for a long time but caching is really the easiest way to improve your site speed. A static version of the site is created and served to visitors. I used “WP Super Cache” plugin and ensured I checked the box that rebuilds the page after you add something new to ensure that your visitors see the latest content.

Image Optimisation

Google places a lot of emphasis on this. The images that you upload need to be optimised. I reduced the size of the Clyde Street page by about 5mb (a lot) and this alone bumped my google score up by around 40 points.

To do this I used “EWWW Image Optimizer” plugin (there are other tools that can do this just as well). I purchased a API key for cloud optimisation. This cloud option reduces load on your server and does a better optimisation job. It costs $3 a month. I normally won’t pay for plugins but this saved so much hassle (and did such a good job) that I thought it was worth it.

I ran a bulk optimisation job to reduce image size.

There were a few images that google said could be better optimised and so I downloaded these and uploaded them to tinyjpg which is a website that specialises in reducing image size. I then re-uploaded these images and that made google happier, although to be perfect you would also downsize all your images to the exact size required. This may be possible for some sites but for most this is just a bit too much work.

3. Fixes for the theme

The areas that are harder to fix are inbuilt problems within the WordPress Theme you have chosen. Some themes use a lot of javascript and a lot of css and the impact of this on the performance of the site is difficult to fix.

Tip: Run speed tests on your theme before you buy it to check if it is optimised for speed.

There was some other tweaking I did based on the recommendations from the speed test. I reduced the number of google fonts that were used (reducing the number of font files being loaded). I also reduced the number of posts that are displayed on the home page thereby reducing the number of images displayed and the time it takes to load them.

4. Test the results

Following this work (and during) I checked the results of my work and despite there being areas for improvement, the result for the site had improved dramatically from 6/100 to 70/100 in Page Insights and from 65 to 81 in YSlow. These are great improvements that significantly speed up the speed of the website and therefore improving the experience for users and reducing load on your server.

Clyde Street Yslow (after)

5. Things that did not work

I have read a fair bit about “lazy loading”, this is where the images are only loaded on to the page when the user scrolls down to the point where the image will be displayed. This reduces initial load time. I tried a few plugins to accomplish this but I was not successful. It may have been because the plugin was conflicting with the javascript of the site. As I wanted this to be a quick project, I abandoned this but it may be worth trying for you or if you have a bit more time.

6. Areas for future investigation

As with everything, you could spend your entire career dedicated to this area and there are always performance tweaks that can be made. I think the next thing that I will try is using a CDN (content delivery network) to deliver the images to people. CDNs have distributed servers that deliver your website content from a location nearest to the user. Currently all the Clyde Street data comes from a server in the U.S. but if I used a CDN, the static content (images, css and javascript) would get to the user from the closest server be that in Sydney, London or South Africa. Apparently this is a big improvement but as I haven’t tested it, I am yet to find out how it works for me.


I ignored website performance for a long time. I assumed it would be really tricky and boring but actually, if you are using WordPress is is something you can fix very quickly and easily. My goal was not to make the website amazingly fast, for this sort of optimisation you would need skills better than mine (and lots of time) but in an hour I halved the load time of Clyde Street and the site is now ranked respectably by Google in its Page Speed tests and so I know that the website speed won’t be holding the site back. I would suggest that if you devote a small amount of time to your website’s performance you will start to see and feel the benefits.

Leave a Reply

Your email address will not be published. Required fields are marked *