3 items
See detailed information on a fasterized page The Fasterize browser extension is your essential companion to quickly diagnose the state of a page served by Fasterize. In this article we tell you everything about this must-have for all Fasterize users. This extension allows to obtain several informations: The protocol used to serve the page: HTTP / 1.1 or HTTP / 2.0 The toggle button: it allows to switch from the optimized version to the non-optimized version and thus to check if a page is broken by Fasterize. The Debug section: it is particularly useful for the Fasterize team (when configuring client sites for example). It gives key information when opening a ticket to support. The X-fstrz field: it gives details on the status of the optimization by Fasterize. The exact meaning of each letter is indicated on the flyby. The full list is available here (see the Header section). The X-unique-id field: this one is a reference number. It allows the support team to easily find the logs associated with the optimization and reproduce the bugs faster. The Fstrz cookie: particularly useful during an A / B test, it allows to know if the session is optimized or not (true: optimized, false: not optimized). The cookie fstrz_vary: At Fasterize, we apply a segmentation of the hidden pages. Thus, each cached page has different hidden versions: according to the browsers, the terminals or according to a specific cookie (we use the value of a cookie in our cache key). Thanks to this "cookie fstrz_vary" field, we know if the page is hidden according to a particular segment. The "enable trace" button is used to trace more debug information in the logs.
Sep 3, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.