When should I use the top menu options?

WP Rocket's top menu is automatically added to the admin bar so that you can easily run some actions from anywhere in your admin panel, without having to access WP Rocket's Settings page.

Admin bar menu
In this menu, you'll find these options, depending on the server and WP Rocket's enabled features:

⚠️ You don't need to click these actions all the time because WP Rocket automatically triggers them for you in most cases. WP Rocket's automated cache clearing should cover day-to-day usage.

Here are the exhaustive lists of situations where you need to manually run these actions:

Clear cache

In addition to this option, there are certain scenarios where you can see specific options as with Polylang that allows you to clear cache for a specific language, see an example here

You should manually clear the cache whenever you have:

  • Created 301 or 410 redirects.
  • Made changes to the styling in any of the CSS files, and Minify CSS files or Combine CSS files are active.
  • Activated, deactivated and updated any plugin which displays something on the front end of your site.
  • Installed one of the WP Rocket helper plugins that affect the front-end, e.g. exclude files from deferring, LazyLoad, Load CSS Asynchronously.
  • Done changes outside the WordPress editor, via (s)FTP/SSH, on the server, on external proxys, or on CDNs.
  • Made changes that aren't immediately reflected on the front-end and if you just don't see your new content live.

Purge OPcache

This option will appear only if the host allows purging the OPCache.

  • You should clear the OPcache when you've updated or changed the settings in your plugins/theme, in case something isn't working as expected. This shouldn't be done routinely, but it's more like a way to make sure that something isn't working because of cached bytecode (ref.: What is OPCache?).

Clear Cloudflare cache

As of WP Rocket 3.9.1, this option will be only available inside the Cloudflare Add-on when enabled.

  • You should clear the Cloudflare cache when you have Cache Everything enabled. This is done automatically in 3.4.1 if we detect that option to be enabled.
  • Made changes to your files without changing their filenames.

Purge Sucuri cache

This option will be available if the Sucuri Add-on is enabled.

  • Made changes to your files without changing their filenames.

Preload cache

  • You should click on Preload cache when you've manually cleared the cache.
  • You should Preload the cache when the Critical Path generation finishes (because this will clear the cache)

Regenerate Critical Path CSS 

This option will be available only if the Load CSS Asynchronously feature is enabled.

You should run the Regenerate Critical Path CSS option whenever you have:

  • Created custom CSS which would affect the critical path.
  • Made extended changes to your site's CSS.
  • Regenerating CPCSS shouldn't be done routinely. Only, if they make changes in CSS files of the theme (ref.: Load CSS Asynchronously).

Note: this information also applies to the Quick Actions section inside the Dashboard tab.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.