Fasterize Status

Name: Fasterize Status
Rating: 5 (1 reviews)
Author: fasterize

See detailed information on a fasterized page

As of June 2026, Fasterize Status has 1,000 users and a 5.00/5 rating from 1 reviews in the Developer Tools category.

fasterize Developer Tools★ Featured

Chrome Web Store ↗.crx

Users0%

1.0K

1,000

Rating0%

5.00

1 reviews

Reviews0%

Version

4.5.2

Manifest V3

90-day change · In the last 90 days this extension 2 version updates, changed permissions.

History

2 snapshots

Tracking since Apr 18, 2026.

View as table

Date	Users	Rating	Reviews	Version
Apr 18, 2026	1.0K	5.00	1	4.3.1
Apr 28, 2026	1.0K	5.00	1	4.4.3
Now	1.0K	5.00	1	4.5.2

Changelog

Apr 18, 2026

permissions

webRequest, tabs, cookies, storage, declarativeNetRequest

webRequest, tabs, cookies, storage, declarativeNetRequest, scripting, webNavigation

Permissions & access

Permissions: webRequesttabscookiesstoragedeclarativeNetRequestscriptingwebNavigation
Host access: http://*/*, https://*/*

Screenshots

About

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.