CDN for BigCommerce
An edge for BigCommerce storefronts you control.
Headless and custom BigCommerce storefronts still need a CDN with purge, image transformation and origin protection independent of the commerce API.
Cache the storefront application, Stencil or headless assets, and media at Cloud CDN. Keep BigCommerce checkout and admin on BigCommerce.
Why teams use Aptranet
What CDN for BigCommerce 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.
Storefront JS and CSS at the edge
Build assets are cached on 210+ PoPs with long TTLs when they are hashed.
Catalogue media close to shoppers
Product imagery is cached and optionally transformed per template.
APIs stay on BigCommerce
Cart and checkout APIs remain dynamic. The CDN accelerates the storefront layer.
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 origin behind Cloud CDN
Pull the custom storefront or Stencil host, not the BigCommerce control panel.
- 2Cache immutable assets aggressively
Hashed JS, CSS and fonts can use long TTLs. HTML uses a shorter TTL plus purge.
- 3Bypass shopper-specific routes
Do not cache cart, checkout or account HTML.
- 4Map the shop domain
Attach TLS and cut over DNS when the test hostname is correct.
Outcomes
What changes once the hostname is on Aptranet.
- Custom BigCommerce storefronts are delivered globally
- Checkout remains on BigCommerce
- Media can be transformed at the edge
- Deploys purge hashed or HTML paths as needed
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Use Cloud CDN for storefronts and hostnames you map. You can still use BigCommerce image URLs as an origin.
Yes. Treat the Next.js app as the origin. See also CDN for Next.js.
Purge product and category URLs or keep HTML TTLs short enough for the merchandising process.
Yes when many edges miss the same product image or SSR page at once during a campaign.