Find answers to frequently asked questions about EdgeSpeed here.
Platform operation, Core Web Vitals improvement (TTFB, LCP, CLS),
cache management, stability, security, and Web Performance best practices:
this FAQ will help you optimize and manage your performance
without modifying your source code.
Find answers to frequently asked questions about EdgeSpeed, how it works, its applications, and performance management.
EdgeSpeed is Fasterize's web performance optimization solution.
It works on the edge to speed up page loading without
changing your site's source code.
EdgeSpeed optimizes HTML cache, static resources
(CSS, JavaScript, images), compression, script deferral,
and page rendering to improve Core Web Vitals
(TTFB, LCP, CLS, INP).
The goal: to improve speed, stability, and user experience,
while increasing SEO and business performance.
No. All optimizations are applied at the Edge level, without any deployment or modification of the code at the source.
Activation is done by modifying the DNS to route traffic through Fasterize. Fasterize is a service that optimizes web pages by compressing and caching them.
Yes, thanks to targeted rules, you can restrict optimizations to specific pages or segments.
An acceptance phase allows optimizations to be tested before they are deployed in production.
Fasterize caches your HTML pages at the edge to reduce TTFB and limit calls to the origin. The cache takes into account necessary variations (device, bots, context) and can fragment a page via SmartCache to combine dynamic content and strong caching.
You can control the cache duration with TTLs and purge the cache from the console (URL, directories, global purge).
They allow you to control the caching duration and optimize performance without blocking dynamic content.
From the EdgeSpeed console, you can purge the cache in several ways: HTML pages, static resources, by URL (maximum 30), by directory (maximum 30), or via a global purge including the domain and its associated domains.
The HTML cache applies to pages, while the resource cache applies to static files (CSS, JS, images).
They enable you to activate targeted optimizations according to your WebPerf objectives.
Applications are managed directly from the Fasterize console.
Yes, they are designed to work together.
You can track the various KPIs directly in the Fasterize console, in the Monitoring tab.
Fasterize neutralizes certain tracking parameters to improve the cache rate without impacting your measurement tools.
Read the article ➜
If an optimization causes unexpected behavior, you can
start by temporarily disabling the affected application
from the EdgeSpeed console to identify the source of the problem.
It is also possible to test a page without certain optimizations
by adding specific parameters to the URL. These parameters
allow you to temporarily disable Fasterize rules to
compare behavior with and without optimization.
You can also use the Fasterize browser extension, which allows you to
enable or disable optimizations in real time, view
the rules applied, and facilitate diagnosis without changing the configuration.
This approach is particularly useful during the acceptance phase or to
isolate a JavaScript conflict, a rendering issue, or an interaction
with a third-party script. If in doubt, contact support,
specifying the URL tested and the context observed.
Via the Fasterize Support Help widget directly on the console at the bottom right.
Yes, the Fasterize teams can provide you with customized support for your web performance or SEO goals.
Yes, mechanisms guarantee direct access to the source in case of unavailability.
.png)