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

Troubleshooting · Troubleshooting

How to Fix A Slow WooCommerce Orders Page

Short answer

To fix a slow WooCommerce Orders page, first measure it with Query Monitor to find the slowest queries and the plugin behind them. Then clear any past-due Action Scheduler backlog and switch to High-Performance Order Storage on staging, with compatibility mode on. Finally, trim autoloaded options, remove heavy admin plugins, update PHP, and add a persistent object cache if the database is still the limit.

Key takeaways

  • Admin pages are never page-cached, so a slow Orders page means slow PHP and database work on every load.
  • HPOS stores orders in four dedicated tables and is on by default only for new stores from WooCommerce 8.2.
  • Action Scheduler sends tasks in batches of 20 across up to five queues, and a past-due backlog slows admin work.
  • Query Monitor 4.1.1, released 27 October 2026, shows the slowest queries grouped by plugin, theme, or function.
  • WordPress.org recommends PHP 8.3 or newer, MariaDB 10.11 or newer, or MySQL 8.4 or newer.
  • Switch to HPOS on staging first, keep compatibility mode on, and keep Subscriptions and Bookings active during migration.

Why is the WooCommerce Orders page slow?

The Orders page is slow because every visit runs database queries over all your orders, and admin pages are never page-cached, so nothing skips that work.

Before WooCommerce 8.2, orders were stored as posts in the wp_posts table with details in wp_postmeta, so lists, search and reports slowed as order counts grew, according to the High-Performance Order Storage guide from WooCommerce.

That old storage is the most common cause on older stores. The other common causes are a past-due Action Scheduler backlog, heavy plugins adding work to every admin screen, bloated autoloaded options, an old PHP version, and no persistent object cache.

The front of the shop can feel fast while the Orders page crawls. Page caching helps visitors, but it never applies to admin pages, so each admin click runs PHP and database queries in full.

How do you measure what is slowing the Orders page?

Install Query Monitor, open the Orders page, and read its slowest database queries grouped by plugin to find the cause.

Query Monitor is a free developer plugin that shows database queries, PHP errors, hooks and HTTP calls for each page load, grouped by the plugin, theme or function behind them, according to the Query Monitor plugin page on WordPress.org.

Its output is shown only to Administrators by default, and version 4.1.1 was released on 27 October 2026, according to the same Query Monitor plugin page. It supports PHP 7.4 or higher, according to Query Monitor.

Open the Orders page with Query Monitor active and sort the queries by time. Note the slowest query, how long it took, and which plugin made it before you change anything.

Also open WooCommerce > Status > Scheduled Actions and check the Pending, Past-due and Failed tabs, as explained in How Do You Read the WooCommerce Status Report?. A large past-due count points at the background queue, not the Orders page itself.

What is HPOS and why does it speed up the Orders page?

HPOS stores orders in four dedicated tables with dedicated indexes, so order lists and search run faster than on the old post-based storage.

High-Performance Order Storage, formerly Custom Order Tables, stores order data in wc_orders, wc_order_addresses, wc_order_operational_data and wc_orders_meta, according to the High-Performance Order Storage guide from WooCommerce.

HPOS is enabled by default for new installations from WooCommerce 8.2 onward, according to the same High-Performance Order Storage guide. Existing stores are not migrated automatically, and the switch is fully opt-in, so you can switch back any time.

For a plain-language overview, see What Is HPOS in WooCommerce? A Plain Explanation.

Full-text search for orders is experimental from WooCommerce 9.0, according to the High-Performance Order Storage guide. That matters if your team searches orders by product name or customer note.

How do you switch to HPOS safely?

Test the switch on staging first, turn on compatibility mode, let the backfill finish, and only then turn compatibility mode off.

  1. Back up the live store and copy it to staging.
  2. Update WooCommerce first, following How to Update WooCommerce Safely.
  3. Check that your extensions are HPOS-compatible before you switch.
  4. Go to WooCommerce > Settings > Advanced > Features and tick "Enable compatibility mode (synchronizes orders to the posts table)".
  5. Turn on High-Performance Order Storage, then watch the backfill under WooCommerce > Status > Scheduled Actions.
  6. Keep compatibility mode on for a while so you can revert instantly if something breaks.

Background actions backfill 25 orders at a time, using the actions wc_schedule_pending_batch_process and wc_run_batch_process, according to the High-Performance Order Storage guide from WooCommerce. The CLI alternative is wp wc cot sync.

Keep extensions that use custom post types, such as Subscriptions and Bookings, active during migration, according to the same High-Performance Order Storage guide. Turning them off mid-migration can leave order data out of sync.

If an extension outside the WooCommerce Marketplace is incompatible, the switch is disabled and a “View and manage” link lists it, according to the High-Performance Order Storage guide. All extensions on WooCommerce.com are HPOS-compatible.

How do you clear a past-due Action Scheduler backlog?

Open WooCommerce > Status > Scheduled Actions, cancel or run the stuck past-due actions, and fix the task that keeps failing.

Action Scheduler is WooCommerce's background job queue. It sends tasks in batches of 20 and can run up to five queues at once, and it runs through WP-Cron, which depends on site traffic, according to the Scheduled Actions guide from WooCommerce.

