Latest
What You Have to Decide Before Anybody WritesWriting It Before You Need ItCross Training Covered Everything Except the Role That Mattered MostBehind the Book: You Don’t Own Anything AnymoreBehind the Book: The Woke VirusBehind the Book: Galactic InvasionWhat’s New at The Writing King: Week of November 8, 2026Alexander Zhidkov: Decision MakingJessi Szurek: Expand Your RangeYou Don’t Own Anything AnymoreThe Budget Decided How My Department Was ShapedWhy Your Competitor’s Book Is Working and Yours Would NotWhy Are These Guys Smiling? A Business Book That Became a Wrestling MemoirPangram Wants to Decide Who Gets PublishedWhat You Have Enough Material For Right NowWhen a Book Is the Wrong ToolThe Woke VirusGalactic InvasionChatGPT Turns Four: From a Free Research Preview to GPT-6What’s New at The Writing King: Week of November 1, 2026Diwali: The Festival of Lights and the Story Behind the LampsHow Much Water and Power Does Heavy AI Use Take? I Ran My Own NumbersBad Boys: Ride or Die (2024)Vesuvius Day: The Teenager Who Wrote Down Pompeii’s Last DayAnti-Communism Week: Remembering the Writers Communism SilencedVoyager 1 One Light-Day: Fifty Years to Travel One Day of LightVellum Added an Optional AI Feature. A Pile-On Killed It in a Day.Are AI Subscriptions Losing Money? The Gym Membership Math Says NoAI Terms Every Writer Should Know, and Why Each One MattersWorking While Sick: What 24/7 On Call Cost MeHe Banned AI From His Writing Group. His Own Cover Got Called AI Slop.Who Writes the Fake Fan Mail Authors Get? Inside the Scam CompoundsSMS Appointment RemindersJoe Rockey: Ghostwriting His BookDarrell Stern: Stop Being Invisible, Become UnmissableFree BooksHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own Fault
The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

The Plugin Diet: Trimming WordPress Without Losing Muscle

TL;DR: After the theme surgery I put my plugins on a diet, and found them in better shape than expected: plugins have one job, and a job disciplines design. The diet still cut real weight, because every plugin is code someone must maintain and an update channel someone could poison. The rules I now use favor single-purpose plugins over Swiss Army platforms and an audit every year.

After the theme surgery I described earlier in this series, I turned to the plugins, expecting worse. I found better, and that surprise is worth unpacking, because plugins fail differently than themes, and the diet that fixes them is different too.

Why are plugins cleaner than themes?

WordPress plugins did better. When I opened up the plugins on my sites the way I’d opened the theme, the code was, on average, in noticeably better shape. Fewer grafted-together parts. Fewer dead limbs. More evidence that a single mind had thought the thing through.

Part of the reason is structural. A plugin usually exists to do a job, and a job disciplines design in a way that a theme’s job, which is to look like everything to everyone, doesn’t.

Part of it is review: plugins submitted to the official directory get a human security review at initial submission. That gate has limits, though.

Later updates aren’t re-reviewed, so the version you install in year three may share nothing but a name with the version a human once examined. Repository presence means a plugin passed a checkpoint once. I think a lot of site owners read that listing as a promise, and nobody is keeping it.

So plugins start cleaner. Then they grow, and growth is where trouble starts.

The fifteen-things problem

One pattern afflicts even good plugins. You install a plugin because it does one thing you need. It does that thing well. The author, needing reasons to ship updates and upsell a pro version, adds features.

A social sharing module. An analytics dashboard. A page builder element. An AI assistant, these days, always an AI assistant. Five years later the plugin you installed to do one thing does fifteen things, and fourteen of them load on every page of your site whether you use them or not.

You didn’t choose those fourteen things. They arrived by update, one release at a time, each too small to notice. This is how a lean site gets heavy without a single bad decision: every plugin on it is individually reasonable and collectively obese.

I think a lot of site owners read that listing as a promise, and nobody is keeping it.

