CDN for Craft CMS

Cache Craft CMS templates, transforms and public pages with Aptranet Cloud CDN while the control panel stays on the origin.

210+Points of presence worldwide
200+ TbpsNetwork capacity
30 msAverage latency worldwide
85%Average cache hit ratio

CDN for Craft CMS

Craft renders. The edge repeats the result.

Craft sites often generate image transforms and template output on the origin. Global traffic turns those into repeated PHP and volume work.

Cache public template output, web/assets and eligible transforms at Cloud CDN. Bypass the control panel and live preview. Purge on entry save.

Why teams use Aptranet

What CDN for Craft CMS 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.

Public templates at the edge

Anonymous pages are served from 210+ PoPs instead of PHP on every view.

Transforms without origin resize storms

Cache Craft transforms and optionally replace some of them with edge image optimization.

Control panel stays local to origin

cp, live preview and logged-in requests are not cached.

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.

  1. 1
    Pull the Craft web root

    Connect the public origin including asset volumes that are web-accessible.

  2. 2
    Cache anonymous pages

    Honour cache headers or set TTLs. Bypass cp and preview.

  3. 3
    Purge on entry save

    Invalidate entry URLs and related listing pages from a Craft webhook or module.

  4. 4
    Map the site hostname

    Attach TLS and cut over DNS after a successful test hostname.

Outcomes

What changes once the hostname is on Aptranet.

  • Public Craft pages are cached globally
  • Control panel and preview remain dynamic
  • Asset volumes are delivered from the edge
  • Entry saves can purge the reading path

Frequently Asked Questions

No. Origin HTML cache and Cloud CDN stack. The CDN keeps the cached result close to readers.

Yes. Cache them at the edge. You can also generate some sizes with Cloud CDN image optimization.

Map each public hostname separately so cache keys and certificates stay per site.

They must not be. Bypass preview and tokenised draft URLs.

Put CDN for Craft CMS on the Aptranet edge.

Get started in the Management Console, or talk through origin, DNS and cutover with Aptranet.