Plugin Load Filter

79 Quality Score

Active Installs

17/30

At 7,000 active installs it is a niche tool, well below the hundreds of thousands or millions that top cache plugins pull, but its install count is still respectable given how specialised the use case is.

Update Freshness

25/25

Updated 2026-04-20 and tested against WordPress 7.0 with a PHP 8.1 requirement, the maintenance signals are as current as anything in the directory.

User Rating

14/15

96 out of 100 from 52 ratings is an unusually high score, suggesting that the small group of users who do rely on it are very satisfied with the results.

Support Health

8/15

With 0 support threads opened and 0 resolved, there is no track record either way, and you should not expect an active forum presence if you hit a configuration edge case.

WP Compatibility

15/15

Tested with the latest WordPress 7.0 and requiring PHP 8.1 means it will not run on older PHP stacks, which is a deliberate modern cutoff rather than a sign of neglect.

Scores higher than 73% of indexed plugins

About

Dynamically activate the selected plugins for each page. Response will be faster by filtering plugins.

Active Installs 7k+

Rating ★★★★½ 4.8/5

Last Updated 2026-04-20 5:18am GMT

Requires WordPress 6.3+

Tested Up To 7.0.4

Requires PHP 8.1+

✓ No known vulnerabilities

What It Does

Plugin Load Filter lets you control which plugins load on specific pages, URLs, or request types rather than loading every plugin on every request. By skipping plugins that aren't needed for a given view, it trims PHP execution time, memory use, and HTTP requests on a per-page basis. It also supports locale-based filtering, useful for multilingual sites that don't need to load every language's plugins on every page.

Who It's For

This plugin is built for site owners running large stacks of 30+ plugins on constrained hosting, where the cost of loading everything on every request is a measurable bottleneck. It's a good fit for high-traffic sites, WooCommerce stores that want lean checkout pages, and multilingual networks where language-specific plugins should only fire on the matching locale.

Who Should Skip It

If you run a small site with under 15 plugins on decent shared or managed hosting, you almost certainly won't notice enough improvement to justify the complexity of configuring per-page rules. Also avoid it if you don't have the technical confidence to test which plugins are safe to disable on which pages, since over-filtering can silently break admin tools, AJAX handlers, and cron-driven features.

The Bottom Line

Plugin Load Filter solves a real problem that mainstream cache plugins don't address, and its near-perfect user rating and current maintenance show the developer is actively shipping. The trade-off is configuration complexity and a tiny install base with no support history, so it earns its value mainly on large, plugin-heavy sites where someone technical can manage the rules. For most sites, a standard page cache plugin will deliver bigger gains with far less risk.

Related Plugins

LiteSpeed Cache 95/100

Pick LiteSpeed Cache when your host runs LiteSpeed web servers and you want page caching, object caching, and image optimisation in one plugin rather than surgical plugin loading.

Jetpack 94/100

Pick Jetpack when you want a broad suite of performance, security, and growth features bundled together instead of a single-purpose plugin loader.

Redis Object Cache 92/100

Pick Redis Object Cache when your real bottleneck is database query time and you have Redis available on your server, which often delivers bigger wins than plugin filtering.

Super Page Cache 90/100

Pick Super Page Cache when most of your traffic is anonymous and cacheable, since serving static HTML from Cloudflare will outperform any server-side PHP optimisation.

WP Fastest Cache 89/100

Pick WP Fastest Cache when you want the easiest possible page caching setup without server-level configuration and don't need per-page plugin control.