WebSpeed

How fast could your site be?

Enter your address. We measure it as it is and through WebSpeed, side by side.

No signup. See your before/after PageSpeed score in about a minute. What the report shows

Speed up Squarespace without moving off Squarespace

You keep the site, the editor and the hosting: a DNS change routes traffic through WebSpeed, and nothing is installed anywhere. Squarespace makes good-looking sites and gives you almost no control over how they load — no server, no build step, no access to the markup. We measured what actually sits on the critical path across 1,032 Squarespace sites: the same handful of things came back on most of them, and none is reachable from the editor.

No signup. See your before/after PageSpeed score in about a minute. What the report shows

  • Nothing to install
  • Your site stays where it is
  • Any optimization can be switched off
Screen filled · mobile

How fast 1,134 sites fill the screen

Speed Index of the original sites, as they are, without our optimization.

Fastest quarter: 4.3 s or less

Where does yours land? The free check puts your site on this chart.

Across every platform we’ve measured — not enough Squarespace sites yet for a chart of their own. Updated 24 Sep 2026.

What WebSpeed does on Squarespace

Each one is independent and can be switched off for your domain — nothing here is all-or-nothing.

Scripts stop blocking the parse

Inline body scripts are held until rendering is done, then run in order, and parser-blocking files are deferred. Same behaviour, out of the way of the first paint.

Render-blocking resources TBT FCP

The many small stylesheets stop costing round-trips

Small stylesheets are inlined into the first response and the rest stop blocking, so the browser paints on what it already has instead of waiting out a queue of requests.

Critical CSS Render-blocking resources FCP

Unsized images get their real dimensions

We read each image's true aspect ratio server-side and write it into the markup, so the browser reserves the right box before the file lands and the text stops jumping.

CLS

Connections open before they're needed

Stale hints are dropped, and the origins your page genuinely uses get their DNS, TCP and TLS work started early — so the fetch itself is all that's left when the browser arrives.

TTFB

The first screen gets priority

The largest above-the-fold image is preloaded at high priority; everything below the fold waits until it approaches the viewport.

LCP Lazy loading

Your controls

What stays under your control

An optimization you cannot undo is a risk, not a feature. Each of these is a decision you keep after the site is live on WebSpeed.

  • Switch any optimization off

    Each one is independent. If something doesn't suit your Squarespace theme, it can be disabled for your domain alone and everything else keeps working.

  • Keep only what measurably helps

    On a tuned profile we measure each optimization against your own pages and drop the ones that do not earn their place there.

  • Re-check whenever you want

    Your audit page re-runs both measurements on demand, so "did it help" stays a number you can pull rather than a claim you have to take.

  • Turn it off entirely

    WebSpeed sits in front of your site, not inside it. Revert the DNS record and your original site serves again, unchanged — nothing to uninstall.

In progress: a dashboard where you flip these yourself and follow each page's scores over time. Today it is a message to us and we apply it to your domain.

Why Squarespace sites are slow

Measured, not assumed: four things our filter logs recorded across the Squarespace sites we have audited, each with the count behind it.

Measured across 1032 Squarespace audits · snapshot 2026-10-19

83%of sites

Scripts run while the page is drawing

Four sites in five. Squarespace's own runtime and the blocks you added run as inline scripts that execute mid-render, so drawing stops each time one fires. On a phone that is the difference between a page that paints and one that stalls half-drawn.

80%of sites

The stylesheet is delivered as a pile of small files

Nearly all of them. Squarespace splits its CSS across many small stylesheets, and each one is a separate round-trip the browser has to make before it can finish painting. The individual files are tiny; the queue of requests is not.

5846fixes on 809 sites

Images arrive without dimensions

Our highest-volume correction here. Images ship without width and height, so the browser cannot reserve space for them and the text jumps as each one lands — the layout shift Squarespace's polished templates otherwise hide.

2820fixes on 913 sites

The page opens connections it never uses, and misses ones it needs

Squarespace serves your page, its assets, your fonts and your third parties from several origins. We consistently found stale resource hints pointing at origins the page never uses, while the connections that matter were discovered late.

The research behind these numbers

Worked example

Real results

Measured on real Squarespace pages

Stored audits — the original page against the same page served through WebSpeed, on mobile and desktop. Not a demo build: these are the sites as they ship.

Squarespace claradelorenzi.com
Measured with WebSpeed on
Screen filled · mobile
5.0s
was 7.4 s−2.4 s
Page weight
1.3MB
was 3.3 MB−61%
Mobile · PageSpeed
60
was 38+22
Desktop · PageSpeed
77
was 52+25
Forecast · if your visitors get this speed

