Skip to main content
Print

WP Rocket Configuration

See also:Additional notes on how to use WP Rocket with Pressable (with examples)

Ideal bare-minimum optimization settings, which can typically be enabled by default (and are enabled by default on new builds generated from our Templates/Stencils):

File Optimization

CSS Files > Minify CSS files

  • in most cases, it should be OK to minimize CSS files, but you should check to be sure everything is displayed correctly

JavaScript Files > Minify JavaScript files

  • in most cases, it should be OK to minimize JS files, but you should check to be sure everything is displayed and functioning correctly

Media

Lazy Load > Enable for images

Lazy Load > Enable for iframes and videos

Image Dimensions > Add missing image dimensions

Preload

Preload Links > Enable link preloading

  • can improve real-world-feel of browsing a site, but doesn’t improve page speed scores

Prefetch DNS Requests > URLs to fetch

  • check the speed test for 3rd party assets, particularly fonts, and add them to list of URLS to prefetch

Preload Fonts > Fonts to preload

  • Where applicable preload fonts, /wp-content/themes/Divi/core/admin/fonts/modules.ttf is a common one to preload when using Divi

For Pressable sites specifically

(which is most sites we manage)

  1. Install and activate the WP Rocket “Disable Page Caching” plugin (if not already done)
  1. Within the Pressable site dashboard, disable the CDN (if it was enabled)
  • Sites > find your site > Performance > CDN > turn it OFF
  • Soon Pressable plans to remove their CDN entirely anyway, as their newer Edge Cache eliminates the need for it, and WP Rocket has issues with the Pressable CDN.

Further improvements on a site-by-site basis

Additional/harder settings could be configured if/when warranted. Each setting below should be used with care, and extreme caution and testing is required.

File Optimization

  • Optimize CSS delivery
  • Load JavaScript deferred
  • Delay JavaScript execution

Preloading

  • Activate Preloading (for NON Pressable sites)
  • This helps to avoid long TTFB

Add-ons

  • User Cache (for NON Pressable sites)
  • This helps logged-in users still have cache (which can also be a bad thing in some cases)

Advanced Rules (for NON Pressable site)

  • Never Cache URL(s)
  • excluding certain URLs for frontend user login forms, certain WooCommerce custom pages, if using Divi split testing, etc.

Other things to consider for Divi theme and other plugins:

Table of Contents