There is a WordPress plugin called Essential Addons. I have nothing against the plugin, and this is not a review of it. I keep coming back to the name. If it is essential, why is it an add-on?
What the Name Admits
The name says out loud what plugin listings usually leave out: the product underneath shipped without something you cannot do without.
In this case it is two layers deep. Essential Addons extends Elementor, a page builder, and Elementor is itself a plugin on top of WordPress. A single page on the site now depends on three products from three vendors:
| Layer | What it is | Who maintains it |
|---|---|---|
| WordPress | The CMS | WordPress core contributors |
| Elementor | A page builder plugin | Elementor’s vendor |
| Essential Addons | Widgets for the page builder | A third vendor |
Each has its own release schedule, its own licence, its own support channel and its own security advisories. When one of them changes, the other two have to keep up.
The Cost That Is Not on the Plugin Page
Installing a plugin takes a minute. Owning it takes the life of the site. Every plugin is something someone has to:
- install and configure
- update, ideally on staging first
- test against every other plugin on the site
- renew, if it is a premium plugin
- eventually remove, along with whatever it left in the database
We see where that cost lands when we run security updates. The sites that cannot go live on the first pass cluster around the same causes: premium plugins that cannot update themselves, plugins that need more memory than the site was given, and plugins that want a newer PHP version than their neighbours. An add-on to an add-on gives each of those one more place to happen, and the update for the add-on has to wait for the plugin it extends.
This Is Not an Argument Against Plugins
WooCommerce is a plugin, and nobody builds a WordPress shop without it. Plugins that carry the business are worth their maintenance, and in most verticals three to five of them do exactly that: the shop, the booking system, the membership area, the forms that bring in leads.
The rest is convenience. Some of it is worth it. A lot of it adds a widget, a shortcode or three lines of code to a theme. A plugin that adds three lines of code is not convenience. It is a future meeting.
The Rule We Use
Our house position is fewer plugins, more custom code. Small site-specific behaviour goes into a custom plugin, where the next developer will look for it. It updates when the site’s code does and depends on no other vendor’s roadmap.
Before installing the next essential add-on, ask two questions:
- What gap in the base product does it fill?
- Is that gap worth a vendor relationship for the life of the site?
If the answer to the second is yes, install it and keep it updated. If the honest answer is “it saves us an hour today”, the hour is usually cheaper.
