Install.cmd will set up IISpeed on your system. You need to run it with administrative permissions. If you want to enable IISpeed for a website, place an empty file called "iispeed.config" in the web root. After doing so, you can validate the install by request a page on your website with ?PageSpeedFilters=+debug appended. This will make PageSpeed optimization write debug information about its optimization decisions in html comments, and append the applied configuration to the end of the html. You can use view-source to confirm IISpeed is operating correctly.
If you run into any trouble, more detailed information about the install process follows below.
Extract the contents of the zip file to a folder, and run install.cmd with administrative priviliges.
If you have a license key, now is the time to register. Head over the
iispeed.config in the installation directory to validate the configured
By default iispeed.config will point to
c:\iispeed\cache, and the installer will attempt to create that directory and set the permissions for
FileCachePath is required for PageSpeed optimization to operate.
The cache settings can be overridden for each website that will have PageSpeed optimization enabled in the website specific configuration(s).
Optionally: set up Memcached for windows
For improved performance (or in multi-process / multi-server scenarios) you can use Memcached for Windows:
- Download and extract Memcached for Windows
- Open a command with administrative privileges
memcached -d installto add memcached as a service
net start memcachedto fire up memcached
- Optionally use regedit to bump memcached's memory allowance
Optionally: set up PageSpeed's admin interface
For tracking PageSpeed health and benefits as well as cache purging, you can set up PageSpeed's admin interface. As of 2.0.2 the admin interface is set up by default to /pagespeed_admin (only accessible from the local machine).
Enabling PageSpeed optimization
Placing an empty file named 'iispeed.config' in the root of a website will enable PageSpeed Optimization
using the 'core' filters for that site. Note that this need to be done in the root of the server as configured in IIS, not the root of an application.
These consist of reasonably safe but conservative optimizations.
For configuration tuning, see here. Note: If you have not configured a
FileCachePath, you must do so in this website-specific configuration file.
Configuring PageSpeed Optimization
See our PageSpeed Documentation.
Head over to our IIS tuning post to read more about tuning IIS for PageSpeed optimization.
Disabling IISpeed on a website
Delete or rename iispeed.config in the root of the website
Run uninstall.cmd with administrative privileges. Warning: uninstalling IISpeed will reset the application pools. Current sessions will be lost.
IIS Express installation
The installer does not yet install the filter to IIS Express, it is however possible to add it manually.
- Stop IIS Express
- Install IISpeed (this will add IISpeed to IIS, but not add it to a site. If IIS is not installed it will not still install the DLLs)
- Edit the applicationhost.config in the %userprofile%\documents\iisexpress folder. (Just copy and paste the folder part)
Add the following line as the last entry to the <GlobalModules> section:
<add name="We-Amp IISpeed" image="%ProgramFiles%\we-amp\iispeed\release\iispeedmodule.dll" />
Add the following line as the last entry to the <modules> section, this can also be done per site by adding this line in the <modules> section of a web.config in the root of an IIS Express website instead:
<add name="We-Amp IISpeed" />
- Start IIS Express
- If you want to uninstall IISpeed just delete the lines added