Loadzen

WooCommerce performance optimisation

Speed up your WooCommerce store where revenue actually happens

Catalog, cart, and checkout pages carry the most plugins and scripts. We optimise those templates first so shoppers complete purchases on mobile — and so Google ranks your product pages above faster-loading competitors.

Slow WooCommerce stores see more cart abandonment and weaker SEO on product URLs where competitors already outrank you. Every slow page load is a lost sale.

For WordPress shops running WooCommerce — from small catalogs to high-SKU stores.

Why WooCommerce feels slower than the rest of your site

WooCommerce adds a substantial layer of PHP processing to every shop page. Database queries for product availability, stock counts, pricing rules, and tax rates fire on each request. Session handling for cart state and checkout forms adds further overhead. When layered on top of a WordPress install that already has fifteen active plugins, the result is server response times that routinely exceed one second before the browser receives a single byte of HTML.

Payment gateway plugins — Stripe, PayPal, Klarna, Clearpay — each inject their own JavaScript on checkout pages. Review plugins, upsell tools, currency switchers, and loyalty programmes add scripts to product and cart pages. These scripts compete for browser resources on pages where completing a purchase is the only goal. A checkout page with eight third-party scripts loading synchronously directly harms INP (Interaction to Next Paint), making form fields feel sluggish and increasing abandonment.

Cart fragment AJAX requests are another WooCommerce-specific bottleneck. By default, WooCommerce fires an AJAX call to update the mini-cart on every page load for every visitor, whether or not they have anything in their cart. On a busy store, these requests add 200–500ms to the TTFB of every page — a fixed cost that affects crawlers, first-time visitors, and returning shoppers equally.

Google evaluates Core Web Vitals on your actual product and category URLs. If your product archive pages take four seconds to show the first product image, or if your add-to-cart button responds slowly to taps, those signals factor into your organic rankings. In competitive niches where multiple stores sell the same products, performance is one of the few differentiators that is entirely within your control.

  • Product grids with unoptimised images crush mobile LCP scores
  • Checkout plugins block interaction and hurt INP on the most important page
  • Cart fragment AJAX adds 200–500ms latency on every single page load
  • Every new extension risks regressing prior speed improvements
  • Uncached category pages expose slow PHP and database queries to Google's crawler

Key performance facts

69%

average cart abandonment rate

Research consistently shows that checkout friction — including slow page loads — is among the top reasons shoppers abandon their carts before completing a purchase.

200–500ms

added by WooCommerce cart AJAX

Default WooCommerce fires cart fragment requests on every page load for every visitor, adding measurable latency before the page becomes interactive.

8+

scripts on the average checkout

Payment gateways, upsell widgets, and tracking tags load individually on most WooCommerce checkout pages, each competing for the main thread at the worst possible moment.

What we fix for WooCommerce

Shop, cart, checkout, and account flows — without breaking payments or inventory sync.

Cart fragment optimisation

We configure WooCommerce to skip the cart fragment AJAX call for visitors without active cart sessions, reducing unnecessary latency on every page load. For users who do have items in their cart, fragment loading is retained so the mini-cart stays accurate. This single change often reduces TTFB by 200–400ms across the entire site.

Checkout script management

We profile every script firing on cart and checkout pages, defer payment gateway initialisation until after the page is interactive, and consolidate marketing pixels through a tag manager to reduce individual network requests. Checkout INP — how quickly form fields respond to taps — is measured before and after.

Product variation streaming

Products with many variants carry large inline JavaScript payloads for variation data. We replace or configure the variation loader so data is fetched on demand when shoppers select options, rather than front-loading every combination at page load. This can remove 50–200kB of parsing cost on complex product pages.

Product image pipeline

We generate WebP versions of all product thumbnails and full-size images, add explicit dimensions to prevent layout shift during load, and implement responsive srcset so mobile devices receive smaller images than desktop. Product grids with lazy-loaded thumbnails paint significantly faster, directly improving mobile LCP.

Selective script enqueuing

WooCommerce and most of its extensions enqueue their JavaScript and CSS on every page, even non-shop pages. We conditionally load store assets only on shop, product, cart, and checkout templates using WordPress hooks, keeping blog posts, landing pages, and the home page free from unnecessary WooCommerce overhead.

Database optimisation

We clean WooCommerce transients that accumulate in the wp_options table, optimise post meta queries used for product attributes, and add database indexes where query analysis shows table scans on high-traffic queries. On larger catalogs, query time reductions compound into significant TTFB improvements.

