The length of their patience with a supplier portal
5–15ms cached
what xSpeed serves instead of PHP
01
The story
A wholesale catalogue is the case generic cache plugins quietly give up on. Priya’s company lists eleven thousand parts, and the price on any one of them depends on which account is logged in — so the page that matters most is the page you must never serve from a shared snapshot.
Giving up on caching entirely was the status quo, and it showed: every category browse and every search ran the full stack, and buyers who use the site all day felt every second of it.
The split that works is not page-level, it is layer-level. Public catalogue pages and spec sheets cache as static HTML; the priced, logged-in views are excluded but sit on an object cache, so the queries behind them come from memory. Nobody ever sees another account’s price, and nobody waits.
02
When speed decides the outcome
Three beats. Everything xSpeed Cache does on this page is aimed at the gap between the second and the third.
1
The lookup
They know the part number. They just need your site to find it quickly.
2
The price
Trade pricing is per-account, so the interesting page can never be cached whole.
3
The order
Slow procurement sites get replaced by whichever supplier is less annoying.
03
What a site like this actually needs
Not a redesign — three properties the site has to have before anything else matters.
01
Per-account pricing that is never shared
This is the correctness requirement that outranks everything. Logged-in, priced views must never be cached across accounts.
02
A catalogue that browses quickly
Eleven thousand SKUs means heavy taxonomy and meta queries on every category page.
03
Speed for people who live in it
Trade buyers use the site daily. Small delays compound into a reason to call a competitor.
04
The xSpeed features doing the work
Each one is a real setting with a real guide — nothing here is a marketing abstraction.
Connect your site via xSpeed MCP or xSpeed Hub, then paste this into Claude or ChatGPT. It is written for this business, not a generic template.
COPY & PASTE
Using xSpeed, optimise my B2B WooCommerce catalogue. It has 11,000 products and customer-specific pricing for logged-in trade accounts. Set up cookie-based exclusions so no logged-in or priced page is ever cached, cache the public catalogue and spec pages aggressively, and connect Redis object caching to speed up the category and search queries. Verify that a logged-in account never receives a cached page, then benchmark before and after.
What happens: Your AI configures the exclusions, confirms no priced page is cacheable, connects the object cache, and reports the improvement on category browsing.
06
Questions from B2B & wholesale catalogues
Logged-in requests bypass the page cache, and any cookie your pricing plugin sets can be added to the exclusion list so those responses are never stored. You can verify it directly: the cache status of a logged-in priced page should report as excluded, and your AI can check that for you.
The object cache. Those pages are slow because of repeated database queries for taxonomy, product meta, and pricing rules; serving those from memory cuts the page generation time substantially even though the HTML itself is built fresh every time.