Tools & Wizards About Us
help.orcon.net.nz screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

help.orcon.net.nz

Orcon

Page Load Speed

7.6 sec in total

First Response

1.6 sec

Resources Loaded

5.8 sec

Page Rendered

243 ms

help.orcon.net.nz screenshot

About Website

Visit help.orcon.net.nz now to see the best up-to-date Help Orcon content for New Zealand and also check out these interesting facts you probably never knew about help.orcon.net.nz

Visit help.orcon.net.nz

Key Findings

We analyzed Help.orcon.net.nz page load time and found that the first response time was 1.6 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

help.orcon.net.nz performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

help.orcon.net.nz

1590 ms

all.css

2158 ms

support-style.css

1213 ms

modernizr.custom.js

1027 ms

jquery.min.js

51 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Help.orcon.net.nz, 52% (17 requests) were made to Orcon.net.nz and 21% (7 requests) were made to My.nanorep.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Orcon.net.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 351.4 kB (45%)

Content Size

777.2 kB

After Optimization

425.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Help.orcon.net.nz main page is 777.2 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. 60% of websites need less resources to load. Images take 320.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 20.0 kB

  • Original 25.3 kB
  • After minification 18.1 kB
  • After compression 5.2 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. This page needs HTML code to be minified as it can gain 7.2 kB, which is 28% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 20.0 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 814 B

  • Original 320.1 kB
  • After minification 319.3 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. Help Orcon images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 122.3 kB

  • Original 187.3 kB
  • After minification 154.8 kB
  • After compression 65.0 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 122.3 kB or 65% of the original size.

CSS Optimization

-85%

Potential reduce by 208.2 kB

  • Original 244.5 kB
  • After minification 201.7 kB
  • After compression 36.3 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. Help.orcon.net.nz needs all CSS files to be minified and compressed as it can save up to 208.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (35%)

Requests Now

26

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

help.orcon.net.nz

help.orcon.net.nz

1590 ms

all.css

all.css

2158 ms

support-style.css

support-style.css

1213 ms

modernizr.custom.js

modernizr.custom.js

1027 ms

jquery.min.js

jquery.min.js

51 ms

js

js

76 ms

jquery.main.js

jquery.main.js

2047 ms

footer-logo.svg

footer-logo.svg

209 ms

embed.js

embed.js

161 ms

bg-phone.jpg

bg-phone.jpg

254 ms

ico-message.svg

ico-message.svg

251 ms

ico-network.svg

ico-network.svg

249 ms

facebook.svg

facebook.svg

363 ms

twitter.svg

twitter.svg

385 ms

youtube.svg

youtube.svg

396 ms

DINWeb.woff

DINWeb.woff

396 ms

DINWeb-Black.woff

DINWeb-Black.woff

557 ms

DINWeb-Bold.woff

DINWeb-Bold.woff

997 ms

DINWeb-Medium.woff

DINWeb-Medium.woff

577 ms

logo.png

logo.png

500 ms

img-05.jpg

img-05.jpg

1682 ms

trackSupportCenter.gif

trackSupportCenter.gif

54 ms

nrLogo.png

nrLogo.png

53 ms

cnf.js

cnf.js

13 ms

widget.html

widget.html

66 ms

css

css

62 ms

livePersonV3.js

livePersonV3.js

16 ms

faq-widgetui.js

faq-widgetui.js

22 ms

baseURI.lpCsds

baseURI.lpCsds

146 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

35 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

32 ms

lpCheckRepState.js

lpCheckRepState.js

112 ms

repoffline.gif

repoffline.gif

23 ms

Accessibility Review

help.orcon.net.nz accessibility score

95

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

help.orcon.net.nz best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Uses deprecated APIs

SEO Factors

help.orcon.net.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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Help.orcon.net.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Help.orcon.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

help.orcon.net.nz

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