Blog
CDN and Caching: The Complete Configuration Guide for Australian Websites
30/05/2026 • rhixowp
Australia presents a unique challenge for website performance. Our geographic isolation means that without a CDN, visitors from overseas experience 200-300ms of latency just from the physical distance data must travel. Even domestic visitors in Perth accessing a Sydney-hosted site face 50-70ms of unnecessary delay. A properly configured CDN eliminates this problem entirely.
This guide walks through the complete setup of CDN and caching for Australian-hosted websites, from choosing the right provider to advanced configuration that maximises cache hit rates and minimises origin server load.
What a CDN Actually Does
A Content Delivery Network maintains copies of your website’s static files (images, CSS, JavaScript, fonts) on servers distributed around the world. When a visitor requests your site, they receive files from the nearest server rather than your origin server in Sydney. The result is dramatically faster load times for everyone, everywhere.
Latency Comparison: With and Without CDN
| Visitor Location | Without CDN | With CDN | Improvement |
|---|---|---|---|
| Sydney | 5ms | 5ms | — |
| Melbourne | 12ms | 5ms | -58% |
| Perth | 65ms | 8ms | -88% |
| Singapore | 95ms | 8ms | -92% |
| London | 280ms | 12ms | -96% |
| New York | 210ms | 10ms | -95% |
Choosing a CDN Provider for Australia
| Provider | AU Edge Nodes | Free Tier | Best For |
|---|---|---|---|
| Cloudflare | Sydney, Melbourne, Perth, Brisbane | Yes (generous) | Most websites (best free option) |
| Bunny CDN | Sydney | Trial only | High-traffic sites needing raw speed |
| KeyCDN | Sydney | Trial only | Pay-as-you-go pricing |
| Host-included CDN | Varies | Included with hosting | Simplest setup (zero configuration) |
Caching Configuration: The 4 Layers
Layer 1: Browser Caching
Browser caching tells visitors’ browsers to store static files locally. On return visits, these files load from the local disk instead of being re-downloaded. This is configured via HTTP headers in your .htaccess file or server configuration.
RECOMMENDED CACHE DURATIONS
Images (jpg, png, webp): 1 year
CSS files: 1 year (with cache busting)
JavaScript: 1 year (with cache busting)
Fonts: 1 year
HTML pages: No cache (or short, 5 min)
Layer 2: Page Caching
Page caching stores the fully rendered HTML output of each page. Subsequent visitors receive the cached HTML directly without WordPress needing to execute PHP or query the database. This reduces server response time from 500-2000ms to 20-50ms.
Pages that should NOT be cached: shopping cart, checkout, user account pages, and any page with personalised content. Most caching plugins handle these exclusions automatically.
Layer 3: Object Caching (Redis/Memcached)
Object caching stores database query results in server memory. WordPress makes hundreds of database queries per page load — object caching means frequently-requested data is served from RAM (nanoseconds) instead of disk (milliseconds). This is particularly impactful for WooCommerce stores and membership sites where page caching cannot be used.
Layer 4: CDN Edge Caching
The CDN caches your static assets at edge nodes worldwide. Some CDNs (like Cloudflare with APO) can also cache entire HTML pages at the edge, delivering your full page from the nearest data centre without ever hitting your origin server. This is the fastest possible configuration.
Measuring Cache Performance
| Metric | Target | How to Check |
|---|---|---|
| Cache hit rate | >90% | CDN analytics dashboard |
| TTFB (cached page) | <100ms | Browser DevTools > Network tab |
| Bandwidth saved | >60% | CDN analytics |
| Origin requests/day | Decreasing trend | Server access logs |
Downloadable Checklist
CDN & Caching Setup Checklist
☐ Choose CDN provider (Cloudflare recommended for AU)
☐ Point DNS to CDN (change nameservers or add CNAME)
☐ Enable SSL on CDN (Full Strict mode)
☐ Set browser cache TTL (1 year for static assets)
☐ Install page caching plugin (LiteSpeed Cache or WP Rocket)
☐ Configure page cache exclusions (cart, checkout, account)
☐ Enable GZIP/Brotli compression
☐ Enable object caching if available (Redis)
☐ Set up cache purge rules (purge on post update)
☐ Test cache hit rate (target >90%)
☐ Verify TTFB <100ms on cached pages
☐ Monitor monthly via CDN analytics
Published by the Rhixo team. Our Business and Enterprise hosting plans include CDN with Australian edge nodes at no extra cost.