Cache 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 files responsible for the appearance or functionality of the store (css, tpl, js) then your customers may not see your changes.

Force a Cache refresh in the customer's browser

If returning customers can't see the changes you've made to your store, template or modules, this module will solve the problem. The module will force a cache refresh in the browser if there are outdated files in the cache.

Smart method of operation

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

Global.css file version v301:

Quick and unnoticeable

The process of regenerating the cache is unnoticeable to the customer and does not significantly affect the loading speed of the store in the web browser.

The customer'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.

Install the module and forget it

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.