Like most websites, this site relies on a large amount of images, videos, CSS styles and HTML files. On a monthly average, this site you are reading has approximately 1100 visitors, serving 5000+ pages and the data transferred is between 6GB – 8GB. The figure is on the increase and is approaching my hosting’s transfer limit. So I have been looking for ways to reduce it.

A common technique for a smaller and faster webpage transmission is by applying HTTP Gzip. The basic idea is that a webserver compresses the page contents and send it down to the internet “pipe”. When the page arrived at a browser all contents are decompressed on the fly. The process is transparent, lossless, and is supported by all major browsers so there is no plug-in or extension to install. Website visitors will experience an improved page loading time due to less data being transferred, and will view the content the same as before. Magical – I am sold!

You can check whether a website is transmitting with GZIP compression by visiting the site A bonus is that you can also discover other parameters such as sitemap XML and robot.txt availability on a site that you wish to examine – this is a useful tool for blogging webmasters who wish to optimise their sites.

Back to the HTTP Gzip – being a wordpress fan myself , the first thing to look for is a compression plug-in. There are many of them in WordPress’s repository. I tried the WordPress Gzip Compression plug-in and it certainly does the job admirably.

Being adventurous – I am looking for a “low-level” solution. My webhosting is a Cpanel account which gives me control of finer aspects of the webserver. While poking around inside Cpanel, an inconspicuous icon that I noticed was the “Optimize Website” under the Software/Services section.

When enabled, this function operates at server level.  All outputs – being HTML, CSS, PNG, JPEG, XML, AVI will be compressed by Apache – the webserver engine layer. This is below the WordPress’s PHP layer so its performance and scope supersedes WordPress’s plug-ins. Meanwhile this will also work for other webapps such as Joomla, Drupal, Mambo, or in fact anything that is sent via a HTTP request.

So to put it to test, I enabled compression for this site since the start of June, and my pages have been sent in compressed form for almost the entire month. The proof is in the pudding and here is the result.