wp-admin taking forever
Your customers get the fast lane. You're commuting through mud.
A slow wp-admin taxes every hour anyone spends running the site — every product edit, every post, every order processed through wet cement. And because page caching only accelerates the public side, the back office runs raw: whatever's actually slow about your WordPress, admin is where it stops hiding.
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
The public site and the admin live different lives. Visitors mostly receive cached copies — pages pre-baked and served without executing much. Admin can't be cached: every screen is generated fresh, executing every plugin, loading every option, touching the database dozens of times. So admin speed is your true uncached speed, and a crawling dashboard is the honest measurement of accumulated weight the cache has been concealing from everyone but you.
The weight concentrates in known places. Autoloaded options: WordPress loads a set of settings on every request, and over the years plugins (especially deleted ones) leave megabytes behind — dragged into memory for every click. Admin-ajax traffic: dashboards that poll continuously, multiplying requests. Cron pileup: scheduled tasks running on page loads, stacking behind each other. And the database itself: option tables and post tables swollen with revisions, transients, and orphaned rows that make every one of admin's many queries a little slower. None of these show on the homepage. All of them show at 9 a.m. when you try to work.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
Autoloaded option bloat
Megabytes of settings — much of it from long-deleted plugins — loaded on every single request. The most common invisible anchor.
Admin-ajax and heartbeat storms
Live dashboards, builders, and monitors polling every few seconds — a one-person DDoS from your own browser tabs.
Cron congestion
WordPress runs scheduled tasks piggybacked on traffic; heavy or stuck tasks execute while you wait for your screen.
A database wearing every year of its life
Hundreds of revisions per page, expired transients by the thousand, orphaned metadata — every admin query wading through it.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Compare public and admin honestly
Homepage in a private window vs dashboard load. A big gap confirms the uncached-weight diagnosis — the cache has been flattering the site.
- 2
Note which screens are worst
Everything slow points at global weight (autoload, cron). One plugin's screens slow points at that plugin. The pattern is the map.
- 3
Count your browser tabs of wp-admin
Several open tabs each running heartbeat and ajax polls compound the mud. Close them and retest — occasionally the 'server problem' is twelve tabs.
Stop and call when…
- Autoload cleanup is database surgery — measured, reversible, and absolutely not a run-a-plugin-and-hope job
- Object caching (Redis-class) is the right fix — server provisioning plus configuration, done properly once
- The weight is one plugin you depend on — replacement strategy beats deletion bravado
From there it’s our job: same-day look, flat quote, and the $679 flat repair covers most cases of exactly this.
Site Speed Tune-Up — buy it now, skip the hunt.
Images, scripts, and caching tuned — measurably faster inside 48 hours of starting.
Covers one site: image optimization, script cleanup, caching configuration, and a before/after PageSpeed report. Platform-level rebuilds quoted separately if the site needs more.
Questions we hear a lot.
Why is only the admin slow if the server's the problem?
Because the server's problem is being hidden from your visitors by the page cache and revealed to you by admin's cache-proof nature. Admin executes everything, fresh, every click — it's your site's true speed with the makeup off. Which also means fixing admin speed usually improves the real performance of everything uncached: checkout, search, logged-in browsing.
Will a caching plugin fix my dashboard?
No — page caches accelerate the public side by design and can't cache the personalized, always-changing admin. What helps admin: object caching (which accelerates the repeated database lookups underneath every screen), autoload cleanup, cron hygiene, and database maintenance. Different disease, different medicine — this is exactly why 'install a cache plugin' didn't work when you tried it.
What does the $679 tune-up cover for admin speed?
The full uncached-path diagnosis: autoload audit and cleanup, database maintenance (revisions, transients, orphans), cron review, heartbeat/ajax tuning, object caching configured where the hosting supports it — with admin load times measured before and after, in writing. The same measured-results discipline as our public-side speed work, aimed at the half of the site only you see.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
Give yourself the fast lane too.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.