Our SaaS solution automatically improves the your website’s loading speed. Our engine works like a proxy in the Cloud, rewriting your page code on the fly to optimise your website’s loading time on desktop and mobile, for all your users, whatever the browsing context. But in practice, apart from improving the speed perceived by your visitors, how can you measure the impact of optimising loading speed on your conversions? In this article, we look in detail at how to test the effects of Fasterize to evaluate the ROI of our solution.
How does onboarding work at Fasterize? How long does the implementation take? Who needs to be involved? In this article, we explain everything you need to know about the steps involved in deploying our SaaS solution, from the audit to the actual acceleration of your site. Follow the guide!
In the history of web performance, “Load Time” was one of the first indicators used to measure the loading times of web pages. Over time, the other KPIs we’ve talked about—Speed Index, Time To Interactive, etc.—made their way onto the scene to assess the perception of speed and Load Time was retired to a dusty old shelf at the back of a storeroom. Let’s look back on this web performance metric that once played an important role, but which is no longer sufficient for assessing the speed of your website, and we’ll see why.
To assess your loading times and improve them, you need to precisely identify your tasks and events that take up the most time for browsers. But how do you know how long it takes a script to execute? Or when the main image on a page displays? What is the processing time for a user action before it executes?
To answer all of these questions, the conventional tools and metrics may only provide limited responses. The answers can be found with custom metrics via the User Timing API.
Jean-Pierre Vincent explains how to use it.
The Time To First Byte (TTFB) expresses, in milliseconds, the time a server takes to respond. It is taken into account by Google and other search engines to assess the speed at which content will be available. So, as you’ve probably understood, it is an important indicator for your loading times, and also one that counts for your SEO.
In the previous part of our article, we explained why the backend counts as much as the frontend to make your site's pages load quickly. But in practice, how do you do it? What should you think about? Should you take care of it internally or outsource these operations? Here are some tips recommended by our web performance experts.
For pages that load quickly, focusing on what appears in the browser by optimizing your frontend seems quite obvious. But do you also pay attention to what’s happening behind the scenes on your servers?
For optimum performance, your backend requires as much attention as your frontend.
Here is some advice about the criteria you should be taking into account so that your infrastructure can hold its own.
A Content Delivery Network (CDN) helps optimise the distribution of content by bringing it closer to internet users. But that’s not all: it’s also useful for the speed and security of your website. Here’s everything you need to know about what a CDN is, how it works, and what it’s good for. We’ll also explain how Fasterize is a “next generation” CDN, as well as all the benefits you can get from it!
A major challenge for technical teams: absorbing traffic spikes. To ensure the availability and continuity of your services, here are a few tips to get through traffic surges on your website.
Caching is one of the most effective techniques for having fast pages and for improving loading speeds by several hundred milliseconds.
This time scale may seem minuscule, but cumulatively, all of those milliseconds can add up to seconds… and 1 extra second of loading time results in fewer conversions. It’s worth noting that in the retail sector, 1 extra second of loading time can make conversions fall by up to -20%.