CDN for Joomla
Public Joomla traffic should not wait on the CMS host.
Joomla template assets, media manager files and public articles are requested far more than administrator sessions, but they often share one origin.
Put Cloud CDN in front of the public site. Cache templates, media and anonymous article HTML. Bypass the administrator and logged-in paths.
Why teams use Aptranet
What CDN for Joomla 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.
Template assets at the edge
CSS, JavaScript and fonts from the template are served from 210+ PoPs instead of the Joomla server.
Media manager files delivered globally
Article imagery and downloads are cached and can be resized or converted at delivery time.
Administrator stays off cache
Logged-in and administrator routes reach Joomla so editorial workflows do not serve stale HTML.
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.
- 1Create a distribution for the Joomla origin
Pull the public site over HTTPS and confirm template and media paths cache.
- 2Bypass administrator routes
Exclude /administrator and authenticated cookies from cache.
- 3Purge on article updates
Invalidate article URLs and replaced media after editorial changes.
- 4Cut over the site hostname
Map the domain and certificate once the Aptranet hostname looks correct.
Outcomes
What changes once the hostname is on Aptranet.
- Public articles and templates are cached globally
- Administrator sessions remain on Joomla
- Media can be transformed without a second pipeline
- Purge follows editorial updates
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Yes. Origin page cache and Cloud CDN complement each other. Purge both when content changes.
Static extension assets can be cached. Dynamic extension endpoints should follow cache headers or a bypass rule.
Yes. Cloud CDN supports HTTP/3 and HTTP/2 so browsers complete asset waterfalls with fewer handshakes.
Cache each language URL separately. Purge the language prefix or specific article URLs when translations change.