To access the cacheable pages, the user must be equipped with a cookie (which indicates whether he is part of the optimized population or not).
In the case of a new user (and by definition, he does not have a cookie), his request will pass through the fasterize engine which will allocate it to a population via a cookie. The user will have access to the page corresponding to its population and located in the cache *:
If this same user returns in a few days, he will already be equipped with his cookie and his request will no longer pass through the Fasterize engine. The optimized hidden page will be directly served:
This allows us to track users already equipped with a cookie to know the behavior of their browser and the user according to its population (optimized or not).
The advantage of this new feature
Our A / B testing methods are clearly improved. From now on we can integrate the cacheable pages in our A / B tests and thus recover 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 of our A / B test must do the job of looking for the information directly on the server, as shown in the path below. Thanks to him, all the following users will be able to access the optimized pages directly via the cache.