Tools & Wizards About Us
hnry.co.nz screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

hnry.co.nz

Hnry | Tax for sole traders - Never Think About Tax Again®

Page Load Speed

2.7 sec in total

First Response

154 ms

Resources Loaded

1.7 sec

Page Rendered

863 ms

hnry.co.nz screenshot

About Website

Welcome to hnry.co.nz homepage info - get ready to check Hnry best content for New Zealand right away, or after learning these important things about hnry.co.nz

Hnry automatically pays and files all taxes for contractors, freelancers, and sole traders, so they never have to think about tax again.

Visit hnry.co.nz

Key Findings

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

Performance Metrics

hnry.co.nz performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value3,140 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

hnry.co.nz

154 ms

hnry.co.nz

348 ms

uk-redirect.js

67 ms

100412253-100412715.js

162 ms

glide.min.js

63 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 61% of them (37 requests) were addressed to the original Hnry.co.nz, 8% (5 requests) were made to Youtube.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (594 ms) belongs to the original domain Hnry.co.nz.

Page Optimization Overview & Recommendations

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

Content Size

447.6 kB

After Optimization

370.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Hnry.co.nz main page is 447.6 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. 65% of websites need less resources to load. Javascripts take 270.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 74.7 kB

  • Original 94.4 kB
  • After minification 81.9 kB
  • After compression 19.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. This page needs HTML code to be minified as it can gain 12.5 kB, which is 13% 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 74.7 kB or 79% of the original size.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 270.1 kB
  • After minification 270.1 kB
  • After compression 267.3 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.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 83.1 kB
  • After minification 83.1 kB
  • After compression 83.1 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. Hnry.co.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (61%)

Requests Now

54

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hnry.co.nz

hnry.co.nz

154 ms

hnry.co.nz

hnry.co.nz

348 ms

uk-redirect.js

uk-redirect.js

67 ms

100412253-100412715.js

100412253-100412715.js

162 ms

glide.min.js

glide.min.js

63 ms

css

css

75 ms

css

css

93 ms

all.css

all.css

83 ms

stylesheet.css

stylesheet.css

200 ms

slick.min.css

slick.min.css

248 ms

accessible-slick-theme.min.css

accessible-slick-theme.min.css

258 ms

glide.core.min.css

glide.core.min.css

84 ms

youtube-lazy.css

youtube-lazy.css

255 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

411 ms

popper.min.js

popper.min.js

261 ms

bootstrap.min.js

bootstrap.min.js

265 ms

mdb.min.js

mdb.min.js

495 ms

jquery.bcSwipe.min.js

jquery.bcSwipe.min.js

425 ms

smooth-scroll.js

smooth-scroll.js

425 ms

slick.min.js

slick.min.js

425 ms

skipto.min.js

skipto.min.js

408 ms

site.js

site.js

456 ms

consent.js

consent.js

453 ms

pass-uuid-to-app.js

pass-uuid-to-app.js

455 ms

collapsible.js

collapsible.js

454 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

42 ms

platform.js

platform.js

49 ms

campaign-tracking.js

campaign-tracking.js

437 ms

lazysizes.min.js

lazysizes.min.js

561 ms

hnry.js

hnry.js

82 ms

gtm.js

gtm.js

155 ms

hnry-logo.svg

hnry-logo.svg

234 ms

hero-carousel-slide-1.webp

hero-carousel-slide-1.webp

594 ms

hero-carousel-slide-3.webp

hero-carousel-slide-3.webp

589 ms

hero-carousel-slide-4.webp

hero-carousel-slide-4.webp

264 ms

ios-app-store.svg

ios-app-store.svg

236 ms

app-badge-android.webp

app-badge-android.webp

238 ms

quote-left-solid.svg

quote-left-solid.svg

241 ms

Tax.webp

Tax.webp

293 ms

Support.webp

Support.webp

295 ms

Expenses.webp

Expenses.webp

587 ms

Invoices.webp

Invoices.webp

588 ms

Allocations.webp

Allocations.webp

589 ms

Payments.webp

Payments.webp

589 ms

hnry-logo-footer.svg

hnry-logo-footer.svg

590 ms

l4tx07Dnmro

l4tx07Dnmro

203 ms

border-wavy-footer.svg

border-wavy-footer.svg

552 ms

2sDfZG1Wl4LcnbuKjk0j.ttf

2sDfZG1Wl4LcnbuKjk0j.ttf

58 ms

2sDcZG1Wl4LcnbuCJW8zaGW8.ttf

2sDcZG1Wl4LcnbuCJW8zaGW8.ttf

65 ms

fa-brands-400.ttf

fa-brands-400.ttf

31 ms

www-player.css

www-player.css

11 ms

www-embed-player.js

www-embed-player.js

37 ms

base.js

base.js

63 ms

ad_status.js

ad_status.js

187 ms

0eec19jyZJIq-Yrvpx_JX6MyT7H4xziZcfWMUzmhD74.js

0eec19jyZJIq-Yrvpx_JX6MyT7H4xziZcfWMUzmhD74.js

122 ms

embed.js

embed.js

42 ms

id

id

41 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

31 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

39 ms

My-Account.webp

My-Account.webp

117 ms

Create

Create

109 ms

Accessibility Review

hnry.co.nz accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

Best Practices

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

hnry.co.nz SEO score

90

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

hnry.co.nz

Open Graph data is detected on the main page of Hnry. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: