Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Guide

How to Speed Up the WordPress Admin Dashboard

Short answer

To speed up the WordPress admin, first use Query Monitor to find the slowest component on a slow admin page. Then slow the Heartbeat API with the Heartbeat Control plugin, clean up autoloaded options left by old plugins, and deactivate plugins the admin does not need. If pages stay slow with plugins off, the host or PHP version is the likely cause.

Key takeaways

  • The Heartbeat API sends requests every 15 seconds on post edit pages and every 60 seconds on the dashboard.
  • Query Monitor shows which plugin, theme or function is behind each slow database query.
  • The Heartbeat Control plugin lets you raise the Heartbeat interval per location instead of disabling it.
  • Old plugins often leave large autoloaded options behind that load on every admin page.
  • WordPress.org recommends PHP 8.3 or newer as of November 2026, and old PHP slows every admin page.

Why is the WordPress admin slow?

The admin is slow when every dashboard page runs too many database queries, background requests and plugin scripts.

The front end can hide behind a page cache, but logged-in admin pages cannot be cached the same way. Every admin click runs PHP and queries the database, so anything wasteful shows up at once.

CauseSymptomWhere to look
Heartbeat APIDashboard feels slow while editingNetwork tab shows admin-ajax.php
Too many pluginsEvery admin page is slowPlugins screen
Autoloaded optionsSlow on every page loadQuery Monitor
Slow host or old PHPFront end is slow tooSite Health → Info

What do you need before you start?

You need an admin login, a backup, and a note of how slow the dashboard feels right now.

  • An administrator login, since most of these checks need admin screens.
  • A full backup, so you can undo a plugin change that breaks the dashboard.
  • A note of the slowest screens, such as Posts, the Dashboard, or WooCommerce Orders.
  • A low-traffic hour or a staging copy, so your checks do not disturb editors.

Time the slowest screen three times before you change anything. That gives you a baseline to compare against later.

How do you find what is slowing the admin?

Install Query Monitor, open a slow admin page, and read its toolbar panels.

Query Monitor is the developer tools panel for WordPress. Its WordPress.org page says it shows database queries, PHP errors, hooks and actions, enqueued scripts and HTTP API calls, and groups queries by the plugin, theme or function behind them.

Open the slowest admin page, click the Query Monitor menu in the admin toolbar, and read the overview time and the queries grouped by component. The slowest component is your first suspect, so start there instead of guessing.

Query Monitor's output is shown to administrators by default, according to its WordPress.org page, and it needs PHP 7.4 or higher.

If the dashboard itself is the slow screen, our guide to fixing a slow admin dashboard walks through the same checks for that screen.

How do you slow down the Heartbeat API?

Install the Heartbeat Control plugin and raise the interval for the dashboard and post editor.

The Heartbeat API sends AJAX requests to admin-ajax.php while you are logged in, every 15 seconds on post edit pages and every 60 seconds on the dashboard, according to the Heartbeat Control plugin page on WordPress.org. It powers autosave and post locking, as the WordPress vendor Delicious Brains explains in its Heartbeat API guide.

The API arrived in WordPress 3.6, according to the wp_heartbeat_settings reference on Developer.WordPress.org. Each tick loads WordPress core, so a dashboard left open in several tabs multiplies the load.

  1. Go to Dashboard → Plugins → Add New.
  2. Search for “Heartbeat Control” and install the free plugin by WP Rocket, then activate it.
  3. Go to Settings → Heartbeat Control.
  4. Set the Dashboard, Frontend and Post Editor rows to Modify, then raise the interval. A host knowledge base example sets 300 seconds for all three, but 60 seconds is a safer first step for the editor.
  5. Save the settings and reload the dashboard.

Do not disable Heartbeat in the post editor entirely. Slowing it down keeps autosave and post locking working while cutting most of the requests.

How do you clean up autoloaded options?

Find options that load on every admin page and remove the ones left behind by old plugins.

WordPress loads autoloaded options on every page, including admin pages. Old plugins often leave large options behind after deactivation, and those options load on every dashboard visit even though nothing uses them.

Use Query Monitor or a cleanup plugin to list the largest autoloaded options, then remove the ones tied to plugins you no longer use. Do not delete options you cannot identify, since a wrong delete can break a plugin's settings.

Our guide to reducing autoloaded options in WordPress walks through the cleanup step by step.

How do you cut the load from plugins and dashboard widgets?

Deactivate plugins the admin does not need, and hide dashboard widgets you never read.

Every active plugin loads its code on admin pages. Deactivate one plugin at a time and time the dashboard after each change, so you can see which one was costing the most time.

Hide widgets with the Screen Options tab at the top of the Dashboard screen. Widgets that call outside services are the worst, since each one waits on a remote reply before the page finishes.

