PageSpeed Admin Interface
The admin interface provides diagnostics and insights into the health and efficiency of the PageSpeed optimizations next to management tools.
New feature as of IISpeed 2.0 / PageSpeed 220.127.116.11
The PageSpeed console displays graphs of server optimization behavior over time, and reports various problems your installation has that can lead to sub-optimal performance. The console graphs metrics for these problems over time so that you can see the result of your changes improving or degrading your performance.
Configuring the console
# enable statistics tracking pagespeed Statistics on # enable statistics logging pagespeed StatisticsLogging on pagespeed LogDir c:\log\pagespeed # Tell PageSpeed where to expose the interface pagespeed AdminPath /pagespeed_admin
The histograms page shows detailed latency data for visitor page load times, optimizations, the configured optimization caches, and http fetching. The provided histograms can be enriched by enabling latency instrumentation.
The statistics page shows server statistics since startup,
such as how many resources are being optimized by filters, as well as various latency and cache effectiveness metrics.
The provided statistics can be enriched by enabling latency instrumentation.
Enabling statistics tracking
The following configuration enables statistics tracking
pagespeed EnableStatistics on
Enabling statistics logging
The following configuration enables statistics logging. This will store a snapshot of the statistics to disk periodically for displaying historical data.
pagespeed StatisticsLogging on pagespeed LogDir c:\log\pagespeed
Message Buffer Size
Determines the number of bytes of shared memory to allocate as a circular buffer for holding recent PageSpeed log messages. By default, the size of this buffer is zero, and no messages will be retained.
pagespeed MessageBufferSize 100000
Enabling the admin interface
The following example enables serving of the admin pages. Note that you might want to use another server module to not expose them to the general public. You can choose the urls that you want to use to expose the admin interface, in the example blow we use /pagespeed_*.
pagespeed AdminPath /pagespeed_admin pagespeed GlobalAdminPath /pagespeed_global_admin
You can also enable some pages individually.
pagespeed StatisticsPath /pagespeed_statistics pagespeed GlobalStatisticsPath /pagespeed_global_statistics pagespeed MessagesPath /pagespeed_message pagespeed ConsolePath /pagespeed_console
By default PageSpeed collects cross-process statistics. PageSpeed on IIS v 2.0 uses a shim here, and collects statistics separately in each process. While they're mostly intended for debugging and evaluation, the PageSpeed Console depends on them, and statistics are also necessary for limiting concurrent image rewrites and background fetches. It's not recommended to turn them off, as their performance impact is minimal, but if you need to you can do so with:
pagespeed Statistics off