LoadGate Forge

Most sites run a few plugins that are only needed on one or two pages: a form plugin used on the contact page, a gallery plugin used in the portfolio, a chat widget you only want on the homepage. Loading all of them on every request is wasted work.

LoadGate Forge lets you say “do not load this plugin on these URLs” and takes it off those requests entirely, so the code never runs there.

• Pick a URL path and the plugins that should sit out on it.
• Match by “contains”, “starts with”, or an exact path.
• A master switch turns every rule off in one click.
• Nothing is deleted and nothing is permanent. Clear a rule and the plugin loads normally again.

To take a plugin off a request, the decision has to happen before WordPress loads plugins. LoadGate Forge does that through a small must-use loader it installs for you on activation, and removes when you deactivate.

What it does not touch

Rules only ever apply to normal front-end page views. The admin area, the login screen, REST API calls, cron and WP-CLI are always left with every plugin active, so you cannot lock yourself out of the dashboard.

Good to know

• Matching happens before the page template is known, so rules are based on the request URL, not on conditional tags like is_page().
• Disabling a plugin that builds a page will break that page. Test each URL after you save a rule.
• Single-site installs. Multisite network activation is not supported yet.