Performance
Performance from the edge to PHP
Cloudflare serves your images, CSS, and JavaScript from the edge. Your site's server answers most pages from its page cache, and the rest run on PHP workers in your site's own container.
Cloudflare CDN
Static files are cached at Cloudflare's edge, close to your visitors. Purge by URL, tag, or everything from the dashboard. Page caching at the edge is planned.
Server page cache
Pages for visitors who are not logged in are cached on the server, and publishing a post clears the pages it touches. Logged-in pages, carts, and forms are never cached.
Dedicated PHP resources
Each site runs on its own PHP workers and memory pool. Rebalance the threads and the memory each one gets on the Info tab.
Object cache add-on
An object cache with Redis, which keeps database results in memory for busy sites, is available as an add-on.
Bot traffic kept down
Bot protection levels and IP deny rules stop crawlers you do not want before they use PHP time.
Cache statistics
See how often the server cache answers a request, and who purged what, and when.
When a page is slow
- Read the x-avaloi-cache header to see whether the page cache answered
- Check the slow log and the PHP log in the Logs tab
- Look for crawlers in the access log, then raise bot protection
- Raise PHP memory or rebalance workers on the Info tab
Read more in the docs
Start with one site. Add more when you need them.
Sign in with Google or GitHub, choose a plan, and your first site is on staging in minutes.