How to understand the output of optimisation tools
Our apps are optimised to minimise the app loading times by making use of the appropriate caching and compressing mechanisms in order to deliver the best user experience possible.
We are aware that optimisation tools which measure the performance and loading times of a store are often used by merchants and when our apps appear in the results, this is usually a cause for concern. That is the reason why in this article we would like explain in detail about those particular messages.
As an example, please find below some common messages which you might receive from an optimisation tool related with our apps:
However, this is a false positive, as the files will indeed be cached by proxy servers (not shared across different stores, but cached for your customers).
In the following case, it is true that we could combine those files if this were a custom development.
For that reason, we think it is acceptable to have a different file for each installed app.
On the other hand, each of our apps makes a single AJAX call to gather its preferences. This AJAX response is cached for 1 minute. Caching it longer would mean that, after changing the preferences in the app preferences page, your customer would not see the changes.
Please note that this AJAX response is very lightweight.
In the screenshot below we can see a particular message displayed on Pingdom.
This is obviously a glitch