Projections, not measurements: this run's measured LCP improvement scaled by published studies, and CO₂ from the measured bytes at ≈0.15 g/MB. Sources under the grid.

Google traffic ≤ +40%Conversion +21%Bounce −20%CO₂ −61%
37 optimizations applied
  • Images — 24 changes
  • Resource hints — 7 changes
  • CSS delivery — 3 changes
  • JavaScript — 2 changes
  • Fonts — 1 change
Squarespace jenelletremblett.com
Measured with WebSpeed on
Screen filled · mobile
6.2s
was 18.7 s−12.4 s
Page weight
1.9MB
was 79.2 MB−98%
Desktop · PageSpeed
87
was 45+42
Main content (LCP) · desktop
2.2s
was 2.7 s−0.6 s
Forecast · if your visitors get this speed

Projections, not measurements: this run's measured LCP improvement scaled by published studies, and CO₂ from the measured bytes at ≈0.15 g/MB. Sources under the grid.

Google traffic ≤ +8%Conversion +3%Bounce −5%CO₂ −98%
24 optimizations applied
  • Images — 12 changes
  • Embeds — 4 changes
  • Resource hints — 4 changes
  • CSS delivery — 2 changes
  • JavaScript — 2 changes
Squarespace supernaturalkitchen.com
Measured with WebSpeed on
Screen filled · mobile
6.5s
was 14.0 s−7.5 s
Page weight
3.6MB
was 5.5 MB−36%
Mobile · PageSpeed
58
was 42+16
Desktop · PageSpeed
83
was 51+32
Forecast · if your visitors get this speed

Projections, not measurements: this run's measured LCP improvement scaled by published studies, and CO₂ from the measured bytes at ≈0.15 g/MB. Sources under the grid.

Google traffic ≤ +40%Conversion +27%Bounce −20%CO₂ −36%
48 optimizations applied
  • JavaScript — 19 changes
  • Images — 18 changes
  • Resource hints — 7 changes
  • CSS delivery — 4 changes
Squarespace allirizacos.com
Measured with WebSpeed on
Screen filled · mobile
7.8s
was 10.0 s−2.2 s
Page weight
4.9MB
was 6.4 MB−23%
Main content (LCP) · mobile
17.2s
was 25.0 s−7.7 s
Why only this

The rest stayed inside measurement noise.

Forecast · if your visitors get this speed

Projections, not measurements: this run's measured LCP improvement scaled by published studies, and CO₂ from the measured bytes at ≈0.15 g/MB. Sources under the grid.

Google traffic ≤ +19%Conversion +30%Bounce −20%CO₂ −23%
31 optimizations applied
  • Images — 16 changes
  • CSS delivery — 5 changes
  • Resource hints — 5 changes
  • JavaScript — 4 changes
  • Fonts — 1 change

Real Google Lighthouse audits, original vs. WebSpeed Fast. The filled tiles are measured: the score is shown per device only where it moved beyond the ±5 the audit counts as noise, “screen filled” is Speed Index, and page weight is transferred bytes. The outlined pills are projections from those measurements — not guarantees. Scores are per-page; yours will differ.

Google traffic Core Web Vitals are a Google ranking signal; the biggest lift is leaving the “Poor” zone (score < 50), scaled here by device search share.

Conversion Akamai / SOASTA (2017): a 100 ms delay cost 7% of conversions across ~10 billion retail visits; scaled here to the measured improvement.

Bounce Akamai / SOASTA (2017): a two-second delay raised bounce rate by 103%; scaled to the measured improvement, site-specific.

CO₂ The measured byte reduction at ≈0.15 g per MB per visit (Sustainable Web Design v4) — a model of the network and devices, not a measurement of them.

Why it's worth doing

What a faster Squarespace site is worth

SEO Rank ↑ out of the “Poor” band

Search sees a faster page

Core Web Vitals have been a confirmed Google ranking signal since 2021. The biggest win is leaving the "Poor" band, where faster competitors get preferred.

— Google Search Central
Conversion +7% per 100 ms you cut

More visitors finish what they started

Conversion tracks load time closely — on Akamai’s retail numbers a delay of just 100 ms cost 7% of conversions. Shaving seconds is the cheapest funnel work available.

— Akamai / SOASTA, 2017
Bounce ≈ ½ cutting a 2 s delay

Fewer people leave before it loads

Close a two-second gap and bounce rate roughly halves — Akamai measured those same two seconds raising it by 103%. A page that paints early keeps the visit a slow one loses outright.

— Akamai / SOASTA, 2017
CO₂ ≈ 0.15 g saved per MB you cut

Lighter pages, less energy

