Automatic Platform Optimization: WordPress Now Served From the Edge

Cloudflare is rolling out Automatic Platform Optimization (APO), a service that caches and serves entire WordPress sites from its edge network rather than just static assets. The company's testing of 505 customer sites found a 72% reduction in Time to First Byte (TTFB), a 23% reduction in First Contentful Paint (FCP), and a 13% improvement in Speed Index at the 90th percentile for desktop users.

APO is priced at $5/month for Free plan customers and is included with Professional, Business, and Enterprise plans. Usage-based fees do not apply.

Setup From the WordPress Dashboard

Enabling APO requires three steps from the WordPress admin console:

  1. Install or update the Cloudflare WordPress plugin to version 3.8.2 or higher.
  2. Authenticate the plugin to connect with Cloudflare.
  3. Toggle on Automatic Platform Optimization from the Cloudflare section's Home screen.

Free plan users are directed to the Cloudflare Dashboard to purchase the service before activation.

Serving Dynamic Content Like Static Files

Traditional CDNs cache images, CSS, and JavaScript while requests for HTML still traverse back to the origin server. Because no other assets load until the browser receives and parses HTML, that first round trip dominates TTFB. Shared hosting congestion, slow database queries, and plugin overhead only compound the delay.

APO eliminates the origin hop for the entire page. The service runs on Cloudflare Workers to intelligently cache HTML and other dynamic content, serving all requests from an edge network positioned within 10 milliseconds of 99% of developed-world internet users. No origin requests or server processing occur for most visits, and because optimizations run on the edge, no extra JavaScript executes on the client, leaving render and interactivity untouched.

Content updates are handled through the WordPress plugin. When a site changes, the plugin triggers a cache purge across Cloudflare's global network. Sites that cannot or choose not to use the plugin still receive the performance benefits but may serve content up to 30 minutes stale, refreshed when requested again.

Edge Caching Preserves Authenticated Sessions

Authenticated user content is not cached indiscriminately. APO bypasses the cache for standard WordPress and WooCommerce cookies tied to logged-in sessions, ensuring personalized content stays private. This behavior was previously limited to Business-level accounts but now applies to any WordPress deployment with APO enabled.

Third-party fonts also get cached from the edge. Since fonts often block text rendering, removing the round trip to external font hosts improves both paint timing and Speed Index. The service is also noted to benefit from existing Cloudflare TLS connection times and HTTP/2 protocol support.

Independent Testing by Kinsta

Kinsta, a managed WordPress host, ran independent tests on a site hosted in Tokyo from six worldwide locations. The results tracked with Cloudflare's internal numbers:

  • Performance improved by 70-300%, with the largest gains seen from the most geographically distant test locations.
  • Sub-second load times were consistent across all regions with APO, compared with two to three seconds when using only traditional static CDN caching.
  • TTFB remained consistently under 400 ms under load because origin processing time drops to zero.
  • The company described upgrading from a static-only CDN to APO as a "no-brainer" to help WordPress sites compete with edge-native static architectures.

Platform Expansion Planned

WordPress powers 38% of the web, making it the first target for the new service. Cloudflare states that other popular site platforms will receive the same capability in the future and is inviting platform operators to discuss partnership opportunities. APO builds on the prototype work previously detailed in the company's engineering blog for improving HTML TTFB and speeding up Google Fonts delivery via Workers.