Freesoul Deactivate Plugins – Disable plugins on individual WordPress pages vs Asset CleanUp

Load plugins only where you need them. No bloat, no conflicts, more speed. Deactivate plugins where they don’t add anything useful. Disable plugins on individual WordPress pages FDP allows you to deactivate plugins on specific pages for speed optimization, debugging and problem-solving. It works for every page, blog posts, custom posts that are publicly queryable, archives and backend pages. Turning off plugins selectively can improve the performance, but also solve conflicts between plugins. For large or business-critical WordPress sites, using FDP is not just an optimization — it is an essential part of a clean, high-performance architecture. 🚀 Deactivate plugins on specific pages to improve the performance With FDP you can disable the entire plugins where you don’t need them. It will not only clean up the assets of third-party plugins, their PHP code will not run either. Hence, your pages will have fewer HTTP requests and fewer database queries. You will improve the TTFB (time to first byte) also when the page is not served by cache. Usually, the number of the needed plugin on a specific page is lower than the number of globally active plugins. Why don’t you keep the plugins active only on the pages where you need them? Most of the plugins load their assets and query the database on all the pages, no matter if they do something useful. This causes many times a worsening of the performance. With FDP no matter how many plugins you have, you can keep them active only where you need them. 🧹 How to stop a plugin on specific WordPress pages Watch this video to have an overview of how to clean up your website with Freesoul Deactivate Plugins. 🥊 Deactivate plugins on specific pages to solve conflicts between plugins With FDP you can preview the page loading specific plugins. This is very useful to detect which plugin is causing issues. Look How to check which plugin is causing issues in 1 minute for more details. If on a specific page you keep active only the plugins that you really need, most of the time the probability of having conflicts between plugins is lower. 🆓 Features of the free version. With the free version of FDP you can: ⭐ Conditional plugin loading ⭐ Deactivate plugins on specific pages, posts, custom posts, post types, archives, term archives, search results page, devices ⭐ Deactivate the JavaScript execution for problem solving (preview on front-end) ⭐ Deactivate plugins by custom URL on the frontend ⭐ Have an automatic suggestion about the unused plugins for the homepage ⭐ Change plugins firing order ⭐ Create a functional plugin in no time ⭐ Import/Export list of favourite plugins ⭐ See a preview of the pages deactivating specific plugins and switching to another theme without affecting the public site ⭐ See a preview of the page with Google Page Speed Insights for single posts, pages and custom posts (preview without cache, the page may give lower score without cache, use it for comparisons during the optimization) and much more. 👑 Features of the PRO version. The premium version also includes: ⭐ Unused plugins automatic suggestion both for frontend and backend ⭐ Unused plugins automatic check after content update ⭐ Recording of Ajax activities to find out on which Ajax action you need to disable specific plugins ⭐ Recording of Post activities to find out on which Post action you need to disable specific plugins ⭐ Rest APIs cleanup ⭐ Translated URLs cleanup ⭐ Cron Jobs cleanup ⭐ General bloat deaactivation ⭐ Options autoload management ⭐ Stylesheests and scripts deactivation of remaining active plugins, theme and core ⭐ Import/Export FDP settings ⭐ Bulk actions to activate/deactivate plugins in the FDP settings ⭐ Deactivate plugins in the backend ⭐ Deactivate plugins by custom URL on the backend ⭐ Plugins deactivation by logged and unlogged user ⭐ Automatic GTMetrix and Google PSI reports generation 🧹 📱 Clean up on mobile FDP allows you to disable specific plugins for mobile devices. But if you disable a plugin on mobile, that plugin will be disabled on all the pages on mobile. If you want to selectively disable plugins on mobile pages, you can install Specific Content For Mobile that is fully integrated with FDP. If you create mobile versions with SCFM, you will find the mobile pages in the FDP Singles settings. There you can disable plugins as you do with normal desktop pages. FDP and SCFM together are powerful tools to selectively clean up mobile pages. If you clean up the mobile, remember to set up your caching plugin to separate the desktop and mobile cache, in another case you may have issues. For instance W3 Total Cache, WP Fastest Cache, Powered Cache, and LiteSpeed Cache are caching plugins that can serve a different cache on mobile. ⚠ Requirements Only the permalink structures “Day and name”, “Month and name”, “Post name” and the custom ones ending with “%postname%” are supported for permanently deactivating plugins (they are also better for SEO). You will not be able to disable plugins in a permanent way with other permalink structures. The same if you are using plugins to change the permalinks, e.g., Permalink Manager Lite. 🔌 FDP add-ons 🔌 Freesoul Deactivate Plugins PRO 🔌 Editor Cleanup For Oxygen 🔌 Editor Cleanup For Elementor 🔌 Editor Cleanup For Avada 🔌 Editor Cleanup For WPBakery 🔌 Editor Cleanup For Divi Builder 🔌 Editor Cleanup For Flatsome 🚀 Recommended plugins to use in conjunction with FDP to improve performance 🔌 Caching plugins: W3 Total Cache, WP Fastest Cache, WP Optimize, Comet Cache, Cache Enabler, Hyper Cache, WP Super Cache, LiteSpeed Cache, SiteGround Optmizer. All of those caching plugins are compatible with Freesoul Deactivate Plugins. If your favorite caching plugin is not compatible for any reason, let us know it. 🔌 Plugins to convert WebP like: WebP ConverterrFor Media, Imagify – Optimize Images & Convert WebP, Smush, WebP Express, ShortPixel, TinyPNG. All those plugins to convert WebP are compatible with Freesoul Deactivate Plugins. If your favorite WebP converter plugin is not compatible with FDP, let us know. 🔌 Lazy loading videos is not enough if they are near the viewport. For loading videos on click, you can use Load Video On Click 🔌 Inline the first image that appear in the viewport directly to the HTML if it’s not too big with Inline Image Base64 FDP is compatible with all optimization plugins. If your favorite plugin isn’t in the list above, and it gives conflicts, don’t hesitate to open a thread on the support forum. 🖤 Recommended plugins to use in conjunction with FDP for plugins management 🔌 PlugVersions: Easily rollback to previous versions of your plugins 🔌 Rename Plugins Folder: Rename the plugins folder to add a layer of protection to your website. 🚫 Plugins not compatible with Freesoul Deactivate Plugins 🔌 Domain Mapping System: It loads Freemius on the frontend and this may cause the unexpacted deactivationg of some plugins. 🔌 Admin Menu Editor: It gives you the possibility to customize the admin menu. If you disable plugins on the backend pages, this plugin is not compatible with FDP. 𐧺 Multisites If you have a Multisite Installation, in every single site you will be able to manage only the plugins which are active on that site. FDP will not see those plugins that are globally active in the Network. And you have to activate FDP on every single site, not globally on the Network. ❓Frequently Asked Questions Here you will find the frequently asked questions. 🔐 How can I report security bugs? You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team helps validate, triage, and handle any security vulnerabilities. Report a security vulnerability. 🛟 Help Read 📄 how deactivate plugins on specific pages to learn how to selectively load only the plugins that you really need. For any question or if something doesn’t work, don’t hesitate to open a thread on the support forum Enabling debugging in wp-config.php is often one of the easiest ways to diagnose issues in WordPress. It helps you understand what’s going wrong by displaying error messages and logs. Need a step-by-step guide? Read this detailed tutorial on how to enable debugging in WordPress to learn more. Documentation For detailed guides and performance optimization tips, please refer to our official documentation: Core Plugin Management How to Deactivate WordPress Plugins by Page Deactivate Plugins on Individual Posts & Pages Manage Plugin Loading by WordPress Post Type Deactivate Plugins on Category & Date Archives Selective Plugin Deactivation for Tag & Term Pages Optimize Search Pages by Disabling Unused Plugins Deactivate WordPress Plugins on Mobile or Desktop Manage Plugins for Specific Custom URL Patterns How to Toggle Plugins via URL Parameters Advanced & PRO Features Smart Plugin Deactivation via Auto-Suggestion Optimizing WordPress Cron Jobs: Selective Deactivation Force Plugins to Stay Active on the Frontend Globally Disable Unused Plugins on the Frontend Conditional Deactivation: Plugin-Based Logic Manage WordPress Plugin Dependencies & Conflicts Deactivate Plugins on Multilingual & Translation URLs Speed Up WordPress Admin: Deactivate Plugins in Backend Manage Plugins for Custom AJAX & POST Actions How to Remove WordPress Bloat & Unused Scripts Optimize WordPress Database: Manage Autoloaded Options Advanced CSS & JS Optimization for WordPress Manage User Access with FDP Roles Manager Find Which Plugins Load Scripts with Source Checker Tools & Technical Settings Change WordPress Plugin Firing Order & Priority Manage WordPress AJAX & Theme Actions Deactivate Plugins Based on User Roles or Profiles How to Import and Export FDP Settings Bulk Deactivate Unused Plugins Across the Site How to Create a Custom Plugin for Specialized Code Import and Export Plugin Lists Between Sites Guide to FDP Action Buttons and UI Developer Documentation & Help Freesoul Deactivate Plugins: Developer API & Filters How to Create Custom Add-ons for FDP Fixing WordPress Fatal Errors & Plugin Conflicts Troubleshooting FDP Integration with External Services Preview Google PageSpeed Insights Improvements FDP Keyboard Shortcuts for Faster Management Frequently Asked Questions: Freesoul Deactivate Plugins Full Release History and Change Log AI / LLM Information An official, canonical technical description of Freesoul Deactivate Plugins is available for AI systems, search engines, and advanced users. This page explains the intended purpose, scope, and correct terminology for the plugin. Info LLM page: https://freesoul-deactivate-plugins.com/info-llm/

