Front-end speed gets most of the attention, because that’s what visitors and search engines see. But for the people who run a website, the admin dashboard is where they spend their time. Editors writing posts, shop managers processing orders, marketers updating landing pages. When every click in the admin takes five seconds, those seconds add up to hours each week, and people start avoiding updates altogether.
A slow admin is also harder to fix with the usual tools. Page caching doesn’t apply to logged-in users, so every admin page is generated from scratch. Whatever plugins, queries and external requests run in the admin run every time.
Here’s how I diagnose and fix slow WordPress dashboards.
Why the admin gets slow
Common causes include:
- Plugins loading heavy code on every admin page, even when you’re not using their features.
- Dashboard widgets that run expensive queries or fetch external data.
- Admin notices from plugins checking licences, promotions or updates on every page load.
- External HTTP requests to plugin vendors, update servers and APIs, especially slow or failing ones.
- Large databases, particularly bloated options, postmeta or WooCommerce order tables.
- No persistent object cache, so the same data is fetched from the database repeatedly.
- Underpowered hosting with limited PHP workers or slow storage.
- The Heartbeat API and other background requests competing for resources.
Step 1: Measure before changing anything
Install Query Monitor and open slow admin pages. Look at:
- Page generation time.
- Database queries: total count, total time and the slowest queries, with the component responsible.
- HTTP API calls: external requests made during the page load, with their duration. A single request to a slow or unreachable server can add seconds.
- PHP errors and warnings.
- Components: which plugins or theme are responsible for the most time.
This usually points directly at the problem. On many sites I’ve worked on, one plugin or one external request accounted for most of the delay.
Step 2: Fix slow external requests
Plugins frequently contact external servers from the admin: checking licences, fetching news, loading promotions or syncing data. When those servers are slow or unreachable, the admin waits.
In Query Monitor’s HTTP API panel, look for requests that take more than a fraction of a second or fail with timeouts. Then:
- Update the plugin, as vendors often fix these issues.
- Check plugin settings for options to disable remote features, news feeds or usage tracking.
- Replace plugins that make excessive or slow requests.
- If your server can’t reach certain external services, because of firewall rules or DNS problems, fix the connectivity issue or the requests will keep timing out.
You can also check for blocked outgoing requests in your server’s firewall configuration.
Step 3: Remove dashboard widgets you don’t use
The main Dashboard screen often has widgets from WordPress and plugins: news feeds, statistics, activity summaries and promotions. Some fetch data on every load.
Use Screen Options at the top of the dashboard to hide widgets you don’t need. For a cleaner setup across all users, remove widgets in code:
Plugin widgets have their own IDs, which you can find in the page source or plugin documentation.
Step 4: Reduce plugin overhead
Every active plugin loads code on admin pages. Some load much more than necessary.
- Remove plugins you don’t need. The fastest code is code that doesn’t run.
- Replace heavy plugins with lighter alternatives where possible.
- Check settings for options that reduce admin overhead, like disabling real-time features, analytics dashboards or admin bar additions.
- Watch for plugins that load assets on every admin page, even unrelated ones.
Query Monitor shows which components contribute most to page generation time, which helps prioritise.
Step 5: Add a persistent object cache
A persistent object cache, like Redis, helps the admin enormously. Admin pages repeatedly load options, user data, post data and plugin settings. With a persistent cache, much of this comes from memory instead of the database.
On busy stores and multi-editor sites, adding Redis often makes the admin feel noticeably faster on its own.
Step 6: Clean up the database
A bloated database slows admin queries:
- Autoloaded options: large amounts of autoloaded data are loaded on every request, including every admin page. Find and fix large autoloaded options.
- Expired transients: clean them up.
- Post revisions: limit and remove excess revisions.
- Action Scheduler tables: on WooCommerce sites, clean up old completed actions.
- Orphaned data from removed plugins.
My separate guide on database optimisation covers these in detail.
Step 7: WooCommerce admin tips
WooCommerce stores often have the heaviest admins. Specific improvements:
- Enable High-Performance Order Storage, which makes order screens faster on large stores.
- Keep WooCommerce and extensions updated, as performance improvements are frequent.
- Process Analytics data in the background, and avoid running large reports during busy hours.
- Reduce columns and filters on order and product list screens if plugins add heavy custom columns.
- Limit items per page on list screens with Screen Options; showing 500 orders per page is slow.
- Review WooCommerce admin features you don’t use, such as marketing suggestions and remote notifications. WooCommerce provides settings and filters for some of these features; check the current documentation for your version.
Step 8: Tame background requests
The Heartbeat API sends regular requests while admin pages are open. With many staff and many open tabs, these requests compete with page loads. Slowing Heartbeat down on admin pages, while keeping it active enough in the editor for autosave and post locking, reduces load.
Step 9: Check the editor itself
The block editor loads a lot of JavaScript. Slow editor loading can come from:
- Plugins adding many blocks, sidebars or editor scripts.
- Very long posts with hundreds of blocks.
- Heavy meta boxes from plugins running expensive queries.
- Large numbers of reusable blocks or patterns loading at once.
Disable editor plugins you don’t use, and check whether meta boxes from plugins are necessary on every post type.
Step 10: Make sure hosting is adequate
Sometimes the admin is slow simply because the server is struggling:
- Limited PHP workers mean admin requests queue behind front-end traffic.
- Slow storage makes database queries and file operations slow.
- Outdated PHP versions are noticeably slower than current releases.
- No OPcache forces PHP to compile code on every request.
Upgrading to a current PHP version and making sure OPcache is enabled are easy wins. If the server consistently runs out of resources, a hosting upgrade may be the most cost-effective fix.
Admin performance habits
- Test the admin after installing new plugins, not just the front end.
- Review admin speed during regular maintenance.
- Keep the number of plugins with admin dashboards and notices to a minimum.
- Encourage staff to close unused admin tabs.
A quick diagnostic routine
When a client says their admin is slow, I open three or four of the slowest screens with Query Monitor active, note the page generation time, the top three components by time and any external requests over half a second. That ten-minute check usually identifies the cause. Fix the biggest item first, then measure again. Admin performance work rewards patience and one change at a time.
Ask your team
The people who use the admin every day often know exactly which screens are slow and when. A short conversation with editors and shop managers can point you straight to the problem areas worth measuring first.
Plan regular admin reviews
Add a short admin performance check to your quarterly maintenance. Plugins accumulate, data grows and new features appear, and a quick review keeps small slowdowns from turning into daily frustration for your team.
Frequently asked questions
Why is my WordPress admin slow but the front end fast?
Page caching speeds up the front end for visitors, but admin pages are always generated dynamically. Plugins, database queries and external requests affect the admin directly.
Will a caching plugin speed up the admin?
Page caching doesn’t apply to the admin. A persistent object cache like Redis does help.
How do I find which plugin slows down the admin?
Use Query Monitor to see time spent by component, slow queries and external requests. You can also deactivate plugins one at a time on staging and compare.
Does PHP version affect admin speed?
Yes. Current PHP versions are significantly faster than old ones, and OPcache makes a big difference.
Final thoughts
A fast admin makes everyone who works on the site more productive and more willing to keep content fresh. Measure with Query Monitor, fix slow external requests, remove unused widgets and plugins, add a persistent object cache, clean up the database, apply WooCommerce-specific improvements, tame background requests and make sure hosting and PHP are up to date. Most slow dashboards can be transformed with a few focused changes.
