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

Incredible Demos

  • By
    Image Data URIs with PHP

    If you troll page markup like me, you've no doubt seen the use of data URI's within image src attributes. Instead of providing a traditional address to the image, the image file data is base64-encoded and stuffed within the src attribute. Doing so saves...

  • By
    Send Email Notifications for Broken Images Using jQuery AJAX

    It's usually best to repair broken image paths as soon as possible because they can damage a website's credibility. And even worse is having a user tell you about it. Using jQuery and PHP, you can have your page automatically notify you of broken...

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!