Resource Manager

Disable any JavaScript or CSS asset per page, post type, or site-wide from a frontend slide-in panel.

Last updated Feb 21, 2026

Overview

The Resource Manager is a frontend panel that lets you disable any JavaScript or CSS asset on a per-page, per-post-type, or site-wide basis. Instead of editing code or digging through plugin settings, you can visually identify and disable individual scripts and stylesheets directly from the page where they load.

Accessing the Resource Manager

There are two ways to open the panel:

From the admin bar

While logged in as an administrator, go to BoostProAsset Manager in the WordPress admin bar. This appends ?boost_assets=1 to the current URL and opens the panel on that page.

From post and page lists

In the WordPress admin, hover over any post or page in the list table. A Resource Manager row action link appears. Clicking it opens the frontend of that page with the Resource Manager panel active.

Panel layout

The Resource Manager opens as a slide-in panel on the left side of the page. Every JavaScript and CSS asset loaded on the current page is listed, organized into groups:

  • BoostPro Optimizations — per-page controls for BoostPro features
  • WordPress Core — scripts and styles from wp-includes and wp-admin
  • Plugins — assets grouped by the plugin that registered them
  • Theme — scripts and styles from your active theme
  • Miscellaneous — assets from unrecognized sources

Each asset displays its handle name, file URL, and file size.

Disabling an asset

Toggle any asset off to disable it. When you disable an asset, a scoping options row appears below it.

Scoping options

ScopeEffect
EverywhereDisabled site-wide on every page
Current URLDisabled only on this specific page
Post TypeDisabled on all pages of this post type
URL RegexDisabled on URLs matching a regex pattern

Exceptions

When using the Everywhere scope, you can add exceptions to re-enable the asset on specific pages, post types, or URL patterns. This is useful for rules like "disable everywhere except on the checkout page."

How assets are disabled

BoostPro uses script_loader_src and style_loader_src filters at priority 1000 to intercept asset URLs and return false, preventing the browser from loading the file. This approach works without modifying any plugin or theme code.

Testing mode

When testing mode is enabled, asset changes only apply to logged-in administrators. Live visitors see the normal, unmodified page with all assets loading as usual.

This lets you safely experiment with disabling assets without risking a broken experience for your visitors. Once you have verified that everything works correctly, turn off testing mode to apply the changes to all visitors.

Tip

Always enable testing mode before making changes. Once you have verified everything works, disable testing mode to apply changes to all visitors.

Per-page BoostPro feature disable

The BoostPro Optimizations group at the top of the panel lets you disable specific BoostPro features for the current page:

  • Delay JavaScript
  • Defer JavaScript
  • Remove Unused CSS
  • CSS Minification
  • JS Minification
  • Page Caching

These settings are stored as _boost_disable post meta and take effect immediately.

Auto-save

Changes save automatically with a 500ms debounce. After saving, all caches (BoostPro and third-party) are flushed so the changes take effect immediately. A brief notification appears in the panel to confirm each save.

Important

Disabling WordPress Core scripts (like jQuery) can break fundamental functionality. Only disable core scripts if you are certain no other scripts depend on them.