Installing IIS WebSpeed

The download contains an installer which will guide you quickly through the setup process. During installation you need to supply your My We-Amp account in order to activate the module. The server module gets installed as a native http module.

Possible IIS restart / Application Pool recycle during installation

During the install and uninstall of IISWebSpeed, Internet Information Services (IIS) might be restarted or application pools might be recycled.

Free trial period

After installing IIS WebSpeed on your server a free one month trial period automatically starts. When the trials ends you can buy a monthly or yearly subscription on our website.

Upgrading from earler (IISpeed) versions

As of IISWebSpeed v1. some major changes in module installation, filenames and directory structure are made:

  • Previously the module got installed with seperate native modules for 32- and 64 bits. As of IISWebSpeed v1. only 1 module gets installed in IIS, which is used for both 32- and 64 bits applications.
  • Cache and Log folders are moved from c:\iispeed to %ProgramData%\We-Amp\IISWebSpeed. The existing c:\iispeed folder can be removed.
  • Previous versions used to have separate root configuration files for 32- and 64bits applications. As of IISWebSpeed v1. the root configuration file is shared between 32 and 64 bits modules. After upgrading a new root config will be installed at %ProgramData%\We-Amp\IISWebSpeed and both old 32 and 64bits configs are backupped there.
  • To enable IISWebSpeed on a website a (empty) config file should be placed in the website root. This file used to be called iispeed.config and must be renamed to IISWebSpeed.config

Validate file cache path

Head over to IISWebSpeed.config in the %ProgramData%\We-Amp\IISWebSpeed directory to validate the configured FileCachePath. By default IISWebSpeed.config will point to %ProgramData%\We-Amp\IISWebSpeed\Cache, and the installer will attempt to create that directory and set the permissions for IUSR.

A valid 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).

Set up Memcached for Windows (Highly recommended)

For improved performance and stability (or in multi-process / multi-server scenarios) we recommend using Memcached for Windows

Enabling PageSpeed optimization

Placing a config file named IISWebSpeed.config in the root of a website will enable PageSpeed Optimization in a very basic setup for that site using the core filters, but without highly recommended advanced features like loadfromfile, memcached, IPRO and fetchhttps (unless configured at root level).

Note: this config file needs to be in the root of the website as configured in IIS, not the root of an application. If you have not configured a FileCachePath in the root config, you must do so in this website-specific configuration file.

Configuring PageSpeed Optimization

Next step is tuning the PageSpeed Optimizations. See our configuration documentation.

Tuning IIS

Head over to our IIS tuning post to read more about tuning IIS for PageSpeed optimization.

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).

Disabling IIS WebSpeed on a website

Delete or rename IISWebSpeed.config in the root of the website or add the following line to IISWebSpeed.config:

pagespeed off


Run the installer again or go to the windows control panel and head over to 'add or remove programs' and uninstall 'IIS WebSpeed'.
Warning: uninstalling IIS WebSpeed 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 IIS WebSpeed (this will add IIS WebSpeed 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="IISWebSpeed" image="%ProgramFiles%\We-Amp\IISWebSpeed\IISWebSpeed.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="IISWebSpeed" />
  • Start IIS Express
  • If you want to uninstall IIS WebSpeed just delete the lines added