Cache configuration for stores

We set up full-page caching with correct bypass rules: cache is served for logged-out, zero-cart visitors; bypassed for cart, checkout, account, and any URL with a session cookie. This gives anonymous shoppers instant page loads while ensuring personalised pages are never served stale.

Core Web Vitals targeting

We improve LCP on product grids by optimising the first visible product image; INP on add-to-cart, quantity, and filter interactions by reducing main-thread script blocking; and CLS from dynamic mini-cart and stock-availability widgets by reserving space before the content loads.

The WooCommerce performance problems generic WordPress tuning misses

Most WordPress speed guides cover caching, image compression, and plugin reduction — and those apply to WooCommerce stores too. But WooCommerce has additional performance challenges that require specific interventions. Cart fragment requests are a prime example: the default WooCommerce behaviour fires a background AJAX call on every page load to update the mini-cart count. Disabling this for users without an active cart session can shave hundreds of milliseconds from TTFB with a single code change. Generic caching guides never mention it.

Product variation data is another WooCommerce-specific issue. For products with multiple variants — sizes, colours, materials — WooCommerce loads a JavaScript object containing every valid combination upfront. On products with hundreds of variations, this payload can be 50–200kB of inline JSON that must be parsed before the browser can make the add-to-cart button interactive. Streaming this data on demand, or using a plugin that handles variations via AJAX, resolves the issue without changing the shopping experience.

Cache configuration for WooCommerce also requires careful handling. Caching pages when a user has items in their cart — or serving a cached price to a customer in a different tax zone — creates data integrity problems that damage trust more than slow loading does. WooCommerce speed optimisation means configuring cache bypass rules for cart, checkout, account, and tax-sensitive pages, while aggressively caching everything else. Getting that boundary right requires testing under realistic load, not just lab conditions.

Before & after results

Representative outcomes from optimization projects. Your results depend on stack and traffic.

Outdoor gear shop

Before

PageSpeed 35

After

PageSpeed 78

Product image pipeline and database query optimisation

Subscription box

Before

Checkout 6.2s

After

Checkout 2.8s

Payment gateway script deferral and cart fragment fix

Wholesale catalog

Before

CLS 0.28

After

CLS 0.05

Font and layout stabilisation on product archive pages

How Loadzen helps you get faster

  1. 1

    Audit

    We run a deep speed and Core Web Vitals audit on your key templates — home, collection, product, and checkout where relevant. Every issue is ranked by its impact on real user experience and revenue.

  2. 2

    Optimisation

    We implement prioritised fixes: images, scripts, caching, and theme or app bloat — focused on revenue pages first. Each change is tested in staging and measured against a baseline.

  3. 3

    Monitoring

    You get ongoing checks so regressions from new apps, themes, or campaigns are caught before they hurt SEO and sales. Alerts fire when scores drop below your target threshold.

Frequently asked questions

Straight answers about timelines, risk, and what to expect.

What makes WooCommerce speed optimisation different from WordPress?
We focus on areas specific to WooCommerce: cart fragments, product variation data, checkout scripts, payment gateway loading, category page caching, and database query patterns unique to the shop tables. Generic WordPress tuning often misses or actively conflicts with these requirements.
Can you fix a slow WooCommerce checkout?
Yes. Checkout is where we start. We profile every script loading on that page, reduce blocking resources, and validate that caching rules correctly bypass the checkout to prevent session or payment data issues. INP on checkout form interactions is measured and targeted directly.
Will optimisation break my payment gateway?
Payment flows are treated as non-negotiable. We test complete purchase journeys in staging after every change, run smoke tests on production after deployment, and keep gateway scripts fully functional — we only change when they load, not whether they load.
How do you improve WooCommerce Core Web Vitals?
We optimise LCP on product hero and grid images, reduce main-thread work for INP on filters, add-to-cart buttons, and mini-cart interactions, and fix CLS from dynamic cart badge injections and stock-availability text that loads after the page settles.
Do you work with page builders and multi-currency plugins?
We support common builders and multi-currency or geolocation setups, accounting for the additional scripts and cookie-based cache invalidation these plugins require in the audit and caching configuration.
What about stores with hundreds of SKUs?
Large catalogs amplify every performance issue — more product images, more variation data, more database queries. We scale our approach accordingly: image CDN pipelines, database indexing, and paginated collection caching are all part of the scope for high-SKU stores.

Turn your slow WooCommerce store into a fast one

Run a free speed test on your shop URL. We will flag catalog and checkout bottlenecks immediately.