Here at FreshSites we are constantly working to improve the speed and reliability of your WordPress Hosting.
After some extensive testing in the labs this week, we have now rolled out nginx to all of our servers!
What does that mean for me? You might be asking..
Simply put, it should mean your website now loads faster, and server response times should be quicker. There's nothing you need to change to make it work, we've done it all for you behind the scenes!
In testing we have reduced the load times of a basic WordPress site from 0.8 seconds to around 0.5 seconds a 37.5% reduction in loading times without you needing to change a thing! And as ever it is just as compatible with everything WordPress has to throw at it!
How does it work?
For those of you who are interested, nginx (pronounced engine x) is a light weight web server that sits in front of Apache and serves static files (.jpg/.css for example). It's architecture is much better than apache so it can serve static files in a faster manner than Apache ever could. If it receives a request for a non static file (.php for example) it passes the request through to Apache like it would have done before.
Mix this with the WP Super Cache plugin to serve your PHP dynamic pages as static pages when they haven't changed, and your site could load in half the time it previously did!
Traditionally, a web server sends a fresh copy of everything out to the visitor every time they open your site, whether it has changed or not, now we handle data more smartly.
Think of it like this:
If you were to walk into a sandwich shop and order a cheese sandwich, instead of preparing it fresh for you, the sandwich maker hands you a pre made sandwich from the shelf. But say you ask for pickle on that sandwich, he makes it fresh in-front of you.
Making it fresh takes longer, but for most of the queue they want the same standard sandwich (loading an image or a css file for example are static files) so there isn't much point making it fresh.
And if a sandwich changes cheeses, the sandwich maker will then get a fresh copy, and serve this instead.
This is how our web servers now work. If the data has never been requested before, it will be served fresh, if it's been asked for already and is a static file, it will be cached and served for the visitor. If the file changes, nginx grabs a fresh copy for its cache and serves that.
We hope you like these changes and as ever, if you have any questions please feel free to contact us!