When the visitor loads a web site for the first time, his browser will cache the original CSS file, in our example customstyle.css. You can even use more decimal points, for example 1.0.0.1. The numerical value of the CSS file version can be any number with or without the decimal point. * Modified CSS file with updated version */
* Original CSS file with version added */ Here’s an example that shows how it works: /* Original CSS file */ The version of the CSS file needs to be changed in the tag in your web site’s section that embeds the style sheet. All you have to do is change the version number of the style sheet after you’re done editing it. Luckily, there’s a way around and it consists of sending a new version of the CSS style sheet each time it’s modified. There’s no dedicated function that would make browsers clear CSS cache or delete cached CSS files when the visitor reloads a website.
WORDPRESS DISABLE LINK CSS HOW TO
How to clear CSS cache and prevent further caching of CSS files in browsers? Preventing visitor’s browsers from caching CSS files is a quite simple trick. NOTE: Browsers can keep the CSS files in their cache up to 1 year.Īvoid using the question “Have you cleared your browser’s cache?” with your clients over and over again. Another important reason to clear CSS cache and prevent further caching of CSS files in visitor’s browsers. In the best case scenario visitor won’t notice any difference in the visual appearance, but in worst cases they could witness broken designs and be unable to use the web site. Most visitors of such sites have the previous version of the style sheets cached in their browsers. The same scenario occurs when modifications to CSS files are done to live websites with a lot of traffic. That’s why we need to clear CSS cache before delivering the final product. In some cases it can even result with completely broken design.
WORDPRESS DISABLE LINK CSS DOWNLOAD
Since the customer’s browser already cached the previous version of the CSS file, most likely it won’t download the modified version, resulting with no changes in the visual appearance of the web site. When corrections which will most likely include modifications of the CSS files are done, the customer reviews the web site once again. When a finished web site is presented to the customer, in most cases some visual corrections will be additionally requested. It’s a routine operation, until it comes to present the final product to the customer or put the web site live for visitors. To see the changes on the front end, each time developers need to clear CSS cache by performing a cache-bust. So why and when should we clear CSS cache and prevent further caching of CSS files? Why and when should you clear CSS cache in visitor’s browsers?Įvery WordPress or any other web developer edit and modify CSS files quite often in the work process.
With that explained, caching CSS files is a very useful feature of web browsers. Therefore, the whole point of CSS cache is to enhance the web site loading speed. That way the web page will load much faster than if it downloads the cached files again. Next time when the visitor access that web site, those elements won’t be downloaded again, but loaded from the visitor’s browser cache folder on the computer (smartphone, tablet, etc.). Those elements are usually images, various scripts and CSS files. When loading a web page, all modern browsers save elements of the web site on the visitor’s in their cache folders. Furthermore, prevent browser from caching CSS files and load the latest version. Tired of using the sentence “Please clear your browser cache…” with your clients over and over again? It’s time to learn how to clear CSS cache in visitor’s browsers after modifying your style sheets.
0 kommentar(er)
