Unloadly – Disable Unused CSS & JS

विवरण

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/. Email support@versouq.com. After the plugin is listed, you can also use the WordPress.org support forum.