I hate the upsell treadmill behind this. The author needs a reason to charge for version five, so your contact form grows a dashboard, and your visitors pay for somebody else’s business model in page weight on every single visit. The sign is the settings page. Open any plugin’s settings and count the tabs. One tab, maybe two: a tool. Six tabs, a dashboard, an onboarding wizard, and a menu item with a colorful icon at the top level of your admin: a platform, and platforms eat sites.

How do you audit your WordPress plugins?

The diet starts with an audit, and the audit is simpler than it sounds. I went through every plugin on my sites and asked each one the same questions. Anyone can do this in an afternoon, and no code reading is required.

What job does this plugin do for me? Not what can it do. What does it do, on this site, today. If you can’t answer in one sentence, that’s an answer.

What else does it do that I never asked for? Open the settings, look at the modules, see what’s switched on. Most multipurpose plugins let you disable the features you don’t use, and doing so is the cheapest performance win in WordPress.

What does it cost every visitor? A plugin that runs only in the admin costs your visitors nothing. A plugin that loads scripts and styles on every public page costs everyone, always. The distinction outweighs the plugin’s size on disk.

Who maintains it, and how actively? Check the last-updated date, skim the support threads, read the changelog. You’re looking for a living project, and this question matters enough that the next article in this series is devoted to it entirely.

What happens if I remove it? Some plugins leave cleanly. Some leave shortcodes bleeding raw text across five years of posts. Knowing which kind you’ve installed changes how casually you should have installed it.

Five questions for a WordPress plugin audit
Question How to check Why it matters
What job does it do for me? State it in one sentence, for this site, today If you can’t answer in one sentence, that’s an answer
What else does it do I never asked for? Open the settings and see which modules are switched on Disabling unused features is the cheapest performance win in WordPress
What does it cost every visitor? See whether it loads scripts and styles on public pages Admin-only plugins cost visitors nothing; front-end loaders cost everyone
Who maintains it, and how actively? Check the last-updated date, support threads and changelog You want a living project, not an unwatched update channel
What happens if I remove it? Learn whether it leaves cleanly or leaves shortcodes behind Some leave raw text across years of posts

What the diet removed

On my own sites the audit found the usual suspects.

Two plugins doing overlapping jobs because I’d installed the second without remembering the first. A plugin kept for one feature that WordPress itself had since grown natively. Several platforms-with-tabs where I used one module and carried six. A plugin last updated three years ago, which in supply chain terms, as the incident that started this series taught me, is an unlocked door nobody is watching.

Each removal followed the same discipline: confirm what the plugin did, make sure something else covered the real need, snapshot, remove, test. Boring, methodical, and the site got faster and simpler with every pass. The final stack is small, and every plugin on it has a one-sentence justification I can recite.

I’ll tell you what I don’t recommend: the plugin-count fetish. You’ll read that a good site has under ten plugins, or under twenty, as if the number itself were the measure. It’s not, because ten heavy platforms will bury a site that forty small single-purpose tools would leave fast. Count the weight.

My take

Count the weight and ignore the plugin count. Ten heavy platforms will bury a site that forty small tools would leave fast. Give every plugin a one-sentence job, switch off the features you never asked for, and pull anything nobody’s updated in years. Snapshot, remove and test, one at a time. Do the audit every year. An afternoon covers it, and every removal closes an update channel someone could poison.

