Improve WordPress Performance with the Deactivate Plugins Per Page plugin
With the “Deactivate Plugins Per Page plugin – Improve WordPress Performance” feature, you can easily disable plugins on certain WordPress sites (or all but selected sites). This is useful for speeding up your site, especially since many front-end plugins load their JavaScript and CSS content on every page, even if you’re using them on a single page.
Recommended: Divi Shop Builder for WooCommerce
Deactivate Plugins Per Page – How does it work?
You can add rules to deactivate active plugins. For example, for a contact form plugin used only on the contact page, simply add a rule to deactivate it on all URIs except the contact page.
Demo: https://codecanyon.net/item/deactivate-plugins-per-page-improve-wordpress-performance/23801359
Deactivation Rules Options for Deactivate Plugins Per Page
1. Deactivation Type
- Deactivate on selected URIs
- Deactivate for all but selected URIs
2. URL. Select a type
3. Select Page Extraction URI (this will automatically update if the page slug changes)
4. Customize URI Conditions
- URI is equal to…
- URI is not equal to…
- URI contains…
- URI does not contain…
- URI starts with…
- URI does not start with…
- URI ends with…
- URI does not end with…
5. Affected Devices
Plugin Groups
Create multiple plugin groups to add deactivation rules that affect all plugins.
Debug Mode
Deactivate Plugins Per Page Enable debug mode to see what the URI is and which plugins are active/inactive on the current page on the front-end. This will help you create rules and inspect existing rules. If you are an administrator, a debug box will appear on the user interface.
Does deactivating plugins per page affect the back-end?
The Deactivate Plugins Per Page plugin has an option (not enabled by default) that causes all rules with custom URI selections to also affect the backend. Some backend pages will remain unaffected to avoid issues, such as those controlling activation, deactivation, updating, and installation of plugins.
Preventive Measures for Deactivating Plugins Per Page
A Group of Plugins That Work Together
If you have a plugin that requires another plugin to work, you’ll need to add those plugins to a plugin group and add the deactivation rule to that group. Deactivating just one plugin may cause errors or deactivate all other plugins.
Do not deactivate plugins required by your theme
Some themes require certain plugins to work properly. If you deactivate these plugins, you may experience issues.
Deactivation hooks not run
When deactivating the Deactivate Plugins Per Page plugin via my plugin, the actual deactivation function is not called, and the deactivation hook is not run. Instead, to make it work on every page, the plugin is simply dynamically removed from the list of active plugins before the page loads. This means that if a plugin performs certain actions when deactivated, those actions will not run when deactivated through the plugin.
For example, some plugins add code to your .htaccess file when activated and remove it when deactivated. In this case, if you use my plugin to add a deactivation rule to disable the plugin on a certain page, the .htaccess code will still be present and work on that page, even though the plugin will not work on that page.
Do not use this plugin to hide sensitive data
It is not designed to work securely. It’s primarily used for site speed optimization, but can also be used to debug or resolve plugin compatibility issues. Deactivate Plugins Per Pageplugin.
Backup Your Website
Deactivating plugins on a page-by-page basis isn’t something natural for WordPress and plugin developers, and the Deactivate Plugins Per Page plugin isn’t intended to be. It works well most of the time, but sometimes it can cause crashes that disable other plugins or change settings. Always make a recent backup of your site, and if possible, test your changes on a staging site.
Currently tested up to
These Deactivate Plugins Per Page plugins are tested against the highest WordPress and PHP versions I’ve tested them on. They are not required, and will work with lower versions as well. They may also work with higher versions, but they haven’t been tested on higher versions yet.
Changelog: Deactivate Plugins Per PagePlugin – Improve WordPress Performance
v1.14.3 – 14 April 2022 Deactivate Plugins Per Page - Improve WordPress Performance - 4 FIXED: The settings were not showing correct values in Firefox after importing new values due to Firefox trying to autocomplete the old values after page reload. v1.14.2 – 9 April 2022 Deactivate Plugins Per Page - Improve WordPress Performance - 4FIXED: Assets not loading and incorrect paths when used in WAMP on Windows, due to incorrect directory separator. The PHP constant DIRECTORY_SEPARATOR has been removed now from the plugin.
⭐See also: Collection WordPress Plugins Updated Daily Free WP
DownloadDeactivate Plugins Per Page Plugin v1.17.0 – Improve WordPress Performance
Note: You may need to unzip the plugin before installing it. We offer no guarantee if any theme/plugin contains a virus. Please check Virustotal before using on localhost.