Tools & Wizards About Us
hnry.io screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

hnry.io

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

Page Load Speed

4.2 sec in total

First Response

347 ms

Resources Loaded

3.2 sec

Page Rendered

633 ms

hnry.io screenshot

About Website

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

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

Visit hnry.io

Key Findings

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

Performance Metrics

hnry.io performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value4,090 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.108

88/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

hnry.co.nz

347 ms

css

45 ms

css

56 ms

all.css

178 ms

stylesheet.css

128 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hnry.io, 15% (11 requests) were made to Youtube.com and 6% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (441 ms) relates to the external source Hnry.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 71.0 kB (10%)

Content Size

708.4 kB

After Optimization

637.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hnry.io main page is 708.4 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. Javascripts take 319.3 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 62.7 kB

  • Original 82.2 kB
  • After minification 72.5 kB
  • After compression 19.5 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 9.7 kB, which is 12% 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 62.7 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 4.7 kB

  • Original 236.6 kB
  • After minification 231.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. Hnry images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.6 kB

  • Original 319.3 kB
  • After minification 319.3 kB
  • After compression 315.7 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 70.3 kB
  • After minification 70.3 kB
  • After compression 70.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. Hnry.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (57%)

Requests Now

63

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 63 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 30 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hnry.co.nz

hnry.co.nz

347 ms

css

css

45 ms

css

css

56 ms

all.css

all.css

178 ms

stylesheet.css

stylesheet.css

128 ms

slick.min.css

slick.min.css

197 ms

accessible-slick-theme.min.css

accessible-slick-theme.min.css

198 ms

youtube-lazy.css

youtube-lazy.css

197 ms

collapsible.js

collapsible.js

255 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

321 ms

popper.min.js

popper.min.js

257 ms

bootstrap.min.js

bootstrap.min.js

321 ms

mdb.min.js

mdb.min.js

441 ms

jquery.bcSwipe.min.js

jquery.bcSwipe.min.js

259 ms

smooth-scroll.js

smooth-scroll.js

315 ms

slick.min.js

slick.min.js

319 ms

skipto.min.js

skipto.min.js

321 ms

site.js

site.js

376 ms

consent.js

consent.js

381 ms

campaign-tracking.js

campaign-tracking.js

383 ms

lazysizes.min.js

lazysizes.min.js

382 ms

hnry.js

hnry.js

172 ms

gtm.js

gtm.js

186 ms

hnry-logo.svg

hnry-logo.svg

158 ms

ios-app-store-150.png

ios-app-store-150.png

158 ms

google-play-badge-150.png

google-play-badge-150.png

154 ms

quote-left-solid.svg

quote-left-solid.svg

156 ms

Tax_Green.png

Tax_Green.png

157 ms

Support_Green.png

Support_Green.png

157 ms

Expenses_Green.png

Expenses_Green.png

242 ms

Invoices_Green.png

Invoices_Green.png

244 ms

Allocations_Green.png

Allocations_Green.png

243 ms

Payments_Green.png

Payments_Green.png

243 ms

hnry-logo-footer.svg

hnry-logo-footer.svg

243 ms

1JttaW5VChI

1JttaW5VChI

219 ms

border-wavy-footer.svg

border-wavy-footer.svg

237 ms

2sDfZG1Wl4LcnbuKjk0j.ttf

2sDfZG1Wl4LcnbuKjk0j.ttf

153 ms

2sDcZG1Wl4LcnbuCJW8zaGW8.ttf

2sDcZG1Wl4LcnbuCJW8zaGW8.ttf

154 ms

fa-brands-400.woff

fa-brands-400.woff

109 ms

js

js

56 ms

analytics.js

analytics.js

84 ms

bat.js

bat.js

102 ms

qevents.js

qevents.js

238 ms

pixel

pixel

107 ms

fbevents.js

fbevents.js

165 ms

js

js

109 ms

js

js

163 ms

events.js

events.js

233 ms

www-player.css

www-player.css

15 ms

www-embed-player.js

www-embed-player.js

14 ms

base.js

base.js

14 ms

iframe_api

iframe_api

216 ms

1JttaW5VChI

1JttaW5VChI

213 ms

collect

collect

76 ms

114 ms

collect

collect

153 ms

www-player.css

www-player.css

20 ms

www-embed-player.js

www-embed-player.js

42 ms

base.js

base.js

84 ms

www-widgetapi.js

www-widgetapi.js

64 ms

My-Account.png

My-Account.png

383 ms

360 ms

ga-audiences

ga-audiences

331 ms

ad_status.js

ad_status.js

291 ms

Hg8RJ6IYDEt2XfeS9TTatHSj5NgA1bkUUg8jx44YVvw.js

Hg8RJ6IYDEt2XfeS9TTatHSj5NgA1bkUUg8jx44YVvw.js

72 ms

embed.js

embed.js

22 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

128 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

131 ms

id

id

127 ms

NZ-Payslip.png

NZ-Payslip.png

149 ms

Create

Create

66 ms

pixel

pixel

24 ms

Accessibility Review

hnry.io accessibility score

91

Accessibility Issues

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

Image elements do not have [alt] attributes

Best Practices

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

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

    EN

  • Encoding

    UTF-8

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

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: