Velocity Forge is a WordPress performance plugin. It measures what real visitors actually get — Core Web Vitals collected from their browsers, per page and per device — and then names what to do about it: which element was the largest paint and what file it was, which control the slow interaction hit, and whether the time went on a busy main thread, on the site’s own handler or on the repaint afterwards. Those three are three different problems with three different fixes, and until a measurement carries one of them a number is only a number.
What it does with that knowledge is deliberately narrow: defer, delay or dequeue the scripts that block the first paint, inline the critical CSS, generate WebP/AVIF sidecars, and clear out bloated autoloaded options — with the optimiser living in the paid add-on and the measurement living in the free plugin.
Its organising rule is not speed but reversibility. Every optimisation has an undo, and the undo has to work when the site is already broken: a VELOCITYFORGE_PANIC constant in wp-config.php that reads no database at all, a URL panic switch whose secret is also written to a file readable over SFTP, a Safe Mode toggle in the admin bar on the front end as well as in wp-admin, and a recovery drill that presses all of those on a day when nothing is wrong so you find out then rather than later. uninstall.php restores any unreverted autoload backups even when the user did not opt into destructive uninstall — deleting a performance plugin must not leave its white screen behind.
Since 2026-09-05 the reversibility runs the other way too: with the Pro add-on a rule that has just started applying is measured for a day against the week before it, and undone by the plugin itself if real visitors got slower.
A set of hard rails is never optimisable, whatever the settings say: jQuery, the block-editor runtime, WooCommerce cart and checkout, Stripe and PayPal SDKs, captchas, and Velocity Forge’s own beacon.
Velocity Forge is built by Avakode (avakode.com) and is one of the Forge Suite tools. Its landing is velocityforge.app.
## Quick facts
- Two plugins, not a flag:
velocityforge(Free, WordPress.org channel) contains no Pro code and calls no licence check anywhere;velocityforge-prois a separate add-on that requires the free core. Every entry in the feature map (plugin/includes/class-license.php) is checked from insidepro/— a lock screen over code the free user already downloaded is what wp.org rejected a sibling plugin for in August 2026, and two tests hold the line. - The five paid keys, in full:
asset_rules(the optimiser, whole — asset rules, critical CSS, image conversion, autoload and transient cleanup, sold as one purchase),alert_channels,beacon_retention,ai_advisor,scheduled_monitoring. Nothing else in the product is gated. - Free: real-user Core Web Vitals (LCP, INP, CLS, TTFB, FCP) profiled per URL and per device, kept thirty days by default and up to ninety on request; attribution and the two cards built on it — the ten controls that cost the most interaction time and the five elements that most delay the first paint, each with the file and the plugin behind it; the thirty-day p75 trend chart, inline SVG with no JavaScript; the Speculation panel; the asset inventory; image delivery hints; database health with the owner of every heavy autoloaded option; cache-plugin detection and coexistence across seventeen plugins; post-update regression monitoring with the e-mail and with the list of assets the update changed; batch scanning up to fifty URLs; the recovery drill; the Safe Mode toggle in the admin bar; and the whole rollback surface including both panic switches.
- Pro: the optimiser (defer / async / delay / dequeue rules with per-page scoping, critical CSS, WebP/AVIF conversion, autoload cleanup, expired-transient purging); self-reverting rules — a watch that undoes a rule the field data disagrees with; regression alerts to Telegram, Slack or a webhook with the secrets encrypted at rest; a year of field data instead of thirty days, with CSV export; scheduled lab audits through the operator’s own PageSpeed Insights key; and the AI performance advisor.
- Credits: exactly one thing in Velocity Forge spends Forge credits — the Pro AI performance advisor, which posts the
perf_adviseaction to the shared Forge API. That action is priced at 1 credit per run in both tables —ACTION_COSTSin forge-api and the badge mapForge_Credits_Widget::get_action_costs()in the add-on (pinned explicitly on 2026-09-06; before that the API fell back to 1 and the button showed no badge) — so the button quotes 1 credit before you press it. Everything else — measuring, deferring, converting, reverting, the rule watch, the alerts, the lab audits — costs no credits at all. Credit packs are 250 for $3, 1,000 for $9, 5,000 for $35 and 25,000 for $149. - Free, and often assumed to be Pro: the attribution cards, the “what changed” column on a regression, the owner column on autoloaded options, the recovery drill, the admin-bar Safe Mode toggle, the regression e-mail, the trend chart, the database health report, LCP hints and fifty-URL batch scans. Five of those became free in 1.1.0 because their code always shipped in the free download.
- Not features, and deliberately so: “agency reports” was listed until 2026-09-03 with nothing behind it and was withdrawn rather than hurried. Alert digest mode and quiet hours exist in Guard Forge and were deliberately not ported: Velocity Forge has one severity of event, so there is nothing to schedule around. There is no import/export of the alert channel configuration. The AI advisor applies nothing — there is no apply-the-plan button, which is also why no watch opens on its advice.
- Pricing (annual, Forge Builder): Personal $49/yr (1 site), Professional $109/yr (5 sites), Agency $189/yr (unlimited). Set discounts: 2 tools 15%, 3 tools 25%, 4 or more 35%, on every renewal.
- Requirements: WordPress 6.5+, PHP 7.4+.
- Money-back: 30 days.