Title: Unloadly – Disable Unused CSS &amp; JS
Author: versouq
Published: <strong>सितम्बर 2, 2026</strong>
Last modified: सितम्बर 22, 2026

---

Search plugins

![](https://ps.w.org/unloadly/assets/banner-772x250.png?rev=3676981)

![](https://ps.w.org/unloadly/assets/icon-256x256.png?rev=3676981)

# Unloadly – Disable Unused CSS & JS

 [versouq](https://profiles.wordpress.org/babatechs/) लिखले बारे

[डाउनलोड](https://downloads.wordpress.org/plugin/unloadly.1.1.0.zip)

 * [Details](https://bho.wordpress.org/plugins/unloadly/#description)
 * [समीक्षा](https://bho.wordpress.org/plugins/unloadly/#reviews)
 *  [Installation](https://bho.wordpress.org/plugins/unloadly/#installation)
 * [Development](https://bho.wordpress.org/plugins/unloadly/#developers)

 [मदद](https://wordpress.org/support/plugin/unloadly/)

## बिबरन

Contact forms, sliders, shop plugins, and page builders often print their CSS and
JavaScript on **every** page — including pages that never use them. That extra weight
slows first paint, blocks rendering, and shows up in PageSpeed as unused CSS and
unused JavaScript.

**Unloadly** stops those files from loading in the first place. Edit a page, tick
a plugin, and its frontend CSS and JS stay off that URL. You do not copy script 
handles. You do not minify. You do not fight a cache plugin.

Use it next to any cache plugin. Unloadly removes the files; the cache plugin serves
what is left. Flush or regenerate the page cache after you change Unloadly rules.

#### Features

 * **Per-page plugin unload** — In the editor sidebar, tick plugins whose CSS and
   JS should not load on that page. Search the list when you have many plugins.
 * **Per-category and per-tag unload** — Set the rule once on a category or tag 
   and every post in that term follows it. A post with its own selection always 
   wins over its terms.
 * **Sitewide CSS and JS dequeue** — On Settings  Unloadly, list style or script
   handles once. Matching files are removed on the entire frontend.
 * **Head link cleanup** — Optionally remove oEmbed, REST API, and RSD discovery
   tags from `wp_head`.
 * **Quick sanity check** — View the page source and search for the plugin folder
   name. If the name is gone, those files were likely not printed. This is a hint,
   not a full audit.
 * **Safe by design** — PHP still runs. Only matching frontend CSS and JS are dequeued.
   Core jQuery stays loaded.
 * **Lightweight** — No cache, no minify, no delay-JS. One job: do not print unused
   assets.
 * **Developer hooks** — Filters and actions are prefixed with `unloadly_`. See `
   includes/Hook.php`.

#### How it works

 1. Edit a page or post. In the Unloadly box, tick plugins that are not needed on that
    URL (for example WooCommerce on an About page, or a contact form plugin off the
    contact page).
 2. Update the page. Those plugins’ CSS and JS are dequeued on the frontend for that
    URL only.
 3. Optional: edit a category or tag (**Posts  Categories** or **Posts  Tags**) and
    tick plugins there. Every post in that term inherits the rule, so you do not repeat
    the work on each post. A post that has its own ticks ignores its term rules.
 4. Optional: open **Settings  Unloadly** to dequeue CSS or JS handles sitewide, and
    to strip discovery links from the document head.

#### Rule priority

For each URL Unloadly applies one list, in this order:

 1. **The post’s own selection**, when the post has at least one plugin ticked.
 2. **The terms of that post** — the combined rules of its categories and tags. A rule
    on a parent category also covers posts in its child categories.
 3. **Nothing per page**, when neither is set. Sitewide handle rules still apply.

Category and tag rules also apply on that term’s own archive page.

#### Typical stacks

Unloadly unloads assets by plugin folder and by script/style handle. It is meant
to sit beside the tools you already use, not replace them.

 * **WooCommerce** — Unload shop CSS and JS on pages that are not the shop, cart,
   or checkout.
 * **Elementor and Divi** — Unload builder CSS and JS on pages that do not use the
   builder. Leave them loaded on pages that do. Unloadly does not strip assets on
   Elementor editor or preview requests, so the canvas keeps its files.
 * **Page cache** — Change Unloadly rules, then flush the cache so visitors get 
   the new HTML.

Do not tick a plugin on a URL that actually needs it.

#### Who it is for

Site owners who already cache and still see “Reduce unused JavaScript” or “Reduce
unused CSS”. Agencies that want a checkbox per plugin instead of a full asset scanner.
Unloadly is not a replacement for a cache or CSS minifier.

#### Hooks

Developers can change post types, protected plugins, protected handles, and the 
disabled list for a request. Hook names are prefixed with `unloadly_`. See `includes/
Hook.php`.

#### Support

Plugin page: [https://versouq.com/unloadly-disable-unused-css-js/](https://versouq.com/unloadly-disable-unused-css-js/).
Email **support@versouq.com**. After the plugin is listed, you can also use the 
[WordPress.org support forum](https://wordpress.org/support/plugin/unloadly/).

## Screenshots

[⌊Per-page settings: in the editor, tick plugins whose CSS and JS should not load
on that page.⌉⌊Per-page settings: in the editor, tick plugins whose CSS and JS should
not load on that page.⌉[

Per-page settings: in the editor, tick plugins whose CSS and JS should not load 
on that page.

[⌊General settings: dequeue CSS and JS handles sitewide, and optionally remove oEmbed,
REST API, and RSD links from the document head.⌉⌊General settings: dequeue CSS and
JS handles sitewide, and optionally remove oEmbed, REST API, and RSD links from 
the document head.⌉[

General settings: dequeue CSS and JS handles sitewide, and optionally remove oEmbed,
REST API, and RSD links from the document head.

[⌊Sanity check: view source and search for the plugin folder name. This is a quick
check, not a complete audit.⌉⌊Sanity check: view source and search for the plugin
folder name. This is a quick check, not a complete audit.⌉[

Sanity check: view source and search for the plugin folder name. This is a quick
check, not a complete audit.

## Installation

 1. Upload the `unloadly` folder to `/wp-content/plugins/`.
 2. Activate Unloadly through the Plugins screen.
 3. Open Settings > Unloadly for sitewide options.
 4. Edit a page or post and use the Unloadly box to disable plugin assets for that 
    URL.
 5. If you use a page cache, flush it after you change rules.

## FAQ

### Does this replace a caching plugin?

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.

### Will this disable a plugin completely?

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

### Can I keep a plugin’s assets on some pages?

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

### How do category and tag rules interact with page rules?

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

### A post inherits a category rule but needs that plugin. What do I do?

Tick 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.

### Can I turn off term inheritance?

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.

### Does it work with WooCommerce, Elementor, or Divi?

Yes. Tick those plugins only on pages that do not use them. Leave WooCommerce loaded
on shop, cart, and checkout. Leave Elementor or Divi loaded on pages built with 
them.

### How do I check that a plugin’s CSS and JS were unloaded?

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.

### Where can I get support?

Email support@versouq.com or open a thread on the WordPress.org support forum.

## समीक्षा

There are no reviews for this plugin.

## Contributors & Developers

“Unloadly – Disable Unused CSS & JS” is open source software. The following people
have contributed to this plugin.

Contributors

 *   [ versouq ](https://profiles.wordpress.org/babatechs/)

[Translate “Unloadly – Disable Unused CSS & JS” into your language.](https://translate.wordpress.org/projects/wp-plugins/unloadly)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/unloadly/), check out
the [SVN repository](https://plugins.svn.wordpress.org/unloadly/), or subscribe 
to the [development log](https://plugins.trac.wordpress.org/log/unloadly/) by [RSS](https://plugins.trac.wordpress.org/log/unloadly/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.1.0

 * Added per-category and per-tag plugin unloading. Posts inherit the rules of their
   terms.
 * Parent category rules cascade to child categories and to the posts filed under
   them.
 * Term rules also apply on the term’s own archive page.
 * The editor box now lists the rules a post inherits and shows when its own selection
   overrides them.
 * Added `unloadly_supported_taxonomies`, `unloadly_term_disabled_plugins`, `unloadly_resolved_plugins_for_post`,`
   unloadly_resolved_plugins_for_term`, `unloadly_inherited_plugin_details`, `unloadly_inherited_terms`,`
   unloadly_inherit_term_ancestors`, `unloadly_apply_term_rules_to_archive`, and`
   unloadly_term_saved`.

#### 1.0.0

 * Initial release
 * Per-page plugin CSS and JS unload
 * Sitewide handle dequeue
 * Head discovery link cleanup
 * Public action and filter hooks

## मेटा

 *  Version **1.1.0**
 *  Last updated **2 days पहिले**
 *  Active installations **10 गो से कम**
 *  WordPress version ** 5.8 चाहे एकरो से ऊपर **
 *  Tested up to **7.1.2**
 *  PHP version ** 7.4 चाहे एकरो से ऊपर **
 *  Language
 * [English (US)](https://wordpress.org/plugins/unloadly/)
 * Tags
 * [dequeue](https://bho.wordpress.org/plugins/tags/dequeue/)[pagespeed](https://bho.wordpress.org/plugins/tags/pagespeed/)
   [unused css](https://bho.wordpress.org/plugins/tags/unused-css/)
 *  [Advanced View](https://bho.wordpress.org/plugins/unloadly/advanced/)

## रेटिंग्स

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/unloadly/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/unloadly/reviews/)

## Contributors

 *   [ versouq ](https://profiles.wordpress.org/babatechs/)

## मदद

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/unloadly/)