Tools & Wizards About Us
worldnet.co.nz screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

worldnet.co.nz

Worldnet Broadband

Page Load Speed

9.1 sec in total

First Response

1.3 sec

Resources Loaded

7.6 sec

Page Rendered

163 ms

worldnet.co.nz screenshot

About Website

Visit worldnet.co.nz now to see the best up-to-date Worldnet content for New Zealand and also check out these interesting facts you probably never knew about worldnet.co.nz

Get Broadband at unbelievably low price in NZ. Enjoy fast and reliable internet connection. Provide not only Broadband but also VoIP, Landline and Business Services. Sign Up Today.

Visit worldnet.co.nz

Key Findings

We analyzed Worldnet.co.nz page load time and found that the first response time was 1.3 sec and then it took 7.7 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

worldnet.co.nz performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value20.7 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value940 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.114

86/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

worldnet.co.nz

1341 ms

www.worldnet.co.nz

2051 ms

Cabin.css

406 ms

bootstrap.min.css

775 ms

style.css

590 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 65% of them (71 requests) were addressed to the original Worldnet.co.nz, 13% (14 requests) were made to Embed.tawk.to and 7% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Worldnet.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 643.9 kB (39%)

Content Size

1.7 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Worldnet.co.nz main page is 1.7 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. 70% of websites need less resources to load. Images take 642.9 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 221.8 kB

  • Original 239.4 kB
  • After minification 227.5 kB
  • After compression 17.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 221.8 kB or 93% of the original size.

Image Optimization

-10%

Potential reduce by 64.3 kB

  • Original 642.9 kB
  • After minification 578.7 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. Worldnet images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 327.8 kB

  • Original 614.2 kB
  • After minification 602.2 kB
  • After compression 286.4 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 327.8 kB or 53% of the original size.

CSS Optimization

-19%

Potential reduce by 30.1 kB

  • Original 158.7 kB
  • After minification 158.7 kB
  • After compression 128.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. Worldnet.co.nz needs all CSS files to be minified and compressed as it can save up to 30.1 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 83 (85%)

Requests Now

98

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

worldnet.co.nz

worldnet.co.nz

1341 ms

www.worldnet.co.nz

www.worldnet.co.nz

2051 ms

Cabin.css

Cabin.css

406 ms

bootstrap.min.css

bootstrap.min.css

775 ms

style.css

style.css

590 ms

shop.style.css

shop.style.css

598 ms

sss.css

sss.css

596 ms

line-icons.css

line-icons.css

608 ms

font-awesome.min.css

font-awesome.min.css

609 ms

jquery.fancybox.css

jquery.fancybox.css

786 ms

owl.carousel.css

owl.carousel.css

791 ms

settings.css

settings.css

793 ms

page_faq1.css

page_faq1.css

809 ms

pricing_v7.css

pricing_v7.css

812 ms

red.css

red.css

967 ms

custom.css

custom.css

1182 ms

business_6.css

business_6.css

988 ms

js

js

86 ms

js

js

140 ms

css

css

35 ms

css

css

53 ms

modernizr-custom.js

modernizr-custom.js

989 ms

jquery.min.js

jquery.min.js

1218 ms

jquery-migrate.min.js

jquery-migrate.min.js

816 ms

bootstrap.min.js

bootstrap.min.js

960 ms

sss.min.js

sss.min.js

991 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1382 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1427 ms

custom.js

custom.js

1153 ms

address.js

address.js

1179 ms

app.js

app.js

1184 ms

revolution-slider.js

revolution-slider.js

1345 ms

options.js

options.js

1375 ms

jquery.cookie.js

jquery.cookie.js

1380 ms

jquery.mask.min.js

jquery.mask.min.js

1417 ms

app.css

app.css

1152 ms

ie8.css

ie8.css

1183 ms

blocks.css

blocks.css

1194 ms

plugins.css

plugins.css

1192 ms

animate.css

animate.css

1234 ms

box-shadows.css

box-shadows.css

1241 ms

style-switcher.css

style-switcher.css

1343 ms

header-default.css

header-default.css

1378 ms

css

css

19 ms

header-v1.css

header-v1.css

1386 ms

header-v2.css

header-v2.css

1385 ms

header-v3.css

header-v3.css

1428 ms

header-v4.css

header-v4.css

1428 ms

footer-default.css

footer-default.css

1517 ms

footer-v1.css

footer-v1.css

1383 ms

footer-v2.css

footer-v2.css

1394 ms

footer-v3.css

footer-v3.css

1386 ms

footer-v4.css

footer-v4.css

1433 ms

footer-v5.css

footer-v5.css

1429 ms

footer-v6.css

footer-v6.css

1507 ms

footer-v7.css

footer-v7.css

1393 ms

app.css

app.css

1388 ms

shop.plugins.css

shop.plugins.css

1385 ms

shop.blocks.css

shop.blocks.css

1416 ms

nz.png

nz.png

238 ms

kr.png

kr.png

238 ms

cn.png

cn.png

238 ms

logo_worldnet.svg

logo_worldnet.svg

238 ms

Fibre_START_price_59.png

Fibre_START_price_59.png

237 ms

Hyperfibre2_price_109.png

Hyperfibre2_price_109.png

237 ms

footer_logo.svg

footer_logo.svg

408 ms

icon-facebook.png

icon-facebook.png

400 ms

icon-linkedin.png

icon-linkedin.png

406 ms

icon-instagram.png

icon-instagram.png

402 ms

icon-youtube.png

icon-youtube.png

401 ms

icon-twitter.png

icon-twitter.png

395 ms

fbevents.js

fbevents.js

142 ms

main_slide_bg_001_1920_500.png

main_slide_bg_001_1920_500.png

1091 ms

main_slide_bg_003_1920_500.png

main_slide_bg_003_1920_500.png

1112 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

88 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

89 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

113 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

125 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

125 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

126 ms

K6ngFdK5haaaRGBV8waDwA.ttf

K6ngFdK5haaaRGBV8waDwA.ttf

591 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

125 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

125 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

789 ms

sdk.js

sdk.js

4 ms

analytics.js

analytics.js

81 ms

default

default

312 ms

sdk.js

sdk.js

63 ms

arr.png

arr.png

316 ms

collect

collect

21 ms

35 ms

collect

collect

35 ms

js

js

59 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

725 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

103 ms

twk-event-polyfill.js

twk-event-polyfill.js

125 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

72 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

202 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

80 ms

twk-main.js

twk-main.js

141 ms

twk-vendor.js

twk-vendor.js

177 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

255 ms

twk-chunk-common.js

twk-chunk-common.js

268 ms

twk-runtime.js

twk-runtime.js

210 ms

twk-app.js

twk-app.js

230 ms

like.php

like.php

88 ms

6Zhf9tKLJ14.js

6Zhf9tKLJ14.js

21 ms

FEppCFCt76d.png

FEppCFCt76d.png

12 ms

widget-settings

widget-settings

96 ms

en.js

en.js

25 ms

Accessibility Review

worldnet.co.nz accessibility score

78

Accessibility Issues

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

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

worldnet.co.nz best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

worldnet.co.nz SEO score

92

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

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

worldnet.co.nz

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