We are pleased to announce that after some successful Server Side Compression trials at the start of this month HTTP Compression has been deployed across all web servers. HTTP Compression works simply by the web server compressing website content before sending it to the clients browser. The clients browser will then uncompress the content. The result is lower bandwidth usage for your website and possible faster loading time of your website.We currently compress all static and dynamic content on the servers.

However there are times when compression might not take place. This is due to the configuration we have in place. If the server detects the client browser does not support compression then compression will not take place. Server side compression can be resource intensive server side depending on what is being compressed. Because of this compression may not be performed if the server resources are above a particular threshold. This is to prevent any server side issues with compression to the detriment of up time and performance.In additional the HTTP compression is not compatible with ISAPI_Rewrite. So any pages accessed by a rewritten URL will not be compressed. Customers likely to see the biggest benefit are those with static html pages high in text content. Although the majority of customers should see some benefits.

Â