+1 (571) 622-8755
Code Craft — web development and digital marketing
WooCommerce

Speed Up WooCommerce: From 6 Seconds to Under 1

Code Craft EngineeringWooCommerce Team·June 30, 2026·10 min read

The exact process we've used to rescue dozens of slow WooCommerce stores — what actually causes the slowdown, what to fix first, and the numbers to aim for.

A six-second WooCommerce store isn't a hosting problem or a WordPress problem — it's an accumulation problem. Plugins pile up, the theme does too much, the database bloats, and nobody notices until conversion craters. Here's the de-accumulation process we run, in the order that pays off fastest.

First, measure honestly

Test product and category pages (not just the homepage) on throttled mobile via PageSpeed Insights and WebPageTest. Note LCP, INP, TTFB and total requests. Typical rescue-project baseline: 5–8s LCP, 100+ requests, 2s+ TTFB. Target: LCP under 1.5s, TTFB under 400ms, requests under 50.

Step 1: Full-page caching (biggest single win)

A cached page skips WordPress, PHP and MySQL entirely and serves static HTML in milliseconds. The catch on WooCommerce: cart, checkout and account pages must never be cached, and mini-cart fragments need care. A Woo-aware cache (this is exactly why we built our Speed Optimizer plugin) handles the exclusions automatically. Typical result: TTFB drops 60–90%.

Step 2: The plugin audit

Every active plugin costs queries, hooks and often front-end assets. Deactivate anything unused, replace heavy multitools with focused ones, and check which plugins enqueue CSS/JS on every page (Query Monitor reveals this). Rescue projects routinely go from 60+ plugins to ~25 with zero feature loss.

Step 3: Images and assets

Serve WebP, lazy-load below the fold, dimension everything, and preload the LCP image. Minify + combine CSS/JS, defer what isn't critical, and delay third-party scripts (chat widgets, trackers) until first interaction — they're the silent INP killers.

Step 4: Database hygiene

Woo stores accumulate expired transients, orphaned meta, old sessions and revision bloat. Clean them on a schedule, convert tables to InnoDB if any are still MyISAM, and add object caching (Redis) for stores past ~5,000 products.

Step 5: Hosting reality check

After software optimisation, if TTFB is still high, the server is undersized — Woo needs PHP workers and RAM, not marketing-page shared hosting. Managed WordPress hosting or a tuned VPS pays for itself in conversion.

Faster stores sell more — every case study we've published shows it. If you'd rather hand it over, our WooCommerce optimisation service delivers this whole process with before/after numbers.

Code Craft Engineering

WooCommerce Team at Code Craft — the team behind our published work and products and the 39-plugin product suite.

Ready to grow?

Let's build it together.

Tell us about your project and get a free, no-obligation proposal within 24 hours.

Reviewed on the platforms you trust
Google reviewsTrustpilotGoodFirmsClutch
Read all reviews →