Management of cookies set on optimized sites

Modified on Thu, 8 Feb at 9:12 AM

Fasterize cookies ensure the proper working of the solution and make it possible to guarantee the reliability of the engine optimization by recognizing a visitor as being unique during his various visits (knowing that he is the same Internet user without knowing who he is). Specifically, these "cookies" store the application of the optimization setting to which the user is submitted with the sole purpose of being able to show the same version during these subsequent visits. This system ensures that no differences in behaviors are generated. These "cookies" do not store any personal information about visitors.

Fasterize does not collect or store any data to identify a visitor via these cookies.

Here is the complete list of cookies that can be used on your site by the platform for your visitors:

fstrz = [true | false] : this cookie allows to enable or disable the optimizations for a given user. It is used as part of an A/B test to divide incoming traffic into two populations: an optimized population and a non-optimized one. In addition, it is set by the browser extension when the buttons "See optimized pages | See unoptimized pages" are pressed. The TTL of the cookie is equal to the A/B test period defined in the account settings.

frz_of_id = UUID and frz_of_id.sig: these cookies are used as part of the Traffic Limiter system to filter the sessions allowed to view a site using this feature. This cookie is only set if the Traffic Limiter feature is enabled in the configuration. The TTL of the cookie is one hour.

fstrz_vary: this cookie is used when using the cache variation feature, according to the settings defined in the engine. It serves as a variation identifier for the page. The cache variation is used when a page varies according to the language, country, selected store ... The TTL of the cookie is one year.

frz-forced-state = true: this cookie is set by the browser extension when the buttons "See optimized pages |See unoptimized pages" are pressed. This cookie allows a session to force a state of optimization different from the activation of the engine. The TTL of the cookie is equal to one year.

fstrz_referer: this cookie allows the referer header to be replaced in the smartcache request that goes to the origin. When we have a cached page with smartcache fragments, if the call to the origin (to retrieve the fragments) returns a redirection, then the smartcache script performs this redirection in javascript. Before that, the frz-referer cookie is created to keep the original referer and pass it to the page once the redirection is done.

fstrz_referer: this cookie allows the referer header to be replaced in the smartcache request that goes to the origin. When we have a cached page with smartcache fragments, if the call to the origin (to retrieve the fragments) returns a redirection, then the smartcache script performs this redirection in javascript. Before that, the frz-referer cookie is created to keep the original referer and pass it to the page once the redirection is done.

frz-optimize-edge-speed : this cookie allows to enable or disable EdgeSpeed optimisations.

frz-optimize-edge-seo : this cookie allows to enable or disable EdgeSeo optimisations.