Plugin bloat is real. But the “lean” solutions most agencies are selling? They’re often worse than the problem.
I just saw a post about reducing plugin bloat. The solution? A list of plugins (that you might not even need, that might not even fit your requirements) and WPCode to manage tracking pixels.
Let me explain why this is the opposite of lean—and how to spot when an agency’s ‘solution’ is actually making things worse.
The Fake Lean Promise
You see a list of 5 or 6 plugins and tell yourself, “Great, this agency knows what they’re doing.”
Then you look under the hood.
Your theme is loaded with functionality: custom post types, taxonomies, filters to modify other plugins, ACF field code, business logic that has nothing to do with design.
Now something goes wrong. ACF fails to update (yes, I’ve seen this happen). For some reason, it can’t be activated after the update.
Your site is broken. Completely inaccessible. Because your content structure lives in your theme and depends on a plugin that’s now broken. And because most of these custom themes are overpacked with spaghetti code and usually don’t include failsafe mechanisms.
This is fake lean.
They bragged about ‘only 6 plugins’ while hiding all the complexity and risk in your theme. Now your content structure is married to your design. Want to switch themes? Your post types disappear. ACF breaks? Your site dies.
That’s not lean architecture. That’s a ticking time bomb disguised as simplicity.
Stop Counting Plugins. Start Asking Better Questions.
Agencies obsess over plugin count like it’s the only metric that matters. “We only install 6 plugins!” But they’re asking the wrong question.
Before you accept an agency’s “lean” pitch based on plugin count, ask:
- Are those plugins doing things WordPress core can already do?
- Are they solving actual problems or creating dependency on the agency?
- Could custom blocks replace half of them?
- Are they Band-Aids for poor architecture decisions?
Plugin count isn’t the metric. Proper architecture is.
The Separation Problem Isn’t Just Themes
Even plugins get this wrong. A “contact form” plugin that also handles email marketing, CRM integration, analytics, and payment processing isn’t lean—it’s doing five different jobs poorly instead of one job well.
Or a “security” plugin that also handles performance optimization, image compression, and CDN management. Now if you want to switch security solutions, you lose half your site’s functionality.
When plugins (or themes) violate separation of concerns, you end up with:
- Can’t switch tools without breaking multiple features
- Updates become risky (one plugin update affects unrelated functionality)
- Debugging nightmares (which of the plugin’s 20 features is causing the issue?)
- Vendor lock-in (everything depends on this one bloated tool)
Proper separation means:
- Themes handle presentation
- Plugins handle discrete functionality
- Custom post types live in their own plugin
- Each tool does one thing well
- You can swap any piece without breaking others
And Then There’s the WPCode Approach
What baffles me is they could do the same with Google Tag Manager, which is much more efficient at it and is literally designed for this purpose. GTM keeps all your marketing tracking in one place, manageable by your marketing team, without touching your WordPress code at all.
But instead, they’re installing a plugin to store code snippets in your database.
Installing WPCode for tracking pixels isn’t lean. It’s:
- Adding another plugin (the thing you’re trying to avoid)
- Storing executable code in your database (security risk)
- Creating dependency on a third-party tool for basic functionality
- Something WordPress handles natively with template parts OR better handled by GTM
This is like buying a special tool to open a jar when you already have hands, and ignoring the jar opener sitting right there on the counter.
Why Agencies Do This
Because if clients could edit template parts themselves or switch themes without losing functionality, they wouldn’t need the agency. The ‘lean solution’ is actually a lock-in strategy.
Here’s the Reality
Not all sites need the same plugins. There’s no one-size-fits-all tech stack. Most sites could do just fine with core WordPress blocks plus a few custom blocks tailored to their specific needs.
But that requires agencies to actually understand what the client needs instead of installing their standard ‘essential plugins’ list on every project.
Red Flags That Sound Lean But Aren’t
🚩 “We build lean sites”
🚩 “We keep plugins to a minimum”
🚩 “We handle everything in the theme”
🚩 “We use the same proven stack for all our clients”
🚩 “We follow best practices”
What Actual Lean Looks Like
✅ Site built for YOUR specific needs, not agency’s standard stack
✅ Core blocks + custom blocks for your use cases
✅ Custom post types in a dedicated plugin (portable, theme-independent)
✅ Tracking scripts in template parts (no WPCode needed)
✅ Theme handles design, plugins handle functionality (proper separation)
✅ You or anyone on your team can update content
✅ Code lives in version control, not database
✅ Switch themes without losing functionality
Questions to Ask Your Agency
- Are my custom post types in the theme or a plugin? (They should be in a plugin)
- What happens if I want to switch themes?
- Why do we need a plugin for something WordPress does natively?
- Can I make basic changes myself, or do I need to call you?
- What happens if one of your ‘essential’ plugins breaks?
The Bottom Line
Real lean isn’t about having fewer items in the plugins list. It’s about proper architecture—themes for design, plugins for functionality, using WordPress core features correctly, and only adding solutions when they genuinely solve problems core can’t handle.
If an agency’s ‘lean solution’ looks the same for every client and creates more dependency on them, it’s not lean. It’s marketing.
Ready to build WordPress sites the right way? At Groundworx Agency, we focus on clean architecture, client empowerment, and maintainable solutions. Get in touch to discuss your project.