Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Explainer

Is Cloudflare APO Worth It for WordPress?

Short answer

Cloudflare APO is worth $5 a month for most public WordPress blogs and brochure sites whose visitors are far from the origin server, because it serves full HTML pages from the edge instead of running PHP on every view. It is not worth it for multisite installs, sites where most visitors are logged in, or stores where most pages are personal, because those requests bypass the cache. Check the price on your own dashboard before you pay, as of November 2026.

Key takeaways

  • APO costs $5 a month on the Cloudflare Free plan and is included with Pro and higher plans, as of November 2026.
  • APO caches full HTML pages at the edge for up to 30 days and purges a changed page within about 30 seconds.
  • Logged-in users, WooCommerce sessions, checkout, wp-cron.php and feeds always bypass the APO cache.
  • APO does not support WordPress multisite, so multisite owners need a different caching route.
  • A good Largest Contentful Paint is 2.5 seconds or less at the 75th percentile of page loads, per web.dev.
  • Turn off other page caching plugins first when you set up APO, then test one change at a time.

What is Cloudflare APO for WordPress?

Cloudflare APO is a paid add-on that caches your full WordPress HTML pages on Cloudflare's edge network, so many visitors get a whole page without a trip to your origin server.

APO stands for Automatic Platform Optimization. Cloudflare's own APO overview says Cloudflare normally caches only static content, while APO also caches dynamic content such as HTML.

The WordPress plugin connects your site to Cloudflare. It tells the edge when a page has changed, so edited content is purged and fresh content is served.

APO is built for WordPress only. It is not a general cache for every platform, and it does not replace your host, your backups, or your security plugin.

How does APO work?

APO stores a copy of each eligible public page at a nearby Cloudflare data center, then serves that copy to the next visitor who asks for the same page.

When a visitor requests a page, Cloudflare checks the edge first. If a fresh copy is there, it serves it at once. If not, the request goes to your origin, WordPress builds the page, and Cloudflare stores a copy for later.

Cloudflare's APO overview lists the exact rules for caching a page as HTML. The request must use GET or HEAD, the origin must return HTTP 200 with a text/html content type, and the WordPress plugin must send a header that permits caching.

APO also caches third-party scripts with the page, which cuts the number of requests that leave the edge. That detail matters on pages with many widgets and embeds.

What happens when you update a post?

When you publish or edit content, the Cloudflare WordPress plugin purges the cached copy. Cloudflare states that cached HTML lasts up to 30 days, and a changed page is purged within about 30 seconds when the plugin is installed.

That short purge time is why APO fits blogs and news sites. You edit a post, and visitors see the new version within a minute in most cases.

How much does Cloudflare APO cost?

APO costs $5 a month on the Cloudflare Free plan, and it is included with Pro and higher plans, as of November 2026.

The Cloudflare plans page lists Pro at $20 a month billed annually, or $25 a month billed monthly. Business is listed at $200 a month billed annually, or $250 a month billed monthly.

That pricing makes the maths simple. If you only want HTML edge caching, Free plus the $5 APO add-on costs $60 a year. Pro costs $240 a year on annual billing, so you should only move to Pro if you also want its other features.

Compare the plans on the Cloudflare Free vs Pro guide before you upgrade for APO alone. Prices change, so confirm the figure shown in your own Cloudflare dashboard.

PlanAPO cost as of November 2026Monthly plan price
Free$5 a month add-on$0
ProIncluded$20 billed annually, $25 billed monthly
BusinessIncluded$200 billed annually, $250 billed monthly

What does APO cache, and what does it skip?

APO caches public, anonymous HTML pages, and it skips anything personal, logged in, or state changing.

Cloudflare's APO docs list the full set of conditions. A page is cached only when every rule is met, and any failed rule sends the request to the origin instead.

  • Public posts and pages with no bypass cookie
  • Static assets such as images, CSS, and JavaScript
  • Third-party scripts served with the cached page

APO skips the cache for logged-in users and administrators, so editors always see live pages. It also skips requests that carry session or WooCommerce cookies, so shoppers see their own carts.

