Your WordPress is slow or got attacked: how to find out why
Diagnosis before solution: measure, do not guess
Why a WordPress site turns slow or gets attacked, how to diagnose it with data and which fixes make sense for each case.
The short answer
A slow or attacked WordPress almost never has a single cause. It is diagnosed by measuring three things: what the server sends, what the browser loads and what the admin area does. Without that data, “optimising” means changing things at random.
The usual causes, by frequency
- Overloaded shared hosting. The site is not slow: the neighbour is eating the machine.
- Plugins. Many, badly built or abandoned. Often there are fifteen and three are used.
- Bloated database. Revisions, transients, trash and old analytics tables.
- Unoptimised images. A 4 MB hero makes the site feel slow even when the server is fine.
- Automated attacks. Password guessing and mass requests to the admin area.
- Heavy theme. Page builders that load half a megabyte of code to show a headline.
How to diagnose it (without guessing)
- Measure the server response time on a simple page.
- Measure the weight and number of files on the homepage.
- Check access logs: repeated attempts at
wp-loginorxmlrpc. - Check disk space and database health.
- Review which plugins are active and which have never been updated.
- Check certificate, backups and PHP version.
What to do depending on the result
- Overloaded server → change hosting or hosting model.
- Plugins → remove them, do not just deactivate.
- Database → clean and limit revisions.
- Images → convert and serve proper sizes.
- Attacks → firewall, access limits and, if needed, take the admin panel off the internet.
- All at once → maybe the question is not how to fix it, but whether this site should be a WordPress at all.
When the fix is not migrating
If the site sells, manages members or has a complex editorial workflow, changing technology fixes nothing: what exists needs care. Migrating is a solution for sites that only publish and demand more maintenance than they give back.
Frequently asked questions
How do I know if the problem is hosting or the site?
By measuring. A static site on the same server that runs slow rules out hosting; a slow WordPress with few plugins and little traffic usually points at the server or the database. Without measurements, any change is a bet.
Does updating always help?
Updating closes known holes, but it does not fix a heavy site or an overloaded server. And an update without a backup can leave the site half broken.
Do I need to reinstall everything?
Almost never. First the causes are separated: machinery, plugins, content, traffic or attack. Reinstalling only makes sense when the site is compromised and cannot be cleaned reliably.
How much traffic must my site handle?
Usually far less than people think. Most cultural and small business sites peak at dozens of simultaneous visits, not thousands. Often the problem is not capacity but the weight of each page.
→ Moving a WordPress site to static · Hosting and maintenance · Contact