FacetWP v.4.x includes built-in support for WP Rocket. (For older FacetWP versions see our recommended settings below).

WP Rocket should work with FacetWP without issues, using any of WP Rocket’s settings mentioned in the list below.

Tested WP Rocket settings

WP Rocket File Optimization settings and FacetWPWe tested WP Rocket with the following settings in combination with FacetWP v4.x and found no problems:

File Optimization > CSS Files settings:

  • Minify CSS files
  • Combine CSS files
  • Optimize CSS delivery:
    • Remove unused CSS
    • Load CSS asynchronously

File Optimization > JavaScript Files settings:

  • Minify JavaScript files
  • Combine JavaScript files
  • Load Javascript deferred
  • Delay Javascript execution

Media > LazyLoad settings:

  • Enable for images

Media > Image Dimensions settings:

  • Add missing image dimensions

CDN settings:

  • Enable Content Delivery Network

Open a support ticket if you do encounter issues with these or other WP Rocket settings and FacetWP v4.x.

When to clear WP Rocket cache

WP Rocket clear cacheMake sure to click the “Clear cache” button on WP Rocket’s “Dasboard” tab:

  • after making changes to FacetWP’s general settings.
  • after making changes to facet settings, Listing Builder settings or add-on settings.
  • after enabling or disabling (FacetWP) plugins.
  • after making changes to WP Rocket settings.

How to test WP Rocket setting changes

The best way to test new cache settings is in an incognito/private window, with caching turned off. In Chrome DevTools, there is a “Disable cache” checkbox on the “Network” tab.

Also make sure to test in a separate browser in which you are logged out of WordPress admin (or activate “Enable caching for logged-in WordPress users” on the “Cache” tab).

Using older FacetWP versions (pre v4.0)

Only if you are using a FacetWP version older than v4.0, the following WP Rocket settings need tweaks to work with FacetWP.

Browse to Settings > WP Rocket, click on the “File Optimization” tab and check the settings described below:

Combine CSS files

Add the following to WP Rocket’s “Combine CSS Files” exclusion list:

/wp-content/plugins/facetwp/(.*).css

The results should look like this:

https://facetwp.com/wp-content/uploads/2022/02/wprocket-css-v5.png

Load JavaScript deferred

FacetWP should work fine with the “Load JavaScript deferred” setting enabled. We found no problems testing it with FacetWP and WP Rocket 3.10.9+. If you do encounter issues with this setting enabled, try the following:

Click the “Excluded JavaScript Files” box under “Load JavaScript deferred” and add the following:

(.*)facetwp(.*)

The results should look like this:

FacetWP and the WP Rocket Load JavaScript deferred setting

If you have enabled FacetWP’s debug mode, or if you are using the Conditional Logic add-on installed and you are using custom jQuery selectors in its settings, the following code needs to be added to your (child) theme’s function.php. Make sure to clear the WP Rocket cache afterwards.

How to use custom PHP code?
PHP code can be added to your (child) theme's functions.php file. Alternatively, you can use the Custom Hooks add-on, or a code snippets plugin. More info
// Excludes FWP_JSON from WP Rocket inline defer when debug mode is enabled or Conditional Logic has custom jQuery selectors
// Clear WP Rocket cache after adding this to your (child) theme's functions.php

add_filter( 'rocket_defer_inline_exclusions', function( $exclusions ) {
  $exclusions[] = 'FWP_JSON';
  return $exclusions;
} );

Delay JavaScript execution

When using the “Delay JavaScript execution” setting, you will notice that facets do not show up until there is user interaction (cursor movement, clicks, scroll) on the page. See this WP Rocket page for more info.

To fix this, click the “Excluded JavaScript Files” box under “Delay JavaScript execution” and add the following:

(.*)facetwp(.*)

The results should look like this:

FacetWP and the WP Rocket Delay JavaScript execution setting

Delay JavaScript execution and Proximity / Map facets or hooks with jQuery

In two cases the above (.*)facetwp(.*) exclusion leads to new issues:

  1. If you are using a Proximity facet or a Map facet, you will see google is not defined errors in the browser console. In this case, add the second line of the example below.
  2. If you are using any FacetWP hooks that insert JavaScript that uses jQuery, you will see jQuery is not defined errors in the browser console. In this case, add the third line in the example below.
(.*)facetwp(.*)
(.*)maps.googleapis(.*)
/jquery-?[0-9.](.*)(.min|.slim|.slim.min)?.js

With both additions in place, the results should look like this:

FacetWP and the WP Rocket Delay JavaScript execution setting

Exclude files from CDN

If you have CDN enabled under the “CDN” tab, add the following to the box under “Exclude files from CDN”:

(.*)facetwp(.*)

The results should look like this:

FacetWP and the WP Rocket Exclude files from CDN setting

See also