Core Web Vitals for Squarespace

What real Squarespace sites measure

We measured Squarespace’s own homepage and Franklin Barbecue — the Austin restaurant, a real production Squarespace site — with Lighthouse 13, mobile emulation, in July 2026. squarespace.com scored 27/100 with lab LCP at 19.7 s and TBT of 2,417 ms: a heavily animated, video-forward marketing page that illustrates the ceiling problem vividly. franklinbarbecue.com scored 35/100 with LCP at 11.9 s, TBT 1,205 ms, and CLS 0.01. Two readings matter. First, layout shift is near zero on both — the platform renders stably, and CLS is rarely a Squarespace problem. Second, both LCPs are dominated by full-bleed hero media arriving late. On a closed platform where you cannot touch the delivery pipeline, the hero you choose is your performance budget — every fix in this guide is downstream of that observation.

Know what you control on 7.1

On Squarespace 7.1 there is no theme marketplace, no plugin system, and no server access — every site runs Squarespace’s own frontend runtime on Squarespace’s CDN. You cannot reduce the platform bundle, and lab findings pointing at Squarespace’s core scripts are not actionable. Accept that baseline and focus on the deltas you own: how many sections a page stacks, what media sits in them, which fonts load, whether animations run, and what third-party code you inject.

This matters for expectations too. A content-disciplined Squarespace site lands in the same performance band as disciplined sites on any builder, but the ceiling is lower than a hand-tuned custom build — if your business case demands 95+ mobile scores, you are on the wrong platform. If it demands “passing Core Web Vitals with a site an owner can edit,” Squarespace gets there.

Images and galleries: let the loader work

Squarespace’s image loader is genuinely good: it generates multiple sizes of every upload and serves the smallest variant that fits the container, lazy-loading as it goes. Feed it well — upload images around 2500px on the long edge (Squarespace’s own guidance), pre-compressed, and let the platform do the rest. Uploading 6000px originals slows processing and yields heavier variants; uploading 800px images forces upscaling on large screens.

Where owners get into trouble is banner sections: a full-bleed background banner per section, times ten sections, is a multi-megabyte page regardless of the loader’s cleverness. Use full-bleed imagery for the hero and one or two key moments, not as the default section background. Prefer gallery sections and summary blocks (which participate in lazy loading) over stacking dozens of individual image blocks, and keep autoplaying background video out of the first fold — it competes with the hero for bandwidth exactly when LCP is decided.

Fonts, animations, and section sprawl

Every font family and weight you pick in Site Styles is a network fetch before text settles. Squarespace makes it easy to accumulate four or five weights across headings, body, buttons, and navigation — consolidate to one family in two weights and you remove requests from the critical path of every page. Squarespace applies font-display handling for you, but fewer fonts is still the lever you own.

Site-wide animations (Site Styles → Animations) are the other global toggle: they translate and fade content into view as you scroll, which reads as polish on desktop and as delayed, shifting content on a mid-range phone. Setting animations to none — or at most the simplest fade — measurably improves perceived load and stability. Finally, resist the single-page-with-twenty-sections pattern: long index-style pages stack every section’s media and DOM into one load. Split content across pages; each page gets lighter, and you gain separately indexable URLs with focused titles.

Code Injection: the only place Squarespace lets you hurt yourself

Squarespace’s escape hatch — Settings → Advanced → Code Injection — is where most self-inflicted damage happens. Scripts in the Header slot load on every page of the site before content renders: analytics duplicated alongside built-in analytics, chat widgets, font kits, popup tools, and “Squarespace plugin” snippets from third-party vendors all accumulate there over the years. Audit the slot: move everything that can move to the Footer slot, add defer or async to what remains, and delete tools nobody has looked at in a year.

Third-party Squarespace plugins (custom-code vendors) deserve honest scrutiny — each is JavaScript running on every page, unvetted by Squarespace. Before adding one, ask whether a built-in block achieves 90% of it. Per-page injection (page settings → Advanced) is always better than site-wide when the tool only serves one page.

Measuring Squarespace correctly

Test the live public site — password-protected trial sites can’t be reached by lab tools, and the editor preview carries editing scaffolding that misrepresents real load. Measure your homepage plus one blog post and one shop page if you sell: commerce pages carry additional platform JavaScript, and blog templates behave differently from index pages.

Because the platform layer is fixed, before/after testing is unusually clean on Squarespace: change one thing — animations off, a lighter hero, one fewer font weight, a purged Code Injection slot — re-run the test, and the delta is attributable to your change. Iterate through the levers in this guide in that order, and remember Google’s field data (the Core Web Vitals that affect ranking) trails your fixes by up to 28 days.