Tools & Wizards About Us
hnry.io screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% 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.io

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

Page Load Speed

3.3 sec in total

First Response

328 ms

Resources Loaded

2.3 sec

Page Rendered

739 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 328 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

hnry.io performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value6,330 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

Network Requests Diagram

hnry.co.nz

328 ms

uk-redirect.js

62 ms

100412253-100412715.js

48 ms

glide.min.js

54 ms

css

51 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 420.9 kB (53%)

Content Size

791.6 kB

After Optimization

370.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Hnry.io main page is 791.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. 55% of websites need less resources to load. CSS take 427.3 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 269.9 kB
  • After minification 269.9 kB
  • After compression 267.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.

CSS Optimization

-80%

Potential reduce by 343.5 kB

  • Original 427.3 kB
  • After minification 426.5 kB
  • After compression 83.8 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 needs all CSS files to be minified and compressed as it can save up to 343.5 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

55

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 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

328 ms

uk-redirect.js

uk-redirect.js

62 ms

100412253-100412715.js

100412253-100412715.js

48 ms

glide.min.js

glide.min.js

54 ms

css

css

51 ms

css

css

70 ms

all.css

all.css

57 ms

stylesheet.css

stylesheet.css

183 ms

slick.min.css

slick.min.css

188 ms

accessible-slick-theme.min.css

accessible-slick-theme.min.css

244 ms

glide.core.min.css

glide.core.min.css

66 ms

youtube-lazy.css

youtube-lazy.css

248 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

310 ms

popper.min.js

popper.min.js

257 ms

bootstrap.min.js

bootstrap.min.js

322 ms

mdb.min.js

mdb.min.js

448 ms

jquery.bcSwipe.min.js

jquery.bcSwipe.min.js

301 ms

smooth-scroll.js

smooth-scroll.js

306 ms

slick.min.js

slick.min.js

319 ms

skipto.min.js

skipto.min.js

363 ms

site.js

site.js

367 ms

consent.js

consent.js

371 ms

pass-uuid-to-app.js

pass-uuid-to-app.js

382 ms

collapsible.js

collapsible.js

385 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

37 ms

platform.js

platform.js

49 ms

campaign-tracking.js

campaign-tracking.js

422 ms

lazysizes.min.js

lazysizes.min.js

427 ms

hnry.js

hnry.js

147 ms

gtm.js

gtm.js

173 ms

hnry-logo.svg

hnry-logo.svg

144 ms

hero-carousel-slide-1.webp

hero-carousel-slide-1.webp

471 ms

hero-carousel-slide-3.webp

hero-carousel-slide-3.webp

468 ms

hero-carousel-slide-4.webp

hero-carousel-slide-4.webp

229 ms

ios-app-store.svg

ios-app-store.svg

143 ms

app-badge-android.webp

app-badge-android.webp

144 ms

quote-left-solid.svg

quote-left-solid.svg

201 ms

Tax.webp

Tax.webp

203 ms

Support.webp

Support.webp

201 ms

Expenses.webp

Expenses.webp

465 ms

Invoices.webp

Invoices.webp

466 ms

Allocations.webp

Allocations.webp

466 ms

Payments.webp

Payments.webp

466 ms

hnry-logo-footer.svg

hnry-logo-footer.svg

467 ms

l4tx07Dnmro

l4tx07Dnmro

181 ms

border-wavy-footer.svg

border-wavy-footer.svg

435 ms

font

font

132 ms

fa-brands-400.ttf

fa-brands-400.ttf

38 ms

www-player.css

www-player.css

5 ms

www-embed-player.js

www-embed-player.js

28 ms

base.js

base.js

49 ms

ad_status.js

ad_status.js

124 ms

C0W8c044oElyKk6slHQq9cj4mgIB0cSN5MnHWqwEeWg.js

C0W8c044oElyKk6slHQq9cj4mgIB0cSN5MnHWqwEeWg.js

103 ms

embed.js

embed.js

37 ms

id

id

19 ms

My-Account.webp

My-Account.webp

86 ms

Create

Create

77 ms

Accessibility Review

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

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