Setting up the optimization engine

Modified on Fri, 15 Dec 2023 at 04:12 PM

Fasterize allows you to configure optimisations for your website and easily create or modify, activate or deactivate them. This article guides you through how to set up the engine so that you have total control over every optimisation carried out on your site.


Access to configuration

The configuration is accessible from this address: 

To log in, use the credentials you created when you registered or were given to you by the Fasterize team.


Create / modify your configuration

Fasterize is an optimization engine that you can set. 

The modification of each parameter is taken into account almost in real time by the entire Fasterize platform.

For some changes, it may be necessary to empty the cover at the motor. By default, the cache is not emptied after each modification but it can be done by checking a box when saving the new parameters.


Customise and configure optimisations

Optimisation applications are managed from the configuration.

You can add a new application or modify an existing one.

Activated applications are displayed directly in the configuration. To deactivate an application, simply click on the application's three dots and remove it from the configuration.

You will find explanations for the setting of each rule on this page .


Domain names

The "Domain" application lets you manage your domains.

The "Origin" field indicates the domain name (generated at installation and managed by Fasterize) that points to the IP addresses of your origin server. If you change servers, remember to notify us or change the domain name in the configuration.

In order to activate Fasterize, you will need to modify the DNS record in order to point your domain name to the Fasterize servers. For this, you will need to add a CNAME DNS record. You will find on this link explanations on the manipulation to be done .

It is also possible to add secondary domain names (used for static objects for example) so that objects referenced with these domain names in HTML pages are also optimized. By default, the origin used for these "static" domain names is the same as for the main domain, but this can be modified.


By default, static objects (JS, CSS, images, fonts, Flash, PDF) are hidden for 1 month. You can change this duration or disable this setting by unchecking the box.

It is possible to add specific cache rules for some parts of the site, including HTML pages.

For example, to hide all the pages of a site, just add a rule containing the regular expression .*

Apart from the rules added in the configuration, Fasterize respects the HTTP headers sent by the origin servers of each response and more generally complies with RFC 2616 .

You may wish to force cached items to be updated. In this case, simply empty the cache from the 'Quick Action' button at the top right, then click on 'Flush cache'. Select the "Purge all files" option and confirm by clicking on "Flush".

dedicated article explains how the Fasterize cache works .


Exclusions are URLs for which no optimisation is performed. These are global exclusions. This may concern internal tracking pixels, a backoffice, etc ...

To carry out an exclusion, you need to add targeted rules to the configuration dashboard.

More details on the dedicated page .

Other useful information


/! \ Attention, for the exclusions, for the rules of caching, for the whitelist / blacklist, it is necessary to write real regular expressions (* .jpg is for example by a valid regex,. * \. Jpg if)

Extension Chrome

A Chrome extension allows you to quickly see the optimization status of a page and diagnose a problem. See the dedicated page .


If a page is broken because of a rule, it is possible

  • to disable the rule for this page (blacklist)
  • to exclude the page from all optimizations
  • to disable the rule for all pages

The most likely rules to break the pages are in order:

  • DeferJS: if Javascript is used to build the layout
  • Concatenation: if a syntax error JS or CSS at the end of a single file (and being hidden) is in the middle of the file via the concatenation
  • Minification: Rare Cases Where Invalid HTML Causes Errors
  • Lazyloading: rare cases where lazyloading already exists but has not been detected by Fasterize

In case of real concern, there is an on / off button on the dashboard that allows to stop optimizations instantly (but the traffic still goes through the platform).

More details on this page.


HTTP X-fstrz headers provide information on what the engine did or did not do. The full list of X-fstrz headers is available.


We encourage you to read our Fasterize Impact Measurement documentation .

Functional metrics (loading times, timetoclick, errors, etc ...) are available here ([id]/monitoring ).


If you have any questions, do not hesitate to contact us .

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article