Enable GZIP Compression on nginx Servers
Speed kills, and there's nothing like a speedy website. When you come to this blog, I want you to have a great experience, which is why I've worked tirelessly to compress every asset and avoid unnecessary synchronous interactions. In reviewing my site with Google Pagespeed Insights, I noticed that my virtual private server from Media Temple wasn't configured to serve assets gzip compressed. Oh no! Here's how I enabled gzip compression and made my site miles faster!
Create a file at /etc/nginx/conf.d/gzip.conf with the following content:
gzip on;
gzip_proxied any;
gzip_types text/plain text/xml text/css application/x-javascript;
gzip_vary on;
gzip_disable "MSIE [1-6]\.(?!.*SV1)";
With that file now in place, restart your server and you will now be serving site assets with gzip compression. Google takes site speed into account when ranking and placing your sites in their search engine so do your users a favor and strive for the fastest site possible -- especially for mobile users!
![Vibration API]()
Many of the new APIs provided to us by browser vendors are more targeted toward the mobile user than the desktop user. One of those simple APIs the Vibration API. The Vibration API allows developers to direct the device, using JavaScript, to vibrate in...
![Introducing MooTools Templated]()
One major problem with creating UI components with the MooTools JavaScript framework is that there isn't a great way of allowing customization of template and ease of node creation. As of today, there are two ways of creating:
new Element Madness
The first way to create UI-driven...
![CSS Kwicks]()
One of the effects that made me excited about client side and JavaScript was the Kwicks effect. Take a list of items and react to them accordingly when hovered. Simple, sweet. The effect was originally created with JavaScript but come five years later, our...
![Detect Vendor Prefix with JavaScript]()
Regardless of our position on vendor prefixes, we have to live with them and occasionally use them to make things work. These prefixes can be used in two formats: the CSS format (-moz-, as in -moz-element) and the JS format (navigator.mozApps). The awesome X-Tag project has...
You can use
gzip_comp_level 1
Sets a gzip compression level of a response. Acceptable values are in the range from 1 to 9.
Nice article, I also like to use
gzip_min_lengthparameter which reduces some overhead to gzip small responses.To test if gzip is enabled, run:
You should see
content-encoding: gzipFor production systems, I would suggest the use of
gzip_static.If you want to quickly test whether GZIP is enabled on your website or not use this tool: http://www.giftofspeed.com/gzip-test/
Saved me a lot of time. It also shows you the compression percentages and stuff (for some of my pages it was 70% or more! :-))
so gzip is only work on text type content?
I prefer this line as this enables for javascript too
This snippet made it so when I restarted nginx it failed. Not sure what the deal is. Just an FYI for anyone planning to follow those directions exactly.
nginx fails to restart because sometimes you’ll have gzip already enabled.
So removing the line “gzip on;” or commenting it with a # should do the job!
If you are using Ubuntu 10.04 just execute this command “sudo nginx”, and it shows you where is the problem if exist, my Nginx fails because this line “gzip on;”.
It seems Gzip already ON but no configuration was set.
Hey Brent,
That depends on where you put the code and how you did it.
Can you share your error So I can help.
I put the code into my website config file at
/etc/nginx/sites-enabled/foobar.com/and it works 100%Consider the addition of application/javascript. More in http://stackoverflow.com/questions/23939722/nginx-gzip-not-compressing-javascript-files
Thanks.. I thought it was because of my outdated nginx version. I updated it to latest version but still getting the same that all
.jsfiles were not gzip-compressed. Hence I added"application/x-javascript application/javascript text/javascript"all together. Thanks