These paths are excluded by APO:

  • Checkout pages
  • wp-cron.php
  • Feeds

Query strings are cached only when they use supported marketing parameters. A page with a random or unknown query string is served from the origin instead.

Is APO worth it for a small blog?

Yes, APO is usually worth $5 a month for a small public blog when your readers are spread across regions or your host is slow to answer.

A blog is the best case for APO. Most readers are anonymous, most pages are the same for everyone, and posts change rarely after publication. That means a high share of requests can be served from the edge.

The gain is largest when your origin is far from your readers. A reader in another country gets a page from a nearby data center instead of waiting for a round trip to your host.

The WordPress.org Cloudflare plugin page says APO serves sites from more than 250 data centers worldwide. It also lists more than 200,000 active installs for the plugin, which needs PHP 7.4 or higher and WordPress 6.7 or newer.

APO is less useful when your readers are all near your host and your host already answers fast. In that case, measure before and after with PageSpeed Insights, and keep APO only if the numbers move.

Is APO worth it for a WooCommerce store?

APO is worth it for the public catalog pages of a store, but it does not speed up carts, checkout, or logged-in account pages, because those bypass the cache.

Product and category pages are public and shared, so they can be cached like blog posts. That is where a store gains from APO.

Cart, checkout, and account pages carry session cookies, so APO sends them to the origin. That is correct behaviour: a shared cache must never show one shopper's cart to another.

If most of your traffic lands on product pages, APO can still pay for itself. If most of your traffic is logged-in customers or checkout flows, the $5 buys little, and your money is better spent on faster hosting or fewer heavy plugins.

How do you turn on APO for WordPress?

You buy APO on the Free plan first, install the official Cloudflare plugin, connect it with an API token, and switch APO on.

Cloudflare's APO setup guide gives this order, and it warns Free plan users to purchase APO before installing the plugin.

  1. In the Cloudflare dashboard, go to Speed, then Settings, then Content Optimization, and select Purchase for Automatic Platform Optimization for WordPress.
  2. In WordPress, go to Plugins, then Add New, search for Cloudflare, and install and activate the official plugin.
  3. In the Cloudflare dashboard, create an API token with the WordPress template, then add it in the plugin settings.
  4. Switch the Automatic Platform Optimization toggle to On.
  5. Turn on Auto Purge Content On Update so edits clear the cached copy.

Cloudflare also recommends turning off plugins such as WP Rocket or W3 Total Cache when you first set up APO. Run APO alone first, confirm it works, and only then test whether another caching plugin adds anything.

How do you check that APO is working?

Open a public post in a logged-out browser, inspect the response headers, and look for a cache HIT from the edge.

Use your browser's developer tools or a header checker. A cached page shows cf-cache-status: HIT, and APO pages also carry the cf-apo-via header.

If you see cf-cache-status: DYNAMIC, the page bypassed the cache. Check the cf-apo-via header, which names the reason, and compare it with the caching rules in the APO docs.

Test with a page you have not just edited, and test while logged out. Logged-in requests always bypass the cache, so testing while signed in tells you nothing.

Which numbers should you watch?

Watch Time to First Byte and Largest Contentful Paint. APO targets the server wait, so those two move first when caching works.

Google's Web Vitals guide sets a good Largest Contentful Paint at 2.5 seconds or less, a good Interaction to Next Paint at 200 milliseconds or less, and a good Cumulative Layout Shift at 0.1 or less. Each is judged at the 75th percentile of page loads, split by mobile and desktop.

Google Search Central repeats the same three thresholds in its Core Web Vitals guide and says it highly recommends good scores for success with Search. For background on the interactivity metric, read our guide on what INP is.

APO or a free Cache Rule: which should you pick?

Pick APO if you want managed purging and setup handled for you, and pick a Cache Rule if you want free HTML caching and are happy to manage the rule yourself.

Both routes cache HTML at the edge. APO adds the WordPress plugin, automatic purging, and the Workers and KV layer that shares cached pages across regions. A Cache Rule is a setting you write in the Cloudflare dashboard, and you manage purging yourself.

