Compression is a simple and effective way to optimize web pages by reducing size of web pages using some algorithms. When we reduce the size of our web pages, it reduce the load time for that web page. It save a lot of bandwidth and serve our web pages quickly. The compression can saves around 50 to 70 percent of the file size.
When we hit a URL from our web browser, our browser send a request to web server to deliver the content in corresponding file. Then the web server check that if the file is available at there. If it is available, web server send a response code (200 K) and then start to send the whole content associated with that file to web browser. This is normally happened in Web.
Just consider that the size of our file in web server is 250KB. When some one hit the URL corresponding to that file, web server understand that the file is available at there, then send response code and start to send the whole file in to his web browser. He want to wait till his web browser receive the whole 250KB file to read that web page.
If we can deliver the same content with a reduced file size of 50KB, the visitor’s web browser can quickly receive that file than 250KB file. That means, when we reduce the file size, it reduce load time and increase page speed of web pages.
we can reduce the file size of Web pages by compressing it using some modules in web server softwares. This is a major part in web optimization. Through this article, I like to share my knowledge about compression of web content using two modules, mod_deflate and mod_gzip in Apache web servers.
Top benefits by using compression
- A better user-experience, since web pages are load quickly.
- SEO benefits, search engines like sites that load faster.
- Reduced server load, due to small file size.
Why compression is possible in Web environment
We already know that Web pages are almost HTML and CSS files. The CSS and HTML files use a lot of repeated text, whitespace and similar tags. The compression algorithm locates similar strings within a text file and replaces those strings temporarily to make the overall file size smaller.
- First the browser sends a header telling the server it accepts compressed content. :-
Accept-Encoding: gzip, deflate
- Then the server sends a response if the content is actually compressed. :-
- Then the browser receives the compressed file which is significantly smaller.
- If the server doesn’t send the content-encoding response header, it means the file is not compressed and browser want to receive the uncompressed version.
Two Apache modules for compression
The Apache use two modules for compression and decompression.
This two modules are based on same deflate algorithm. But the mod_gzip is little more than mod_deflate.
We can consider that output of mod_Gzip have the same output of mod_deflate with a few dozen byte header wrapped around it including a checksum.
Due to the checksum, mod_gzip is slower than mod_deflate in compression and decompression. Also mod_gzip use little more resource than mod_deflate due to this checksum.
The mod_deflate is is easy to configure and well documented. If you are using Apache v2, the mod_deflate is already installed with Apache. But some old browsers are broken when using mod_deflate.
The compressed file by mod_gzip is little more than mod_deflate compressed file due to header and checksum. Additionally some shared and reseller host provider not support mod_gzip.
Any way this two modules are commonly used to compress web content. To utilize any compression, they must be configured and enabled on server. Then we want to add specified codes in our directory level configuration file like
Enable compression on Apache server using mod_deflate
- First Open
.htaccessfile in your web server*.
- Add below lines of code in to your
- Test the performance and page size after compression.
Enable compression on Apache server using mod_gzip
- If your host support mod_gzip, add below lines of code in to
.htaccessfile instead of above code snippet.
- Then save
.htaccessfile and test the performance with page size after compression.
*You can access your .htaccess file through cPanel by clicking on the File Manager. When the popup box appears, click on the Web Root option and make sure that the “Show hidden files” option is checked.