Tools & Wizards About Us
totalutilities.co.nz screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

totalutilities.co.nz

Home - Total Utilities

Page Load Speed

6.8 sec in total

First Response

455 ms

Resources Loaded

5.7 sec

Page Rendered

683 ms

totalutilities.co.nz screenshot

About Website

Visit totalutilities.co.nz now to see the best up-to-date Total Utilities content and also check out these interesting facts you probably never knew about totalutilities.co.nz

Visit totalutilities.co.nz

Key Findings

We analyzed Totalutilities.co.nz page load time and found that the first response time was 455 ms and then it took 6.4 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

totalutilities.co.nz performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value2,370 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.088

93/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

totalutilities.co.nz

455 ms

totalutilities.co.nz

1086 ms

js

66 ms

column-numbers.min.css

909 ms

column-stacking.min.css

674 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 78% of them (45 requests) were addressed to the original Totalutilities.co.nz, 16% (9 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Totalutilities.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 232.7 kB (17%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Totalutilities.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. 50% of websites need less resources to load. Images take 893.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 228.5 kB

  • Original 272.1 kB
  • After minification 267.5 kB
  • After compression 43.7 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 228.5 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 2.8 kB

  • Original 893.2 kB
  • After minification 890.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. Total Utilities images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.4 kB

  • Original 200.5 kB
  • After minification 200.5 kB
  • After compression 199.1 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 40 (87%)

Requests Now

46

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

totalutilities.co.nz

totalutilities.co.nz

455 ms

totalutilities.co.nz

totalutilities.co.nz

1086 ms

js

js

66 ms

column-numbers.min.css

column-numbers.min.css

909 ms

column-stacking.min.css

column-stacking.min.css

674 ms

divi-blog-module.min.css

divi-blog-module.min.css

683 ms

divi-portfolio-module.min.css

divi-portfolio-module.min.css

675 ms

divi-gallery-module.min.css

divi-gallery-module.min.css

687 ms

pagenavi-css.css

pagenavi-css.css

1085 ms

ivory-search.min.css

ivory-search.min.css

1332 ms

css

css

33 ms

style.min.css

style.min.css

1144 ms

choices.min.css

choices.min.css

1125 ms

style.css

style.css

490 ms

frontend-gtag.min.js

frontend-gtag.min.js

498 ms

jquery.min.js

jquery.min.js

512 ms

jquery-migrate.min.js

jquery-migrate.min.js

522 ms

et-core-unified-2.min.css

et-core-unified-2.min.css

533 ms

email-decode.min.js

email-decode.min.js

333 ms

basic.min.css

basic.min.css

342 ms

theme-ie11.min.css

theme-ie11.min.css

1068 ms

theme.min.css

theme.min.css

1400 ms

widow-fixer.min.js

widow-fixer.min.js

1362 ms

scripts.min.js

scripts.min.js

1577 ms

smoothscroll.js

smoothscroll.js

1568 ms

frontend-bundle.min.js

frontend-bundle.min.js

1840 ms

common.js

common.js

1712 ms

ivory-search.min.js

ivory-search.min.js

1994 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

2048 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

2212 ms

wp-polyfill.min.js

wp-polyfill.min.js

2225 ms

dom-ready.min.js

dom-ready.min.js

1724 ms

hooks.min.js

hooks.min.js

2374 ms

i18n.min.js

i18n.min.js

2066 ms

a11y.min.js

a11y.min.js

2638 ms

jquery.json.min.js

jquery.json.min.js

2704 ms

gravityforms.min.js

gravityforms.min.js

2726 ms

api.js

api.js

32 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

2860 ms

utils.min.js

utils.min.js

2878 ms

vendor-theme.min.js

vendor-theme.min.js

2124 ms

scripts-theme.min.js

scripts-theme.min.js

2131 ms

akismet-frontend.js

akismet-frontend.js

2133 ms

white-total-utilities-logo.png

white-total-utilities-logo.png

1397 ms

AdobeStock_619509578-1-scaled.jpeg

AdobeStock_619509578-1-scaled.jpeg

2868 ms

Toitu-website-mockup.png

Toitu-website-mockup.png

3104 ms

christian-bisbo-johnsen-TnzAK9Hhe8E-unsplash.jpg

christian-bisbo-johnsen-TnzAK9Hhe8E-unsplash.jpg

2392 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

46 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf

47 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf

225 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf

255 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf

225 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf

255 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf

256 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf

256 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf

254 ms

modules.woff

modules.woff

2302 ms

recaptcha__en.js

recaptcha__en.js

42 ms

Accessibility Review

totalutilities.co.nz accessibility score

85

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

High

Some elements have a [tabindex] value greater than 0

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

totalutilities.co.nz SEO score

85

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

totalutilities.co.nz

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