Deactivate Plugins Per Page - Improve WordPress Performance

Deactivate Plugins Per Page is a WordPress plugin designed to optimize your website's performance by selectively deactivating extensions on specific pages. Instead of loading all plugins on every route of your site, this plugin allows you to create clear rules at the page, content type, or file level, running only what you really need at each moment.

The problem it solves is very common: many front-end plugins load their JavaScript and CSS files on all pages, even when they are only used on one. This generates more HTTP requests, more database queries, and slower loading times. With this plugin, you can add deactivation rules for specific plugins. For example, if you use a contact form plugin only on your contact page, you can create a rule to deactivate it on all other URLs.

Its main features include:

• Rules by page, content type, and file: control exactly where each plugin is loaded.
• Plugin groups: group extensions that depend on each other to avoid errors when deactivating only one of them.
• Resource optimization: reduce HTTP requests and database queries, improving TTFB and overall site speed.
• Debugging and conflict resolution: useful for identifying which plugin causes problems on specific pages.
• Simple interface: intuitive admin panel that allows managing rules without needing advanced technical knowledge.
• WooCommerce compatibility: ideal for online stores where unnecessary plugins can be deactivated on product or checkout pages.

This plugin is aimed at WordPress administrators, developers, and agencies that manage sites with many installed plugins and seek to improve loading speed without rewriting code or changing themes. It is especially useful for e-commerce sites, blogs, portals, and corporate pages where performance is critical for user experience and SEO positioning.

It is important to note that page-level deactivation is not native WordPress behavior, so it is recommended to make backups and test changes in a staging environment before applying them in production. The plugin is designed mainly for speed optimization and debugging, not for hiding sensitive content.