Transfer weight maps to emissions at roughly 0.15 g of CO₂ per MB. Cutting bytes is the one optimization that shows up on a sustainability report.

— Sustainable Web Design v4

Each figure links to the page that publishes it. The studies measure what delay costs; read here as what speed returns. Industry benchmarks, not a guarantee for a specific site — the per-site numbers are the audits above, and yours is a free check away.

Two defects on most Squarespace sites we audited

The platform’s own help pages offer the usual list: compress your images, use fewer fonts, keep your pages short. It is not wrong, and it is also the only advice a Squarespace owner can act on, because everything else is out of reach.

So we went and measured 1,032 of them (as of October 2026). Two findings came back on most of them, and neither is reachable from the editor.

The CSS arrives as a pile of small files. On 80% of the sites we audited. Squarespace splits its stylesheets into many small requests, and the browser has to work through the queue before it can finish the first paint. No single file is heavy; the number of round-trips is the cost.

Scripts run while the page is still drawing. On 83%. The platform’s own runtime plus the blocks you added ship as inline scripts that execute mid-render, and each one that runs is a pause in the drawing of the page.

Underneath those two sit the familiar rest: images without dimensions, so the layout shifts as they land (our highest-volume correction on this platform); resource hints pointing at origins the page never uses; the first-screen image fetched at the same priority as everything else.

The image advice also aims at the smaller half of the page. On the 155 Squarespace homepages whose network log we read, the platform’s own JavaScript came to a median of about 1 MB compressed, 83% of all the JavaScript on the page, and it outweighed every image combined on 88 of them. That part is not yours to trim.

How to speed up a Squarespace website from the editor

Some of the page is yours, and it is worth trimming first, because nothing else will touch it:

  • Third-party code you added. Everything in Code Injection and every embed block (chat, booking, reviews, pixels) loads on top of the platform’s scripts. Remove the ones nobody uses, and keep the rest off the pages that do not need them.
  • The first screen. A video background or an auto-playing gallery at the top is the heaviest thing a template lets you put there, and it competes with everything else for the first paint. A still image arrives sooner.
  • Fonts. Each family and each weight is a separate file. Two families in two weights cover most designs.
  • Images. Squarespace already resizes what you upload and serves smaller versions to phones, so the gain here is smaller than most guides suggest.

What the editor does not reach is the larger part. On those 155 homepages the platform’s own scripts were 83% of the JavaScript, and the split CSS and the mid-render scripts above come from the same place. Trimming your own additions takes weight off the top; the platform’s share is what the next section is about.

Why you can’t fix it from inside the editor

Squarespace is among the most closed platforms we audit, and that is usually described as a gap in what support can change. It is really a limit on operations.

Speeding up a page is mostly deferring, reordering and dropping things the platform already emits — and every one of those verbs needs access to the markup. On Squarespace you cannot defer a script the runtime injected, combine stylesheets the platform split, or remove a connection hint you did not write. So the honest Squarespace speed guide ends where they all do: keep your pages light, and wait for the platform.

A reverse proxy moves where the work happens. Your Squarespace site keeps serving the page it always did; WebSpeed receives that page, rewrites its critical path, and hands the result to the visitor. Nothing inside Squarespace changes, so there is nothing for a platform update to undo and nothing for your team to relearn.

One honest caveat: Adobe Fonts

Most of what we do is invisible — the page looks the same and loads faster. There is a single exception worth stating up front, because it is specific to Squarespace and to how proxies work.

Squarespace offers typography through Adobe Fonts, and an Adobe Fonts kit is licensed to a named list of domains. The kit checks, in the browser, whether the current domain is on that list — and served through a different host it isn’t, so the fonts don’t load. The fix is yours and it takes two minutes: add the serving host to your kit’s published-domains list in your Adobe Fonts account, and we tell you exactly what to add. Fonts you host on Squarespace itself, or pull from Google Fonts, are unaffected. And if you would rather not touch the kit, the on-site integration keeps your original domain and the question never comes up.

We would rather you read that here than meet it in your own audit.

What you get from the audit

It needs nothing but the URL:

  1. Your score, both devices — mobile and desktop, original vs the WebSpeed-served page.
  2. The individual metrics — LCP, CLS, TBT and the rest, side by side rather than rolled into one number.
  3. What actually changed — the itemised list of optimizations behind the result.
  4. A before/after video of your page loading, if the gain is big enough to see.

Squarespace speed — questions

Do I have to move my site off Squarespace?

No — that is the point. WebSpeed runs in front of your existing site. You keep the editor, the hosting and your workflow; only what the browser receives changes.

Will the Squarespace editor still work normally?

Yes. We never touch the site inside the platform. Your team keeps editing in Squarespace exactly as before, and every publish flows through unchanged.

Is the Squarespace admin or checkout affected?

No. Squarespace runs its admin on your own domain under /config/, and that path goes to Squarespace untouched, with nothing cached or rewritten. The same holds for /cart, /checkout/, /commerce/ and customer accounts under /account/. Any request carrying a session cookie still gets the optimized page, though never from the shared cache.

How does a multilingual Squarespace site work through it?

Each language on a Squarespace site usually gets its own address: a set of pages under a folder such as /fr/, or a subdomain, depending on how the translation is set up. Each address is optimized and cached separately. A language remembered only in a cookie sends the request past the shared cache, so nobody lands on a page in the wrong language.

I use Adobe Fonts (Typekit) through Squarespace. Does that keep working?

This is the one thing to know before you start, and we would rather say it plainly. Adobe Fonts are licensed to a specific list of domains and the kit checks the domain in the browser, so served through a different host they will not load until that host is added to your kit's published-domains list — a two-minute change you make in your Adobe Fonts account, and we tell you exactly what to add. Fonts you host on Squarespace itself, or use from Google Fonts, are unaffected. If you would rather not touch the kit at all, the on-site integration keeps your original domain and sidesteps this entirely.

Why does the accelerated copy in my audit show a different font?

Because the audit serves that copy from our test domain, and your Adobe Fonts kit only loads on the domains listed in it. The browser falls back to the next font in your stack, so headings in the screenshots and the side-by-side video can look different from your site. It does not flatter the score. Of 153 Squarespace audits that passed our measurement checks in September 2026, 41 lost their Adobe Fonts this way, and they gained a median of 5 points, against 5.5 on sites that don't use Adobe Fonts at all. How to keep the fonts in a live setup is the question above.

Squarespace already looks fast and modern. What is left to gain?

Our measurements agree with them on the visual polish — the problem is not how the site looks, it is what the browser has to do before it can show it. On most of the 1,032 sites we audited that was CSS split across many requests and scripts running during render. Those do not show up in the editor, and they are exactly what the audit measures.

Do I have to install anything?

No, and on Squarespace you largely could not: the usual route is the proxy, where traffic is routed through WebSpeed with a DNS change and nothing is installed anywhere.

Will it change how my site looks?

It should not — every optimization here is about when and in what order things load, not what they are. The one exception is Adobe Fonts, covered above. The audit shows you the before and after so you can check the result yourself before deciding anything.

Pricing

Pick how hands-off you want it

The before/after check is free to run; it isn’t one of these plans. Choose a plan when you’re ready to make the speed-up permanent — or buy the report once and apply it yourself.

Most popular
SaaS subscription

Fast

from €10 · /mo, billed yearly
Zero-code, automatic
14-day free trial
  • The whole optimization pipeline, live
  • One site
  • Proxy or on-site SDK, no code changes
  • Cached delivery keeps your site up during origin outages
  • Priced by monthly visits, scales with you
Request access
We connect it for you.
SaaS subscription

Growth

from €79 · /mo
For several sites at once
14-day free trial
  • Everything in Fast, across multiple sites
  • Priority cache — your pages stay warm
  • Support with a named contact
  • One invoice for the whole portfolio
Request access
Agencies and multi-site owners.
SaaS + hands-on service

Custom

from €179 · /mo
Hand-tuned for your site
  • Everything in Growth
  • A config built by hand for your site
  • What only you can change, written up for your team
  • Set up, measured and maintained by us
Get a plan for my site
We look at your site by hand first, then keep it tuned. Six months minimum.

Subscriptions start with a 14-day free trial (Fast and Growth). After it, Fast is billed yearly, and Growth and Custom run for a minimum of 6 months — you commit only after the trial. Fast is priced by monthly visits; indicative launch pricing.

Downloadable report

Not ready for a subscription?

Buy the Audit once and apply it yourself — the same findings the pipeline acts on, written up as instructions.

  • One site, up to 5 pages you choose
  • Fast’s changes to your page code, written up as a guide you run yourself
  • Server settings, code changes and ready-to-paste head snippets
  • Before/after PageSpeed from the free check (PDF / HTML / MD)
  • Re-issued free for a year as your site changes
€149 · one-time
DIY: you apply it
Get the audit See an example report →
Not useful? Email us within 14 days and we refund it. A document, not a service — you apply it; Custom is the same work done for you.

See your own before / after

Paste your URL for a free PageSpeed comparison on mobile and desktop. No signup, about a minute.

No signup. See your before/after PageSpeed score in about a minute. What the report shows

Other platforms: WordPress Duda WooCommerce Divi Wix Tilda Bitrix