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
    Welcome to My New Office

    My first professional web development was at a small print shop where I sat in a windowless cubical all day. I suffered that boxed in environment for almost five years before I was able to find a remote job where I worked from home. The first...

  • By
    fetch API

    One of the worst kept secrets about AJAX on the web is that the underlying API for it, XMLHttpRequest, wasn't really made for what we've been using it for.  We've done well to create elegant APIs around XHR but we know we can do better.  Our effort to...

Incredible Demos

  • By
    Send Email Notifications for Broken Images Using MooTools AJAX

    One of the little known JavaScript events is the image onError event. This event is triggered when an image 404's out because it doesn't exist. Broken images can make your website look unprofessional and it's important to fix broken images as soon as possible.

  • By
    New MooTools Plugin:  ElementFilter

    My new MooTools plugin, ElementFilter, provides a great way for you to allow users to search through the text of any mix of elements. Simply provide a text input box and ElementFilter does the rest of the work. The XHTML I've used a list for this example...

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!