Improving SharePoint Site Performance with Static Compression in IIS

The SharePoint sites which are having pages of large site faces the lot of performance issues. The issue sometimes comes because SharePoint page processing pipeline adds a lot of extra weight to the page. It adds certain default files such as core.js, core.css, init.js, and ie55up.js which are required for various reasons. These files can add 500 KB of uncompressed data to the original page size. These extra KBs can add up to 10–20 seconds of download time on slower connections. These files can not be easily removed as Office SharePoint Server requires these files to work properly, and Office SharePoint Server adds them automatically to the page at run time.
One way to improve performance is by doing IIS Compression. IIS can be compressed Statically or Dynamically. IIS 6.0 supports this.
Lets see what is Static Compression is:
Static compression To compress static assets such as .js files, .html files, and others this method is used. Static compression is a very simple process with little or no impact on server load. In this approach, the files are compressed the first time they are accessed, and are kept in a temporary folder and served to the user from the temporary directory from then on. In the case of Office SharePoint Server, all files in _layout directories (for example, .js files and .html files) are compressed. All other files, including files that are static in nature, are not treated as static if they are stored inside Office SharePoint Server. Mostly the large core.js file is compressed, and its size is reduced from about 250 KB to 57 KB. In addition, other system .js files such as init.js and init55up.js are compressed, which solves our biggest problem involving page size.