On WooCommerce stores, the Orders screen has its own load. Our guide to fixing a slow WooCommerce admin orders page covers that screen in detail.

How do you speed up the post editor?

Slow the Heartbeat interval in the editor, close unused tabs, and keep the editor free of heavy blocks.

The editor is the heaviest admin screen because autosave and post locking run there. Raise the post editor interval in Heartbeat Control instead of switching Heartbeat off, so drafts still save on their own.

Close other tabs editing the same site. Each open tab sends its own Heartbeat ticks, and the plugin page warns that requests pile up when the admin stays open for long periods.

Check the editor with Query Monitor's hooks and HTTP API panels for slow remote calls. A block that fetches data from an outside service on every keystroke will show up there.

Why does the admin feel slower with many users logged in?

Each logged-in user adds their own Heartbeat ticks and uncached requests, so the load grows with every open dashboard.

On a site with several editors, five open dashboards mean five sets of Heartbeat requests every minute. The plugin page warns that requests pile up when the admin stays open for long periods, and that pile-up can strain a small hosting plan enough to slow every editor at once.

Ask editors to close tabs they are not using, and set the dashboard interval higher than the editor interval. Editors need frequent ticks while they write, but a dashboard tab sitting idle does not.

Logged-in traffic also skips the page cache, so the host's PHP workers do the work instead. If the admin slows down at the same hour each day, check whether that hour matches the editors' working hours before you blame a plugin.

When is the host the problem?

The host is the problem when the front end is slow too, or when admin pages stay slow with plugins off.

WordPress.org recommends PHP 8.3 or newer as of November 2026. An old PHP version or a crowded shared server slows every admin page, no matter how clean the plugins are.

Test it on staging: deactivate all plugins briefly and reload the dashboard. If the admin is still slow, talk to the host about the PHP version, PHP workers and database load.

Our guide on whether hosting affects WordPress speed explains what to ask the host and what the answers mean.

How do you check that it worked?

Time the same admin screens before and after, and compare Query Monitor's query counts.

Load the dashboard and the slowest screen three times each and note the times. Query Monitor's overview shows the total query time for the page, so compare that number before and after each change.

Fewer Heartbeat requests also show in the browser Network tab. Filter for admin-ajax.php and watch the gap between requests grow after you raise the interval.

Repeat the check a week later. Plugins update and editors add widgets, so a fast admin can slow down again without anyone noticing.

For the front end as well, our guide to speeding up WordPress covers page caching and the other layers that sit around the admin fixes.

What mistakes should you avoid?

The main mistakes are disabling Heartbeat entirely, deleting options you cannot identify, and changing many things at once.

  • Do not disable Heartbeat in the post editor. You lose autosave and post locking, and drafts can vanish.
  • Do not delete autoloaded options you cannot identify. A wrong delete can break a plugin's settings.
  • Do not test on the live site during busy hours. Use staging or a quiet hour instead.
  • Do not keep ten dashboard tabs open while you measure speed. Each tab adds Heartbeat traffic of its own.
  • Do not judge a plugin from one slow load. Deactivate it, reload the page, and compare the times before you decide.

Frequently asked questions

What is the WordPress Heartbeat API?

The Heartbeat API sends requests to admin-ajax.php while you are logged in, every 15 seconds on post edit pages and every 60 seconds on the dashboard. It powers autosave and post locking, so slow it down with the Heartbeat Control plugin instead of switching it off.

Is it safe to disable the Heartbeat API completely?

No. Disabling it in the post editor stops autosave and post locking, so drafts can be lost and two editors can overwrite each other. Raise the interval instead, for example to 60 seconds in the editor, and keep the feature running.

Can I find the slow plugin without guessing?

Yes, if you deactivate one plugin at a time and time the dashboard after each change. Query Monitor shows which plugin, theme or function is behind each slow database query, so use its panels to confirm a suspect before you remove anything.

Why is the admin slow when the front end is fast?

Admin pages are logged in, so they skip the page cache that speeds up the front end. Every admin click runs PHP and queries the database, which is why a slow admin usually points at plugins, Heartbeat traffic or the host rather than at caching.

When should I blame the host instead of a plugin?

The host is the likely cause when the front end is slow too, or when admin pages stay slow on staging with all plugins off. Ask the host about the PHP version, PHP workers and database load, and check that the site runs PHP 8.3 or newer.

Sources

  1. Heartbeat Control WordPress.org
  2. Query Monitor WordPress.org
  3. wp_heartbeat_settings() – Function WordPress Developer Resources
  4. Taming the Heartbeat API: Preventing admin-ajax.php Overload Delicious Brains
  5. What is a Heartbeat in WordPress? GreenGeeks
  6. Requirements WordPress.org

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test