Your site has got slow, something broke after an update, and the advice you keep hearing is that WordPress is bloated and you should move to something modern.
Usually that is wrong, and expensively so. WordPress runs a very large share of the web, including sites far busier than yours, at speeds yours is not achieving. The platform is rarely the constraint. What you have installed on top of it almost always is.
How it happens
Nobody sets out to install thirty plugins. It accumulates, one reasonable decision at a time.
A contact form. A slider, because the homepage needed one. An SEO plugin. A second SEO plugin, because someone recommended a different one and the first was never removed. A backup plugin. A security plugin. A page builder, which brings its own add-ons. Three plugins that each exist to speed up the site.
Every one of those was a sensible answer to a real need. Collectively they are the reason the site takes six seconds to load.
What they actually cost you
The cost is not really the count. Ten heavy plugins are worse than thirty light ones. The cost shows up in four ways.
- Weight on every page. Many plugins load their own scripts and styles on every single page, whether that page uses them or not. A form plugin loading its assets on a blog post with no form is the normal case, not the exception.
- Database work. Each plugin asks its own questions on every page load. Individually trivial, collectively the reason a page takes seconds instead of milliseconds.
- Conflicts. Two plugins doing similar jobs will eventually disagree. Three caching plugins is not three times the caching, it is a debugging exercise.
- Abandonment. The real risk. A plugin whose author stopped maintaining it three years ago is an open door that no update will ever close.
That last point is the one that turns a slow site into an incident.
An audit you can do yourself
Open your plugins list and go through it once, honestly. For each one, answer three questions.
- What does this do, in one sentence? If you cannot say, that is the finding.
- When was it last updated? WordPress tells you, and it warns when something has not been tested against recent versions. Anything untouched for two years is a liability whatever it does.
- Does something else already do this? Duplicate SEO, caching, security and form plugins are extremely common.
Most sites lose a third of their plugins to those three questions without losing a single feature anyone uses.
Removing them without breaking the site
Order matters, and this is where people get burned.
- Take a full backup first, and confirm you can actually restore it. An untested backup is a hope.
- Deactivate, do not delete. Leave it off for a week and see what anyone notices.
- One at a time. Removing six at once and finding something broken tells you nothing about which one did it.
- Check the front end, not the dashboard. Forms, checkout, the contact page. Especially forms: silent form failures are the most expensive kind, because nothing looks wrong.
- Watch for orphaned content. Page builders and shortcode plugins leave their markup behind. Removing one can turn a page into visible code.
If you have no staging site, that is the finding to act on first. Doing this directly on a live site is possible but unnecessarily nervous.
When it genuinely is not the plugins
Two other causes account for most of the remainder.
Hosting. Very cheap shared hosting is slow under load in ways no amount of tuning fixes, because you are sharing a machine with hundreds of other sites.
Images. A photograph straight off a phone can be several megabytes. Ten of those on a page is the entire problem, and it is the single most common cause of a slow site that has nothing to do with plugins.
Working out which of the three you have is worth doing before spending anything, and it is a measurable question rather than a matter of opinion.
The honest summary
A slow, fragile WordPress site is usually a maintenance problem, not a platform problem. Rebuilding on something else moves the same habits to a new address, and in two years you will be having this conversation again about a different technology.
An afternoon of auditing is frequently the entire fix, and it costs nothing.
If you have gone through the list and cannot tell what half of them do, or something broke and you would rather not be the one experimenting on a live site, describe what is installed. How website work is handled here is set out separately.
Common questions
How many plugins is too many?
The count matters less than the weight. Ten heavy plugins are worse than thirty light ones. What actually causes trouble is duplication, abandonment, and assets loading on pages that never use them.
Is it safe to deactivate a plugin on a live site?
Deactivate rather than delete, take a backup you have actually tested restoring, and do one at a time. Check the front end, not the dashboard, and check forms in particular.
Should we move off WordPress to fix this?
Usually not. A rebuild moves the same maintenance habits to a new address, and in two years you have the same conversation about a different technology.