Find the right JavaScript files to exclude from minification

The Minify JavaScript files feature can be quite hard to troubleshoot, especially when you have a lot of files. However, sometimes it’s possible to identify and exclude the problematic files by checking the console errors.


In this example, we refer specifically to using the Chrome browser.


Open Developer Tools. You do that either by right-clicking and choosing Inspect Element, or at the top of the window go to: View→Developer→Developer Tools


Find the red error message indicator on the right-hand side:


Click it to open the Console, then click the file referenced in the error notice:


This takes you directly to the code in the file that is related to the error. Look for the red underline and copy part of that code:


Open a new browser tab and load the uncached version of the page. You do that by adding ?nowprocket to the URL—this will load an uncached, unminified version of the page. It is necessary in order to find the original URLs of the files.

An uncached URL would look something like: or:


Open Developer Tools, then click the 3 dots on the right side and select Search All Files:


Paste the problematic code in the search box and it will locate the file in which that code is found:


It’s not possible, unfortunately, to copy the filename from this screen. So to do that, click on the Network tab (reload the page if necessary to pull in the files). Then search for the file in the list:

Once you’ve located the file, right-click on the filename, select Copy, then Copy Link Address.


Paste this into the  Exclude JavaScript Files text field in the File Optimization tab of WP Rocket. If you need to exclude all files from a specific sub-folder, you can use a wildcard (see first line in the text field on the screenshot):

After saving this you can visit your site again, reload the page and check that there are no more JavaScript errors reported in the console.

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