3.1Install & manage plugins
The essentials in 30 seconds
- A plugin adds functionality without coding: form, SEO, cache, shop, backups.
- Install only from the official directory or a reputable publisher, and check updates, ratings and active installs.
- Few, but good: every plugin adds code and risk; overload is a major cause of slowness and vulnerabilities.
Running mini-case — equipping without weighing down
Samir must add a form, an SEO module, a cache and backups to Hassan's site. A colleague advises him to install a “pack” of twenty plugins to cover everything. Samir knows that every additional module adds weight and opens a security door. He chooses one plugin per need, checks their quality and clears out those that are not used.
Sequel to case 2.5 — the site is beautiful and responsive; it now needs the right tools.
1. Choosing a quality plugin
Plugins are WordPress's superpower: they add features without writing code. The official directory contains tens of thousands, many of them free. But every plugin is code running on the site: it can slow it down, conflict with another or contain a vulnerability.
Before installing, Samir checks four signals: a recent last update, a high rating, the number of active installations and compatibility with the WordPress version. He installs from the admin, activates the plugin, then notes where it adds its settings.
2. Avoiding overload and doing housekeeping
The rule is “few, but good”. One plugin per real need, not one plugin per imagined feature. A site creaking under forty plugins becomes slow, hard to maintain and more vulnerable. Many features can also overlap: two cache plugins or two SEO modules work against each other.
Samir keeps a list of plugins and their purpose. He uninstalls — not just deactivates — those that have become useless, after a backup. He enables automatic updates for trusted plugins and checks the site after every major update.
🔎 Concrete example — Equipping the workshop without overload (Samir's case)
Need 1: form → WPForms.
Need 2: SEO → Rank Math.
Need 3: cache → LiteSpeed Cache (depending on hosting).
Need 4: backups → UpdraftPlus.
→ 4 plugins, one per need, all maintained.
→ Uninstall the two unused modules left by the previous provider.Result: a site that is well equipped, clear and maintainable.
Lesson: every plugin must have a written reason to exist.
Section vocabulary
- Plugin
- Module that adds functionality to WordPress without coding.
Simple example: a contact form via a plugin.
What it is not: confusing a plugin with a theme (appearance).
Reflex: feature = plugin.
- Official directory
- The wordpress.org/plugins catalogue: checked plugins that can be installed from the admin.
Simple example: Samir installs from Plugins → Add New.
What it is not: downloading a “nulled” plugin from a third-party site.
Reflex: official = safe source.
- Quality criteria
- Recent update, high rating, many installations, compatibility.
Simple example: ruling out a plugin abandoned three years ago.
What it is not: choosing solely on the promise of the marketing page.
Reflex: four signals before installing.
- Freemium plugin
- Free version with a paid Pro option; the free version is often enough.
Simple example: free Rank Math for basic SEO.
What it is not: paying for Pro without an identified need.
Reflex: free first, Pro when needed.
- Plugin overload
- Too many plugins: slowness, conflicts and a larger attack surface.
Simple example: forty plugins for a brochure site.
What it is not: installing several plugins for the same feature.
Reflex: few, but good.
In practice — Installing a plugin properly
- Plugins → Add New: search for a useful plugin and check its update date, rating and installations.
- Install it, activate it and find where its settings are.
- Enable automatic updates for trusted plugins.
- Go through the list and uninstall the ones that are not used, after a backup.
Ready-to-use script — explaining plugins (20 s)
“WordPress stays lightweight: we add only the modules you need, one per function. The fewer modules there are, the faster and safer the site. I review them regularly and keep everything up to date.”
Link restraint to security and speed.
Copy-paste template — plugin register
PLUGIN: _______________ / NEED: _______________
LAST UPDATE: _______________ / RATING: _______________
AUTOMATIC UPDATES: yes / no
PLUGINS UNINSTALLED: _______________
BACKUP BEFORE CLEAN-UP: yes / noBrochure site
Four to six plugins are enough: SEO, form, cache, backups.
Shop
WooCommerce and its dedicated plugins, without duplicates.
Non-profit site
Avoid gadget modules; favour reliability and simplicity.
Taking over a site
Audit the list, back up, then gradually uninstall what is useless.
✓ Best practices
- One plugin per real need.
- Check maintenance before installing.
- Uninstall, not just deactivate, what is useless.
✗ Common pitfalls
- Installing a “pack” of dozens of plugins.
- Downloading pirated plugins.
- Stacking two plugins for the same feature.
Key takeaways
- Plugins add features without coding.
- Official directory and quality criteria above all.
- Overload is a major cause of slowness and vulnerabilities.
- Few, but good: one plugin per need.
48h Challenge — apply tomorrow
List your site's plugins and write down the need each one serves. Uninstall one useless plugin after a backup, then check that the site still works. 20 minutes.
- I choose a plugin on objective criteria.
- I install from a safe source.
- I limit the number of plugins and do the housekeeping.
Frequently asked questions
How many plugins can you install?
There is no magic number, but every plugin must serve a real need. A well-designed brochure site often runs with fewer than ten plugins; beyond that, each one must be justified and performance monitored.
Should I deactivate or uninstall a plugin?
Deactivating is enough for a temporary test. If the plugin is no longer useful, uninstall it: otherwise the useless files and tables remain on the server and increase the attack surface. Back up first.
Are automatic updates safe?
For reputable plugins and a backed-up site, yes in most cases. For major updates or critical plugins, it is better to test on a staging environment before production.
Samir wants to add a form and a cache to the site. How should he proceed properly?