Tools & Wizards About Us
sixtyproof.co.nz screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

sixtyproof.co.nz

Sixtyproof

Page Load Speed

1.4 sec in total

First Response

85 ms

Resources Loaded

604 ms

Page Rendered

732 ms

sixtyproof.co.nz screenshot

About Website

Click here to check amazing Sixtyproof content. Otherwise, check out these important facts you probably never knew about sixtyproof.co.nz

Visit sixtyproof.co.nz

Key Findings

We analyzed Sixtyproof.co.nz page load time and found that the first response time was 85 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

sixtyproof.co.nz performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.087

93/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

www.sixtyproof.co.nz

85 ms

css2

58 ms

legacy.js

46 ms

modern.js

54 ms

extract-css-runtime-1b5a843f6ab72c57699c-min.en-US.js

47 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Sixtyproof.co.nz, 58% (11 requests) were made to Assets.squarespace.com and 16% (3 requests) were made to Static1.squarespace.com. The less responsive or slowest element that took the longest time to load (347 ms) relates to the external source Images.squarespace-cdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 728.2 kB (14%)

Content Size

5.2 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sixtyproof.co.nz main page is 5.2 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. 40% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 144.5 kB

  • Original 170.3 kB
  • After minification 156.1 kB
  • After compression 25.7 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 144.5 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 10.5 kB

  • Original 3.4 MB
  • After minification 3.4 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. Sixtyproof images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 570.0 kB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 1.0 MB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 570.0 kB or 36% of the original size.

CSS Optimization

-16%

Potential reduce by 3.1 kB

  • Original 19.6 kB
  • After minification 19.6 kB
  • After compression 16.5 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. Sixtyproof.co.nz needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (72%)

Requests Now

18

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.sixtyproof.co.nz

www.sixtyproof.co.nz

85 ms

css2

css2

58 ms

legacy.js

legacy.js

46 ms

modern.js

modern.js

54 ms

extract-css-runtime-1b5a843f6ab72c57699c-min.en-US.js

extract-css-runtime-1b5a843f6ab72c57699c-min.en-US.js

47 ms

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

extract-css-moment-js-vendor-6c569122bfa66a51a056-min.en-US.js

147 ms

cldr-resource-pack-e85130cf44bc2d365b8b-min.en-US.js

cldr-resource-pack-e85130cf44bc2d365b8b-min.en-US.js

53 ms

common-vendors-stable-b03dd66b7c78e5e40bc7-min.en-US.js

common-vendors-stable-b03dd66b7c78e5e40bc7-min.en-US.js

150 ms

common-vendors-7598f4eb50a2ef12b555-min.en-US.js

common-vendors-7598f4eb50a2ef12b555-min.en-US.js

151 ms

common-e355b58b9255912494c5-min.en-US.js

common-e355b58b9255912494c5-min.en-US.js

152 ms

user-account-core-27a870eaae438480541c-min.en-US.js

user-account-core-27a870eaae438480541c-min.en-US.js

147 ms

user-account-core-b6e8cafbf34b05da5c2b-min.en-US.css

user-account-core-b6e8cafbf34b05da5c2b-min.en-US.css

57 ms

performance-eb022691e09e39c54c48-min.en-US.js

performance-eb022691e09e39c54c48-min.en-US.js

60 ms

site.css

site.css

64 ms

static.css

static.css

47 ms

site-bundle.5ba448b7aa80223d4688bd176bcb7afb.js

site-bundle.5ba448b7aa80223d4688bd176bcb7afb.js

52 ms

Secondary+Logo+%283%29.png

Secondary+Logo+%283%29.png

56 ms

sixtyproof_068.jpg

sixtyproof_068.jpg

291 ms

sixtyproof_019.jpg

sixtyproof_019.jpg

347 ms

Accessibility Review

sixtyproof.co.nz accessibility score

99

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

Best Practices

sixtyproof.co.nz best practices score

92

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

Page has valid source maps

SEO Factors

sixtyproof.co.nz SEO score

93

Search Engine Optimization Advices

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 Sixtyproof.co.nz 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 Sixtyproof.co.nz 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

sixtyproof.co.nz

Open Graph description is not detected on the main page of Sixtyproof. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: