Tools & Wizards About Us
nhe.nz screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

nhe.nz

Steel Fabricators Auckland | Engineering & Architectural Metalwork

Page Load Speed

8.4 sec in total

First Response

31 ms

Resources Loaded

7.7 sec

Page Rendered

650 ms

nhe.nz screenshot

About Website

Welcome to nhe.nz homepage info - get ready to check Nhe best content right away, or after learning these important things about nhe.nz

We specialise in providing solutions for difficult & complex steel, sheet metal & bespoke metalwork. High-quality architectural metal fabrication & welding.

Visit nhe.nz

Key Findings

We analyzed Nhe.nz page load time and found that the first response time was 31 ms and then it took 8.3 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

nhe.nz performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

nhe.nz

31 ms

nhe.nz

925 ms

style.min.css

886 ms

pagenavi-css.css

660 ms

frontend.css

655 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 92% of them (58 requests) were addressed to the original Nhe.nz, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Nhe.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.3 kB (2%)

Content Size

3.6 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Nhe.nz main page is 3.6 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. 35% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 78.8 kB

  • Original 97.2 kB
  • After minification 93.4 kB
  • After compression 18.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 78.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 448 B

  • Original 3.3 MB
  • After minification 3.3 MB

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. Nhe images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 221.0 kB
  • After minification 221.0 kB
  • After compression 219.9 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 39 (64%)

Requests Now

61

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nhe.nz

nhe.nz

31 ms

nhe.nz

nhe.nz

925 ms

style.min.css

style.min.css

886 ms

pagenavi-css.css

pagenavi-css.css

660 ms

frontend.css

frontend.css

655 ms

royalslider.css

royalslider.css

676 ms

rs-default-inverted.css

rs-default-inverted.css

671 ms

js_composer.min.css

js_composer.min.css

1097 ms

jquery.min.js

jquery.min.js

1514 ms

jquery-migrate.min.js

jquery-migrate.min.js

1321 ms

style.css

style.css

1527 ms

css

css

40 ms

formreset.min.css

formreset.min.css

1304 ms

formsmain.min.css

formsmain.min.css

1738 ms

readyclass.min.css

readyclass.min.css

1715 ms

browsers.min.css

browsers.min.css

1940 ms

email-decode.min.js

email-decode.min.js

1306 ms

dom-ready.min.js

dom-ready.min.js

1972 ms

hooks.min.js

hooks.min.js

2131 ms

i18n.min.js

i18n.min.js

2151 ms

a11y.min.js

a11y.min.js

2364 ms

jquery.json.min.js

jquery.json.min.js

2406 ms

gravityforms.min.js

gravityforms.min.js

2798 ms

conditional_logic.min.js

conditional_logic.min.js

2611 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

2787 ms

yith.infinitescroll.min.js

yith.infinitescroll.min.js

2799 ms

yith-infs.min.js

yith-infs.min.js

3017 ms

api.js

api.js

38 ms

js_composer_front.min.js

js_composer_front.min.js

3070 ms

utils.min.js

utils.min.js

3457 ms

vendor-theme.min.js

vendor-theme.min.js

3447 ms

scripts-theme.min.js

scripts-theme.min.js

3448 ms

frontend-legacy.min.js

frontend-legacy.min.js

3466 ms

jquery.royalslider.min.js

jquery.royalslider.min.js

3889 ms

lazyload.min.js

lazyload.min.js

3086 ms

enquire.min.js

enquire.min.js

3770 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

4089 ms

fixto.min.js

fixto.min.js

4102 ms

headroom.min.js

headroom.min.js

4109 ms

jQuery.headroom.min.js

jQuery.headroom.min.js

4114 ms

custom.js

custom.js

3805 ms

gtm.js

gtm.js

122 ms

sprite@1x.png

sprite@1x.png

2386 ms

north-harbour-engineering-logo.svg

north-harbour-engineering-logo.svg

2397 ms

stairs-railing-1.jpg

stairs-railing-1.jpg

2415 ms

bar-front.jpg

bar-front.jpg

3948 ms

steel-structure.jpg

steel-structure.jpg

2589 ms

20200620_101843-scaled.jpg

20200620_101843-scaled.jpg

2603 ms

bg-01.jpg

bg-01.jpg

2595 ms

footer-contact-bg.jpg

footer-contact-bg.jpg

2605 ms

font

font

22 ms

recaptcha__en.js

recaptcha__en.js

34 ms

commercial-engineering.jpg

commercial-engineering.jpg

1031 ms

residential-fabrication.jpg

residential-fabrication.jpg

1039 ms

architectural-metalwork.jpg

architectural-metalwork.jpg

1044 ms

steel-frame-1.jpg

steel-frame-1.jpg

2345 ms

aluminium-mesh-screens.jpg

aluminium-mesh-screens.jpg

2516 ms

steel-sheet.jpg

steel-sheet.jpg

2327 ms

stair-stringer.jpg

stair-stringer.jpg

2134 ms

steel-umbrella.jpg

steel-umbrella.jpg

2403 ms

steel-bar-front.jpg

steel-bar-front.jpg

3629 ms

steel-umbrella.png

steel-umbrella.png

3201 ms

hera-scnz-logo.jpg

hera-scnz-logo.jpg

2988 ms

Accessibility Review

nhe.nz accessibility score

94

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

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

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

nhe.nz SEO score

91

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

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

nhe.nz

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