IISpeed

While Microsoft's IIS is not as widespread as Apache, NginX, or Litespeed, it is still a very powerful and reliable Web server regardless.

IISpeed tries to leverages some of the features and technologies developed by Google and made freely available via its PageSpeed SDK, allowing IIS to serve websites faster, improving the site's page loading time and its SEO "friendliness."

Using IISpeed allows IIS webmasters to improve their site by automatically performing all the PageSpeed Google-recommended optimizations.

This includes a list of over 40 operations, like adding client-side latency instrumentation, collapsing whitespace in the site's code, minifying and combining JS and CSS files, deferring JavaScript execution, caching improvements, moving small external CSS and JS files to inline code, saving and caching CSS and JS to localStorage, and many other more.

All of these are handled via IISpeed, freeing the developer's time and avoiding delaying the site's launch due to maintenance or optimization procedures.

IISpeed is available for free, but a Business License offers some extra features.

Features:

• Free version features:
• Automatic WPO
• Mobile WPO
• Bandwith optimization
• 32/64 bits support
• Works with all supported Windows versions
• Business version features:
• IPRO (In Place Resource Optimization) support
• No branding

What is new in this release:

• New feature:
• In Place Resource Optimization (IPRO), currently only available for Business customers.
• Fixes and improvements:
• IISpeed will now attempt to hook up as the very first to catch the incoming URL, before any other module or filter is able to modify it. This fixes issues when IISpeed is combined with (for example) IIS Url Rewrite.
• Don't respond with an http error status code to invalid requests on IISpeed's beacon URL. Most notably, this fixes an error message that might be displayed in Google's Webmaster Tools regarding the "/x_iispeed_beacon" url. The beacon is used by some of IISpeed's filters to determine which assets are needed for rendering above the fold, amongst other things.
• An issue where sometimes url() statements in optimized css would be left blank.
• Reduce the verbosity of the X-PageSpeed & X-IISpeed headers we send out.