=== Unloadly – Disable Unused CSS & JS ===
Contributors: babatechs
Tags: pagespeed, unused css, unused javascript, dequeue, disable scripts
Requires at least: 5.8
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Stop unused plugin CSS and JS from loading. Faster pages, fewer requests, and a cleaner document head, effortless website optimization.

== Description ==

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.
* **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: open **Settings → Unloadly** to dequeue CSS or JS handles sitewide, and to strip discovery links from the document head.

= 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/).

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

== Frequently Asked Questions ==

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

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

== Screenshots ==

1. Per-page settings: in the editor, tick plugins whose CSS and JS should not load on that page.
2. General settings: dequeue CSS and JS handles sitewide, and optionally remove oEmbed, REST API, and RSD links from the document head.
3. Sanity check: view source and search for the plugin folder name. This is a quick check, not a complete audit.

== Changelog ==

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

== Upgrade Notice ==

= 1.0.0 =
First public release.
