<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[WeAreBlastOff - Medium]]></title>
        <description><![CDATA[The small blog dedicated to all things website performance related - Medium]]></description>
        <link>https://medium.com/blast-off?source=rss----e329bce1413d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>WeAreBlastOff - Medium</title>
            <link>https://medium.com/blast-off?source=rss----e329bce1413d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:37:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/blast-off" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I finally did it. Bye bye Apache, hello real Wordpress performance!]]></title>
            <link>https://medium.com/blast-off/i-finally-did-it-bye-bye-apache-hello-real-wordpress-performance-236ce3d6a67a?source=rss----e329bce1413d---4</link>
            <guid isPermaLink="false">https://medium.com/p/236ce3d6a67a</guid>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[web-hosting]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[wordpress]]></category>
            <dc:creator><![CDATA[Nathan Smith]]></dc:creator>
            <pubDate>Fri, 04 Nov 2016 12:26:06 GMT</pubDate>
            <atom:updated>2016-11-04T12:26:05.616Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*unioAiUHwuXbRgwrVXxC7g.png" /><figcaption>Apache VS Nginx Comparison</figcaption></figure><p><em>There’s a common saying in life; you can’t polish a turd </em>— and I really learnt this first hand when it came to choosing a Wordpress hosting platform.</p><p>There’s a back story to how all this project came about that I’ll link to later; when I’ve finally written it — but basically, I started offering Wordpress optimisation services through Upwork simply because there was a vast gap in the market of people there with the skills to actually do this type of job, properly. To many freelancers there, Wordpress optimisation is simply activating a couple of plugins and you’re done — but the simple fact is, it’s really not that simple.</p><blockquote>Now, I’ve been asked by very many people recently about Nginx, and specifically, this article — so I’ve opted to publish it earlier than anticipated. I will however be adding in more content to it soon, and will ‘polish’ it a little so to speak, as at this stage, it’s fairly unedited and was written as I went along. The main thing is, everyone asking me about it, can now see the real world comparison!</blockquote><blockquote><strong>TL;DR:</strong> Nginx absolutely hands-down destroys Apache for Wordpress speed — if setup correctly. You’ll probably have to lose your cPanel because it doesn’t work natively with Nginx (and it’s another thing to go wrong). Move to Nginx anyway, you won’t be disappointed.</blockquote><h3>How all this started…</h3><p>Brace yourself, this could be a very long final post!</p><p>I originally, I ended up helping a client who was desperate for help because they’d had some performance optimisation work done cheaply — only later to find out that it had broken a lot of things on the site, that they hadn’t originally seen before paying the money, closing the contract and leaving great feedback. As a result, they had a website that half worked, crashed a lot and had random slow responses under even a small load.</p><p>They went back to Upwork yet again looking for someone to help, not really sure who to trust, and it just so happened I was flicking through the jobs at the time and felt like it was something I could help with. After a long discussion about it, and mainly why I disagreed with what the previous freelancer had done, I helped them out and we got the issues fixed fairly quickly. It was a nice easy project, the client was extremely relieved and in the process I’d found a little side project I quite enjoyed doing whenever I had the spare time.</p><p>As time went on, I decided to apply for a few other jobs there every now and again but a trend I constantly noticed over time was that people weren’t necessarily interested in how fast their site actually was — they were more interested in the score they were getting from Google’s <a href="https://developers.google.com/speed/pagespeed/insights/">PageSpeed Insights</a> tool. Now, as an SEO, I’m all for trying to please Google, but Upwork clients treat it as though it’s the holy grail of website speed optimisation — as though a 100/100 score means the site is as fast as can be, but, it simply doesn’t.</p><p>Don’t get me wrong, PageSpeed Insights has it’s place in helping to optimise your site for best practice — but where exactly does it tell you how long it takes for a user to be able to download and view the site? It doesn’t.</p><blockquote><strong><em>Take away point:</em></strong><em> You should be more concerned with your user experience, i.e. how fast they can initially view, and move around your site; than a relatively pointless PageSpeed Insights score.</em></blockquote><h3>Yeah, I went there. The great pursuit of happiness aka, the perfect PageSpeed Insights score</h3><p>My own site was always well-optimised and performed pretty fast, but in the spirit of showing potential new clients I could do what many others couldn’t, I decided to go for the ‘holy grail’, perfect 100/100 score for both desktop and mobile on PageSpeed Insights. At this stage, I knew it was a fairly pointless project, but in the spirit of learning something new and trying to overcome unexpected obstacles along the way — I threw logic out the window and decided to do it anyway. After all, there’s very few people on Upwork that can show a perfect PageSpeed Insights score so it was also something extra to make me stand out and highlight my knowledge of Wordpress and performance optimisation.</p><p>Now at this stage of the project, I never had any intention of documenting how I did it, or what tools I used so it’s hard to put down here on (virtual) paper how I achieved it. From memory, the site was already running about 65 for mobile and 80 for desktop, but to get improve this, I ended up testing (read: wasting time) with just about every performance plugin available — often breaking the site in the process.</p><p>For the sake of a little extra knowledge, I even experimented with Google’s <a href="https://developers.google.com/speed/pagespeed/module/">PageSpeed module</a>, but found it difficult to get it to play nicely with everything else. The PageSpeed module is great, but despite what Google claim, it doesn’t ‘automatically optimize your site’ — it takes a lot of configuration to get right. It’s cool with what they’ve done with it, but SSL and multiple Wordpress installs on the same server just made it difficult to manage and play nicely. Having said that, it was something I installed on quite a few projects, and people are still happy with it.</p><p>Every Wordpress install is different — different themes, different plugins, different hosting — what works for one might not work for the next. The PageSpeed module is great, but I’ve officially decided to stopped rolling it now on the basis that it can be troublesome and a pain to install sometimes.</p><p>After deciding to drop the PageSpeed module, and after hours and hours of tweaking and testing, deleting and adding plugins; I finally managed to find the right combination of plugins that allowed me to hit the coveted 100/100 score. Great, eh? I did the near impossible <strong>and</strong> I got to feel like a king for the day.</p><p>With the new found perfect 100/100 score, I applied for a few more jobs along the way and using it as an example, potential clients were much more interested in opening a discussion with me — simply because no one else had shown anything remotely close to what I had achieved.</p><p>I was always upfront and still stressed the point to new clients that I though the PageSpeed Insights score was a flawed metric for performance optimisation, and I explained why — but the fact was, clients loved it and it landed me extra jobs.</p><h3>“Give me all your money” — your average hosting provider</h3><p>I am by no means a ‘guru’ in anything, and I like to learn as much as I can, as I go along. After all, as the saying goes “The more you know, the more you know you don’t know.”</p><p>So as I started getting more and more involved in the performance optimisation side of things, I started getting invited more and more often to discuss jobs about sites crashing, stalling, being slow or otherwise just being resource hungry.</p><p>Just about every client I ever had a discussion with always had the same situation:</p><ol><li>Purchased a VPS from a mainstream provider (why always GoDaddy?!)</li><li>Ran into performance issues</li><li>Performance optimised it (you guessed it, more plugins)</li><li>Took advice from host to upgrade VPS</li><li>Ran into more performance issues</li><li>Took advice from host to upgrade VPS</li><li>Rinse and repeat several times</li><li>Ended up spending hundreds (or thousands!) of dollars every month for hosting.</li></ol><p>At this stage, I’d performance optimised sites that were comparatively small to the discussions I was currently having — we’re talking under 40,000 monthly visits was the maximum for most of my main clients. I could easily optimise smaller scale sites, I could do it with my eyes closed, I’d done it that often; but when it came to building a setup that could easily scale for consistently high-traffic, or sites experiencing exponential growth — I wasn’t ready for it.</p><p>I had a look and tried to help on a few occasions when people were desperate and I made suggestions where feasible, but I was in over my head and was upfront with clients about it — and I never charged for my advice. It wasn’t my area of expertise, but I wanted to understand it better, so like most things in life, I decided to learn about it.</p><h3>Apache load testing begins…</h3><p>Being the curious one I am, and wanting to learn more, I decided to load test my own site to see what it could handle at any one time. At this stage, I was running:</p><ul><li>2GB memory, 2 CPU VPS, from <a href="http://www.vultr.com/?ref=6918273-3B">Vultr</a></li><li>Apache 2.4</li><li>cPanel</li><li>PHP 5 (I never upgraded the EasyApache to the latest PHP 7)</li><li>Cloudflare (disabled security checking/DDOS protection for testing)</li><li>Wordpress 4.6</li></ul><p>All in, it cost about $45 a month with the cPanel licence and backups. It was used solely for my main company website which is a relatively small Wordpress install with less than 20 plugins, not exactly tons of pages or posts — and of course, the perfect 100/100 score as noted above.</p><p>Using <a href="https://loader.io/">Loader.io</a> to perform a load test, I set it to simulate 5,000 visitors over a minute — 10,000 is the maximum for the free plan with Loader.io so I thought I’d start small and see where we could get to.</p><p>Brace yourself for the amazing results — and remember our perfect Google PageSpeed Insights score that showcased just how great the site was.</p><p>Well, it helped us get to this point:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/915/1*rGC3cZLGegyCzefaFSJU0w.png" /><figcaption>Load Test Results For Apache, cPanel and PHP 5</figcaption></figure><p>Amazing results like we expected, right? Er, no, not quite. It managed an amazing 254 concurrent connections before the test aborted due to the number of connections that had timed out. Also look at that average response time — 4392ms! I mean, I like my site, it’s pretty cool and all, but I’m not sure anyone would have waited that long to see it.</p><p>Now, I know this is a hypothetical situation; realistically, what are the chances of 5,000 visitors wanting to visit your site at the same time? Probably fairly small. However, it’s not that uncommon though, I often see people share links on sites like Reddit and Hacker News, and within 10 to 20 minutes, the site is offline. They just can’t keep up.</p><p>If I ran this same test on something resource hungry like Magento (I know clients love that platform too), the site would fall over in absolutely no time. If you’re in the e-commerce industry (or just about any commercial industry for that matter), think about what something like this could cost you financially in lost sales due to down time, time and resources for supporting customers opening support tickets, and generally just the bad publicity often experienced with the help of today&#39;s social media platforms.</p><p>I prefer a proactive approach to hosting than a reactive one. Websites in today&#39;s day and age need stability, and the ability to scale quickly. A reactive approach is often too slow to fix problems when they arise — hence why I run these types of experiments. With today’s technology, stability issues are not a something you should be facing, especially when there’s a better, more efficient way to do things.</p><p>So with a new problem facing me, I decided to do some extensive research to see how I could still maintain that perfect score, but still build something that could scale as well. Besides, what’s speed without scalability and stability? We could have the fastest site in the world, but if it takes a 100 customers to crash it — what’s the use. We could keep upping the server resources indefinitely, but where does it end, and where’s the fun in that?</p><h3>But what other options are really out there?</h3><p>In the spirit of learning, I decided to go ahead and see what other options were out there, and the research began. I started googling a lot of things related to Wordpress performance and scaling, and almost all pages referred to caching plugins — especially creating static HTML. Don’t get me wrong, some of the performance plugins are great — especially when you’re a small website or on a tight budget — but you have to choose wisely. Do you really need 8 different performance plugins? And yes, I’ve seen it done before.</p><p>On my Internet travels, I kept delving deeper and I constantly kept seeing more and more positive things being written about Nginx compared with Apache — but many of them were from a few years ago so I wasn’t too sure how it stood now. Was Nginx still better, or had Apache upped their game?</p><p>At this point, I stopped searching and decided to start testing. After all, reading was only going to get me so far — actions speak louder than words. I logged onto my favourite host (yes, that’s you Vultr!), fired up the smallest VPS they had, and installed Ubuntu — easy peasy.</p><p>Now, I just had to get Wordpress on it. I could install it all manually, but I’m not a great fan of manual labour, so started looking around and found out about <a href="https://easyengine.io/">EasyEngine</a> — I read good reviews, the support forum seemed well supported, and the GitHub build seemed active. Ahead I went.</p><p>Now, EasyEngine has become one of my favourite tools due to the ease and speed in which I can launch a new Wordpress instance — especially coupled with Vultr. It’s a great tool, and there’s decent tutorials about setting things up, but if you’re non-technical and new to Nginx, I’d advise either letting a professional set it up, or have one on hand to guide you.</p><p>I’ll write about EasyEngine coupled with Vultr and Nginx in another post because there are some drawbacks — nothing major, but still a learning curve to get used to. For now, I’ll highlight the biggest issue new users will probably face — the control panel.</p><p>Like most people that currently use, or started off using Wordpress, I began on shared hosting, just simply to learn and see what could be achieved. The great thing about shared hosting is, you almost always get <a href="http://cpanel.com/products/">cPanel</a> installed. Hands down, I think it’s the best control panel out there, and when you compare it to other panels on the market — you really begin to see the difference. The issue is, once you’ve used cPanel, you never ever want to stop using it, and to go without it feels like losing a limb. No, really! So naturally, when you outgrow shared hosting, you end up taking a VPS with cPanel installed — it’s almost like a family member by this stage, it has to move with you too.</p><p>cPanel isn’t natively supported by Nginx so you can’t take it with you to the new install — sorry! There’s extra plugins and codes you can add to get it to work, but I opted not to go this route since it just becomes another thing to debug if an issue arises — and cPanel support have already said they can’t/wont offer support for anyone that’s ported cPanel to Nginx. The good news is, Nginx is in the roadmap for development, but they’ve publicly stated that the project wont even start to begin until late 2016, early 2017. It’s probably still some way off yet.</p><p>So with no cPanel — I had to go without, and in hindsight, I’m actually pretty glad I reached this crossroad. cPanel is great — it’s so easy to and it does everything — but that’s part of it’s issue. It offers so much bloat and extra features that you’ll probably never use — that you end up paying for extra server resources, to support the features you probably don’t need. Would you buy a car and pay for all the extras that you know you’d never use? Probably not.</p><p>I’m not slating cPanel in the slightest, I love it, but there’s a new direction to go now, for me at least. I’m sure when they port it to Nginx, more of my clients will make the transition to Nginx without less hesitation — but obviously, it depends on performance degradation that comes with it.</p><p>So there we have it — a fully functioning Nginx server, now installed and working with Wordpress nicely. Now what?</p><h3>“Say hello to my little friend” — Scarface</h3><p>Yes, I did just quote Scarface in a technical (geeky) post — but in fairness, the little friend referred to, really is just that. Compared to the previous Apache setup, this current build really is little and lightweight — but it’s a heavyweight contender.</p><p>Now for the sake of honesty, I was going to run the server without a control panel, since it’s enough for me; but in the interests of catering to you guys (and making your life easier), I saw EasyEngine had the option to install the Webmin control panel so added that too. I know, I’m nice to you!</p><p>Now before you start looking up Webmin and saying it looks basic and ugly — it really is, at least for the latter part. No bother though, a simple installation of a theme (<a href="http://theme.winfuture.it/">this was my choice</a>) and it doesn’t look half bad any more. The thing is, Webmin is lightweight, uses very little resources and does just about everything you could ever need. Do you really need those gazillion cPanel features when really you just use FTP and email? No, you don’t.</p><p>So this is how the new setup looks compared to before:</p><ul><li>756mb memory, 1 CPU VPS, from <a href="http://www.vultr.com/?ref=6918273-3B">Vultr</a></li><li>Ubuntu Linux 16.04</li><li>Nginx</li><li>Webmin control panel</li><li>PHP 7 with FastCGI</li><li>Redis Cache</li><li>Zend Opcache</li><li>Cloudflare (disabled security checking/DDOS protection for testing)</li><li>Wordpress 4.6</li><li><strong>Zero</strong> (yes, zero!) performance plugins</li></ul><p>Now I know the PHP 7, Redis Cache and Zend Opcache might come off as a little confusing — but they’re built into EasyEngine and easily addable and changeable. Don’t be put off by the terminology.</p><p>At this stage, bare in mind that we’ve more than halved the server memory, and we’ve gone from two CPU’s down to the single one. Ready to see the new comparison?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*0LSVzd8hjzPZ4cHp8DAC8w.png" /><figcaption>Load Test Results For Nginx, Webmin and PHP 7 (and other caching) with 10,000 connections over a minute</figcaption></figure><p>Yes, you’re seeing that right. It successfully handled all 10,000 connections over the space of a minute — without any failures. Let’s also compare that average response time of 95ms to Apache’s 4392ms — a slightly better result I’d say!</p><p>Since it can handle that amount of traffic, what else can it do, you ask? Well, let’s try the same again, 10,000 connections but over half the time — now 30 seconds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*aDsnSZ_lpNJ1ZBtQDfMVhQ.png" /><figcaption>Load Test Results For Nginx, Webmin and PHP 7 (and other caching) with 10,000 connections over 30 seconds</figcaption></figure><p>Well there’s your answer, it successfully handled all 10,000 connections over the space of half a minute — without any failures. Average response time was slightly quicker at 94ms — however the maximum response time of 5070ms seems to have been an anomaly in a single connection — but still much much quicker than compared to the Apache test.</p><h3>And the scores on the doors are…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ofbz-MNzOAJvs0OI7PYOdw.png" /><figcaption>Pingdom Page Speed Result</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Upzna7Uq6eLS_fjUga2i1g.png" /><figcaption>GTmetrix Result</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*tFIZBytW0VKSs45JQhCdvA.png" /><figcaption>WebPageTest.org Result</figcaption></figure><h3>And not forgetting PageSpeed Insights!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I1dGmNH5mEfGfx6916FMtg.png" /><figcaption>PageSpeed Insights Mobile Result</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eBurrPLIng7nxWL_Z0u1jw.png" /><figcaption>PageSpeed Insights Desktop Result</figcaption></figure><h3>Final Conclusions</h3><p>Well there you have it, Nginx absolutely outperforms Apache on both a speed and stability front. As a result of moving to Nginx, the site is now much faster, more stable — and I’ve removed a ton a performance plugins which no longer means having to worry about updating them, anything breaking during a plugin upgrade. It also decreases the attack surface of the Wordpress install by using less plugins, which thereby probably also increases the security of the site. You still need to take adequate security precautions however!</p><p>Another great benefit of the move, aside from the learning experience, is that the hosting bill for my main site has now been slashed from $45 a month, down to $6 (it’s an extra $1 a month for the backup). It’s a nice saving every month, but when you consider that saving across multiple servers and hosts — it really starts to add up. For e-commerce clients spending hundreds, or even thousands of dollars in some cases, per month on hosting — Nginx will really start to prove it’s worth in performance and cost savings.</p><p>As a developer, the EasyEngine/Nginx collaboration makes it much easier, quicker, and cheaper to fire up new Wordpress installs — literally in less than 2 minutes now.</p><h3>Before you start!</h3><p>If you’ve read this far and are just about to jump in at the deep end, please wait a second — there’s a few considerations first. I’ll list a more in-depth post of these things later when I get the chance, but for now, these should cover the immediate issues.</p><p>For email hosting, cPanel is much easier to configure mailboxes than Webmin is — you will either need to be a little-technical or consult someone to help you if you wish to host your email on the same server. Personally, I choose to always host my email separately — there’s several posts online as to why it’s better to host your website an email separately, so there’s not much point in me covering it here. From my point of view, I wanted a lightweight webserver and there was no need to slow it down with email hosting services when there’s much easier and better external services to handle it.</p><p>On this occasion, I chose to host the email with Namecheap using their Private email service which costs about $10 a year for their lowest level plan. I opted for Namecheap initially as I wanted a ‘catch-all’ email service (which I couldn’t find anyone else offering), and I’ve always had great support from them. I’ve been with them for about a month now for the email hosting and had no issues so far. If you prefer something else, there’s hosted email services offered by Amazon ($4 a month per user), Google ($5 a month per user) and Rackspace ($2 a month, but you need to purchase a minimum of 5 mailboxes). There are obviously other service providers out there, but these are the ones I personally shortlisted for their premium service and reviews.</p><p>With cloud providers like Vultr, Digital Ocean and Linode, they are unmanaged servers — meaning you are responsible for securing, maintaining and updating them. These providers simply provide you the physical resources to do what you wish with.</p><p>It’s fairly easy to learn the basics of securing an install online, and using a service like Cloudflare will help mitigate some attacks — but I would recommend consulting an expert in securing a VPS for you if you are unsure. From experience, it isn’t that expensive in the grand scheme of things. Good freelancers on Upwork often came in at around or under $100 for the initial securing.</p><p>The Webmin panel will also alert you to any packages that need updating and can even be set to update them automatically for you — so that becomes one less thing to worry about.</p><p>It may sound a little technical, and it may start to put you off the idea now, but it’s really not that complex, with the right help. You need to be informed of the implications and costs of each setup before you move — as the the last thing anyone wants, is to end up confused by it all or costs spiralling out of control (the cost part only applies to external email hosting costs if you have a lot of users).</p><blockquote>To sum it all up in one section. If you run a personal blog with a little traffic — stay on shared hosting to keep things simple. If you run a commercial website or something that’s important to you — make the switch to a VPS and run Nginx — you will not be disappointed.</blockquote><blockquote><strong>Shared hosting isn’t the place for anything important.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=236ce3d6a67a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blast-off/i-finally-did-it-bye-bye-apache-hello-real-wordpress-performance-236ce3d6a67a">I finally did it. Bye bye Apache, hello real Wordpress performance!</a> was originally published in <a href="https://medium.com/blast-off">WeAreBlastOff</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>