Check GZip Encoding with curl

By  on  

Last week I detailed how I enabled gzip encoding on nginx servers, the same server software I use on this site.  Enabling gzip on your server exponentially improves the site load time, thus improving user experience and (hopefully) Google page ranks.  I implemented said strategy and used another website to check if the gzip encoding worked, but little did I know, you can use the curl utility check if the encoding update worked.  Here's how you can check if the gzip encoding worked:

curl -H "Accept-Encoding: gzip" -I https://davidwalsh.name

After executing the shell command, you'll get a response that looks like this:

HTTP/1.1 200 OK
Server: nginx
Date: Mon, 21 Jul 2014 01:12:36 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 20
Connection: keep-alive
X-Pingback: https://davidwalsh.name/xmlrpc.php
Cache-Control: max-age=1, private, must-revalidate
Expires: Mon, 21 Jul 2014 01:12:37 GMT
X-Powered-By: PleskLin
MS-Author-Via: DAV
Vary: Accept-Encoding
Content-Encoding: gzip

From the above response, you can see that the page was served gzipped via the Content-Encoding: gzip header.  You can check individual files instead of pages to ensure they have been gzipped as well.  The amount of effort you put into gzipping your site is worth it -- imagine how fast it makes your site to the thousands and millions of visitors you have each day!

Recent Features

  • By
    JavaScript Promise API

    While synchronous code is easier to follow and debug, async is generally better for performance and flexibility. Why "hold up the show" when you can trigger numerous requests at once and then handle them when each is ready?  Promises are becoming a big part of the JavaScript world...

  • By
    Serving Fonts from CDN

    For maximum performance, we all know we must put our assets on CDN (another domain).  Along with those assets are custom web fonts.  Unfortunately custom web fonts via CDN (or any cross-domain font request) don't work in Firefox or Internet Explorer (correctly so, by spec) though...

Incredible Demos

  • By
    MooTools-Like Element Creation in jQuery

    I really dislike jQuery's element creation syntax. It's basically the same as typing out HTML but within a JavaScript string...ugly! Luckily Basil Goldman has created a jQuery plugin that allows you to create elements using MooTools-like syntax. Standard jQuery Element Creation Looks exactly like writing out...

  • By
    Fix Anchor URLs Using MooTools 1.2

    The administrative control panel I build for my customers features FCKEditor, a powerful WYSIWYG editor that allows the customer to add links, bold text, create ordered lists, and so on. I provide training and documentation to the customers but many times they simply forget to...

Discussion

  1. Spencer

    You can also use the --compressed flag.

  2. Another great tool is: http://checkgzipcompression.com/
    Same thing but a very pretty graphic output.

  3. Aravind

    You can also try this:

    curl -k --compressed -o mydata.txt "https://url"
    
  4. https://api.cryptomkt.com/v1/order"
       -H "X-MKT-APIKEY:  "
       -H "X-MKT-SIGNATURE:  "
       -H "X-MKT-TIMESTAMP:  "
       -X POST
    
  5. Wasin

    To be able to see “text” data from gzipped content use the following (as found here https://stackoverflow.com/a/18984239/571227)

    curl -sH 'Accept-encoding: gzip' http://example.com/ | gunzip -
  6. Chris

    This didn’t work for me. It worked for some sites, but not for others that I knew for sure, had gzip enabled. The problem is the -I option. It sends a HEAD request. Try this, it worked with all sites:

    curl -sD - -o /dev/null https://example.com
    

    https://stackoverflow.com/a/26644485/960857

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!