Let’s talk about Best Cache Plugins 2019, let’s talk about WordPress and its plugins … Let’s also talk about SEO. Today I bring you an article + video that is going to create some controversy and raise some blister, but it is something that we know for a while and after trying to find a solution (we are still in the dept of experimentation of Webpositer) , I wanted to share it with you. But first, a little theory
The Cache (and not so Cache) plugins that we use:
Here is a small controversy, since the name cache has been standardized so much that nowadays, a plugin that improves the WPO is already a Cache plugin and as we are no less, we also fall into the error and generalize with the names , so we go with the “Cache” plugins that we use most in day to day:
WP3 Total Cache
As Alvaro de Raiola says, “This is like killing flies with bazocazos” (it is essential to put an accent “Galleguiño” to the leero?). This plugin is one of the most complete, but a misconfiguration can cause an excessive consumption of resources that ends up resulting in a “worsening” of the WPO in matters of server performance.
This plugin in particular is more a minifier and code unifier than a cache plugin, but since it also has the function (no matter how simple it is cached) and is incredibly easy to use, then move on!
Another plugin that gives good results for the little work it takes to set it up, really if it were not for Autoprimize and Fastest Cache, it would be tremendously complicated for some people to have the web cached and minified.
Today the best option, but like any good option you have to leave “lereles”, specifically “39lereles” per site, the good is paid, and the bad too, but in the long run? We like WP Rocket so much because with 4 settings it has, it offers the same effectiveness as W3Totalcache and Fastest Cache, one pass. And they also have a great support, they understand the pasta that you leave in the happy plugin and that this has to work perfect.
Actually this plugin is in the doldrums, it stays away from its competitors, for being old and making bad decisions regarding cache management, but we still have it in memory and that is why we name it!
What do (or should) the Caché plugins (or WPO Suits)?
As we said at the beginning, really if we stick to the concept cache, we should only look at:
Caching on Server
The plugin compiles the PHP and data from the Database and generates a static HTML in plain text. So it performs the task of loading the entire web and storing it on the server, before any user makes a query to it.
Caching in client
This point is one of the most important, since they establish the time of stay of the files downloaded on the server so that they do not have to be downloaded again the next times they are needed. That is, the browser checks if it has the information saved and if it is, it loads it from the computer itself and displays it, so you do not have to download it again.
And some other functions that we associate with Cache Plugins (to simplify the term) and that directly affect the WPO:
Minify the code
Reduce and eliminate all the code that the browser can not (or does not want to process), such as HTML comments, spaces or line breaks.
Unify CSS and JS
- This technique is what brings us here today, because really, on paper is a great option, reduce to the maximum the number of CSS and JS (always taking into account the weight of that resulting file). This is not only an improvement in terms of weight and page load, but also to file processing for GBOT, because if we reduce the number of JS files, less Java Script will have GBOT than trying to interpret and if we do with the CSS, you will have to load Page Speed to check the accessibility of our website. As we say this on paper works perfectly, but the vast majority of the plugins (at least those we have tried) at this point fail dramatically for a simple nonsense.
- These plugins generate a url with unique characters (HASH) each time they minify and unify the code. This they do for a very clear reason, and that is because these plugins establish in the Htacces that the files remain on the servers for years (to heal in health), and the browser checks by the name of the file if it has already been downloaded previously. If we make a change in a CSS (or JS) and the browser checks that CSS had already downloaded before and above our htacces says it must remain in cache for years, that CSS file will not be downloaded until the cache is cleaned Or spend the time set in Htacces, so there are people who might be seeing the web badly for months. To solve this problem, these plugins began to work with “HASHES”, sets of unique alphanumeric characters, thus forcing the browser to always download these files as they are changing their name and in this way there is never an equal file hosted in the browser.
problems of these Plugins
The first problem
As these plugins have the main feature to clean the cache every X days (or even hours), this causes new files are generated with different urls, which causes when the browser compares the url that has cached with the server it offers to download, it finds that it is a totally new file and re-downloads it, so if we have a plugin configured to clean the cache, for example, once a day (which as we discussed can be configured until it stops be done every X hours) the next time the user enters my website, you will have to download it completely, doing the opposite of what you should do, download as little information as possible.
And the second problem:
By cleaning the cache in this indiscriminate way, the plugins generate new files with new urls, thus creating a new file for GBOT to track, given that we attach great importance to that file “linking it” from all the pages of our web, that file acquires a very high relevance (apart from how important it is for itself and CSS and JS for Google to understand our website) and GBOT tracks and processes it very effectively. As we already know if we tell GBOT that one file is more important than another, GBOT will, as far as possible, track that file more frequently, accumulating a huge number of events in that file.
The problem is not that a CSS or JS file accumulate many events (readings by Google), they really are for that, the problem is that when cleaning the cache, these files, which yesterday were the most important, cease to exist (in some cases generate 404 and others a “false” 200) and google has to retrace new ones, but since GBOT is a bighead, it will not stop tracking these files that no longer exist and will also start to track and prioritize new ones, that will cause an immense amount of tracking in these erroneous urls, and will leave out the pages that we try to position.
This problem, especially affects pages that are new or has a low frequency of tracking, because if I have few events and these occur in 404 or “false” 200, these pages will take a long time to index and google will take them as pages of low priority
Well, from the Dept. of Experimentation of Webpositer, as marketing professionals that we are, we will see in a next installment (and so you are attentive), for now the only thing we can say is: if your website is relatively new and does not take a lot in loading (less than 3 seconds), for now forget the unification of CS and JS, the problem is better than the solution, we tell you from own experience.
While we prepare the best WPO guide ever told, we offer you the box of questions to leave the topics you wanted to address and doubts you have about the WPO in general.