A large past-due backlog slows admin work, according to the same Scheduled Actions guide. Check the Pending, Past-due and Failed tabs to see which tasks are stuck.

Our step-by-step fix is in How to Fix Past-Due Actions in the WooCommerce Action Scheduler.

Do not just delete failed actions and move on. Find why the task failed, fix that cause, and watch the queue for a day to confirm new tasks run on time.

How do heavy plugins and autoloaded options slow the Orders page?

Plugins that add queries or scripts to every admin screen slow the Orders page, and bloated autoloaded options add database work to each load.

Use the Health Check plugin's troubleshooting mode to find the culprit. It disables plugins for your user only, so visitors and other staff see no change while you test.

Turn plugins back on one at a time and reload the Orders page after each one. When the page slows down again, you have found the plugin that adds the extra work.

Next, trim autoloaded options in wp_options and remove old data such as expired transients, old logs and abandoned draft orders. Autoloaded data loads on every admin request, so a bloated set taxes every Orders page visit.

Replace or remove plugins that query on every admin screen when a lighter option does the same job. Keep only the plugins the store needs, and keep them updated.

Does the PHP version affect the Orders page speed?

Yes, an old PHP version makes every admin query slower, so updating PHP is one of the cheapest fixes for a slow Orders page.

WordPress.org recommends PHP 8.3 or greater, MariaDB 10.11 or newer, or MySQL 8.4 or newer, and HTTPS, according to the WordPress Requirements page.

WordPress still runs on PHP 7.4 or newer and MySQL 5.5.5 or newer, but those versions are end of life and may expose the site to security problems, according to the same WordPress Requirements page.

Update PHP on staging first and check that your theme and plugins still work. If the host panel offers a PHP version switch, change it there and reload the Orders page to confirm the admin still loads.

When should you add a persistent object cache?

Add Redis or Memcached when the database repeats the same queries on every admin load and faster storage alone does not fix it.

A persistent object cache keeps repeated query results in memory, so WordPress asks the database less often. It helps most on stores where the same order data is read again and again.

Ask your host whether Redis or Memcached is available on your plan and how to turn it on. Some hosts add it with one toggle, while others need a plugin and a server setting.

Check what your plan should provide in What Hosting Resources Does WooCommerce Need?.

How do you know the fix worked?

Reopen the Orders page with Query Monitor active and check that the slowest queries are shorter and fewer than before the fix.

FixWhat to checkSign it worked
Query MonitorSlowest queries by timeThe top queries take less time than before
HPOS switchOrders page list and searchLists and search load without long waits
Action Scheduler backlogPast-due tab countPast-due count stays near zero for a day
PHP updateSite Health infoPHP shows 8.3 or newer
Object cacheRepeated query countFewer repeated database queries per load

Compare the same page before and after each change, not different pages. Change one thing at a time so you know which fix helped.

If the database itself is still the limit after these fixes, ask the host. Slow disks, a busy shared database server, or a plan that is too small for the order volume are host problems, not plugin problems.

What mistakes should you avoid?

Most slowdowns get worse when fixes are applied on the live store without a backup or a staging test.

  • Switching to HPOS on the live store without staging or a backup.
  • Turning off compatibility mode before the 25-at-a-time backfill has finished.
  • Deactivating Subscriptions or Bookings during the HPOS migration.
  • Clearing failed Action Scheduler tasks without fixing the task that keeps failing.
  • Updating PHP on the live store without testing the theme and plugins on staging first.
  • Blaming the cache plugin, since admin pages are never page-cached.

Frequently asked questions

Can I switch back from HPOS if something breaks?

Yes. HPOS is fully opt-in, and you can switch back any time. Keep compatibility mode on while you test, so orders keep syncing to the posts table and the revert is instant. Turn it off only after the Orders page, search, and your extensions have worked well for a while.

Will switching to HPOS delete my old orders?

No. The switch backfills old orders into the new tables in batches of 25, and nothing is deleted from the posts table while compatibility mode is on. Keep Subscriptions, Bookings, and other extensions that use custom post types active during the migration so their data moves across too.

Why is only the Orders page slow while the shop is fast?

The front of the shop can use page caching, but admin pages are never page-cached, so every Orders page visit runs PHP and database queries in full. A slow Orders page usually means slow order queries, a past-due Action Scheduler backlog, or heavy plugins adding work to admin screens.

Do I need a bigger hosting plan to fix a slow Orders page?

Not always. Measure first with Query Monitor, clear the Action Scheduler backlog, switch to HPOS, and update PHP before you pay for a bigger plan. Ask the host about a bigger plan only when the database or server itself is still the limit after those fixes.

Is Query Monitor safe to leave active on a live store?

Query Monitor is a free developer plugin, and its output is shown only to Administrators by default, so visitors never see it. It is best used while you measure a problem, then deactivated when you are done, so it adds no extra work to normal admin use.

How long does the HPOS migration take?

It depends on how many orders the store has, because background actions backfill 25 orders at a time. Watch progress under WooCommerce, Status, Scheduled Actions, and wait until the queue is clear before you turn compatibility mode off or judge the result.

Sources

  1. High-Performance Order Storage WooCommerce
  2. Scheduled Actions WooCommerce
  3. Query Monitor WordPress.org
  4. Query Monitor Query Monitor
  5. 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