WordPress plugin intelligence profile

LoadGate Forge

Stop selected plugins from loading on chosen front-end URLs. Lighter pages, reversible, and admin, login and REST are never touched.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.1.1
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.3 · PHP 7.4
Directory statusactive
Last directory update28 Oct 20265d ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records LoadGate Forge version 1.1.1 as active, updated 5d ago and tested up to WordPress 7.1.

Overview

About this plugin

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.
WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • conditional
  • optimization
  • performance
  • plugins
  • speed
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.3 · PHP 7.4
Update activity28 Oct 20265d ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

Version1.1.01.1.1
WordPress compatibility7.1.37.1.4
Version1.0.01.1.0
WordPress compatibility7.1.27.1.3
Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.