If your WooCommerce store feels slower since the 10.8 update, you are not imagining it. The High-Performance Order Storage system, known as HPOS, changes how WooCommerce stores and reads every single order. Set it up right and checkout flies. Get the setup wrong and order admin crawls. This guide breaks down WooCommerce HPOS performance in plain terms: what HPOS actually does, why it can feel slow at first, and what it really takes to keep checkout fast as your order count grows.
What HPOS actually is
Before HPOS, every order in your store was stored as a WordPress post. The order itself lived in the wp_posts table, and all of its details, the billing address, line items, totals, shipping method, and dozens of other values, were scattered across wp_postmeta as individual rows.
That wp_postmeta table is shared with everything else on your site. Pages, blog posts, revisions, and every plugin that stores data all pile into the same place. On a busy store it grows into millions of rows, and every order query has to dig through all of it.
HPOS moves order data into its own purpose-built tables, mainly wp_wc_orders and a small set of related tables designed specifically for order queries. As of WooCommerce 10.8, HPOS is the default for new stores and the recommended setup for existing ones. Instead of fighting a giant shared table, order lookups, status filtering, and reporting now hit lean, indexed tables built for exactly that job.
That is the upside, and it is real. So why do some stores feel slower right after the switch?
Why HPOS can feel slow right after the 10.8 update
A few things tend to happen in the first days after you flip the switch, and they can mask the real gains.
- The migration is still running. When you enable HPOS, WooCommerce copies your existing orders into the new tables in background batches. While that runs, your database is doing extra work on top of normal traffic.
- Compatibility mode doubles your writes. Many stores leave the “keep both data stores in sync” option on so older plugins keep working. That means every order is written twice, once to the new tables and once to the old ones. It is safe, but it is not free.
- Caches got cleared. An update flushes object and page caches, so the first wave of visitors after the upgrade hits a cold store until those caches warm back up.
None of these are permanent. Once the migration finishes and your caches refill, HPOS should be faster than the old setup, not slower. If it is not, the bottleneck is almost always somewhere in your database or your hosting.
The database is doing the heavy lifting now
Here is the key thing to understand about WooCommerce HPOS performance: it is database-heavy by design. The whole point of HPOS is to turn slow, sprawling meta lookups into fast, indexed SQL queries. That only pays off if your database has the room to do it well.
On a store with tens of thousands of orders, the order tables and their indexes need to live in memory to stay fast. If your MySQL or MariaDB buffer pool is too small, the database constantly reads from disk instead of memory, and every order screen and checkout write slows down. This is exactly where many cheap hosting plans fall over, because the database is squeezed onto a shared box with hundreds of other sites competing for the same memory and CPU.
Two practical moves help here:
- Keep compatibility mode off once you are confident your plugins support HPOS. Cutting the double writes lightens every order operation.
- Give the database real resources. HPOS rewards a server where MySQL has enough memory to hold the working set of order data in the buffer pool.
Object caching is no longer optional
If you run a serious store, persistent object caching with Redis is one of the highest-impact upgrades you can make under HPOS. WooCommerce repeats a lot of the same queries: cart contents, product data, session lookups, and order reads during checkout. Without a persistent object cache, every one of those hits the database again.
With Redis in place, those repeated queries are served straight from memory in a fraction of the time. The database is freed up to focus on the writes that actually need it, like new orders landing during a sale. The combination of HPOS plus a warm object cache is what keeps checkout snappy when traffic climbs.
The catch is that real object caching needs a server you control. Shared plans often disable Redis or share one cache across many sites, which defeats the purpose.
Your hosting resources are the real ceiling
You can tune HPOS, trim plugins, and add caching, but there is a hard limit you cannot code around: the resources your host actually gives you. On shared hosting, your store competes with everyone else on the machine for CPU and database time. When a neighbor gets a traffic spike, your checkout pays for it. That is the single biggest reason WooCommerce stores slow down under load, and it is the focus of our deeper guide on keeping WooCommerce fast during traffic spikes.
HPOS makes this even more important. A database-heavy storage system needs guaranteed database resources to shine. When those resources are yours alone, HPOS does what it was built to do.
Your PHP version is part of that same stack. A current release gives WooCommerce a real throughput boost on the exact days it matters, and we cover how to choose and upgrade safely in our guide to the best PHP version for WordPress and WooCommerce.
A quick HPOS performance checklist
- Confirm the order migration has fully completed before judging speed.
- Turn off compatibility mode once your plugins fully support HPOS.
- Run persistent object caching with Redis.
- Make sure your database has enough memory to hold order data in the buffer pool.
- Keep your plugin count lean, since every active plugin can add queries to each request.
- Put your store on hosting where CPU and database resources are guaranteed, not shared.
How Forge keeps WooCommerce fast under HPOS
This is where the hosting model matters most. Every Forge Web Services plan runs on a dedicated VPS, so your store never shares CPU or database resources with anyone else. HPOS gets the guaranteed database headroom it needs, and a sales spike on someone else’s store can never touch your checkout.
On top of that, every plan includes the pieces a fast, safe WooCommerce store actually needs:
- Managed caching tuned for WordPress and WooCommerce, so repeated queries stay out of the database.
- BitNinja server security and All-in-One WordPress Security plus CDN, included on every plan.
- Transactional email through ForgeMail, so order confirmations and receipts actually land.
- Free migration on every plan, so moving your store over is on us.
Plans start at $39 per month and scale with your store, with no shared hosting at any tier. If HPOS has your store working harder, the fix is usually resources that are only yours.
See everything included and find the right plan on our features page.
Frequently asked questions
Does HPOS make WooCommerce faster or slower?
Faster, once it is set up correctly. HPOS replaces slow shared meta lookups with lean, indexed order tables. If a store feels slower after the 10.8 update, the cause is usually the in-progress migration, compatibility mode doubling writes, or a database that does not have enough resources to keep order data in memory.
Should I turn off HPOS compatibility mode?
Yes, once you have confirmed every plugin you use supports HPOS. Compatibility mode writes each order to both the old and new tables so legacy plugins keep working. That safety has a cost. Turning it off after you verify support removes the double writes and speeds up every order operation.
Do I need object caching for HPOS?
You do not strictly need it, but for any store with steady traffic it is one of the biggest wins available. Redis object caching serves WooCommerce’s repeated queries from memory and frees the database to handle order writes during busy periods.
Why is my checkout still slow after enabling HPOS?
If the migration is finished and caching is in place, the remaining bottleneck is almost always hosting. Shared plans throttle CPU and database resources, which HPOS depends on. Moving to a dedicated VPS where those resources are guaranteed is what keeps checkout fast under load.
Ready to give your store the resources HPOS needs? Explore the plans on our features page and let us handle the migration for free.
