Why We Limit Plugin Count for Performance
It is tempting to add a plugin for every small feature, but each one adds code that loads on your pages, consumes server resources, and must be kept updated. More plugins is not more value — often the opposite.
We deliberately keep your plugin list lean to protect speed, security and stability.
How Plugins Affect Speed
Some plugins load extra scripts and styles on every page, even pages where their feature is not used. This bloats page size and slows loading.
The Hidden Costs
- More code to update and test each month.
- Greater chance of two plugins conflicting.
- A larger surface area for security issues.
- Harder troubleshooting when something breaks.
Our Approach
- Question whether a feature truly needs a plugin.
- Prefer one capable plugin over several narrow ones.
- Remove plugins that are no longer used.
- Measure page speed before and after additions.
Frequently Asked Questions
Is there a 'right' number of plugins?
There is no fixed limit — quality matters more than count. A few well-built plugins beat many poor ones.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.