11 WordPress ServicesView all
8 industry verticalsAll industries
12 UK locationsAll locations
Home/Blog/Performance
Performance15 November 2026· 6 min read

Why Is the WordPress Admin Dashboard So Slow?

Your WordPress website looks fine to visitors but the admin dashboard takes forever to load, posts hang on save, and the media library is unusable. Here's why and how to fix it.

A slow WordPress admin is different from a slow front end. Your site might load quickly for visitors while the dashboard is painfully sluggish — 15 seconds to load the posts list, the media library won't open, saving a page times out. These issues have specific causes that are separate from front-end performance.

Cause 1: Too many revisions in the database

Every time you save a post or page in WordPress, it creates a revision. By default, WordPress keeps unlimited revisions. Sites that have been active for a year or more can accumulate hundreds of thousands of revision records, bloating the database and slowing admin queries. Fix this in two steps: first, delete existing revisions using the WP-Optimize plugin (free). Second, limit future revisions by adding this to wp-config.php:

WordPress speed optimisation — PageSpeed 90+ guaranteed →
define('WP_POST_REVISIONS', 5);

This keeps only the last 5 revisions per post. For most sites, this is enough history without the database bloat.

Cause 2: A plugin making external HTTP requests on every admin page load

Some plugins call external APIs on every admin page load — checking for updates, loading fonts, fetching licence data. If that external server is slow or unresponsive, every admin page load waits for the timeout. Use the Query Monitor plugin (free) to see which external HTTP requests are being made and how long each takes. Any request taking over 2 seconds is your bottleneck. Update or replace the offending plugin.

Cause 3: Heartbeat API set too aggressively

The WordPress Heartbeat API sends regular AJAX requests from your browser to the server to keep your session alive and enable autosave. By default it fires every 15 seconds in the post editor — which is excessive and can slow the editor on shared hosting. Use the Heartbeat Control plugin (free) to increase the interval to 60 seconds in the post editor and reduce or disable it on other admin pages.

Cause 4: Too many installed plugins, particularly premium ones

Every active plugin adds PHP code that runs on every admin page. Premium plugins from large vendors (Elementor, WooCommerce extensions, SEO suites) often load significantly more code than lightweight alternatives. If you have 30+ active plugins, the cumulative overhead is likely slowing your admin. Audit your installed plugins: deactivate anything you don't actively use, and check whether two plugins are doing the same job.

Cause 5: Underpowered shared hosting

If your site is on cheap shared hosting (under £10/month), you share server resources with potentially hundreds of other sites. During peak hours, your PHP processes queue behind others and admin requests time out. This is a hosting problem, not a WordPress problem. The fix is upgrading to a managed WordPress host (Kinsta, WP Engine, Cloudways) or at minimum moving to a VPS. Check your server response time (TTFB) in GTmetrix — if it's above 800ms consistently, your hosting is the bottleneck.

Cause 6: The wp_options table has too many autoloaded options

WordPress loads a subset of the wp_options database table on every request — this is called autoloading. Plugins that store large amounts of data in wp_options with autoload=yes can bloat this load significantly. Check the total size of your autoloaded data with this SQL query in phpMyAdmin:

SELECT SUM(LENGTH(option_value)) FROM wp_options WHERE autoload = 'yes';

If the result is above 800KB, you have an autoload bloat problem. The WP-Optimize plugin shows which options are autoloaded and lets you disable autoloading for specific ones. Deactivating and deleting plugins that add large autoloaded data is the more permanent fix.

ImportantIf your admin is slow only on specific pages (like WooCommerce orders or the posts list), the issue is page-specific — likely a plugin or database query issue on that screen. Use Query Monitor to identify slow database queries on the specific page that's slow. It logs the query time for every database call and shows which plugin or file triggered it.

Frequently asked questions

Why is my WordPress admin dashboard loading slowly?+

The most common causes are too many installed plugins (even inactive ones add database overhead), bloated wp_options autoload data from deactivated plugins that did not clean up after themselves, slow hosting with no object caching, or a plugin making external HTTP requests on each admin page load.

How do I speed up the WordPress admin dashboard?+

Deactivate and delete unused plugins, check autoloaded wp_options size in phpMyAdmin using a simple SQL query, install Redis or Memcached object caching if your host supports it, and use the Query Monitor plugin to identify which plugins are adding slow database queries or external HTTP requests on admin pages.

Does a slow WordPress admin affect my website front-end speed?+

Not directly — they share the same database, so a database performance issue will slow both. But admin-only issues such as a plugin making external API calls only on admin pages only affect the backend. Front-end caching means visitors often see fast load times even when the admin is sluggish.

Why is WordPress admin slow only on specific pages like WooCommerce orders?+

Page-specific admin slowness means a plugin or feature is loading particularly heavy content on that screen. Use the Query Monitor plugin on the slow page — it shows every database query, its execution time and which plugin or file triggered it, letting you pinpoint the exact cause without guesswork.

Related service

If your admin is slow because of an underlying performance issue affecting your whole WordPress stack, our speed optimisation service addresses the root cause — not just the symptoms.

WordPress Speed Optimisation →

Next article

Troubleshooting

A WordPress Plugin Update Broke My Site: How to Recover

→
← All articles