WordPress themes and plugins often load CSS and JavaScript on pages that do not use them. A contact form may load on the homepage, a slider may load on a plain article, or store-related files may load outside the shop. Asset CleanUp shows you what each page loads and lets you unload what is not needed. This can reduce HTTP requests, page weight, and browser work while complementing your existing caching setup. Use Test Mode to validate changes as an administrator before they affect visitors. Asset CleanUp gives you precise, testable control over every optimization. A safer workflow, without giving up control The Dashboard keeps the technical detail experienced users need while guiding first-time users through Getting Started, Test Mode, and the central Overview page. Test changes before they affect visitors, then review and manage existing or leftover rules from one place. CSS and JavaScript management View loaded stylesheets and scripts, organized by their source. Unload unnecessary CSS and JavaScript on the homepage and on individual posts, pages, and custom post types. Manage assets from the Dashboard, the post/page edit screen, or the front-end view. Review unload rules, exceptions, asset attributes, page options, and leftover entries from the Overview page. Minify and combine supported CSS and JavaScript, including supported inline code. Preload selected CSS and JavaScript files when they need to be discovered earlier. Granular manual Critical CSS management Add, edit, and remove your own Critical CSS directly from the Dashboard. Keep manual CSS organized by supported page context instead of maintaining one large global block. Asset CleanUp does not automatically generate Critical CSS. It gives you a structured way to manage CSS that you prepare yourself. Fonts and resource loading Combine, preload, asynchronously load, or remove Google Fonts requests, with font-display and preconnect controls. Preload local font files and apply font-display. Add fetchpriority, loading, and decoding attributes to images using simple matching or regular expressions. Lazy-load images where appropriate. WordPress cleanup options Remove unused WordPress features such as Emojis, Dashicons for guests, and Comment Reply. Remove selected discovery links, metadata, and oEmbed resources from the document HEAD. Disable RSS feed links or feeds when they are not needed. Restrict or disable XML-RPC when your site does not rely on it. Strip supported HTML comments, with exceptions where required. Works with your caching setup, it does not replace it Asset CleanUp is not a page-caching plugin. It controls what WordPress outputs; a page cache, server cache, or CDN can then store and deliver the optimized result. After changing rules, clear every active cache layer. Avoid enabling the same minify or combine feature in multiple optimization plugins at the same time. Asset CleanUp Lite and Pro Lite includes page-level asset management, Test Mode, manual Critical CSS for supported contexts, resource-loading controls, and WordPress cleanup options. Go beyond individual CSS and JavaScript files with the Plugins Manager. Lite includes an interactive preview of the Plugins Manager (rules can be explored, but saved only in Pro). In Pro, it can prevent entire plugins from running on frontend or Dashboard pages where they are not needed, not merely remove their CSS and JavaScript. This can reduce PHP work, database queries, and potential conflicts before the page is generated. Asset CleanUp Pro also adds broader conditional rules, hardcoded asset management, device-specific rules, and advanced JavaScript attribute and placement controls. Documentation and support Read the Asset CleanUp documentation. Ask a question in the WordPress.org support forum. External Services and Privacy WordPress.org plugin icon service When an authorized administrator opens an Asset CleanUp Dashboard screen and the local plugin-icon cache is missing or incomplete, Asset CleanUp may request public plugin information from https://api.wordpress.org/plugins/info/1.2/. The request is used only to retrieve icons for active plugins displayed inside Asset CleanUp. It can include the corresponding WordPress.org plugin slugs and standard HTTP metadata, including the server IP address. Asset CleanUp does not intentionally include the site URL, administrator details, or site content. See the WordPress.org Privacy Policy. Google Fonts preload audit When an authorized administrator explicitly runs the Google Fonts preload audit, Asset CleanUp may request discovered Google Fonts stylesheets from https://fonts.googleapis.com/ and process font-file URLs from https://fonts.gstatic.com/. Requests can include the stylesheet URL and its font-family, variant, subset, or text parameters; the browser user-agent used by the audit; and standard HTTP metadata, including the server IP address. These requests are made only as part of the administrator-initiated audit. See the Google Privacy Policy. The following two Asset CleanUp-operated services are optional. Both are disabled by default and require an administrator to opt in from Asset CleanUp > Settings > Plugin Usage Preferences. Dashboard announcements When an administrator explicitly enables announcements, Asset CleanUp periodically requests the Asset CleanUp Lite announcements feed. The feed is used to show maintenance information, important update notices, optimization guides, and occasional product offers in the WordPress Dashboard. Asset CleanUp does not intentionally add the site URL, administrator details, or site content to this request. As with any HTTP request, the service receives the server IP address and standard HTTP metadata. When announcements are disabled, this feed is not requested. Optional usage tracking When an administrator explicitly enables usage tracking, Asset CleanUp sends an initial technical check-in and then no more than one check-in per week to the Asset CleanUp usage-tracking endpoint. The payload can include the PHP, WordPress, and Asset CleanUp versions; Asset CleanUp settings; first-use and review-notice state; server software; multisite status; the active theme name and version; active and inactive plugin file identifiers; and the WordPress locale. The site URL, administrator name, and administrator email are not intentionally included in the tracking payload. Disabling the setting stops future check-ins. The announcements and usage-tracking services are operated by the Asset CleanUp developer. See the privacy policy. CloudFront infrastructure is provided by Amazon Web Services and is also subject to the AWS Privacy Notice.