FAQs About Freesoul Deactivate Plugins

It depends on how much your current plugins are slowing down your website.

A single poorly optimized plugin can cause more performance drag than 20 lightweight ones combined.

Freesoul Deactivate Plugins itself introduces no performance overhead, as confirmed by the official WordPress smoke tests shown below:

Naturally, the heavier your plugin load, the more significant the benefits of using Freesoul Deactivate Plugins will be. In short, it is highly effective even for just one plugin if that plugin is resource-heavy and not required on every page of your site.

Please read our detailed guide here.

Freesoul Deactivate Plugins allows you to disable specific plugins on a per-page basis. It is up to you to determine which plugins are unnecessary for a specific page.

If you disable a plugin that is not required for the page’s functionality and no other active plugins depend on it, you will not break anything. However, disabling a “core” dependency for another plugin will cause issues.

For example, if you use a WooCommerce add-on but disable the main WooCommerce plugin on that page, the add-on will fail to display content or may trigger PHP errors.

Note: The PRO version includes a feature that automatically suggests which plugins are safe to disable.

Yes, Freesoul Deactivate Plugins is compatible with all major caching plugins. If you encounter any specific issues, please open a thread on our support forum.

Most performance plugins that combine resources generate unique cached files for different script and stylesheet combinations, recognizing that different pages have different requirements. In these cases, you will still enjoy the full benefits of Freesoul Deactivate Plugins.

The following plugins are known to generate unique concatenated files based on the specific resources needed for each page:

Autoptimize WP Fastest Cache LiteSpeed Cache (Note: Avoid the option to “use the same combined file everywhere”) WP Rocket

If you use one of these for concatenation, you are fully covered. If you use a different plugin, ensure that it generates unique combined files for different pages; otherwise, scripts from “disabled” plugins might still be bundled into a global file.

A note on HTTP/2: If your server supports HTTP/2, it is often better not to combine files. Since HTTP/2 downloads assets in parallel, merging files offers little benefit and can actually hinder performance by invalidating browser caches more frequently.

Yes. However, in a Multisite installation, you must activate the plugin on each individual site rather than “Network Activating” it globally. You will only be able to manage plugins that are not already active globally across the network.

While fully supported, Multisite bugs are occasionally discovered due to the unique nature of those environments. If you encounter any issues, please let us know via the support forum.

Please follow the update instructions here.

You can find a detailed explanation and solution for this notice here.