Ironhelm Suite

One plugin instead of sixteen: what we cut, and why

By the Ironhelm team

Most WordPress sites run a stack of single-purpose plugins. What that costs, and how Ironhelm Suite replaces it without becoming the bloat it removes.

Open the plugin list of an ordinary business site and you will usually find the same stack: a security plugin, a login limiter, a two-step login plugin, a cache, an image optimiser, a script optimiser, an SEO plugin, a redirect manager, an analytics script, a cookie banner, an SMTP plugin, an activity log, a maintenance-mode plugin and a header-code plugin. Sixteen is not unusual.

Each one made sense on the day it was installed. Together they are a problem.

What a stack really costs

Every plugin is its own update cycle. Sixteen plugins means sixteen changelogs to trust, sixteen chances for a release to break something, and sixteen vendors whose security practices you are relying on.

Nobody owns the whole. The cache does not know the security plugin just blocked a request. The SEO plugin and the redirect plugin both rewrite URLs. Two plugins each add their own copy of a script. When a page gets slow or a form stops sending, finding the plugin responsible takes longer than fixing it.

Each one wants your attention. Admin menus, notices, upgrade banners and "rate us" prompts. Clients see them and ask what they mean.

Each one loads code. Many plugins load their code on every request, whether or not the feature is being used on that page.

What we built instead

Ironhelm Suite covers those jobs with 46 features in one plugin, and it was designed around three rules so that it would not become the bloat it replaces.

A feature that is off costs nothing

Every feature is a module with its own switch. When a module is off, its code is never loaded: not on the front end, not in the dashboard. You pay only for what you switch on, and the setup assistant switches on only what suits your kind of site.

One system, not a bundle

The parts were designed together. The firewall, login protection and activity log share one event stream. The page cache knows when SEO settings change and clears itself. Speed, security and search checks feed one health score with one list of what to fix next. Every screen uses the same words for the same things.

Plain words and honest defaults

"Login protection", not "brute-force mitigation". Every setting says what it does and what it costs. Risky features are marked, and nothing that could break a site is switched on without telling you.

What we deliberately left out

  • Page builders, forms and e-commerce. Ironhelm protects, speeds up and measures sites; it does not build them.
  • Backups. Your host should keep off-site backups, and a plugin that backs up the site it lives on shares that site's fate.
  • Cloud dependencies for core work. Images are converted on your own server, fonts are served from your own server, and visitor statistics stay in your own database.

Moving over

Switch Ironhelm's features on one area at a time, and deactivate the plugin each one replaces after checking the site. Coming from Yoast, Rank Math, All in One SEO, SEOPress, The SEO Framework or Redirection, run the importer first so your titles, descriptions and redirects come with you. The getting-started guide walks through it.

Fewer plugins is not the goal in itself. Fewer things that can go wrong is.


Ironhelm Suite is one WordPress plugin for security, speed, SEO and analytics. See plans or tour the features.