E-commerce

A practical WooCommerce performance checklist.

Most slow WooCommerce stores share the same handful of causes.

7 min read

Store speed isn't a cosmetic issue. Slow product pages and a sluggish checkout cost you sales directly — shoppers abandon carts when pages lag — and they cost you visibility indirectly, since page speed is a factor in how search engines rank e-commerce sites. The good news is that most slow WooCommerce stores are slow for the same small set of reasons, which makes them straightforward to diagnose.

Where to look first

  • Image sizes and formats. Product photos are usually the single biggest weight on a page. Serve WebP or AVIF where possible, compress properly, and make sure the site isn't shipping a full-resolution image and scaling it down in the browser.
  • Plugin bloat. Every plugin adds queries, scripts and stylesheets, whether or not it's still in active use. Audit the plugin list periodically and remove anything that isn't earning its place.
  • Caching strategy. Page and object caching make the biggest difference to perceived speed, but they need to be configured carefully around cart and checkout pages — cache the wrong fragment and customers can see stale prices, stock levels or an old cart total, which is worse than a slow page.
  • Database table bloat. Years of orders, abandoned carts and session data accumulate in the database and slow down every query that touches those tables. Regular cleanup of expired sessions and old transient data keeps queries fast.
  • Theme and page-builder overhead. Heavy themes and page builders often load CSS and JS for features you don't use on every single page. A leaner theme, or trimming unused builder modules, reduces the amount of code the browser has to process before it can render anything.
  • Hosting and server resources. A shared hosting plan sized for a brochure site will struggle under real WooCommerce traffic, especially during traffic spikes or sales. Make sure PHP resources, database performance and server-level caching are matched to what the store actually receives, not what it received when it launched.

What to measure

Don't optimise against a single lab score in isolation. Check Core Web Vitals from real visitor data where you can, and test actual page load on a throttled mobile connection — that's a much closer approximation of what a real customer experiences than a fast office Wi-Fi connection hitting a synthetic testing tool. Track checkout completion rate alongside speed metrics; that's ultimately the number the optimisation needs to move.

D&K WEB includes a full performance pass as part of a Digital Product Audit, and for stores that need ongoing attention we offer it as part of Maintenance & Development — so performance doesn't quietly regress after the next plugin update.

Start a project

Want a second opinion on your store's speed?

Start a project