Fasterize allows you to define optimizations applied to your website and easily create / modify, activate / deactivate ... This article explains how to set the engine to have the hand on each optimization made on your site.
Access to configuration
The configuration is accessible from this address: https://my.fasterize.com .
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. This setting requires that you enter:
- the domain names used by the site
- the optimization rules you want to activate
- caching rules
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.
Customize optimization rules
Optimization rules are managed from the "Rules" menu.
The activated rules are checked. To activate / deactivate a rule, simply check and save.
You will find explanations for the setting of each rule on this page .
The "Domains" menu allows you to 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 want to force the update of cached items. In this case, simply clear the cache from the "Overview" section of the Administration Console.
Exclusions are the URLs for which no optimization is done. These are global exclusions. This may concern internal tracking pixels, a backoffice, etc.
More details on the dedicated page .
Although this is not recommended in good practice, it is possible to set up redirects based on the type of device consulting your site. This concerns mobiles and tablets.
For these two types, it is possible to redirect:
- either on a given URL (absolute URL) whatever the URL is consulted (if mobile / tablet sites do not have the same page structure)
- the same URL as the visited URL (if the mobile / tablet sites have the same page structure)
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)
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:
- 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 ( http://www.fasterize.com/website_configs/[id]/monitoring ).
If you have any questions, do not hesitate to contact us .