WP AlphaSee pricing
STAGING
Home / Knowledge base / WooCommerce speed problems

Slow WordPress admin

A slow WordPress admin is almost always caused by one or two plugins doing far too much work on every page load, or by the database being asked the same questions over and over. Install Query Monitor to see which plugin

The short answer

A slow WordPress admin is almost always caused by one or two plugins doing far too much work on every page load, or by the database being asked the same questions over and over. Install Query Monitor to see which plugin is slow, trim or replace it, and make sure object caching is turned on so repeated database lookups are served from memory. On WP Alpha, Redis object caching is already included and is the biggest single lever for admin speed.

What it means

The public side of your site is usually served from a page cache: a saved copy of each page handed out without running WordPress at all. The admin side has no such shortcut. Every time you open the dashboard, the post list or the WooCommerce orders screen, WordPress starts from scratch, loads every active plugin, runs their code and asks the database hundreds of questions.

That is why a site can feel fast to visitors and painfully slow to you. Any plugin that is wasteful, any database table that has grown huge, or any setting that makes WordPress load more than it needs will show up first in the admin. Slowness here is a warning sign for the whole site, because the same work happens whenever a visitor hits a page the cache does not cover, such as a search or a checkout.

The fix is rarely a bigger server. It is finding the few things that are doing the most work and either removing them or giving WordPress a faster way to get the answers it needs.

Common causes

  • One or two heavy plugins. Page builders, backup plugins that run inside WordPress, analytics and “related posts” plugins, and anything that phones home on every admin load are the usual suspects. Often a single plugin accounts for most of the delay.
  • Bloated autoloaded options. WordPress keeps settings in a table called wp_options and loads everything marked “autoload” on every request. Plugins that were removed long ago often leave hundreds of kilobytes behind, and some stuff whole log files in there.
  • No object cache. Without one, WordPress asks the database the same questions on every page. Redis object caching, a store in memory for the database lookups WordPress repeats on every page, removes most of that work.
  • The Heartbeat API. The admin sends a background request to the server every 15 to 60 seconds to check for autosaves and locked posts. On a busy site with several editors this adds constant load.
  • Old PHP or an oversized database. PHP 8.3 or 8.4 is noticeably faster than older versions. Tables full of expired transients, post revisions and spam comments slow every query.

How to fix it

  1. Measure first. Go to Plugins > Add New Plugin and install Query Monitor. Open a slow admin page and look at the Query Monitor bar: it shows total queries, time taken, and a breakdown by plugin under Queries > Queries by Component. The plugin at the top of that list is your main target. This works on any host.
  2. Deal with the heavy plugin. Check whether it has a setting to do less (disable dashboard widgets, turn off admin tracking, lower a scan frequency). If not, find a lighter alternative or remove it. Test on a staging copy first.
  3. Clean autoloaded options. In Query Monitor, the Overview panel reports the autoloaded size. Anything over about a megabyte needs attention. A plugin such as WP-Optimize or a WP-CLI command can list the largest autoloaded options so you can delete leftovers from uninstalled plugins. Back up before deleting.
  4. Turn on object caching. Confirm your host provides Redis, then install the Redis Object Cache plugin and enable it. Query Monitor will show the drop in database queries immediately. If your host does not offer Redis, ask whether an object cache is available.
  5. Slow the Heartbeat. Many performance plugins include a Heartbeat control. Set it to run every 60 seconds or longer in the dashboard and post editor, or disable it on pages where you do not need it.
  6. Update PHP. In the management console (Plesk with WP Toolkit), open Websites & Domains, choose the site, and set the PHP version to 8.3 or 8.4. Check the site afterwards; an old plugin that breaks on a new PHP version should be replaced.
  7. Tidy the database. Limit post revisions by adding define('WP_POST_REVISIONS', 10); to wp-config.php, delete spam comments, and clear expired transients. WooCommerce stores can run WooCommerce > Status > Tools > Clear transients.
  8. Re-measure. Open the same admin page with Query Monitor and compare. Repeat on the next plugin down the list until the admin feels responsive.

On WP Alpha

Redis object caching is included on every WP Alpha plan and is the biggest single speed-up for the admin side of a site, because the database lookups WordPress repeats on every page are served from memory instead. Page caching is included as well for the public side.

PHP 7.0 to 8.5 is available, with 8.3 or 8.4 recommended, and you can change the version yourself in the management console (Plesk with WP Toolkit). Staging sites are one click in WP Toolkit, so you can test removing a plugin or changing PHP without risk to the live site. WP-CLI and phpMyAdmin are available if you want to inspect autoloaded options directly, and backups run every two hours and are kept 30 days, so a database clean-up can be undone if needed.

If you would like a second pair of eyes, support is available 24/7 by live chat, with tickets and an urgent escalation form.

In this category