The Plugin Bloat Problem: How Many Is Too Many?

This article may contain affiliate links. See our affiliate disclosure.

Hot take incoming.

We're going to make an argument here that we know will annoy some people. That's fine. The point of writing this is to think through something we've been quietly wrong about for years.

The conventional wisdom

For a long time, the standard advice has been clear. Pick the popular option. Use what the experts use. Don't reinvent the wheel. There's a reason this advice persists — it's right often enough that following it usually works out fine.

But 'usually' is doing a lot of work in that sentence.

Why we think the conventional wisdom is now wrong

Three things have changed.

First, the gap between 'popular' and 'good' has widened. The most popular WordPress plugins in the directory aren't necessarily the best — they're the ones with the best onboarding flow and the biggest marketing budgets.

Second, Google has gotten meaningfully better at rewarding original, useful content over content that just exists. Five years ago you could rank a thin 'ultimate guide' by stuffing keywords. In 2026 you cannot. The bar for ranking is higher than it's ever been, and that changes how the supporting tech stack should look.

Third, performance budgets matter in a way they didn't before. A site that loaded in 4 seconds on mobile in 2018 was acceptable. In 2026 it's a deal-breaker — both for users and for rankings.

What we're doing differently

On current projects, we're:

• Choosing lighter, less popular options when they have a clear performance edge
• Writing original analysis instead of summarizing what's already on page one of Google
• Skipping features we don't actively need, even if they're 'free'
• Investing in fewer but better external tools instead of more cheap ones
• Spending more time on testing and less on building

Where we might be wrong

We could be reading too much into a small sample of sites. The data we're working from is real but limited. Maybe in two years the popular options catch up and this whole essay reads as a temporary blip.

That said, the cost of being wrong is small. The cost of being right and not acting on it is much larger.

What you should take from this

Question the defaults. Read the actual code or actual reviews of the tools you're using. Stop using a plugin just because everyone else does. Run your own tests. Form your own opinion.

If you want to see what we're currently using on production sites, we keep a running list at RevealTheme.

— The RevealTheme Team