Performance
Why your WordPress admin is slow (and what actually fixes it)
Front-end caching does nothing for wp-admin. If every click takes three seconds, the cause is in the database, the admin requests, or the server — not in your page cache.
There is a specific kind of frustration in a slow WordPress dashboard. The public site might load in 1.2 seconds, the homepage scores 95, and yet every click in wp-admin waits two or three seconds. Caching plugins do not help, because the admin is deliberately excluded from the cache.
The admin is a different application from the front end: every screen runs PHP, queries the database, and often fires several AJAX requests. That is why the causes are different too.
Start with the request, not the plugin list
Open the Network tab in your browser developer tools while loading /wp-admin/. Sort by time. You are looking for three things:
- One slow document request — the admin page itself takes seconds. That is PHP or database time on the server.
- Many
admin-ajax.phprequests — something is polling. Heartbeat, a security plugin, a dashboard widget, or a page builder. - Slow static assets — usually not the real problem in admin, but a clue that the server is saturated.
If the document request is slow, the cause is above the front-end layer. Do not install a caching plugin; it will not touch it.
The usual causes, in order of frequency
1. Autoloaded options bloat
WordPress loads every row in wp_options marked autoload = yes on every request, admin included. Plugins that leave data behind can push this past several megabytes. Check the size:
SELECT SUM(LENGTH(option_value))
FROM wp_options
WHERE autoload = 'yes';
Under 800 KB is reasonable. Multi-megabyte autoload is a guaranteed slowdown, and it is usually caused by a handful of rows from plugins you no longer use.
2. admin-ajax polling
Heartbeat API fires every 15–60 seconds and is fine on its own. Combine it with a security plugin, a backup plugin, a dashboard widget and a page builder, and you have six requests per cycle competing for PHP workers. On a shared host with a low worker limit, the admin waits behind them.
You can throttle Heartbeat without disabling it, and you can usually turn off dashboard widgets you never read.
3. A security plugin scanning on every request
Some firewall plugins run file scans or remote checks inline. They make the admin slower in exchange for protection. The right answer is not to remove protection but to configure it to run on a schedule instead of per request.
4. Slow database queries
Large postmeta tables, missing indexes, and plugins that query inside loops. If the admin is slow only on the posts list or the orders screen, the query is the suspect, not the server. Enable SAVEQUERIES on a staging copy and look at the slowest entries.
5. Server-level limits
No opcache, PHP 7.4, throttled CPU, or a low max_children on PHP-FPM. The admin runs more PHP per click than the front end, so it exposes a weak server earlier. A front-end page cache can hide this for months.
What actually fixes it
- Measure first. Time the admin document request on a staging copy, then compare after each change. Without a baseline you are just rearranging plugins.
- Clean autoload. Delete rows from uninstalled plugins, reduce transients, and audit anything over 100 KB. Back up the database first.
- Reduce admin requests. Throttle Heartbeat, remove unused dashboard widgets, and check for plugins polling on every screen.
- Move scans off the request path. Scheduled scans instead of inline scans, where the plugin allows it.
- Fix the server. Current PHP with opcache, enough memory, and PHP-FPM workers sized for the traffic. This is often the only change that moves the needle on shared hosting.
- Remove plugins you do not use. Deactivated plugins still leave tables, cron events and options behind. Deleting them is part of the cleanup, not a separate task.
What does not fix it
- A front-end caching plugin. The admin is excluded by design.
- “Optimizing” the database with a one-click tool. It may drop expired transients, but it will not touch autoload rows from active plugins or slow queries.
- Switching themes. Only relevant if the theme adds admin pages or metaboxes — check that before rebuilding anything.
- Adding more plugins. Every performance plugin you add to fix a slow admin makes the admin slower.
A note on expectations
A well-configured admin on decent hosting responds in 300–600 ms per screen. If yours takes two seconds, something concrete is wrong and it is findable. The work is diagnosis, not a settings checklist.
If you would rather have it measured and fixed properly, WordPress speed optimization covers the admin and the front end as one system, with before-and-after numbers.