1,723
edits
Difference between revisions of "WordPress Caching Optimization and Performance"
WordPress Caching Optimization and Performance (view source)
Revision as of 11:30, 30 May 2022
, 11:30, 30 May 2022→Other Thoughts
m (→Other Thoughts) |
m (→Other Thoughts) |
||
| 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. | |||
Not Sure Things | Not Sure Things | ||
| Line 66: | Line 67: | ||
*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. | ||
==Other Thoughts== | ==Other Thoughts== | ||
| Line 88: | Line 78: | ||
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. | ||