From the outset, Fasterize has optimized pages, in particular by hiding resources and pages that can be hidden.
However, when we were running an A/B test(measure the impact of Fasterize), we were unable to apply this A/B test to cacheable pages.
Explanation:
But that was before!
With the development of the A/B testing cache, that’s a thing of the past!
From now on, to access cacheable pages, the user must be equipped with a cookie (which indicates whether or not he or she is part of the optimized population).
In the case of a new user (who, by definition, does not have a cookie), the request will pass through the fasterize engine, which will assign it to a population via a cookie. The user will then have access to the page corresponding to his population and stored in the cache* :
If the same user returns in a few days’ time, he’ll already have his cookie and his request will no longer pass through the Fasterize engine. The hidden optimized page will be served directly:
This allows us to track users already equipped with a cookie, in order to know the behavior of their browser and of the surfer according to his population (optimized or not).
The advantage of this new feature
Our A/B testing methods have clearly been improved. We can now integrate cacheable pages into our A/B tests, giving us more information on the effects of Fasterize on your site.
*In order for the optimized page to be saved in the cache, the very first user in our A/B test has to do the work of fetching the information directly from the server, as shown in the path below. All subsequent users will then be able to access the optimized pages directly via the cache.
Discover the impact of webperf on your site and your business!
>
