ecommerce-caching

Cache the full HTML page for anonymous visitors and load personalized data like cart count client-side after page load. Fetch it from a fast API endpoint that sets Cache-Control: private, no-store so it is never cached at the CDN or browser.

Product pages use max-age=60, s-maxage=300 with stale-while-revalidate=600, while collection pages use max-age=120, s-maxage=600. Static assets with content-hashed filenames use max-age=31536000 with the immutable directive.

Use event-driven invalidation that reacts to price change events rather than waiting for TTL expiry. Purge both the product page and related collection pages, using Surrogate-Key tags or URL-based purging via the CDN API.

Yes, the skill covers platform-specific setups. Shopify manages CDN and page caching for you, so you optimize Liquid templates and apps; WooCommerce uses a three-layer stack of Redis object cache, WP Rocket page cache, and Cloudflare CDN.

Low hit rates usually come from tracking parameters like utm_source creating unique cache keys and Vary: Cookie headers disabling caching. Strip marketing query parameters at the CDN and unset cookies for cacheable pages in Varnish.

No, only purge the page cache when stock status transitions between in-stock and out-of-stock. A quantity change from 50 to 49 does not need a purge; store live inventory in Redis and serve it through the personalization endpoint instead.