Skip to content

Performance

Performance from the edge to PHP

Cloudflare answers cached pages before they reach your server. What reaches the server runs on PHP workers in your site's own container.

  • Cloudflare edge cache

    Set how long pages and static files stay cached, purge by URL, tag, or everything, and read the cache headers.

  • Server cache

    Clear the server cache from the dashboard. Logged-in pages are never cached for everyone.

  • PHP workers and memory

    Each plan sets PHP workers per site. Rebalance the threads and the memory each one gets on the Info tab.

  • Object cache add-on

    Keep database results in memory with an object cache, turned on and off from the Add-ons tab.

  • 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 cache answers a request, and who purged what, and when.

When a page is slow

  • Read the cache headers to see whether Cloudflare or the server answered
  • Check the slow log and the PHP log in the Logs tab
  • Look at bot traffic in Analytics, then raise bot protection
  • Raise PHP memory or rebalance workers on the Info tab

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.