Freesoul Deactivate Plugins – Disable plugins on individual WordPress pages
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/
Top keywords
- deactivate27×1.64%
- fdp26×1.58%
- pages22×1.34%
- wordpress17×1.03%
- cache16×0.97%
- specific15×0.91%
- mobile13×0.79%
- page12×0.73%
- disable11×0.67%
- custom10×0.61%
- cleanup9×0.55%
- active8×0.49%
DietPress
DietPress is a free WordPress speed optimization plugin with a built-in page cache. Page caching, browser caching, GZIP and Brotli compression, deferred JavaScript, critical CSS, image loading attributes, preloading, locally hosted Google Fonts and selective asset loading, all in one plugin and all free. And it goes further than a caching plugin: it also puts WordPress itself on a diet, switching off the features your site never uses. It pairs that with a clean, risk-based interface. Everything is configurable, the optimizations are already on by default, and nothing is hidden behind a paid tier. Activate it and your site is faster, or open the settings and tune every detail. By default WordPress loads functions, services and scripts that most sites do not need. They slow down loading times and consume hosting resources. DietPress lets you trim that fat and apply battle-tested performance tweaks, with a clear description of what each option does and what might break, organized by risk level so you always know what is safe. WHY CHOOSE DIETPRESS Page caching, for free. Serve anonymous visitors a copy stored on disk instead of building the page again. The feature people buy WP Rocket or a NitroPack subscription for, with no licence and no monthly fee. No drop-in, no changes to wp-config.php. Unlike WP Super Cache or W3 Total Cache, DietPress installs no advanced-cache.php and never edits wp-config.php. Switching it off leaves your site exactly as it was, with nothing orphaned behind. It tells you why. Most cache plugins leave you guessing when nothing is cached. DietPress reports its own status, tests itself against your home page, and names the exact reason a page was skipped. WooCommerce-safe by design. Carts, checkout, my account and any visitor carrying a cart cookie always get the live site, so nobody ever sees somebody else’s basket. Diet as well as speed. Where Perfmatters focuses on disabling scripts, DietPress covers that ground and adds page caching, critical CSS, local Google Fonts and a dashboard, admin and email cleanup, in one plugin. Light on your server. No account, no external service, no telemetry, no upsell nags. Everything runs on your own hosting. WHAT THE PAGE CACHE DOES TO YOUR RESPONSE TIME Measured on a WordPress 7.0 install with GeneratePress, WooCommerce and a 76 product catalogue, PHP 8.5, taking the median of 15 requests per URL. Your own hosting will give different figures, but the shape of the result will not change. Server response time, the same pages with the page cache off and on: Home page – 52.7 ms without, 15.1 ms with, 71% faster WooCommerce shop – 45.4 ms without, 14.8 ms with, 67% faster A 110 KB article – 43.0 ms without, 15.1 ms with, 65% faster A 98 KB page – 41.0 ms without, 14.9 ms with, 64% faster A product category – 41.3 ms without, 15.1 ms with, 63% faster The interesting part is not the percentage, it is that the cached figure barely moves. Serving a stored file costs the same whether the page was cheap or expensive to build, so the saving grows with the size of your site rather than with the power of your server. The heaviest page in the test is the one that gained most. It also changes how much traffic your hosting can take at once. In the same test the server went from serving about 40 visits a second to more than 210, five times as many, on exactly the same plan. That is what keeps a small site standing up when one of your posts does well. TWO THINGS IN ONE PLUGIN 1. Performance optimizations (on by default) Automatic Critical CSS inlined in the head (optional experimental deferral of non-critical CSS) JavaScript defer parsing with smart dependency handling Image loading attributes safety net: lazy loading, decoding=async and fetchpriority for images that bypass core Automatic image dimensions for better CLS scores (including picture elements) Resource hints: preconnect and DNS prefetch for common third-party origins Theme stylesheet, critical fonts and logo preloading for a faster LCP Google Fonts display=swap Google Fonts local hosting: serve the fonts your theme uses from your own server, GDPR-friendly with a silent fallback to the Google CDN (opt-in) Selective third-party loading: WooCommerce, Contact Form 7, block library, Slider Revolution, TablePress, Smash Balloon, Formidable Forms and Everest Forms assets only load where they are used (opt-in) RSS feed optimization (cache headers and item limit) Server rules in .htaccess: browser caching with a configurable lifetime for media, for styles and scripts and for fonts, GZIP and Brotli compression, immutable cache headers, CORS for fonts and keep-alive (master switch plus per-feature toggles) Database maintenance: daily expired-transient cleanup and safe query optimizations Page cache: store each page on disk and serve it to anonymous visitors without building it again, with automatic purging, gzip precompression and a status panel that says whether it is working (opt-in, in its own tab) 2. Put WordPress on a diet (risk-based, opt-in) Light (safe for any site): emojis, RSD/WLW tags, shortlinks, self-pingbacks, comment pagination, and more Moderate (evaluate first): oEmbed, jQuery Migrate, Dashicons on the frontend, Global Styles and Duotone, remote block patterns, avatars and Gravatar, comment threading, and more Strict (site-specific): granular RSS feed control, Heartbeat API mode, post revisions and autosave, disable comments, XML sitemap, native lazy loading/fetchpriority, content types, selective loading for WooCommerce, Contact Form 7, block assets, Slider Revolution, TablePress, Smash Balloon, Formidable Forms and Everest Forms, and more Widgets: dashboard widgets (including third-party ones from Yoast, WooCommerce, Elementor, Jetpack, Wordfence, Rank Math, Gravity Forms), classic sidebar widgets, block-editor widgets and the Customizer Emails: silence the automatic emails WordPress sends on its own, grouped by area: auto-update results for core, plugins and themes (plus the new-version notice), comment moderation and new-comment notices, and new user, password and email-change notices, plus toggles for the admin email verification prompt and post-by-email. Every option is off by default, and critical notices such as a failed core update are always kept SCALE, PROFILES AND ANALYZER Savings indicator: HTTP requests removed, CSS/JS saved and active optimizations at a glance Quick profiles: Personal Blog, WooCommerce Store, Landing Page and Maximum Cleanup Site analyzer: personalized recommendations based on your active plugins and content, page cache included Import and export your whole configuration as a JSON file COMPATIBILITY AND EXTENSIBILITY The plugin includes filters for developers: dietpress_critical_css – Customize the inline critical CSS dietpress_critical_css_handles – Define which CSS handles are critical dietpress_skip_defer_script_handles – Opt scripts out of the JavaScript defer dietpress_skip_defer_style_handles – Opt stylesheets out of the CSS deferral dietpress_preconnect_hints – Customize preconnect origins dietpress_dns_prefetch_domains – Customize DNS prefetch domains dietpress_critical_fonts – Define critical fonts to preload dietpress_exclude_local_fonts – Exclude Google Fonts stylesheets from local hosting dietpress_selective_{module}_has_content – Mark a page as showing the content of a selective loading module, so its assets are kept. The module is wc, cf7, formidable, everest_forms or revslider dietpress_selective_{module}_styles / dietpress_selective_{module}_scripts – Adjust the handles removed by each module dietpress_selective_page_hides_content – Mark a page as rendering content the content scan cannot reach, so no module removes anything (this is what handles Elementor) dietpress_selective_is_wc_page – Override the WooCommerce page detection of selective loading dietpress_selective_wc_keep_cart_fragments – Keep the cart fragments script when your theme has a hand-coded mini-cart dietpress_selective_cf7_has_form – Mark pages that load a Contact Form 7 form dynamically dietpress_selective_blocks_dequeue – Override the block library dequeue decision dietpress_selective_everest_forms_dequeue_dashicons – Keep Dashicons when another plugin enqueues it directly dietpress_native_sitemap_in_use – Tell DietPress your plugin builds on the native WordPress sitemap, so the option that removes it becomes unavailable dietpress_cache_bypass – Keep the current page out of the page cache dietpress_cache_bypass_cookies – Adjust the cookie name prefixes that make a visitor uncacheable dietpress_cache_ignored_params – Adjust the query parameters that do not change the page dietpress_cache_exclude_urls – Adjust the excluded URL patterns dietpress_cache_post_urls – Adjust the URLs purged along with a post Compatible with: Well-coded themes and page builders (Divi, Elementor, Beaver Builder, Bricks Gutenberg) Cache plugins (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, etc.). The one exception is the optional page cache module, which will not run beside another page cache and says so; everything else in DietPress works alongside them as it always has Security plugins (DietPress focuses on performance and deliberately leaves security to them; we recommend our free Vigilant) CDNs (Cloudflare, StackPath, KeyCDN, etc.) thanks to CORS and Vary headers WordPress Multisite (except the optional page cache module, which does not support it yet) HOW TO VERIFY THE OPTIMIZATIONS Cache rules: check your .htaccess for a block marked # BEGIN DietPress with immutable Cache-Control headers Logo preload: view page source and look for pointing to your logo Critical CSS: view source and look for in the head Compression: test at giftofspeed.com/gzip-test Always measure with tools like Google PageSpeed, GTMetrix or WebPageTest, and run each test at least twice to account for caching. Support Need private support or custom development? Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just contact me and tell me what you need. Need help or have suggestions? Official website WordPress support forum YouTube channel Documentation and tutorials Love the plugin? Please leave us a 5-star review and help spread the word! About AyudaWP We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.