5/26/2023 0 Comments Image cleaner wpWe recommend choosing a Weekly frequency for auto cleanup. Selecting every option in these sections is recommended. Post Cleanup, Comments Cleanup, Transients Cleanup, Database Cleanup Databases can accumulate cruft due to a plethora of reasons such as abandoned shopping carts, post-saved draft points, transients, and more. One of the most significant contributing factors to slow sites is unnecessary data within the database. In such cases, you can use the available options in this section to fine-tune the cache. Sometimes, you need to ensure some pages are never explicitly cached, or a specific cookie needs to be avoided. WP Rocket also provides more granular control over what it can add to its cache. Copy the external domains for any third-party scripts and paste them (one per line) in the URLs to prefetch area. Using a site performance tool such as Pingdom Tools or GTMetrix can help you identify any external resources (i.e., resources that aren’t being loaded from your site’s domain).įor example, in GTMetrix, look at the Reduce DNS Lookups section in the YSlow report. If you are using Google Analytics, are serving ads, or have other external resources on your site, Prefetch DNS Requests can help speed up the loading of these resources. This feature works similar to Preload Cache above and can degrade site performance. Please keep the preload feature disabled. This feature is very taxing on servers and often will degrade overall site performance rather than improve it. WarningThe Preload Cache feature seeks to generate cached pages before a real visitor hits them. Keep in mind this feature only serves WebP images. If planning to convert images to WebP format, select to enable support for caching them. EmojiĬheck this option to prevent others from embedding content from your site. Given the benefits of HTTP/2 and the new HTTP/3, lazy loading is no longer beneficial in a post-HTTP 1.1 world. Sometimes, this feature is not compatible with other plugins or theme page builders and results in performance degradation rather than improvement. Check out these articles from WP Rocket for more information:įix Large Cache Folder Size Caused by Dynamic Inline JS NoteThe Combine JavaScript files option, when used along with dynamic inline JavaScript in the site’s code (usually added by a theme or plugin), can cause a massively bloated cache folder.Īdditionally, if a site uses HTTP/2, combining files is not necessarily recommended. Disable Combine JavaScript files (see note below).If enabled, ensure to test the site within an incognito window to ensure the site displays correctly. However, sometimes it can break the CSS rendering of some sites. This option generates critical CSS and helps to prevent render-blocking CSS. Use Optimize CSS Delivery with caution.However, the file optimization cache for static files (JS and CSS) will still work.Ĭheck every option in the Basic Settings. Adjusting caching settings such as Mobile Cache, User Cache, and Cache Lifespan will have no effect.īecause plugin caching is disabled, we recommend disabling any Preloading options as well, as these will be ineffective and could even impact system resources. When WP Rocket detects that a site is on Flywheel, page caching is disabled automatically. Note Want to utilize WP Rocket’s cache? Follow this help doc to enable WP_CACHE to allow that.
0 Comments
Leave a Reply. |