Fasterize Help Center & FAQ

Test the page without optimizations using the Fasterize extension or by accessing the source directly to check if the problem persists.

5xx errors usually originate from the source. Check the server logs, infrastructure availability, and forward the requestID to support.

Fallback mechanisms ensure direct access to the source in the event of an incident on the Fasterize platform.

X-fstrz headers indicate precisely which optimizations have been applied to a request (cache, exclusions, rules).

To connect your site to Fasterize, you usually just need to edit the DNS record for the www subdomain.

Note 1: The period (.) at the end of the value is required but may be added automatically by your DNS provider.
Note 2: The TTL is for reference only and can be adjusted according to your configuration.

Collect key information (URL, time, requestID), check the platform status, and contact support if necessary.

To connect your site, you must whitelist the platform's official IP addresses.

When your site is hosted by Fasterize, your server no longer receives users' IP addresses directly, but rather the IP address of the Fasterize platform.

To work around this, Fasterize adds HTTP headers containing the actual IP address:

• X-Forwarded-For
• True-Client-IP

True-Client-IP contains the client's IP address directly, whereas X-Forwarded-For lists the various IP addresses that relayed the request, with the first one being that of the browser.

True-Client-IP: 203.0.113.1

💡 In most cases, True-Client-IP is the easiest to implement on the server side.

You must then configure your server (Apache, Nginx, Varnish, etc.) or your application to use these headers instead of the default source IP address.