Our guide to Cloudflare Cache Rules for WordPress walks through the free route. Read it before you write a rule by hand, because a wrong rule can cache a logged-in page or a cart.

Never run APO and a Cache Rule that caches the same HTML at the same time. Pick one route, and remove or disable the other.

OptionCost as of November 2026PurgingBest for
APO$5 a month on Free, included on Pro and higherAutomatic through the WordPress pluginOwners who want setup and purging handled
Cache Rule$0Managed by you or a pluginOwners who want free HTML caching and can manage a rule

What are the common myths about APO?

The most common myth is that APO makes every page fast, when it only speeds up pages that qualify for the cache.

Myth 1: APO fixes slow hosting. It does not. A cache miss still runs PHP and the database on your origin, so a slow host still shows on first visits and on every bypassed request.

Myth 2: APO caches everything. It does not cache logged-in pages, carts, checkout, feeds, or wp-cron.php. Those requests always reach your origin.

Myth 3: APO replaces a caching plugin. It replaces page caching for public pages, but it is not an object cache, and it does not fix slow PHP, slow queries, or heavy images.

Myth 4: APO guarantees a fixed speed gain. Cloudflare's plugin page says APO can speed up a site by up to 300%, but that is the vendor's own wording, not a promise for your site. Your gain depends on your host speed, your visitors' distance, and how many of your requests qualify for caching.

If your main cost question is the CDN itself rather than APO, read our guide on how much a CDN costs for WordPress.

For the wider picture on speed and rankings, read does page speed affect SEO.

What mistakes should you avoid?

The costliest mistake is running APO beside another page cache, because the two systems can purge and serve different copies.

  • Running APO with WP Rocket, W3 Total Cache, or a Cache Rule that caches the same HTML
  • Turning APO on for a WordPress multisite install, which Cloudflare lists as unsupported
  • Testing while logged in, then concluding APO does nothing
  • Forgetting Auto Purge, so edited posts stay stale at the edge
  • Judging APO on one load, instead of checking cache headers and field data over days

If your site already uses host-level page caching, compare the two routes in our guide on WP Rocket vs host caching before you add APO on top. One cache, tested and checked, beats two caches fighting each other.

Frequently asked questions

Does Cloudflare APO work without the WordPress plugin?

Cloudflare says APO works best with the WordPress plugin installed and does not recommend using APO without it. The plugin sends the header that permits caching and purges edited pages from the edge. Without it, you lose automatic purging and the cache permission signal, so install and connect the plugin first.

Does APO slow down wp-admin or the WordPress dashboard?

No. Logged-in and administrator requests bypass the APO cache, so the dashboard always runs live against your origin. APO only caches public, anonymous pages. If wp-admin feels slow after enabling APO, the cause is your host, a plugin, or the database, not the edge cache.

Can APO cache a site with a contact form?

Yes, for the page that holds the form, because the form page itself is public HTML. Form submissions use POST requests, which APO does not cache, so each submission still reaches your origin. Test the form after enabling APO to confirm submissions arrive and confirmation messages display correctly.

How long does APO keep a page cached?

Cloudflare states that APO caches HTML for up to 30 days. When the WordPress plugin is installed, editing a post or page purges that page from the edge within about 30 seconds. You can also purge the whole cache from the Cloudflare dashboard if you make a site-wide change such as a new theme.

Is APO better than upgrading my hosting plan?

They fix different problems. APO cuts the wait for cached public pages, while faster hosting cuts the wait for every request, including cache misses, logged-in pages, and checkout. If your host is very slow, upgrade the host first. If your host is fine but your readers are far away, APO is the cheaper fix.

Sources

  1. About Automatic Platform Optimization Cloudflare Developers
  2. Activate the Cloudflare WordPress plugin Cloudflare Developers
  3. Cloudflare WordPress.org
  4. Cloudflare plans Cloudflare
  5. Web Vitals web.dev
  6. Understanding Core Web Vitals and Google search results Google Search Central

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test