WordPress Caching Optimization and Performance: Difference between revisions
| (One intermediate revision by the same user not shown) | |||
| Line 55: | Line 55: | ||
*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. Works as described, but is crap. Do NOT use it. | *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. | ||
| Line 61: | Line 61: | ||
*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. | *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). | *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 | Not Sure Things | ||
| Line 66: | Line 68: | ||
*Regenerate Critical CSS also regenerates Page Cache. Fine, but might want to mention that or show that it's happening. | *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. | *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== | ==Other Thoughts== | ||
| Line 88: | Line 80: | ||
SkyBoot Icons (part of Elementor or addon for Elementor) | SkyBoot Icons (part of Elementor or addon for Elementor) | ||
== Bottom Line == | ==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. | 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. | ||