Features
xSpeed Hub Pricing Docs Blog Scan
Get Plugin
WooCommerce

Your store, faster than the buy button

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.

How a page gets served

A visitor asks for a page

xSpeed checks the cache

HIT 5–15ms

Static HTML straight off disk. No PHP, no database.

MISS PHP · WP · DB

Built once, stored, warmed. The next visitor gets a hit.

5–15ms
cached product-page response
17×
faster than uncached WordPress
0
cart pages ever cached
01

What actually goes wrong

Three failure modes, specific to this kind of site. Everything below is aimed at them.

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.

02

How xSpeed Cache speeds up WooCommerce

Store-aware caching out of the box: fast where pages are static, correct where they are personal.

03

6 ways people put xSpeed to work

Each one shows when it applies and what to set up — or what to ask your AI for. Filter by role in the sidebar, or use the chips below.

Store owners

Survive the flash-sale email blast

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.

Store owners

Stop losing mobile shoppers

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.

Store owners

Fix a checkout that crawls

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.

Marketers

Push a price change everywhere, instantly

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.

Developers

Keep the database lean as orders pile up

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.

Developers

Pre-season audit in one conversation

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.

04

The exact prompts to use

Connect via xSpeed MCP or the Hub, then paste any of these into Claude or ChatGPT.

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.

05

Or just ask your AI

Every xSpeed Cache install speaks MCP. Connect Claude or ChatGPT once — directly or through xSpeed Hub — and everything on this page becomes something you ask for instead of something you configure.

you › Our product pages feel slow before big sale weekends. Fix it.

xspeed · run_benchmark → 58 · TTFB 640ms

xspeed · page cache on · cart/checkout excluded

xspeed · object cache → Redis connected

xspeed · start_preloader → warmed top 120 products

xspeed · run_benchmark → 97 · TTFB 11ms

Done — product pages serve from cache; cart and checkout stay live.

06

See the story for your business

Each one is a real scenario — the moment speed bites, the fix, and the exact prompt to hand your AI.

07

Frequently asked questions

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.

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.

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.

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.

08

Keep reading

Fast for your kind of site.

Install xSpeed Cache free, or connect your AI and ask for a 100.