# Speed Up WooCommerce — xSpeed Cache for Online Stores > Every extra second of load time costs carts. xSpeed Cache serves product pages as static HTML in 5–15ms, keeps the cart and checkout dynamic where they must be, and takes the database weight off every query in between. Page: https://xspeedcache.com/use-cases/woocommerce/ ## The problems - **Product pages carry the whole stack** — Every uncached view boots PHP, WordPress, WooCommerce, and your theme before a shopper sees a price. On busy stores that is hundreds of milliseconds of TTFB, per page, per visitor. - **Cart and checkout break naive caching** — Generic cache plugins either cache the cart (showing shoppers each other’s orders) or give up on the whole store. Neither is acceptable. - **The database grows until it hurts** — Orders, sessions, transients, and revisions pile up. Query times creep up with them — and checkout is the most query-heavy page you have. ## How xSpeed Cache speeds up WooCommerce - **Page cache with store-safe exclusions** — Product and category pages serve as static HTML while cart, checkout, and account pages stay dynamic — cookie- and URL-based exclusions handle it automatically. Guide: https://xspeedcache.com/docs/excluding-pages-urls-and-cookies - **Redis / Memcached object cache** — WooCommerce is database-heavy even on cache misses. An object cache layer cuts repeated queries from hundreds to a handful on cart, checkout, and admin. Guide: https://xspeedcache.com/docs/object-cache-redis-memcached - **WebP / AVIF image conversion** (Pro) — Product galleries are most of a store’s page weight. Automatic next-gen conversion shrinks them dramatically with zero visual difference. Guide: https://xspeedcache.com/docs/image-conversion-webp-avif - **Predictive cache warming** (Pro) — Your bestsellers are re-cached before shoppers arrive, so the pages that earn the money never take the slow first hit. Guide: https://xspeedcache.com/docs/predictive-cache-warming - **Separate mobile cache** — Most store traffic is mobile. A dedicated mobile cache means phones get pages built for phones — not desktop HTML squeezed down. Guide: https://xspeedcache.com/docs/separate-mobile-cache - **Scheduled database cleanup** — Expired sessions, transients, and revisions are swept on a schedule, with OPTIMIZE TABLE included — so checkout queries stay quick as the store grows. Guide: https://xspeedcache.com/docs/scheduling-automatic-database-cleanup ## 6 ways people put xSpeed to work ### Survive the flash-sale email blast (Store owners) You send 40,000 emails at 9am and the first thing shoppers meet is a cold cache and a struggling server. - When: A campaign, drop, or sale is scheduled and a traffic spike is coming at a known time. - Setup: Warm the sale and top product pages with the preloader beforehand; the spike lands on static HTML instead of PHP. ### Stop losing mobile shoppers (Store owners) Most store traffic is mobile, and mobile is where heavy product galleries hurt the most. - When: Mobile conversion trails desktop, or PageSpeed flags image weight on product pages. - Setup: Separate mobile cache plus WebP/AVIF conversion and lazy-loaded galleries — phones get light pages built for phones. ### Fix a checkout that crawls (Store owners) Checkout is the most query-heavy page you have, and it is the one page full-page caching can never touch. - When: Shoppers report slow checkout, or it degrades at busy hours. - Setup: Connect the Redis/Memcached object cache and enable heartbeat control — checkout queries come from memory instead of the database. ### Push a price change everywhere, instantly (Marketers) After a bulk price update, stale cached pages showing old prices are worse than slow pages. - When: A bulk edit, sale start, or sale end changes prices across many products at once. - Setup: Publish-time auto-purge handles single edits; after bulk changes, one purge — from the dashboard, WP-CLI, or your AI — rebuilds everything fresh. ### Keep the database lean as orders pile up (Developers) Sessions, transients, and revisions grow with every order until every query drags. - When: The store has been live for a year or more, or admin pages are noticeably slowing. - Setup: Scheduled database cleanup with OPTIMIZE TABLE — set once, swept weekly, no plugin-hopping. ### Pre-season audit in one conversation (Developers) Peak season readiness usually means a consultant and a checklist. Now it means asking. - When: Black Friday, launch week, or any high-stakes period is approaching. - Setup: Connect Claude or ChatGPT via MCP and ask for a full benchmark-and-fix pass; review the changes in the activity log. ## Copy-paste AI prompts Connect via xSpeed MCP (https://xspeedcache.com/docs/mcp-server-setup) or xSpeed Hub, then paste: ### The full store tune-up ``` Using xSpeed, run a benchmark on my store, then enable page caching with cart, checkout, and account pages excluded, connect the Redis object cache if available, and warm my top 100 product and category pages. Re-run the benchmark and show me before and after. ``` ### Before a sale weekend ``` We have a sale starting Friday 9am. Using xSpeed, preload the sale landing page, our 50 best-selling products, and every category page, raise their cache priority, and confirm the cache hit rate is above 95% before then. ``` ### After a bulk price update ``` I just bulk-updated prices across the store. Using xSpeed, purge the entire page cache, re-warm the top products from the sitemap, and verify no cached page still shows an old price. ``` ## Industry stories - [Fashion & apparel stores](https://xspeedcache.com/use-cases/for/fashion-boutiques/) — Drop day is a stampede. Cache is the door that holds. - [Electronics stores](https://xspeedcache.com/use-cases/for/electronics-stores/) — Spec-sheet shoppers open nine tabs. Win the race. - [Food & grocery delivery](https://xspeedcache.com/use-cases/for/food-delivery/) — Dinner rush hits your site before it hits your kitchen. - [Handmade & craft sellers](https://xspeedcache.com/use-cases/for/handmade-sellers/) — You left Etsy for freedom. Keep the speed too. - [Car dealerships](https://xspeedcache.com/use-cases/for/car-dealerships/) — Thirty photos per car, and the stock changed this morning. - [B2B & wholesale catalogues](https://xspeedcache.com/use-cases/for/b2b-wholesalers/) — Ten thousand SKUs and a different price for every customer. - [Event venues & conferences](https://xspeedcache.com/use-cases/for/event-venues/) — Tickets go on sale at ten. Everyone arrives at 09:59. - [Travel agencies & tours](https://xspeedcache.com/use-cases/for/travel-agencies/) — Your customers are on the other side of the planet. ## FAQ ### Will xSpeed Cache cache my cart or checkout pages? No. Cart, checkout, and account pages are excluded from the page cache automatically, and cookie-based exclusions keep any personalised page dynamic. Shoppers always see their own cart — never a cached one. ### Does xSpeed Cache work with my WooCommerce theme and plugins? Yes. xSpeed Cache is tested with WooCommerce and works alongside common store stacks. Safe-minify automatically skips any asset that could break, and per-URL rules let you exclude anything unusual. ### What actually makes the biggest difference for store speed? Three things, in order: serving product and category pages as static HTML (page cache), cutting database queries on the dynamic pages (Redis or Memcached object cache), and shrinking image weight (WebP/AVIF conversion). xSpeed Cache does all three from one plugin. ### Can I prepare the store for a sale or traffic spike? Yes. The preloader warms your key URLs ahead of time, and Pro’s predictive warming keeps your most-visited products permanently hot, so a spike lands on cached pages instead of cold ones. ## More - [All use cases](https://xspeedcache.com/use-cases/index.md) - [Pricing](https://xspeedcache.com/pricing/index.md) - [Free plugin](https://wordpress.org/plugins/xspeed/)