The WordPress plugin food pyramidA hand-drawn food pyramid titled The WordPress plugin food pyramid, recommended daily allowance for a lean site. The wide base, eat daily, is single-purpose plugins: one job, one settings tab. The next layer, plenty, is admin-only plugins, which cost your visitors nothing. Above that, in moderation, are plugins that load scripts on every public page. The tiny red tip, sparingly, is platforms: six tabs, a setup wizard, a colorful menu icon and, these days, always an AI assistant. A box beside the pyramid lists what never to eat: a plugin last updated three years ago, two plugins doing the same job, and a plugin for something WordPress now does by itself. A footnote says to count the weight, not the plugins, and to check the label once a year.The WordPress plugin food pyramid(recommended daily allowance for a lean site)EAT DAILYSingle-purpose pluginsone job, one settings tabPLENTYAdmin-only plugins(cost your visitors nothing)IN MODERATIONScripts on everypublic pageSPARINGLYPlatforms: six tabs, a wizard,a colorful menu icon and,these days, always an AI assistantNEVERxA plugin last updatedthree years agoxTwo plugins doingthe same jobxA plugin forsomething WordPressnow does by itselfServing size: count the weight, not the plugins. Check the label once a year.
The WordPress plugin food pyramidA hand-drawn food pyramid titled The WordPress plugin food pyramid, recommended daily allowance for a lean site. The wide base, eat daily, is single-purpose plugins: one job, one settings tab. The next layer, plenty, is admin-only plugins, which cost your visitors nothing. Above that, in moderation, are plugins that load scripts on every public page. The tiny red tip, sparingly, is platforms: six tabs, a setup wizard, a colorful menu icon and, these days, always an AI assistant. A box beside the pyramid lists what never to eat: a plugin last updated three years ago, two plugins doing the same job, and a plugin for something WordPress now does by itself. A footnote says to count the weight, not the plugins, and to check the label once a year.The WordPress plugin food pyramid(daily allowance for a lean site)EAT DAILYSingle-purpose plugins(one job, one tab)PLENTYAdmin-only plugins(free for visitors)IN MODERATIONScripts onevery pageSPARINGLY:platforms (see 1)1. Platforms: six tabs, a wizard, a colorful icon and, always, an AI assistantNEVERA plugin last updated three years agoTwo plugins doing the same jobA plugin for something WordPressnow does by itselfServing size: count the weight,not the plugins. Check the label yearly.

What are the rules for a maintainable WordPress stack?

Going forward, four rules keep the weight off. Prefer single-purpose over Swiss Army. You can evaluate, trust, and replace a plugin that does one job. You have to adopt a platform, and adoption is the expensive relationship this whole series keeps warning about.

Audit annually. The stack that was lean last year has been updated fifty times since. The fifteen-things problem keeps happening one release at a time, so the diet has to keep happening too. Watch the front end. Before keeping any new plugin, look at what it adds to a public page. If a contact form plugin loads its scripts on pages with no form, that’s the author telling you how much they care about your visitors.

And treat every plugin as a standing update channel into your server, because that’s what it is. Fewer channels, better watched, from healthier projects. I’d much prefer to run a site on a dozen boring plugins I understand than on one flashy platform I can’t account for, and the security side of that choice is where this series goes next. If your own stack has gone soft and you’d rather have a professional run the audit, that’s work I do.

Frequently Asked Questions

How many plugins should a WordPress site have?
There’s no fixed number, and I distrust anyone who gives you one. People will tell you a good site keeps plugins under ten or under twenty, as if the count itself were the measure, but ten heavy platforms will bury a site that forty small single-purpose tools would leave fast. What matters is whether every plugin does a job you can name in one sentence and whether you know what it costs your visitors on every page. My own final stack is small, and I can recite the justification for every plugin still on it. I’d rather run more plugins that each do one clean thing than fewer plugins that have slowly grown into platforms.
Are WordPress plugins safer than themes?
On average, yes. A plugin exists to do one job, and a job disciplines design. Directory plugins also get a human security review at submission. Themes are built to look like everything to everyone, and it shows in the code.
Which WordPress plugins should you remove first?
Start with plugins doing a job WordPress itself now handles natively, since keeping them around just adds weight for nothing. Next look for overlap, where two plugins cover the same task because you installed the second without remembering the first. Then check the platforms-with-tabs, the ones where you use one module but the plugin loads six, and disable or remove the ones you never asked for. Finally check the last-updated date on everything, because a plugin last touched three years ago is an unlocked door nobody is watching. If you can’t state what a plugin does for you in one sentence, that itself is your answer to remove it.
Do unused plugins slow down WordPress?
Active ones can, deactivated ones mostly don’t, but speed is the lesser concern. Every installed plugin is code someone must maintain and an update channel someone could poison. The diet is about risk as much as weight.

Sources

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment