CDN for WooCommerce
A faster aisle, without moving checkout.
WooCommerce storefronts are image-heavy and campaign-driven. Product galleries, category pages and theme assets are requested far more often than cart or checkout, yet they often share the same origin capacity.
Cache the catalogue, theme and media at the edge. Leave cart, checkout, account and admin dynamic. Origin Shield reduces duplicate product-image and CSS misses during sales.
Why teams use Aptranet
What CDN for WooCommerce looks like on this network.
Cloud CDN caches and accelerates eligible content on 210+ points of presence, with Origin Shield when the origin must stay out of the way.
Catalogue pages that keep up with ads
Category HTML, product imagery and theme assets are served from 210+ PoPs so paid traffic does not queue behind origin PHP.
Product imagery without extra derivatives
Convert and resize gallery images at the edge. Keep a single source file in the WordPress media library.
Checkout stays on WooCommerce
Cart, coupons, payments and account pages bypass cache. The edge accelerates what is safe to reuse, not shopper state.
How to set it up
A cutover you can validate before DNS moves.
Create the Cloud CDN configuration, prove it on an Aptranet hostname, then point production DNS when the path looks correct.
- 1Put the storefront behind Cloud CDN
Pull the WooCommerce origin over HTTPS and cache theme, plugin and uploads paths first.
- 2Exclude cart and checkout
Bypass cache for cart, checkout, my-account and admin. Validate with a test order on an Aptranet hostname.
- 3Optimise product media
Use image transformation for listing and pdp sizes instead of generating every derivative at upload time.
- 4Prepare for campaign traffic
Prefetch hero SKUs, set purge rules for price or stock changes, and keep Origin Shield in the miss path.
Outcomes
What changes once the hostname is on Aptranet.
- Product imagery and catalogue assets are cached globally
- Cart and checkout remain origin-dynamic
- Sale-day misses are consolidated through Origin Shield
- Theme and plugin releases can be purged by directory
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Not if cart, checkout and account paths bypass cache. Anonymous catalogue pages should not include shopper-specific HTML.
Yes, with a TTL that matches how fast availability must update, plus purge on stock or price changes for the affected URLs.
No. Object cache still helps PHP. Cloud CDN reduces how often those PHP workers run for public storefront traffic.
Yes. Cloud CDN delivers over TLS 1.3, with managed certificates or a custom certificate on the shop hostname.