WordPress plugins: how many do you really need?
People ask how many WordPress plugins are too many as if there were a safe number. There is not. What matters is what each plugin does, who maintains it, and whether the site would miss it.
What is a plugin?
A plugin is a package of code that adds a function to WordPress. A contact form, a store, a second language, a cache, a booking calendar. Some are large systems in their own right: WooCommerce turns a site into a store, and LearnDash or Tutor LMS turn it into a course platform. Others do one small job. All of them run inside your site with full access to it.
Is there a right number?
No. A site with many small, well-written plugins can run better than a site with a few heavy ones. One careless plugin that loads its files on every page, or that asks the database too much, does more harm than several tidy ones together. So I would not count them. I would ask of each one what it loads, where, and why it is there.
What does every plugin add to my upkeep?
Four things. Code that has to load, which touches speed. Updates that have to be applied and checked. A chance of conflict with another plugin or with the theme. And a door that has to stay locked, because a plugin its maker has abandoned no longer receives security fixes. A plugin is never just installed. It is adopted.
How do I decide whether to add one?
Ask whether the function is needed at all, or only nice to have. Check whether the theme or the page builder already does it, since duplicates are common. Look at when the plugin was last updated, whether it is tested with current WordPress, and who makes it. And prefer one plugin that does the job well over three that each do a part.
How do I review the ones I already have?
Open the plugins list and go through it line by line. For each, name the feature on the site that depends on it. If you cannot, switch it off on a quiet day, check the site, and delete it if nothing changed. Deactivated plugins should be removed, not left in place, because their files still sit on the server and still need updating.
Who should install plugins after handover?
You can, but treat it as a change to the site, not as a download. Take a backup first. Install one plugin at a time, then look at the main pages, the forms and the checkout if there is one. If the site has a store or members, try the new plugin on a copy of the site first. When in doubt, ask the person who built it.
How I handle it
I build WordPress sites with Elementor Pro, and where the project needs it, with WooCommerce, LearnDash or Tutor LMS. The functions the site needs are settled at the design stage: every project is drawn in Figma and approved by you before the build, so nothing gets added later just because it was available. You get the dashboard, and for 180 days after launch support covers anything that breaks. Tell me what your site has to do, and I will tell you what I would build it with.
New articles every day on our Facebook page: Learn with MK
Have a project in mind?
Tell me what you are building and I reply within 24 hours.
