PicPerf Turbulence for Squarespace

PicPerf Turbulence for Squarespace puts the public hostname behind PicPerf's edge and rewrites each HTML response. This is useful when a managed template emits heavy images, fonts, marketing tags, or external scripts that are difficult to change directly. The Squarespace origin stays where it is; Turbulence applies its performance layer with DNS.

What gets optimized on Squarespace

• Eligible image URLs present in the initial HTML
• Font preloading and external-origin connection hints
• Known-safe third-party scripts loaded asynchronously
• Same-origin CSS and JavaScript minification and edge caching
• Transformed HTML caching with stale-while-revalidate

Squarespace-specific caveats

Squarespace's editor, preview, and account surfaces are not public storefront traffic and should remain on their normal hosts. JavaScript that injects images after the initial HTML response may not be rewritten. Forms, commerce, member areas, analytics, and consent banners should be tested on a staging or low-risk hostname first. Squarespace's official DNS connection guide provides the platform-side context; use PicPerf's Turbulence setup guide for verification and routing.

How to set it up

1. Create a Turbulence site for the public hostname, such as www.example.com.
2. Add the dashboard's TXT record to verify ownership.
3. Point the public hostname's CNAME at optimize.picperf.io.
4. Keep Squarespace editor and preview hosts on Squarespace DNS.
5. Test pages, forms, commerce, and third-party blocks, then compare performance.

When it is worth using

Turbulence is a strong fit when you cannot safely edit the template but the public site still has render-blocking scripts, external fonts, missing resource hints, or uncached HTML. Request a free analysis to identify likely wins before changing DNS.

Learn what Turbulence is, review Core Web Vitals without code, or see the complete optimization pipeline.