We want edge caching but aren't sure it fits.
Cloudflare's edge cache (free tier) speeds up static assets almost instantly. Dynamic pages (WP) need APO or a custom cache rule.
Try this first
- 1Connect the domain to Cloudflare. Change nameservers at the registrar; within 24 hours the site is behind Cloudflare.
- 2By default Cloudflare caches CSS, JS, fonts and images at the edge. That alone shaves visible TTFB worldwide.
- 3For WordPress: buy Cloudflare APO (five dollars per month). It caches HTML at the edge, dropping TTFB from 800ms to 100ms for anonymous visitors.
- 4Page Rules or Cache Rules: set specific paths to Cache Everything (e.g. /blog/* but not /cart or /my-account).
- 5Purge after publishing via the WP-Cloudflare plugin or WP Super Cache. Otherwise visitors see stale content after edits.
- 6Test in incognito with devtools: cf-cache-status header should be HIT for anonymous requests, BYPASS or MISS for logged-in sessions.
When to bring us in
E-commerce, dynamic personalisation or memberships? Edge caching gets subtle. A Cloudflare Workers engineer or experienced WP architect prevents cart-data leaks.
See also
- WordPress, plugins and theme have gone 6+ months without updatesOut-of-date WP is the number-one entry for malware. Don't just hit 'update all', back up first.
- Theme update broke the layout or threw a fatal errorThemes overwrite custom CSS on update unless you use a child theme.
- WordPress shows a blank screen after a plugin install or updateWSOD (white screen of death) is usually one crashing plugin. You isolate it.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.