Tools & Wizards About Us
petersmith.net.nz screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

petersmith.net.nz

PeterSmith.net.nz: anchors & anchoring, photos from Patagonia & Antarctica

Page Load Speed

2.1 sec in total

First Response

186 ms

Resources Loaded

1.5 sec

Page Rendered

442 ms

petersmith.net.nz screenshot

About Website

Click here to check amazing Peter Smith content. Otherwise, check out these important facts you probably never knew about petersmith.net.nz

Peter Smith: boat builder, long distance cruising sailor, and Rocna anchors designer. Articles about anchoring; Peter’s yacht; and photo journals from Patagonia, Antarctica, and more…

Visit petersmith.net.nz

Key Findings

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

Performance Metrics

petersmith.net.nz performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.508

16/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

petersmith.net.nz

186 ms

petersmith.net.nz

253 ms

www.petersmith.net.nz

314 ms

style.221220.css

71 ms

js

78 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 66% of them (27 requests) were addressed to the original Petersmith.net.nz, 15% (6 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (531 ms) belongs to the original domain Petersmith.net.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 166.2 kB (18%)

Content Size

909.0 kB

After Optimization

742.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Petersmith.net.nz main page is 909.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 662.5 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 37.2 kB

  • Original 50.4 kB
  • After minification 49.4 kB
  • After compression 13.3 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 37.2 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 313 B

  • Original 662.5 kB
  • After minification 662.2 kB

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. Peter Smith images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 128.7 kB

  • Original 196.2 kB
  • After minification 191.7 kB
  • After compression 67.5 kB

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 128.7 kB or 66% of the original size.

Requests Breakdown

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

Requests Now

32

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

petersmith.net.nz

petersmith.net.nz

186 ms

petersmith.net.nz

petersmith.net.nz

253 ms

www.petersmith.net.nz

www.petersmith.net.nz

314 ms

style.221220.css

style.221220.css

71 ms

js

js

78 ms

mc-validate.js

mc-validate.js

60 ms

css2

css2

33 ms

analytics.js

analytics.js

122 ms

phpThumb.php

phpThumb.php

119 ms

sdk.js

sdk.js

139 ms

phpThumb.php

phpThumb.php

101 ms

phpThumb.php

phpThumb.php

171 ms

phpThumb.php

phpThumb.php

250 ms

phpThumb.php

phpThumb.php

238 ms

phpThumb.php

phpThumb.php

292 ms

bullet_rect.141005.gif

bullet_rect.141005.gif

230 ms

phpThumb.php

phpThumb.php

363 ms

phpThumb.php

phpThumb.php

245 ms

phpThumb.php

phpThumb.php

364 ms

phpThumb.php

phpThumb.php

382 ms

phpThumb.php

phpThumb.php

319 ms

phpThumb.php

phpThumb.php

440 ms

phpThumb.php

phpThumb.php

419 ms

phpThumb.php

phpThumb.php

388 ms

phpThumb.php

phpThumb.php

436 ms

phpThumb.php

phpThumb.php

495 ms

phpThumb.php

phpThumb.php

508 ms

phpThumb.php

phpThumb.php

459 ms

phpThumb.php

phpThumb.php

491 ms

phpThumb.php

phpThumb.php

508 ms

phpThumb.php

phpThumb.php

514 ms

phpThumb.php

phpThumb.php

531 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4nY1M2xYkS.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4nY1M2xYkS.ttf

51 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4nY1M2xYkS.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4nY1M2xYkS.ttf

59 ms

xfuu0WDhWW_fOEoY8l_VPNZfB7jPM6__Dmczd-YnOg0A.ttf

xfuu0WDhWW_fOEoY8l_VPNZfB7jPM6__Dmczd-YnOg0A.ttf

159 ms

xfuu0WDhWW_fOEoY8l_VPNZfB7jPM68YCWczd-YnOg0A.ttf

xfuu0WDhWW_fOEoY8l_VPNZfB7jPM68YCWczd-YnOg0A.ttf

130 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVcUwaEQXjM.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVcUwaEQXjM.ttf

109 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVcUwaEQXjM.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVcUwaEQXjM.ttf

107 ms

collect

collect

28 ms

sdk.js

sdk.js

7 ms

115 ms

Accessibility Review

petersmith.net.nz accessibility score

97

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

petersmith.net.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

SEO Factors

petersmith.net.nz SEO score

98

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

High

Tap targets are not sized appropriately

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 Petersmith.net.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 Petersmith.net.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

petersmith.net.nz

Open Graph description is not detected on the main page of Peter Smith. 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: