Compression can be used to reduce traffic between the web server and the client browser. It usually improves download speed, though it requires some extra CPU activity to compress content.

Compression of static elements (images, CSS files, JavaScript files, documents) is usually enabled on the server (IIS7: Compression Icon in Server Management and Site Management), while compression of dynamic content may either be configured on the server as well or in DotNetNuke*, affecting dynamically rendered html only (i.e. HTML contained in default.aspx).

Notes:

• Dynamic compression in DotNetNuke has been deprecated in version 6.2, please use serverside compression instead.
• Host Settings "Performance Settings": GZip is preferred Compression Setting in most situations, though the differences towards deflate might be neglectable. Do not enable compression and whitespace filtering.
• Host Settings "Caching Settings": you may specify a regular expression for Paths to exclude from caching. As long as Whitespace Filter is not used, the other setting might be safely ignored.