Should I use PicPerf or PicPerf Turbulence?

Use PicPerf if you can change image URLs (or install the WordPress plugin) and only need images. Use PicPerf Turbulence if you want the whole HTML page optimized — images, fonts, scripts, hints, CSS/JS — with a DNS change and no code edits.

Yes. Turbulence rewrites eligible image URLs in HTML automatically, so you usually do not also prefix those tags. Hosted or proxied PicPerf URLs are still useful for assets outside HTML, emails, or places you want manual control.

PicPerf vs PicPerf Turbulence

PicPerf optimizes individual images. PicPerf Turbulence optimizes the entire HTML page from a DNS change. Same company, different jobs.

Last updated: August 15, 2026

Bottom line: choose PicPerf when you only need image optimization and can prefix URLs or upload files. Choose PicPerf Turbulence when you want full-site frontend performance — images plus fonts, scripts, resource hints, and HTML caching — without touching the codebase.

	PicPerf (images)	PicPerf Turbulence
Job	Optimize individual image URLs	Rewrite every HTML page at the edge
Setup	Prefix URLs, upload, or WordPress plugin	TXT + CNAME to optimize.picperf.io
Scope	Images only	Images, fonts, scripts, hints, CSS/JS, HTML cache
Code changes	Yes, unless you use an integration	No
Starting price	$5/month (500 unique images)	$19/month (1 site, unlimited pages)
Best for	Dev teams that want a simple image CDN	Sites that need a no-code Core Web Vitals lift

When PicPerf images is enough

You control templates, you can prefix https://picperf.io/, or you run WordPress with the official plugin. Images are the main weight on the page and you do not want a reverse proxy in front of HTML.

When PicPerf Turbulence is the better fit

You cannot easily change the theme (Squarespace, a locked CMS, an agency handoff). Render-blocking scripts and third-party fonts are part of the problem. You want one DNS change instead of a performance project. See improve Core Web Vitals without code.

Using both

Turbulence already routes eligible HTML images through the PicPerf engine. Keep hosted/proxied PicPerf URLs for newsletters, PDFs, or assets that never appear in HTML. Do not double-prefix tags Turbulence already rewrites.

Frequently asked questions

Use PicPerf if you can change image URLs (or install the WordPress plugin) and only need images. Use PicPerf Turbulence if you want the whole HTML page optimized — images, fonts, scripts, hints, CSS/JS — with a DNS change and no code edits.
Yes. Turbulence rewrites eligible image URLs in HTML automatically, so you usually do not also prefix those tags. Hosted or proxied PicPerf URLs are still useful for assets outside HTML, emails, or places you want manual control.

Related guides

PicPerf Turbulence vs NitroPack Two full-site optimizers compared on setup, platform coverage, and scope.
PicPerf Turbulence vs Cloudflare How an HTML-rewriting edge layer differs from Cloudflare’s CDN and Speed products.
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