Too often, webperf optimizations are not automated or are even poorly implemented, meaning that they’re counter-productive.
At Fasterize, all of our optimizations are automated and smart so they can be fully effective and interact with each other perfectly. You save time and get efficient optimizations that are adapted to your content and your technical constraints across all devices (desktop, tablet, and mobile).
CSS on top
The CSS is placed at the top of the page to avoid delaying page rendering.
Optimization of your gross performance
Most sites are becoming increasingly rich, they are constantly becoming larger, and each request comes at a high cost (especially on mobile!). At Fasterize, we strive to remove those extra kilobytes from your page elements while retaining the same final layout as well as to save you from unnecessary requests for the benefit of your users (and also to save the polar bears as well!).
WebP / AVIF image compression
Fasterize optimizes all your images in next-gen compression formats, and turns image tags into picture tags with WebP and / or AVIF sources.
We add a version number to the URL of each static object so it can be stored for longer in caches (browser caches, CDN caches and proxy caches). This also makes purging caches much easier. No more need to use Ctrl+F5!
Fasterize automatically segments its optimizations – and therefore its cache – by incorporating categorization based on the device used (desktop, mobile, etc.) in the cache key. Different versions of the same page are then cached without running the risk of serving a mobile page to a desktop client.
TLS Session Resumption
We’ve implemented TLS session re-use, which is one of the most significant mechanisms for improving TLS layer performance.
Browser checks on certificate validity account for around 30% of the total additional time required by HTTPS. Thanks to OCSP stapling, the server sends the certificate with an indication of its validity in the TLS response.
TLS False Start
TLS False Start is a protocol extension that allows the browser to send page data before the TLS handshake has been completed. Essentially, TLS False Start results in just one return journey when establishing new TLS connections.