Cache system in web browsers

Web browsers save some of your store's resources in their cache to make the store load faster. When a browser can load some files from its cache, it:

• The store loads much faster
• The link is less loaded
• Your server uses less CPU and RAM resources

The cache system in the client's browser refreshes itself from time to time, but not with every change, as you implement on the store. If you modify the files responsible for the appearance of the store (*.css, *.tpl) or functionality (JavaScript) then it is likely that the browser will load files from its own cache before it downloads fresh files from your server.

How to refresh the cache in the client's browser?

If returning customers can't see the changes you've made to your store, template or modules, this module will solve your problem.

Smart cache system

1. The module versions files on your server that are stored in the browser cache .
2. The module compares the version of the browser cache files when loading the store with the version of the file on the server.
3. If the versions differ, a request is sent to the browser to generate a new cache
4. The browser updates its cache

Global.css file version v301:

Smart and efficient

The process of regenerating the cache is unnoticeable to the client and affects only slightly during the first page load.

The client's browser will delete and generate a new cache only for files that have changed on your server. The rest of the browser cache will remain unchanged.

Enable and forget

Install and then enable the module. From the moment you enable the module, your returning customers will always see the current version of your store. The module requires no additional configuration.

The module refreshes the cache in all browsers available on the market, including Chrome, Firefox, Opera, Edge, GNOME Web, Midori, Falkon, Pale Moon, Waterfox and others.