Tools & Wizards About Us
contact.co.nz screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

contact.co.nz

NZ Electricity, gas and broadband provider | Contact Energy

Page Load Speed

6.9 sec in total

First Response

987 ms

Resources Loaded

5.7 sec

Page Rendered

295 ms

contact.co.nz screenshot

About Website

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

Join one of NZ's leading providers of electricity, natural gas, broadband, solar & renewable energy. We put our energy where it matters.

Visit contact.co.nz

Key Findings

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

Performance Metrics

contact.co.nz performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value2,540 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

contact.co.nz

987 ms

residential

692 ms

gtm.js

1432 ms

VisitorIdentification.js

639 ms

site.min.css

2335 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 50% of them (10 requests) were addressed to the original Contact.co.nz, 25% (5 requests) were made to Fonts.gstatic.com and 10% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Contact.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 519.7 kB (36%)

Content Size

1.4 MB

After Optimization

919.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 226.0 kB

  • Original 254.1 kB
  • After minification 206.2 kB
  • After compression 28.0 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 47.8 kB, which is 19% 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 226.0 kB or 89% of the original size.

Image Optimization

-15%

Potential reduce by 83.4 kB

  • Original 555.3 kB
  • After minification 471.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. Obviously, Contact needs image optimization as it can save up to 83.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-34%

Potential reduce by 141.8 kB

  • Original 416.1 kB
  • After minification 416.1 kB
  • After compression 274.2 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 141.8 kB or 34% of the original size.

CSS Optimization

-32%

Potential reduce by 68.5 kB

  • Original 213.9 kB
  • After minification 213.9 kB
  • After compression 145.4 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. Contact.co.nz needs all CSS files to be minified and compressed as it can save up to 68.5 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (23%)

Requests Now

13

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

contact.co.nz

contact.co.nz

987 ms

residential

residential

692 ms

gtm.js

gtm.js

1432 ms

VisitorIdentification.js

VisitorIdentification.js

639 ms

site.min.css

site.min.css

2335 ms

embed.js

embed.js

18 ms

site.min.js

site.min.js

2214 ms

css

css

32 ms

css

css

47 ms

custom-logo.png

custom-logo.png

71 ms

cat-vpleft-d-960x353-v2.ashx

cat-vpleft-d-960x353-v2.ashx

370 ms

gift-a-night-vp-r-d-960x353-v1.ashx

gift-a-night-vp-r-d-960x353-v1.ashx

508 ms

nzc--ee-awards-2023-desktop-1400x415.ashx

nzc--ee-awards-2023-desktop-1400x415.ashx

880 ms

nzc--ee-awards-2023-mobile-500x409.ashx

nzc--ee-awards-2023-mobile-500x409.ashx

912 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

21 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

30 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

50 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

57 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

58 ms

hpb-mobile-grp-1920x488-v2.ashx

hpb-mobile-grp-1920x488-v2.ashx

526 ms

Accessibility Review

contact.co.nz accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

[id] attributes on active, focusable elements are not unique

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

contact.co.nz best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

contact.co.nz SEO score

79

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Contact.co.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 Contact.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

contact.co.nz

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