Drop-in page optimization without touching your codebase.

Hosted and Proxied Images optimize individual image URLs — you change how images are referenced on your site. Turbulence sits in front of your entire site at the edge. Point DNS at PicPerf and every HTML page is rewritten automatically: images, fonts, scripts, resource hints, and more. No theme changes, no build pipeline, no per-asset URL prefixes. Turbulence optimizes HTML responses only — APIs, JSON, PDFs, and other non-HTML routes pass through unchanged.

No. Turbulence sits between your site and your visitors. You add DNS records and traffic routes through the edge. Your origin stays exactly as it is — Turbulence fetches pages, applies optimizations, caches the result, and serves it to visitors. HTTPS is handled at the edge; your origin URL stays whatever it is today.

Any site that serves HTML over HTTP — WordPress, Squarespace, static generators, Laravel, Shopify storefronts, and more. Logins, carts, and cookies work normally; Turbulence is a reverse proxy for HTML, not a session layer. If you already use Cloudflare or another CDN, you may need to route that hostname through Turbulence rather than stacking proxies blindly — see the troubleshooting guide at picperf.io/docs/turbulence/troubleshooting.

Each HTML response runs through a transformation pipeline: images routed through PicPerf (with sizing, lazy loading, and dimension hints), Adobe Fonts self-hosted at the edge, Google Fonts preloaded for earlier fetch, known-safe third-party scripts loaded asynchronously, same-origin CSS and JS minified and edge-cached, critical CSS inlined, resource hints injected, speculation rules for link prefetch on supporting browsers, and stale preload tags cleaned up. See picperf.io/docs/turbulence/optimizations for the full list.

Images already on major CDNs (Cloudinary, Imgix, Shopify, and similar) are left alone. JavaScript that injects images after page load isn't rewritten. URLs inside cross-origin CSS or JS files aren't touched. Non-HTML responses — APIs, JSON, downloads, video — pass straight through. If your site is already fully optimized, gains will be smaller; the free analysis shows exactly which steps fire for your URL.

Yes. Turbulence rewrites eligible image URLs in your HTML automatically, so you don't need the per-asset URL prefix approach on top of it. Hosted and Proxied Images are still useful when you want manual control over specific assets outside Turbulence.

Create a Turbulence site in the PicPerf dashboard, then add a TXT record to verify ownership and a CNAME pointing your hostname at optimize.picperf.io. Using www is the straightforward path; apex (root) domains need ALIAS or CNAME flattening from your DNS provider, or you can redirect the root to www. Step-by-step instructions are at picperf.io/docs/turbulence/getting-started. To roll back, remove the CNAME — your origin is never modified.

Your origin, code, and hosting stay untouched. Cookies, authentication, and form posts pass through normally. If something looks wrong after setup, you can bypass the cache for a single request with ?pp_verify=1 or purge a URL from the dashboard. Removing the CNAME puts traffic back on your origin immediately.

Transformed HTML is cached at the edge per URL. By default, entries stay fresh for 15 minutes, then serve stale for up to 7 days while revalidating in the background — visitors always get a fast response. The first request to a URL is slower (a cache miss); repeat visits are served from the edge. You can adjust TTL per domain in the dashboard, purge the whole site or a single URL, and cached pages keep serving during brief origin outages. Details at picperf.io/docs/turbulence/caching.

Within the 15-minute freshness window, Turbulence serves the cached HTML without re-fetching your origin. After that, stale-while-revalidate updates the cache in the background — most publishes appear within 15 minutes. For an urgent fix, purge the URL or domain from the PicPerf dashboard.

Often immediately on pages Turbulence can rewrite — especially image-heavy sites with render-blocking scripts or third-party fonts. The first visit to each URL runs the full pipeline inline, so test a URL twice or check response headers after the initial load. Already-optimized sites see smaller gains. Run PageSpeed Insights on the same URL before and after pointing DNS, or use the free analysis below for a simulated before-and-after without changing DNS.

Load your site and inspect the HTML response headers. You should see X-PicPerf-Cache (HIT, MISS, or STALE), X-PicPerf-Optimized: true, and X-PicPerf-Steps listing which transformations ran. Image src attributes on optimized pages point through picperf.io. Full checklist at picperf.io/docs/turbulence/verifying.

Yes. Sign up for a 14-day free trial — no credit card required, no charge until the trial ends. You can also request a free performance analysis below: we run PageSpeed Insights on any public page and email a before-and-after report with no DNS changes required.

Enter any public URL and your email. We audit the page with PageSpeed Insights (lab data), simulate Turbulence's optimizations, and send a report with your current scores alongside the optimized version — Core Web Vitals, specific enhancements, and which pipeline steps would apply.

Starter ($29/mo) covers one site and up to 100 pages. Professional ($79/mo) covers three sites with up to 500 pages each, plus speculation rules and advanced resource hints. Agency ($199/mo) covers ten sites with unlimited pages, white-label options, and team collaboration. Every plan includes the core optimization pipeline, edge caching, Core Web Vitals tracking, and a 14-day trial.