One slow WordPress dashboard doesn't necessarily mean your public site is slow. In fact, caching can keep public pages fast while the admin area takes several seconds to respond.
I always start by checking where the problem actually is. That way I avoid applying unnecessary optimizations site-wide.
Confirm that only the WordPress dashboard is slow
First, I open the public site in a private window. Then I compare its speed with several admin screens: Posts, Media, Plugins and editing a page.
- If the whole site is slow, I check the server, PHP, the database or available resources.
- If only wp-admin is slow, I look at plugins, AJAX or REST requests, and admin tasks.
- If only one screen is problematic, I focus my diagnosis on that specific page.
This distinction often saves a lot of time.
Identify the type of slowdown
Next, I observe when the delay occurs. A page that’s slow to appear can indicate PHP processing or a slow query. However, if the screen appears quickly then freezes, JavaScript may be to blame.
When slowness occurs mainly during saving, I also check requests to admin-ajax.php and the REST API. The browser developer tools let you spot the requests that take the longest.
Analyze wp-admin with Query Monitor
To go further, I often use Query Monitor. This plugin lets you inspect database queries, PHP errors, HTTP calls, and the scripts and styles loaded.
I pay particular attention to the following:
- Slow queries : a very long query can be enough to slow down an entire screen.
- HTTP calls : a plugin may be waiting for a response from an external service.
- Scripts and styles : some plugins unnecessarily enqueue their files across the admin area.
- PHP errors : a repeated warning can reveal a conflict or outdated code.
In practice, the total number of requests isn’t always the issue. A single very slow operation can have much more impact.
Test extensions one at a time
Extensions can add analytics, license checks, editing tools, or connections to external services. As a result, they’re often among the first things to check.
- I first create a recent backup or a test copy.
- I measure the load time of the problematic screen.
- I disable a single suspicious extension.
- I reload exactly the same screen.
- Finally, I re-enable the extension to confirm the result.
This method avoids changing multiple variables at once.
Check WP-Cron and external services
WordPress also uses WP-Cron to run scheduled tasks. A misconfigured extension can therefore add too many tasks or redundantly repeat certain operations.
Additionally, backup, security, analytics, or license plugins may contact external servers. If one of these services responds slowly, wp-admin can wait for its response.
In that case, I check Cron events, HTTP calls, and server logs before modifying the database.
Methodically fixing a slow WordPress dashboard
To fix a slow WordPress dashboard, I always prefer to proceed by elimination. I identify the affected screen, measure what’s slowing it down, then change only one element at a time.
If you’d rather entrust me with diagnosing or maintaining your site, you can also view the services offered in my online store.