WordPress Caching Optimization and Performance: Difference between revisions
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
All of them do a good job in terms of speeding things up. | All of them do a good job in terms of speeding things up. | ||
This article is not intended to be a review or step by step instruction for doing stuff. It's just some notes that no other review or comparison has written about (IE, this is a unique bit of information) | |||
==WP Optimize== | ==WP Optimize== | ||
| Line 18: | Line 20: | ||
*OK documentation, others do a much better job. | *OK documentation, others do a much better job. | ||
*Lots of files (especially CSS, even when combined, etc.) makes Google live page tests grumpy about exceeding their "Download Allownance" (or whatever they're calling it now). | *Lots of files (especially CSS, even when combined, etc.) makes Google live page tests grumpy about exceeding their "Download Allownance" (or whatever they're calling it now). | ||
*Higher CPU usage when page cache is used. Possibly / Probably due to the way the Plugin code runs or is designed. | |||
==WP Fastest Cache== | ==WP Fastest Cache== | ||
| Line 32: | Line 35: | ||
*Auto Cache Settings available for each page need to be done from the "Classic" WordPress Editor, not a page builder like Elementor. No big deal, but... | *Auto Cache Settings available for each page need to be done from the "Classic" WordPress Editor, not a page builder like Elementor. No big deal, but... | ||
*Does a poor job of cleaning up after itself when disabled, leaving a bunch of file and stuff behind in the cache directory. | *Does a poor job of cleaning up after itself when disabled, leaving a bunch of file and stuff behind in the cache directory. | ||
*Doesn't seem to do HTTP / HTML compression into GZ (Gunzip) files | *Doesn't seem to do HTTP / HTML compression into GZ (Gunzip) files successfully, even when GZIP is checked off. | ||
* | |||
Not Sure Things | Not Sure Things | ||
* Puts SVG stuff into the HTML file. So slightly larger HTML files than other. That makes Bing grumpy because files end up being over their magic 256 K limit. | *Puts SVG stuff into the HTML file. So slightly larger HTML files than other. That makes Bing grumpy because files end up being over their magic 256 K limit. | ||
* | |||
== WP Rocket == | ==WP Rocket== | ||
Best Features; | Best Features; | ||
| Line 44: | Line 49: | ||
*Great documentation | *Great documentation | ||
*Makes Googles "live page test" VERY happy with very few CSS resources being over the Google "allotment". | *Makes Googles "live page test" VERY happy with very few CSS resources being over the Google "allotment". | ||
*When updating a page, does a decent job spotting the change, rebuilding the cache (just for that one page) most of the time. Sometimes it waits until the page is visited one time (IE, doesn't Pre Load it) | *When updating a page, does a decent job spotting the change, rebuilding the cache (just for that one page) most of the time. Sometimes it waits until the page is visited one time (IE, doesn't Pre Load it). | ||
*Very low CPU utilization when cache is used, so would seem to have very efficient coding for Plugin. | |||
Worst Issue(s); | Worst Issue(s); | ||
*No way to turn Cache off or on, unless... There's a plugin they make to turn off cache. Not a switch for turning on or off, but enabling / disabling the plugin to turn cache on or off. Although there is a Preload on / off check box which achieves more or less the same thing. | *No way to turn Cache off or on, unless... There's a plugin they make to turn off cache. Not a switch for turning on or off, but enabling / disabling the plugin to turn cache on or off. Although there is a Preload on / off check box which achieves more or less the same thing. | ||
*NO indication of cache progress (other than watching one's CPU usage spike while the cache is built, expected of course, but...) And no summary of number of cached pages. | *NO indication of cache progress (other than watching one's CPU usage spike while the cache is built, expected of course, but...) And no summary of number of cached pages. Why? (PS not necessarily). Because if one is using a "Nag Hide" Plugin, that's the way WP Rocket Displays information about preloading, etc. Plus one has to refresh the page to see the progress. | ||
*Preload Links feature actually slows things down. | *Preload Links feature actually slows things down. Works as described, but is crap. Do NOT use it. | ||
*ANY change made to settings will trigger automatic rebuilding of cached files. Understandable that they need to be rebuilt, but removing control of the rebuild process so completely from the end user (especially experts) seems cruel. | *ANY change made to settings will trigger automatic rebuilding of cached files. Understandable that they need to be rebuilt, but removing control of the rebuild process so completely from the end user (especially experts) seems cruel. | ||
*Does not clean up after itself by deleting cached files. | |||
*Combining JSS Files causes some wonky JQuery Errors. And it makes about 1 - 9 ms of difference, so recommend disabling this feature. In fact enabling anything beyond minify JS seems to cause wonky JS issues or break features. | |||
*Clear Cache Button does just what it says. But guess what? It also starts the Preload Cache automatically. So why is the Preload Cache Button there. Because, pressing the Preload Cache Button clears the cache (or at least overwrites everything, so effectively the same as deleting or clearing everything first). | |||
*Image Lazy Load feature may break images loaded with CSS (background images, etc.). And also doesn't make a difference for performance with images loaded via CSS either. | |||
*Optimize CSS Delivery and "Critical CSS", only seems to enable wonky initial display for a page, no notciable increase in speed for end user. Also seems to rely on an external web server to evaluate it, so if any HTTP blocks are in place, they'll need to be bypassed for wp-rocket.me or the feature turned off. | |||
Not Sure Things | |||
*Regenerate Critical CSS also regenerates Page Cache. Fine, but might want to mention that or show that it's happening. | |||
*Any changes made to CSS or JS settings causes a complete rebuild of cache. Understandable, but should mention it somewhere. Or better yet, show cache building progress. | |||
*As it warns, combining CSS may cause issues. A solution, if using Custom CSS & JS is to have the extra CSS files inserted into the HTML, rather than as separate files. This cures quite a few issues when WP Rocket is in the mix | |||
==Other Thoughts== | |||
It would be great to have one of these guys have an admin interface that shows the cache status, files, what it's doing, etc. all live updated without page refreshes. | |||
Perfmatters also helps out with stuff (will write about that later) | |||
In the end, the final judge is the end user and Google. Making them happy is the ultimate goal, with Google coming first. Why? Because odds are the end user won't find the website unless Google is happy about things. The builder or admin of the site is in the mix, but falls last. WP Optimize is my first choice from the perspective of the Admin, but is also a distant last in terms of making Google happy. WP Rocket is last on my list for the WordPress Admin, but by big distance the number one choice for making Google happy. That's just so freaky to have it work out that way. The same applies for the Database Cleanup features, but without the need to factor in the end user or Google. So maybe just use something like Advanced Database Cleaner Pro and forget about the 'database cleaning' tools that seem to come with optimization plugins. | |||
==Bloat Items to Watch Out for== | ==Bloat Items to Watch Out for== | ||
SkyBoot Icons (part of Elementor or addon for Elementor) | SkyBoot Icons (part of Elementor or addon for Elementor) | ||
==Bottom Line== | |||
Use WP Rocket and put up with it's lack of ability to let Admins know what's happening behind the scenes (IE cache files, caching progress, etc.), the silly buttons for cache clearing, etc, and the lack of messages warning what will happen when one changes a setting. Again, all of the dings against WP Rocket are on the Admin side of things. On the Google and End User side of things, they're spectacular. | |||