Super page cache for Cloudflare vs Cloudflare APO

Hi

I have been doing some research trying to understand how your plugin works and how cloudflare apo works. I used your plugin a year ago. Performance was great. Now I see good reviews about CF Apo but also I see you updated your plugin with a new setup specially for woocommerce sites by using “Remove Cache Buster Query Parameter” feature.

I am wondering what would be better option for my woocomerce site for improving speed and performance specially fo mobile devices.

I found these articles that explain how APO works and the reasons why its better than using the cache everything rule:

Cloudflare (in the interview on Freelancer Tools) says:

• The main one is that when APO is enabled, the Cloudflare plugin will automatically trigger a cache purge for the subset of the pages that were modified (including categories and tags).
• When using cache everything, customers need to purge the cache manually which is much less specific and can purge pages from the cache that never changed.
• Secondly, APO uses 2 caching mechanisms: Cache and Workers KV Storage.
• Using KV storage in APO we increased cache hit ratio by 30%.
• Lastly APO uses smart caching, so it will bypass the cache if it detects WordPress specific cookies or query parameters (excluding those commonly related to attribution / marketing like UTMs).
• Additionally, KV purges publish instantly across the global edge while cache everything purges propagate a bit more slowly

Brian Li (from Kinsta) says:

“Contrary to the popular belief that WP Cloudflare Super Page Cache is the same as, or better than, Cloudflare APO, I actually believe that APO is definitively superior – at least from a page caching standpoint. Unlike Cloudflare APO, using a cache everything page rule doesn’t provide you with a global replication layer that automatically copies HTML to data centers around the world. With a “cache everything” page rule configured, a request to your site from Tokyo will only result in a page being cached in Tokyo. With APO, a request to your site from Tokyo will trigger Cloudflare to store the HTML page in Workers KV, which automatically replicates across Cloudflare’s global network within 60 seconds. To put it simply, APO effectively decentralizes your site’s origin by mirroring your site across Cloudflare’s global edge network.”

Kinsta says:

“Previously, the most popular “full page caching” method involved creating a Cloudflare page rule to “cache everything”. While this method could result in significant performance gains, it wasn’t a very efficient method of caching because it relied on a “pull” model instead of Workers KV’s “push” model which automatically pushes HTML globally.”

Knowing this, with the new update of your plugin would I get better results comparing to APO?