Every extra second of loading time costs you buyers. Studies have shown it for years, and I see it anew with every shop audit: a slow WooCommerce shop loses revenue and Google rankings. The good news: WooCommerce performance optimisation is achievable, even without your own developer. In this post I go through the levers I use to make shops noticeably faster.
Measure first, then optimise
Before I change anything, I measure the current state – with PageSpeed Insights and the Core Web Vitals (LCP, INP, CLS). That way I know afterwards whether a measure has actually achieved anything. Important: always test a real product and category page, not just the home page – it is usually the fastest.
1. Caching: the biggest lever
WooCommerce is dynamic, yet most of it can still be cached. A good caching plugin (e.g. WP Rocket or, as used here, Perfmatters combined with server-side caching) serves ready-made HTML pages instead of recalculating them on every request. Important: cart, checkout and “My Account” must be excluded from the cache – otherwise customers see other people’s carts.
2. Images: the most common bottleneck
Product images are the heaviest weight in almost every shop. My standard approach:
- Compress and convert to a modern format (WebP/AVIF).
- Lazy loading for images below the visible area.
- Scale them correctly – no 3000 px image for a 400 px display.
Which image tool is worth it for this I have compared directly: ShortPixel vs. Optimole.
3. Clear out plugins
Every plugin loads CSS and JavaScript – often on all pages, even though it is only needed on one. I deactivate unnecessary scripts selectively per page and remove whatever no one uses anymore. How I go about this systematically I describe in WordPress Plugin Optimisation.
4. Keep the database lean
Over time, WooCommerce accumulates data clutter: expired sessions, orphaned transients, old order metadata. Regular database optimisation keeps queries fast – a real difference, especially with many products and orders.
5. Keep an eye on theme & page builder
An overloaded theme undoes any caching optimisation. If you work with Elementor, it is worth a look at my post Elementor Performance Optimisation – many points there also apply directly to your shop.
6. Hosting: the foundation no one sees
The best caching is of little use on an overloaded budget server. For serious shops I recommend hosting with up-to-date PHP (8.3+), enough memory and ideally object caching (Redis). This is often the cheapest performance improvement of all.
More than just speed: the holistic view
Performance is one building block. Once the shop is fast, you want it to be found too – that is what I wrote the WooCommerce SEO guide for. And tips on the fundamental shop structure you will find in Optimising your WooCommerce shop.
FAQ – WooCommerce Performance
How fast should my WooCommerce shop load?
The goal is an LCP under 2.5 seconds on product pages. Anything over 4 seconds measurably costs conversions.
Is a caching plugin alone enough?
It is the biggest single lever, but not everything. Images, database and hosting have to keep up – otherwise the speed stays piecemeal.
Does more RAM make my shop faster?
Indirectly yes: more memory prevents bottlenecks with many simultaneous visitors and large databases. The loading time of individual pages is improved above all by caching.
Should I measure your shop sometime?
If you don’t want to guess where the problem lies, I offer targeted performance checks and WordPress training sessions – so that you can then handle the optimisation yourself.