Unloadly – Disable Unused CSS & JS

Install Unloadly, edit a page, and in the Unloadly box select the plugins that page doesn’t need. Update the page and clear your cache. The plugin stays active, but its CSS and JavaScript files no longer load on that page, so the page loads faster.

A cache plugin makes pages quicker to deliver, but it doesn’t stop plugins from adding their own CSS and JavaScript to every page. If many plugins load files on pages that don’t use them, those pages stay heavy. Unloadly removes those unneeded files.

Edit the page, open the Unloadly box in the sidebar, and select the plugin. You don’t need to look up script handles or write PHP. Only the plugin’s frontend CSS and JS are stopped on that page; the plugin itself stays active.

Find which plugins add scripts to pages that don’t need them, then disable those plugins on those pages from the Unloadly box. Clear your cache and test again. Unloadly removes the plugin’s JavaScript from that page so the browser never downloads it.

The steps are the same. Select the plugins whose styles a page doesn’t use, update the page, flush your cache, and re-test. Their CSS files are no longer printed on that page.

No. Unloadly only removes selected CSS and JS from the page output. Use it with any page cache, and flush that cache after you change Unloadly rules.

No. PHP still runs. Only matching frontend CSS and JS are dequeued.

Yes. Per-page rules are stored on that page or post. Sitewide handle lists apply everywhere.

Many asset managers list every individual script and style file on a page, which requires technical knowledge. Unloadly works at the plugin level: you choose which plugins a page doesn’t need, and all of their frontend CSS and JS are removed together. Sitewide handle rules are available when you want finer control.

A post with its own Unloadly selection uses only that selection. A post with nothing selected inherits the combined rules of its categories and tags, including rules set on a parent category.

Select any plugin in that post’s Unloadly box. As soon as a post has its own selection, the term rules no longer apply to it, so build the list you want for that post.

Yes. Return false from the unloadly_supported_taxonomies filter (pass an empty array) to hide the term fields, or use unloadly_resolved_plugins_for_post to change what a post inherits. unloadly_inherit_term_ancestors controls whether parent category rules cascade, and unloadly_apply_term_rules_to_archive controls whether term archives use them.

Yes. Disable those plugins only on pages that don’t use them. Leave WooCommerce loaded on shop, cart, and checkout. Leave Elementor or Divi loaded on pages built with them.

View the page source and search for the plugin folder name (the directory under wp-content/plugins ). If the name is gone, those files were probably not printed. That is a quick sanity check, not a complete audit. Some plugins load from a CDN, print inline code, or use handles with no folder path, so the name might be missing even when other code from that plugin is still on the page.

Open a thread on the WordPress.org support forum or email support@versouq.com.