Quick answer: wp-admin bypasses page caching, so its speed reflects raw PHP + database performance. The usual fixes, in order of impact: add a Redis object cache, trim autoloaded options and slow queries (database guide), profile plugins with Query Monitor, and calm down admin-ajax/heartbeat traffic.
Overview
A snappy front end with a treacle-slow dashboard is the classic sign that caching is hiding backend problems. Every admin screen runs full WordPress: all active plugins load, autoloaded options are fetched, and background endpoints (heartbeat, admin-ajax) fire repeatedly. Find what’s heavy instead of upgrading blindly.
Before you start
- Install Query Monitor — it attributes slow queries and hooks to specific plugins per screen.
- Baseline the server while using wp-admin:
htopfor CPU,free -hfor RAM pressure.
Step-by-step guide
- Object cache first: enable Redis — dashboards are exactly the repeated-query workload it eliminates.
- Autoload audit: oversized autoloaded options slow every admin request — measure and trim as shown in the MariaDB guide.
- Profile with Query Monitor: open the slowest screen, sort queries by time, note the responsible plugin — page builders, “analytics dashboards” and broken-link checkers are frequent offenders. Replace or configure them.
- Heartbeat & admin-ajax: reduce the Heartbeat API frequency (Heartbeat Control plugin) — multiple open editor tabs multiply it.
- PHP capacity: confirm OPcache is on and workers aren’t maxed (tuning); a few concurrent editors need workers of their own.
- External calls: plugins phoning home (license checks, feeds) block rendering — Query Monitor’s HTTP panel exposes them.
Common issues
- Slow only on product/post lists: huge tables + missing object cache — Redis plus reasonable per-page counts fixes it.
- Fans of “wp_options is 2 GB”: expired transients hoarded —
wp transient delete --expiredand find the plugin writing them. - Everything slow at specific hours: backup or cron jobs colliding with editors — move heavy jobs to off-peak (system cron, not WP-cron).
When to contact support
If profiling shows healthy queries but the VPS itself is starved (constant 100% CPU with modest traffic, IO wait high), open a ticket about upgrading — NVMe and Power VPS plans lift exactly these ceilings.
Frequently asked questions
Why is my site fast but wp-admin slow?
Page caches only serve anonymous visitors; every admin screen runs full PHP with all plugins and database queries, so wp-admin exposes backend performance the cache was hiding.
Which plugin types most often slow down wp-admin?
Page builders, in-dashboard analytics, broken-link checkers and anything scanning content in the background — Query Monitor shows exactly which one dominates each screen.
Does the Heartbeat API really matter?
With several editor tabs open it can fire requests every 15 seconds each, tying up PHP workers; throttling it to 60+ seconds is a cheap, safe win on busy multi-author sites.
Related articles
- How to configure Redis object cache
- How to optimize MariaDB for WordPress
- How to optimize PHP for WordPress
- How to improve WordPress speed on a VPS
Ready to get started? Order a WordPress VPS at Cloud2Y →
