Adds category and tag rules. Existing per-page selections keep working and still take priority over term rules.<\/p>","1.0.0":"
First public release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3676981,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3676981,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3676981,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3676981,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3676981,"resolution":"1","location":"assets","locale":"","width":1227,"height":627},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3676981,"resolution":"2","location":"assets","locale":"","width":1222,"height":688},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3676981,"resolution":"3","location":"assets","locale":"","width":1226,"height":697}},"screenshots":{"1":"Per-page settings: in the editor, select the plugins whose CSS and JS should not load on that page.","2":"General settings: remove CSS and JS handles sitewide, and optionally remove oEmbed, REST API, and RSD links from the document head.","3":"Quick check: view source and search for the plugin folder name. This is a quick check, not a complete audit."}},"plugin_section":[],"plugin_tags":[126745,1513,247,192898,1592],"plugin_category":[54],"plugin_contributors":[133345],"plugin_business_model":[],"class_list":["post-361719","plugin","type-plugin","status-publish","hentry","plugin_tags-disable-plugins","plugin_tags-pagespeed","plugin_tags-performance","plugin_tags-unused-css","plugin_tags-website-optimization","plugin_category-security-and-spam-protection","plugin_contributors-babatechs","plugin_committers-babatechs"],"banners":{"banner":"https:\/\/ps.w.org\/unloadly\/assets\/banner-772x250.png?rev=3676981","banner_2x":"https:\/\/ps.w.org\/unloadly\/assets\/banner-1544x500.png?rev=3676981","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/unloadly\/assets\/icon-128x128.png?rev=3676981","icon_2x":"https:\/\/ps.w.org\/unloadly\/assets\/icon-256x256.png?rev=3676981","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/unloadly\/assets\/screenshot-1.png?rev=3676981","caption":"Per-page settings: in the editor, select the plugins whose CSS and JS should not load on that page."},{"src":"https:\/\/ps.w.org\/unloadly\/assets\/screenshot-2.png?rev=3676981","caption":"General settings: remove CSS and JS handles sitewide, and optionally remove oEmbed, REST API, and RSD links from the document head."},{"src":"https:\/\/ps.w.org\/unloadly\/assets\/screenshot-3.png?rev=3676981","caption":"Quick check: view source and search for the plugin folder name. This is a quick check, not a complete audit."}],"raw_content":"\n
Is your WordPress site slow, even with a cache plugin? One common reason is that plugins load their CSS and JavaScript files on every page<\/strong>, even on pages that never use them. A contact form plugin loads on your blog posts. WooCommerce loads on your About page. A slider loads on pages with no slider. Every extra file makes your pages heavier and slower to load.<\/p>\n\n Unloadly speeds up your website by stopping that waste.<\/strong> Edit a page, choose the plugins that page does not need, and their CSS and JavaScript files stop loading on that page. No coding, no hunting for script names, no complicated setup.<\/p>\n\n The result is smaller pages, fewer requests, and a faster website. It also helps with warnings like \"Reduce unused JavaScript\" and \"Remove unused CSS\" in tools such as Google PageSpeed Insights and GTmetrix.<\/p>\n\n Unloadly works alongside any caching or optimization plugin. It removes the files you don't need; your cache plugin serves what is left. Flush your cache after you change a rule.<\/p>\n\n For each URL Unloadly applies one list, in this order:<\/p>\n\n Category and tag rules also apply on that term's own archive page.<\/p>\n\n Unloadly removes assets by plugin folder and by script\/style handle. It is meant to sit beside the tools you already use, not replace them.<\/p>\n\n Do not disable a plugin on a page that actually needs it.<\/p>\n\n Developers can change post types, protected plugins, protected handles, and the disabled list for a request. Hook names are prefixed with Need help? Open a thread on the WordPress.org support forum<\/a>, visit the plugin page<\/a>, or email support@versouq.com<\/strong>.<\/p>\n\n\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n No. PHP still runs. Only matching frontend CSS and JS are dequeued.<\/p><\/dd>\n Yes. Per-page rules are stored on that page or post. Sitewide handle lists apply everywhere.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n Yes. Return 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.<\/p><\/dd>\n View the page source and search for the plugin folder name (the directory under Open a thread on the WordPress.org support forum or email support@versouq.com.<\/p><\/dd>\n\n<\/dl>\n\n\nWhy use Unloadly?<\/h4>\n\n
\n
Features<\/h4>\n\n
\n
wp_head<\/code>.<\/li>\nunloadly_<\/code>. See includes\/Hook.php<\/code>.<\/li>\n<\/ul>\n\nHow to speed up your site with Unloadly<\/h4>\n\n
\n
Rule priority<\/h4>\n\n
\n
Works with popular plugins<\/h4>\n\n
\n
Hooks<\/h4>\n\n
unloadly_<\/code>. See includes\/Hook.php<\/code>.<\/p>\n\nSupport<\/h4>\n\n
\n
unloadly<\/code> folder to \/wp-content\/plugins\/<\/code>, or install it from Plugins \u2192 Add New.<\/li>\n\n
How do I speed up my WordPress website by disabling plugins on certain pages?<\/h3><\/dt>\n
Why is my WordPress site slow even with a caching plugin?<\/h3><\/dt>\n
How do I disable a plugin on specific pages without code?<\/h3><\/dt>\n
How do I fix \"Reduce unused JavaScript\" in PageSpeed Insights or GTmetrix?<\/h3><\/dt>\n
How do I fix \"Remove unused CSS\"?<\/h3><\/dt>\n
Does this replace a caching plugin?<\/h3><\/dt>\n
Will this disable a plugin completely?<\/h3><\/dt>\n
Can I keep a plugin's assets on some pages?<\/h3><\/dt>\n
How is this different from other asset managers?<\/h3><\/dt>\n
How do category and tag rules interact with page rules?<\/h3><\/dt>\n
A post inherits a category rule but needs that plugin. What do I do?<\/h3><\/dt>\n
Can I turn off term inheritance?<\/h3><\/dt>\n
false<\/code> from the unloadly_supported_taxonomies<\/code> filter (pass an empty array) to hide the term fields, or use unloadly_resolved_plugins_for_post<\/code> to change what a post inherits. unloadly_inherit_term_ancestors<\/code> controls whether parent category rules cascade, and unloadly_apply_term_rules_to_archive<\/code> controls whether term archives use them.<\/p><\/dd>\nDoes it work with WooCommerce, Elementor, or Divi?<\/h3><\/dt>\n
How do I check that a plugin's CSS and JS were unloaded?<\/h3><\/dt>\n
wp-content\/plugins<\/code>). 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.<\/p><\/dd>\nWhere can I get support?<\/h3><\/dt>\n
1.1.0<\/h4>\n\n
\n
unloadly_supported_taxonomies<\/code>, unloadly_term_disabled_plugins<\/code>, unloadly_resolved_plugins_for_post<\/code>, unloadly_resolved_plugins_for_term<\/code>, unloadly_inherited_plugin_details<\/code>, unloadly_inherited_terms<\/code>, unloadly_inherit_term_ancestors<\/code>, unloadly_apply_term_rules_to_archive<\/code>, and unloadly_term_saved<\/code>.<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n
\n