Detect Google PageSpeed

PluginView evaluates public page signals in these classes when identifying Google PageSpeed. Individual fingerprint rule bodies are proprietary and are not published.

• Response headers

Illustrative indicators derived from public catalog metadata for Google PageSpeed. A live scan may match additional proprietary rules beyond these examples.

• x-mod-pagespeed:
• x-page-speed: .

Establishes

One or more public signals on the scanned page matched a known Google PageSpeed signature (2 rules) at the time of the scan.

Does not establish

A sitewide install of Google PageSpeed, an active vendor contract, exclusive use, or that Google PageSpeed is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Google PageSpeed signals.
2. 2. PluginView reads only public responses (response headers) and scores them against the Google PageSpeed signature set (2 rules).
3. 3. Review the confidence score and text explanation for Google PageSpeed on the results page.

Can PluginView detect Google PageSpeed without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Google PageSpeed — typically response headers. It does not bypass authentication or paywalls.

What category is Google PageSpeed?

Google PageSpeed is classified under Caching, Web server extensions, Performance in the PluginView directory.

How many fingerprint rules cover Google PageSpeed?

This reference currently tracks 2 fingerprint rules across response headers. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Google PageSpeed?

Illustrative public indicators for Google PageSpeed include x-mod-pagespeed:; x-page-speed: .. A live scan may match additional proprietary rules beyond these examples.