Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My WooCommerce store has become slow as the catalogue grew

Short answer

A large WooCommerce store slows down for reasons you can measure: pages not cached on the server, heavy plugins, large images, a cluttered database, orders stored in the general posts tables and an old PHP version. Measure with a tool such as Query Monitor first, then fix the biggest cost, one change at a time.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The shop or category pages take many seconds to load.
  • The admin, especially the products or orders list, is painfully slow.
  • It was fine at fewer products and got worse as the shop grew.
  • Import, export or search time out.
  • Adding another plugin made it noticeably worse.

Why does this happen?

  1. Pages are built from scratch on every visit

    WooCommerce's performance guide recommends server-side caching from your host, such as Varnish, NGINX FastCGI cache or Redis, with cart and checkout left uncached. Without it, every visit runs the full code and database queries.

  2. Plugins add cost to every page

    The guide advises measuring the impact of installed plugins with tools such as Query Monitor and removing or replacing the ones that hurt performance. Filters, related-product widgets and builders often add the heaviest queries.

  3. Orders stored in the general posts tables

    High-Performance Order Storage keeps orders in dedicated tables with their own indexes, which WooCommerce says means fewer reads and writes and fewer busy tables. Switching requires a sync first, and extensions that do not support it block the switch.

  4. A cluttered database and large images

    The guide recommends regularly removing spam comments, post revisions and expired transients, and compressing images before upload. These add up on a store with a long order history.

  5. The server has run out of room

    Memory, PHP workers and database connections are finite. A growing catalogue hits those limits first, and the symptom is a timeout or a server error rather than a slow page.

What can I do about it today?

  1. Time three pages and the adminHome, a category with many products, a product and the products list in the admin. Write the times down, so any change can be compared.
  2. Ask your host what caching they provideServer-side caching is often included or available. Ask what it covers and whether the cart and checkout are excluded.
  3. List your plugins and the last time each updatedRemove only the ones you know you do not use, on a staging copy first. Do not delete anything on the live store to see what happens.
  4. Check image sizesVery large product photos uploaded straight from a camera slow every product grid. Note which ones are largest.
  5. Do not run database cleanup plugins without a backupA cleanup can delete data you still need. Take a full backup first and keep it.

When should I bring someone in?

  • The admin or checkout times out and orders are being lost.
  • The store has many products or orders and every quick fix has only helped briefly.
  • Your host says the server is fine, yet the pages are slow.

How do I handle it?

  1. Measure before changing anythingI profile pages and queries to find which plugin, query or server limit costs the most time.
  2. Work through the biggest costs firstCaching, the heaviest plugins, images, then database tuning and order storage, with a measurement after each change.
  3. Test on a copyEach change is tried on staging with real data volume, because a small test store hides the problem.
  4. Leave you a short recordYou get a note of what was slow, what changed and what to watch, so the next slowdown is quicker to read.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is there a product limit where WooCommerce stops working?

I found no official limit. Official guidance covers caching, plugins, images and database upkeep, so speed depends on how the store and server are set up.

Will High-Performance Order Storage fix it?

It can reduce load from orders, since they move to dedicated tables. WooCommerce says extensions without support block the switch, and it needs a sync step first, so it is a planned change.

Can I fix it with a caching plugin alone?

A cache helps shoppers who browse, but WooCommerce says the cart and checkout should stay uncached, and the admin is not helped by page caching.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.