Back to Top Start a Trial

PicPerf Turbulence for Squarespace

Squarespace themes are hard to rewrite. PicPerf Turbulence speeds the public site up with a DNS change — no code injection, no template edits.

By Alex MacArthur, builder of PicPerf · Published

PicPerf Turbulence for Squarespace puts the public hostname behind PicPerf’s edge. Every HTML page is rewritten (images, fonts, scripts, hints) and cached. You do not touch Squarespace code injection. That is the usual path when you cannot change how the template emits <img> tags.

Why Squarespace sites stay slow

Templates ship large images, Google Fonts, and marketing tags you do not fully control. Image-only CDNs need URL prefixes you cannot apply. An edge HTML optimizer does not need those prefixes.

How to set it up

  1. Create a Turbulence site for www.example.com.
  2. Verify the domain with the TXT record.
  3. CNAME www to optimize.picperf.io. Keep the Squarespace built-in domain connection only if you are not moving that hostname; follow getting started so the public host and the origin host stay distinct.
  4. Leave the Squarespace editor/preview hostname on Squarespace.

More context: what PicPerf Turbulence is and Core Web Vitals without code.

Frequently asked questions

  • Yes. PicPerf Turbulence sits in front of the Squarespace hostname. You point DNS at optimize.picperf.io. HTML is rewritten at the edge. You do not add Squarespace code-injection snippets or change the template.

  • The origin stays on Squarespace. Cookies and form posts pass through. Non-HTML routes pass through. If something looks wrong, purge the URL or remove the CNAME. Preview/editor hosts should stay on Squarespace DNS.

Related guides

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

Start a 14-day Turbulence trial