Troubleshooting · Troubleshooting
How to Fix a Slow Admin Dashboard in WordPress
Short answer
To fix a slow WordPress admin dashboard, install Query Monitor and open the slowest screen to find the cause before changing anything. The usual causes are a plugin running slow database queries, the Heartbeat API sending frequent admin-ajax requests, slow outbound HTTP calls, or an old PHP version. Fix the cause Query Monitor names, then recheck the page time.
Key takeaways
- wp-admin is never page-cached, so slowness hidden from visitors still shows in the dashboard.
- Query Monitor shows page time, query count, and slow HTTP calls for each screen.
- Heartbeat ticks every 15 to 120 seconds and powers autosave, post locking, and login checks.
- WordPress.org recommends PHP 8.3 or newer for hosts.
- Slowing Heartbeat down is safer than switching it off.
Why is the WordPress admin slow when the front end is fast?
The admin is slow while the front end is fast because visitors get cached pages and logged-in users do not.
A page cache stores a finished copy of each public page and serves it without running PHP. The dashboard is built fresh on every click, so it runs WordPress core, every plugin, and the theme admin code each time.
That is why a slow plugin or a slow database query hides from visitors but shows up at once in wp-admin. The admin is the one place where nothing masks a slow stack.
If the front end is slow too, start with how to fix slow WordPress hosting before you chase admin-only causes.
How do you measure what makes the admin slow?
Measure the slow screen first, because guessing at plugins wastes time and often fixes nothing.
Install the free Query Monitor plugin from Plugins → Add New. It adds a panel to the admin bar that shows page generation time, peak memory, query time, and query count for the screen you are on.
Query Monitor is a developer tools panel that reports database queries, PHP errors, hooks, HTTP API calls, and more, WordPress.org's plugin page explains.
Open the slowest screen, such as Dashboard, Posts, or WooCommerce Orders, and read the admin bar figures. Then open the Queries panel and sort by time, and open the HTTP API Calls panel to see slow outbound requests.
Also open your browser developer tools, go to the Network tab, and reload the page. A document request with a slow time to first byte points at the server, while a fast document with a slow finish points at scripts or admin-ajax calls.
Which plugin or query is slowing the dashboard?
The plugin behind the slowest query is usually the cause, and Query Monitor names it in the component column.
| What Query Monitor shows | Likely cause | Fix |
|---|---|---|
| One slow query from a plugin | That plugin scans too much data | Update, reconfigure, or replace the plugin |
| Many duplicate queries | A plugin repeats the same lookup | Update or replace the plugin |
| HTTP calls taking seconds | A plugin waits on a slow remote server | Update, replace, or block that plugin's calls |
| High time with few queries | Heavy PHP code or low server power | Check the PHP version and ask the host |
Query Monitor groups database queries by the plugin, theme, or function behind them, so you can see the slow part at once, WordPress.org's plugin page explains.
Confirm a suspect by deactivating it and reloading the slow screen. If the page time drops, you found the cause. Reactivate it only after you have a fix or a replacement.
Query Monitor's output is shown only to Administrators on single-site installs by default, so other roles will not see it, WordPress.org's plugin page explains.
How does the Heartbeat API slow the admin?
Heartbeat slows the admin by sending a background request to admin-ajax.php every few seconds while a dashboard tab stays open.
The Heartbeat API is a polling API built into WordPress, and each tick runs every 15 to 120 seconds, the Plugin Handbook explains. It was built for autosave, post locking, and log-in expiration warnings while a user writes or edits, Make WordPress Core explains.
Heartbeat sends AJAX every 15 seconds on post edit pages and every 60 seconds on the dashboard, through /wp-admin/admin-ajax.php, Heartbeat Control's WordPress.org page explains.
Each tick loads WordPress core, the theme, and every active plugin, so ten open tabs can mean many background requests a minute. Editors who leave tabs open all day add load without clicking anything.
Open developer tools, filter the Network tab for admin-ajax, and watch for two minutes. Requests with action heartbeat are Heartbeat, and any other action name belongs to a plugin.
Repeated admin-ajax calls also drive high CPU usage, which has its own checks.
How do you slow Heartbeat down safely?
Slow Heartbeat down with the heartbeat_settings filter or a plugin, and keep it running on the post editor.
Disabling Heartbeat everywhere breaks autosave and post locking, so slow it instead. The Heartbeat Control plugin lets you set the interval per screen, and it is free on WordPress.org, Heartbeat Control's WordPress.org page explains.
Add this to a code snippets plugin or a child theme to set a 60 second interval:
add_filter( 'heartbeat_settings', function( $settings ) {
$settings['interval'] = 60;
return $settings;
} );
The heartbeat_settings filter controls the starting interval, the code reference explains. Sixty seconds is a safe first choice for most dashboards.
What if a plugin keeps making slow outbound requests?
A plugin that waits on a slow remote server can stall every admin page, and the fix is to update, replace, or block its calls.
Query Monitor's HTTP API Calls panel lists every outbound request with its URL, status, and time. A call that takes over a second, or ends in a timeout, is a strong lead.
The cleanest fix is updating or replacing the plugin, because a slow license check or news feed is the vendor's code. If the plugin is needed, ask its support team about the slow call.
A plugin that phones home on every admin screen is easy to spot: the same remote address appears in the HTTP panel on every screen you open.
How do PHP version and memory affect admin speed?
Old PHP makes every admin page slower, because each click runs PHP code that newer versions run faster.
WordPress.org recommends PHP 8.3 or greater for hosts, and WordPress will still run on PHP 7.4 and up, WordPress.org's requirements page explains. WordPress 7.1 needs at least PHP 7.4 to run, the WordPress hosting handbook explains.
PHP 8.2 stops getting security fixes on 31 December 2026, and PHP 8.3 gets them until 31 December 2027, the PHP project lists. Sites still on PHP 8.1 or older get no security fixes at all.
Check your version under Tools → Site Health → Info, in the Server section, WordPress.org's Site Health guide explains. Ask your host to move you to PHP 8.3 or newer, and test on staging first.
PHP version also shapes front-end speed, as does PHP version affect WordPress speed explains.
How do you confirm the admin is faster?
The admin is faster when the same screen loads in less time with the same plugins active.
- Write down the page time and query count from Query Monitor before the fix.
- Apply one fix at a time and reload the slow screen.
- Compare the new page time with the old one on the same screen.
- Leave the screen open for a few minutes and check that admin-ajax stays quiet.
- Ask another editor to load the same screen and confirm it feels faster.
A page cache cannot help here, because the admin is never cached. An object cache can help the admin by storing repeated database results between requests, and Redis vs Memcached for WordPress compares the two options.
Site Health flags other server problems too. If it reports a loopback failure, see how to fix loopback request failed.
What mistakes should you avoid?
Most slow-admin fixes fail because they change the wrong layer, not because the cause is hard to find.
- Installing a page cache plugin and expecting it to speed up wp-admin.
- Disabling Heartbeat everywhere and losing autosave and post locking.
- Deactivating many plugins at once, so you never learn which one was slow.
- Upgrading PHP on the live site without testing on staging first.
- Ignoring slow outbound HTTP calls, which no cache can fix.
Frequently asked questions
Why is wp-admin slow but my site is fast for visitors?
Visitors get cached pages that skip PHP, while every admin click builds the page fresh. The admin runs core, all plugins, and theme code on each load, plus update checks and Heartbeat requests. A slow plugin or query hides behind the cache for visitors but shows up at once in the dashboard.
Is it safe to disable the Heartbeat API?
It is safer to slow it down than to switch it off. Heartbeat powers autosave, post locking, and login expiry warnings in the editor. Use the Heartbeat Control plugin or the heartbeat_settings filter to raise the interval to 60 seconds, and keep it running on post edit screens.
How many plugins are too many for a fast admin?
There is no fixed number. One heavy plugin can slow the admin more than 30 light ones. Use Query Monitor to find the plugin behind the slowest queries and HTTP calls, and judge each plugin by what it costs on your slow screens, not by the total count.
Can my host cause a slow admin dashboard?
Yes. Low PHP worker counts, slow disks, and crowded shared servers all show up in the admin first. If Query Monitor shows fast queries but slow page times, or the host cannot raise your PHP version, ask the host about workers and PHP limits, or compare hosts before moving.
Does a slow admin mean my site will rank worse?
Not directly. Search engines measure the public pages visitors see, not your dashboard. A slow admin still matters, because it often points at a slow plugin, an old PHP version, or a weak server, and those problems can reach the front end as traffic grows.
Sources
- Heartbeat API WordPress Plugin Handbook
- Autosave and Post Locking Update Make WordPress Core
- Query Monitor WordPress.org
- Server Environment Make WordPress Hosting
- Supported PHP Versions PHP.net
- Heartbeat Control WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
