CDN for Magento
Take Magento static content off the application nodes.
Magento storefronts mix heavy static content with expensive dynamic layouts. Static files, media galleries and FPC output often share capacity with checkout and admin, which shows up during catalogue campaigns.
Serve pub/static, media and eligible full-page cache output from Cloud CDN. Keep admin, customer accounts and checkout on the Magento origin. Origin Shield consolidates media misses.
Why teams use Aptranet
What CDN for Magento 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.
Static content at the edge
pub/static and theme assets are cached on 210+ PoPs so Magento application nodes spend less time on CSS, JS and fonts.
Catalogue media without origin thrash
Product and category images are cached and optionally transformed at the edge instead of resizing on the Magento host.
FPC and edge cache together
Eligible anonymous pages can be cached at the CDN while Magento full-page cache still protects the origin for other routes.
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.
- 1Point static and media base URLs at Cloud CDN
Configure Magento static and media URLs to the distribution after the origin pull is verified.
- 2Decide which HTML can be cached
Anonymous category and CMS pages can often be cached. Bypass customer, checkout and admin routes.
- 3Align purge with deploys
Purge static versioned paths on deploy and purge media or HTML when catalogue content changes.
- 4Enable Origin Shield
Consolidate cache misses so Magento PHP-FPM and media storage are not hit by every edge independently.
Outcomes
What changes once the hostname is on Aptranet.
- Static and media URLs are served from the edge
- Admin and checkout remain on Magento
- Deploys invalidate versioned static content cleanly
- Origin Shield reduces duplicate media fetches
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
No. Use both. Magento FPC reduces origin work; Cloud CDN keeps that result close to shoppers and off the Magento cluster.
Keep Magento static versioning. Cache those versioned URLs at the edge and purge or let TTLs expire when the version changes.
Yes, when you control the public hostname and origin pull. Review the current Adobe Commerce networking model before cutover.
Cloud CDN sits in front. Varnish can remain an origin-side cache. Origin Shield still helps when many edges miss at once.