Resolving issues with Minify CSS files

To resolve display issues that may occur when Minify CSS files is active, please take the following steps:

  1. Install the Blue Button Chrome extension.
  2. Enter the URL of the page with the CSS issue, and add ?nowprocket to the URL, e.g example.com/about?nowprocket.
    This bypasses WP Rocket, so that you can find the original URLs (unmodified by WP Rocket) of all CSS files.  
  3. Click on Stylesheets or Scripts to get the list of internal and external CSS and JavaScript files on your site. 
  4. Copy the list of CSS files, then go to WP Rocket Settings > File Optimization and paste the list into the Excluded CSS Files field:

  5. Excluding files from external domains
    Files from external domains can be excluded either by the domain name or the full file URL.
    e.g. to exclude: https://bootstrapcdn.com/bootstrap/4.5.2/css/bootstrap.min.css

    You may use either: bootstrapcdn.com
    or https://bootstrapcdn.com/bootstrap/4.5.2/css/bootstrap.min.css

  6. Save the settings and check your site, in a logged-out or incognito window. It should now be displaying correctly.
  7. Now remove each file from the list, one-at-a-time. After each removal, save the settings and check your site. Repeat this until the website is broken again.
  8. When the website breaks, replace the last removed file back into the list and move onto the next file.

Note: this method can also be used for issues with Minify/Combine JavaScript files (using the JS Files and Inline JS results in the asset detector tool), but the method described here is faster.

Also, this can be used for the Combine CSS files feature if you're using a WP Rocket version before 3.15.

Heads up!

Certain patterns of exclusions cannot be handled and are automatically removed.

If you add them, you should see a notice with the "WP Rocket: The following patterns are invalid and have been removed" message.

Please see more in our Invalid patterns of exclusions article.

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