I performed a site scan on my site and was told that the HTML/JSP/CSS efficiency is at 40%. I was further advise the following

A note on HTML/JSP/CSS efficiency:
SiteScan efficiency ratings now include GZIP compression of Web page text and javascript. Web browsers and Web servers support compression of these objects and we are now including zip archives of the compressed files for you to download. GZIP+ compression is the combination of GZIP compression with our comment stripping optimization of HTML text.
Current Web servers support placing the ".gz" (GZIP) files in the same directory as the uncompressed originals. For example Apache, a very widely used Web server, has supported it for a couple years through the content negotiation module
(documented here). Chances are you Web server is already setup to use ".gz" files.
The way content negotiation works is if the browser requests "mypage.html" and signals to the Web server that it can accept a compressed Web page, the Web server will look for "mypage.html.gz" and serve the compressed version instead. The few browsers (mainly Mac variants) that don't support compressed pages are served the original uncompressed version.
So I when to dig up further and realise to add the GZIP encoding I had to do this...
AddEncoding directive
Syntax: AddEncoding MIME-enc extension [extension] ...
Context: server config, virtual host, directory, .htaccess
Override: FileInfo
Status: Base
Module: mod_mime
The AddEncoding directive maps the given filename extensions to the specified encoding type.
MIME-enc is the MIME encoding to use for documents containing the extension. This mapping is
added to any already in force, overriding any mappings that already exist for the same extension.
Example:
AddEncoding x-gzip .gz
AddEncoding x-compress .Z
This will cause filenames containing the .gz extension to be marked as encoded using the x-gzip encoding, and filenames containing the .Z extension to be marked as encoded with x-compress.
Old clients expect x-gzip and x-compress, however the standard dictates that they're equivalent to gzip and compress respectively. Apache does content encoding comparisons by ignoring any leading x-. When responding with an encoding Apache will use whatever form (i.e., x-foo or foo) the client requested. If the client didn't specifically request a particular form Apache will use the form given by the AddEncoding directive. To make this long story short, you should always use x-gzip and x-compress for these two specific encodings. More recent encodings, such as deflate should be specified without the x-.
The extension argument is case-insensitive, and can be specified with or without a leading dot.
The newbie that I am needs help here. I checked Control Panel and tried adding via mime type and apache handlers to no avail. Does anyone knows how one can add encoding via C-Panel or otherwise?
P/S: In any case, hope the above is an interesting read for you as it was for me. :P