Tools & Wizards About Us
squarespace.net screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

squarespace.net

Website Builder — Create a Website in Minutes — Squarespace

Page Load Speed

8.5 sec in total

First Response

120 ms

Resources Loaded

5.4 sec

Page Rendered

3 sec

squarespace.net screenshot

About Website

Welcome to squarespace.net homepage info - get ready to check Squarespace best content for United States right away, or after learning these important things about squarespace.net

Create a customizable website or online store with an all-in-one solution from Squarespace. Choose a website template and start your free trial today.

Visit squarespace.net

Key Findings

We analyzed Squarespace.net page load time and found that the first response time was 120 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

squarespace.net performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value3,520 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.6 s

1/100

10%

Network Requests Diagram

www.squarespace.com

120 ms

gtm.js

502 ms

legacy.js

214 ms

modern.js

309 ms

extract-css-runtime-a0975b2877696a05bec35-min.en-US.js

507 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Squarespace.net, 28% (25 requests) were made to Media-www.sqspcdn.com and 7% (6 requests) were made to Squarespace.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Events.squarespace.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.9 kB (4%)

Content Size

6.5 MB

After Optimization

6.3 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Squarespace.net main page is 6.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Images take 6.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 260.5 kB

  • Original 326.1 kB
  • After minification 300.6 kB
  • After compression 65.6 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 260.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 6.1 MB
  • After minification 6.1 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Squarespace images are well optimized though.

CSS Optimization

-1%

Potential reduce by 379 B

  • Original 65.0 kB
  • After minification 65.0 kB
  • After compression 64.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Squarespace.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 52 (62%)

Requests Now

84

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Squarespace. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.squarespace.com

www.squarespace.com

120 ms

gtm.js

gtm.js

502 ms

legacy.js

legacy.js

214 ms

modern.js

modern.js

309 ms

extract-css-runtime-a0975b2877696a05bec35-min.en-US.js

extract-css-runtime-a0975b2877696a05bec35-min.en-US.js

507 ms

extract-css-moment-js-vendor-98bddc81dc37f44faa7b2-min.en-US.js

extract-css-moment-js-vendor-98bddc81dc37f44faa7b2-min.en-US.js

630 ms

user-account-core-ab28618419610d0b6b57f-min.en-US.js

user-account-core-ab28618419610d0b6b57f-min.en-US.js

541 ms

user-account-core-68c2f27a2a82c80680342-min.en-US.css

user-account-core-68c2f27a2a82c80680342-min.en-US.css

506 ms

polyfills.js

polyfills.js

193 ms

globals.css

globals.css

177 ms

navigation.css

navigation.css

233 ms

homepage-jun-2022.css

homepage-jun-2022.css

186 ms

hero.css

hero.css

186 ms

link.css

link.css

190 ms

link.js

link.js

228 ms

hero.js

hero.js

203 ms

steps.css

steps.css

202 ms

steps.js

steps.js

229 ms

create-website.css

create-website.css

226 ms

create-website.js

create-website.js

478 ms

templates.css

templates.css

223 ms

templates.js

templates.js

477 ms

side-by-side-inline.css

side-by-side-inline.css

223 ms

images.css

images.css

219 ms

images.js

images.js

476 ms

feature-text.css

feature-text.css

223 ms

feature-text.js

feature-text.js

224 ms

side-by-side-inline.js

side-by-side-inline.js

225 ms

sell-anything.css

sell-anything.css

223 ms

image-skewed-mask.css

image-skewed-mask.css

226 ms

image-skewed-mask.js

image-skewed-mask.js

227 ms

sell-anything.js

sell-anything.js

474 ms

business.css

business.css

476 ms

business.js

business.js

461 ms

featured-blog-posts.css

featured-blog-posts.css

462 ms

featured-blog-posts.js

featured-blog-posts.js

503 ms

featured-customers-slideshow.css

featured-customers-slideshow.css

462 ms

featured-customers-slideshow.js

featured-customers-slideshow.js

501 ms

faq-feature-text.css

faq-feature-text.css

459 ms

faq-feature-text.js

faq-feature-text.js

465 ms

mobile-landing-stacked.css

mobile-landing-stacked.css

499 ms

mobile-carousel.css

mobile-carousel.css

464 ms

mobile-carousel.js

mobile-carousel.js

725 ms

mobile-landing-stacked.js

mobile-landing-stacked.js

724 ms

style-guide-grid.css

style-guide-grid.css

449 ms

trustarc.css

trustarc.css

434 ms

footer.css

footer.css

571 ms

i18n.css

i18n.css

571 ms

homepage-jun-2022.js

homepage-jun-2022.js

573 ms

style-guide-grid.js

style-guide-grid.js

555 ms

SQSPGlobal.js

SQSPGlobal.js

549 ms

performance.js

performance.js

537 ms

background-mobile-320.jpg

background-mobile-320.jpg

332 ms

site-scroll-mobile-v2.jpg

site-scroll-mobile-v2.jpg

366 ms

site-scroll-mobile.jpg

site-scroll-mobile.jpg

360 ms

background-v3-320.jpg

background-v3-320.jpg

358 ms

clarkson-500.woff

clarkson-500.woff

257 ms

clarkson-400.woff

clarkson-400.woff

258 ms

making-it-1500w.jpg

making-it-1500w.jpg

48 ms

punos-playground-1500w.jpg

punos-playground-1500w.jpg

29 ms

minaa-1500w.jpg

minaa-1500w.jpg

27 ms

altaloma-2-750w.jpg

altaloma-2-750w.jpg

240 ms

218 ms

me

me

188 ms

notice

notice

188 ms

emmeline-750w.jpg

emmeline-750w.jpg

61 ms

matsuya-2-750w.jpg

matsuya-2-750w.jpg

162 ms

idrah-750w.jpg

idrah-750w.jpg

59 ms

loam-750w.jpg

loam-750w.jpg

57 ms

growwell-750w.jpg

growwell-750w.jpg

58 ms

faded-750w.jpg

faded-750w.jpg

162 ms

accepted-currencies

accepted-currencies

360 ms

current

current

651 ms

offer-banner.css

offer-banner.css

81 ms

mine

mine

674 ms

Track

Track

741 ms

events

events

901 ms

events

events

1065 ms

settings

settings

509 ms

portrait-1500w.jpg

portrait-1500w.jpg

402 ms

yi-mei-portrait-1500w.jpg

yi-mei-portrait-1500w.jpg

475 ms

hero-portrait-1500w.jpg

hero-portrait-1500w.jpg

475 ms

hero-portrait-1500w.jpg

hero-portrait-1500w.jpg

637 ms

hero-portrait-1500w.jpg

hero-portrait-1500w.jpg

784 ms

hero-portrait-1500w.jpg

hero-portrait-1500w.jpg

786 ms

hero-portrait-1500w.jpg

hero-portrait-1500w.jpg

783 ms

hero-portrait-3-1500w.jpg

hero-portrait-3-1500w.jpg

785 ms

craig-portrait-1500w.jpg

craig-portrait-1500w.jpg

785 ms

offer-banner.js

offer-banner.js

208 ms

Accessibility Review

squarespace.net accessibility score

83

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

squarespace.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

squarespace.net SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Squarespace.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Squarespace.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

squarespace.net

Open Graph data is detected on the main page of Squarespace. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: