Tools & Wizards About Us
180.co.nz screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

180.co.nz

Queen Charlotte Sounds Homes & Real Estate For Sale | Trade Me Property

Page Load Speed

3.1 sec in total

First Response

355 ms

Resources Loaded

2.7 sec

Page Rendered

55 ms

180.co.nz screenshot

About Website

Click here to check amazing 180 content for New Zealand. Otherwise, check out these important facts you probably never knew about 180.co.nz

Trade Me has 7 Queen Charlotte Sounds Homes & Real Estate For Sale. View photos, use our mortgage calculator and see local schools to help you find your perfect...

Visit 180.co.nz

Key Findings

We analyzed 180.co.nz page load time and found that the first response time was 355 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

180.co.nz performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value6,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value23.2 s

1/100

10%

Network Requests Diagram

3869475321

355 ms

unsupported-device

544 ms

csp-report-uri

7 ms

csp-report-uri

372 ms

trademe-logo-no-tagline.png

5 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that all of those requests were addressed to 180.co.nz and no external sources were called. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Trademe.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 49.7 kB (65%)

Content Size

76.0 kB

After Optimization

26.4 kB

  • HTML
  • Images

In fact, the total size of 180.co.nz main page is 76.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. 15% of websites need less resources to load. HTML takes 74.1 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 49.7 kB

  • Original 74.1 kB
  • After minification 73.0 kB
  • After compression 24.4 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 49.7 kB or 67% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.9 kB
  • After minification 1.9 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. 180 images are well optimized though.

Requests Breakdown

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

Requests Now

6

After Optimization

2

  • Images
  • JavaScript

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 180. 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

3869475321

3869475321

355 ms

unsupported-device

unsupported-device

544 ms

csp-report-uri

csp-report-uri

7 ms

csp-report-uri

csp-report-uri

372 ms

trademe-logo-no-tagline.png

trademe-logo-no-tagline.png

5 ms

raven.472e031e4c2f2a0e.min.js

raven.472e031e4c2f2a0e.min.js

7 ms

runtime.6797835068b4c755.js

runtime.6797835068b4c755.js

238 ms

polyfills.2825d80609ea0ce6.js

polyfills.2825d80609ea0ce6.js

11 ms

vendor.c422a0c9e40c7e34.js

vendor.c422a0c9e40c7e34.js

1257 ms

main.36bd863fe9929bd1.js

main.36bd863fe9929bd1.js

641 ms

StorySansWeb-Regular.woff

StorySansWeb-Regular.woff

7 ms

Accessibility Review

180.co.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.

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

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

180.co.nz SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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 180.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 180.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

180.co.nz

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