A slow store costs you twice: shoppers leave before they buy, and search engines rank you lower on Core Web Vitals. For small shops the fix is often a better host. For stores with thousands of products and steady traffic, the causes are usually deeper, and throwing a bigger server at them only delays the problem.
These are the twelve causes we find most often, in roughly the order we check them.
Server and Infrastructure
1. Hosting that is not built for WooCommerce
Cached marketing pages hide weak hosting. Cart, checkout and account pages cannot be page-cached, so they expose it. Look for current PHP versions, enough PHP workers for concurrent shoppers, and a managed database with room to grow.
2. No persistent object cache
Without Redis or Memcached, WordPress repeats the same database queries on every uncached request. For any store with more than a few hundred products, a persistent object cache should be a default, not an upgrade.
3. Page caching misconfigured
Either nothing is cached, or cart and checkout are cached by mistake (which breaks them). Cache product and category pages aggressively, exclude cart, checkout and account, and make sure stock updates do not purge the whole cache.
Database
4. Bloated autoloaded options
Plugins store settings in the wp_options table, and autoloaded rows load on every request. We regularly find several megabytes of autoloaded data left behind by plugins that were uninstalled years ago. Cleaning this up is one of the fastest wins available.
5. Orders still in the legacy tables
Older stores keep orders as posts with meta data, which scales poorly. Migrating to High-Performance Order Storage (HPOS) moves orders into dedicated tables and speeds up admin and reporting noticeably on stores with large order histories.
6. Expired transients and orphaned data
Expired transients, old sessions, and meta rows for deleted products slow queries over time. Schedule regular clean-up.
Catalogue and Queries
7. Slow product filtering and search
Layered navigation that filters by several attributes creates expensive meta queries. Make sure the product attributes lookup table is enabled and populated, and for large catalogues move search and filtering to a dedicated search engine such as Elasticsearch, OpenSearch or a hosted search service.
8. Variable products with hundreds of variations
Loading every variation on the product page is slow. Load variation data on demand, or restructure products so a single parent does not carry hundreds of combinations.
Plugins and Theme
9. Plugin bloat
The number of plugins matters less than what they do. One badly written plugin running a query on every page load costs more than ten well-built ones. Profile with Query Monitor or an APM tool such as New Relic to find the actual offenders.
10. Cart fragments and heavy AJAX
Many themes still refresh the mini-cart with an uncached AJAX request on every page view. Load it only when the cart has items, or replace it with a lighter approach.
11. Heavy themes and page builders
Multipurpose themes load scripts and styles for features you do not use on every page. A lean custom theme is usually the largest single front-end improvement.
Front End
12. Images, fonts and third-party scripts
Serve modern image formats at the right sizes, lazy-load below the fold, preload the main product image, and audit third-party scripts: chat widgets, review apps, tag managers and pixels often add more weight than the store itself.
Measure before you fix. Test logged-in and logged-out, and test cart and checkout, not just the homepage. A PageSpeed score on a cached homepage tells you very little about what a shopper experiences at checkout during a sale.
What a Performance Project Looks Like
We start with profiling under realistic load, rank the bottlenecks by impact, fix the database and infrastructure issues first, then work through plugins, theme and front end. Our WooCommerce performance service ends with a load test and a before-and-after report. If your store feels slow, request a free WooCommerce speed audit: we will profile your slowest pages and send a prioritised fix list.
FAQ
Why is my WooCommerce store so slow?
The most common causes on larger stores are hosting not sized for uncached traffic, no persistent object cache, bloated autoloaded options in the database, slow product filtering queries, heavy themes, and one or two badly written plugins. Profiling under realistic load identifies which of these applies to your store.
Does the number of plugins slow down WooCommerce?
Not directly. What matters is what each plugin does on each request. A single plugin running expensive queries on every page can slow a store more than many well-built plugins. Use a profiler such as Query Monitor or an APM tool to find the specific offenders.
What is HPOS in WooCommerce?
High-Performance Order Storage stores orders in dedicated database tables instead of the WordPress posts and post meta tables. It improves performance for stores with large order volumes, particularly in the admin and reporting, and is the default for new WooCommerce stores.
How fast should a WooCommerce store be?
Aim to pass Core Web Vitals on real-user data for product and category pages, and keep uncached cart and checkout responses fast under peak load. Test logged-in and logged-out, and during realistic traffic, not only on a quiet homepage.