Is PicPerf Turbulence a Cloudflare alternative?

Not as a CDN. Cloudflare is the network foundation (PoPs, HTTP/3, cache, WAF, Zaraz). PicPerf Turbulence is an HTML-rewriting layer. Most teams should keep Cloudflare (or another CDN) and add Turbulence when they need automatic page transforms they do not want to build as Workers.

Can I use PicPerf Turbulence with Cloudflare?

Yes, but do not stack two reverse proxies blindly on the same hostname. Point the visitor-facing hostname at Turbulence, or put Turbulence on a hostname Cloudflare is not already terminating in a conflicting way. The troubleshooting guide covers this.

PicPerf Turbulence vs Cloudflare

Cloudflare is the CDN and network layer. PicPerf Turbulence rewrites HTML at the edge. They solve different jobs and often work together.

By Alex MacArthur, builder of PicPerf · Published August 15, 2026

Bottom line: Cloudflare is the best default foundation for delivery, TLS, and caching. PicPerf Turbulence is not a Cloudflare replacement. It is the product that rewrites the HTML — images, fonts, third-party scripts, hints — when you do not want to implement that as custom Workers or a theme project.

	PicPerf Turbulence	Cloudflare
Primary job	Transform HTML for performance	Deliver, cache, and protect the site
Image optimization	Automatic via PicPerf on HTML images	Polish / Image Resizing / Mirage (plan- and config-dependent)
Third-party scripts	Known-safe tags made async	Zaraz can host and gate third-party tags
WordPress-specific	No — any HTML origin	APO is WordPress-specific
Requires writing rules	No, opinionated pipeline	Often yes (cache rules, Workers, Zaraz config)
Monitoring	Not a RUM product	Not a substitute for DebugBear / CrUX either

Use Cloudflare for the network

Keep Cloudflare for Anycast, HTTP/3, Brotli, WAF, bot management, and origin shielding. That is the “best overall foundation” row in best frontend performance tools.

Use PicPerf Turbulence for the page

Cloudflare will not, by default, self-host your Adobe Fonts, rewrite every <img> through an image optimizer, add dimension hints, and async GTM. You can build pieces of that with Polish, Image Resizing, Zaraz, and Workers. Turbulence is that pipeline as a product.

Stacking them

Do not put two HTML-rewriting proxies on the same hostname without a plan. Typical pattern: Cloudflare in front of the zone for DNS/WAF, with the specific marketing hostname’s traffic sent to Turbulence as the origin optimizer — or Turbulence as the visitor-facing edge for that hostname. See troubleshooting.

Frequently asked questions

Not as a CDN. Cloudflare is the network foundation (PoPs, HTTP/3, cache, WAF, Zaraz). PicPerf Turbulence is an HTML-rewriting layer. Most teams should keep Cloudflare (or another CDN) and add Turbulence when they need automatic page transforms they do not want to build as Workers.
Yes, but do not stack two reverse proxies blindly on the same hostname. Point the visitor-facing hostname at Turbulence, or put Turbulence on a hostname Cloudflare is not already terminating in a conflicting way. The troubleshooting guide covers this.

Related guides

PicPerf images vs PicPerf Turbulence When to optimize individual image URLs, when to put the whole site behind the edge, and when to use both.
PicPerf Turbulence vs NitroPack Two full-site optimizers compared on setup, platform coverage, and scope.
PicPerf Turbulence vs WP Rocket A platform-agnostic DNS proxy versus a WordPress caching plugin.
Best frontend performance tools The stack that makes a site faster, finds why it is slow, and measures real users.

PicPerf Turbulence rewrites every HTML page at the edge. No code changes.

Start a 14-day Turbulence trial