Deactivate Plugins Per Page – WordPress Performance Plugin

Product Overview

Many WordPress plugins load their scripts and styles on every page, even when they’re only needed on one. Deactivate Plugins Per Page solves this by letting you create precise rules that disable plugins exactly where they aren’t used—without uninstalling them.

Key Features

• Flexible deactivation rules: Deactivate plugins on specific URIs or everywhere except selected pages
• Multiple URI matching options: Choose from page selection (auto-updates if slugs change) or custom conditions—equals, contains, starts with, ends with, and their negative variants
• Device targeting: Apply rules to all devices, desktop only, or mobile only
• Plugin groups: Bundle multiple plugins and apply a single rule set to all of them
• Debug mode: Admins see a front-end box showing the current URI and which plugins are active or inactive—ideal for testing rules
• Optional backend control: Extend custom URI rules to the admin area (disabled by default, with safeguards for critical pages)

How It Works

Instead of calling WordPress’s standard deactivation hooks, the plugin dynamically removes selected plugins from the active list before the page loads. This per-page approach means:

• Plugin deactivation hooks don’t fire—so cleanup actions (like .htaccess modifications) aren’t triggered
• Plugins remain installed and active elsewhere on your site
• Resources only load where the plugin is actually needed

Benefits

• Faster page loads: Eliminate unnecessary JavaScript and CSS from pages that don’t use certain plugins
• Lower server resource usage: Fewer plugins initialized per request means reduced memory and CPU
• Better Core Web Vitals: Reduced script execution improves LCP, FID, and CLS scores
• Cleaner architecture: Keep plugins installed for the pages that need them without penalizing the rest of your site

Common Use Cases

• Contact form plugins active only on the contact page
• E-commerce plugins (cart, checkout) loaded only on shop pages
• Page builder assets restricted to pages built with that builder
• Analytics or chat widgets limited to landing pages
• Mobile-specific plugins deactivated on desktop (and vice versa)

Important Notes

Because plugins are removed from the active list dynamically rather than formally deactivated, any cleanup routines tied to deactivation hooks won’t run. For example, if a plugin adds rewrite rules to .htaccess on activation and removes them on deactivation, those rules will persist on pages where the plugin is disabled by this tool. Test your rules in debug mode before deploying to production.

Why Choose This Plugin?

Granular, rule-based plugin control without code. Whether you’re optimizing a single contact form or managing dozens of plugins across a complex site, the combination of flexible URI matching, device targeting, plugin groups, and a built-in debug view gives you precise performance tuning—safely and visually.