Using"Deactivate Plugins Per Page," you can quickly disable plugins on particular WordPress webpages (or all except a chosen page).
This helps speed up your website mainly because most front plugins will load their JavaScript and CSS resources on each page, even if you use these on a single page.
How does it work?
It's possible to add deactivation principles for active plugins. To get a contact form plugin, which you use on the contact page, add a rule to deactivate it on all URI except for your contact page.
Deactivation Rules Choices
1. Deactivation Sort
- Deactivate on chosen URI
- Deactivate on all URI except chosen
2. URI selection type
- Page
- Custom
3. [Page] Select webpages to extract URI out of (it will update automatically if the page slug varies )
3. [Custom] Custom URI state
- URI equals...
- URI doesn't contain equivalent...
- URI includes...
- URI doesn't contain...
- URI begins with...
- URI doesn't begin with...
- URI ends with...
- URI doesn't end with...
4. Affected devices
- All
- Desktop
- Mobile
Plugin Groups
Create groups of numerous plugins to be able to add deactivation principles that affect all of them.
Debug Mode
Enable debug mode to determine what's the URI and which plugins are active/inactive on the present page on the front end. This can allow you to create rules and examine current ones. A debug box may show up on the front if you're an administrator.
Does it impact the Back-end?
There's an alternative (not enabled by default) that makes all principles with Custom URI choice impact the backend. Some backend pages may still not be impacted to prevent issues, such as the webpages that restrain plugin activation, deactivation, upgrades, and setup.
Some items to Remember
When plugins are invisibly through my plugin, the true deactivation function isn't called, along with the deactivation hooks won't run. Rather, to make it operate per webpage, plugins are only dynamically removed from the plugins list before the page loads. This implies that when a plugin has any activities, it performs when deactivated; these activities won't run when deactivated through my plugin.
By way of instance, some plugins include code for a".htaccess" document when they're triggered, and if they're deactivated, they eliminate it. In this instance, if you include a deactivation rule together with my plugin to block the plugin on a specific webpage, the".htaccess" code will still be there and operate on such a page, though the plugin won't be busy on it.
Click on the below link to download NULLED version of Deactivate Plugins Per Page. Improve WordPress Performance NOW!
