1.3 sec in total
68 ms
1.1 sec
69 ms
Click here to check amazing Hearing House content. Otherwise, check out these important facts you probably never knew about hearinghouse.co.nz
The Hearing House is a charity providing cochlear implants and support for New Zealanders in the upper North Island with profound hearing loss.
Visit hearinghouse.co.nzWe analyzed Hearinghouse.co.nz page load time and found that the first response time was 68 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
hearinghouse.co.nz performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value7.2 s
5/100
25%
Value9.5 s
12/100
10%
Value1,650 ms
11/100
30%
Value0
100/100
15%
Value16.6 s
5/100
10%
68 ms
33 ms
37 ms
36 ms
32 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Hearinghouse.co.nz, 35% (18 requests) were made to Static.parastorage.com and 27% (14 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (545 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 572.4 kB (44%)
1.3 MB
717.2 kB
In fact, the total size of Hearinghouse.co.nz main page is 1.3 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. 40% of websites need less resources to load. HTML takes 694.7 kB which makes up the majority of the site volume.
Potential reduce by 543.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 543.4 kB or 78% of the original size.
Potential reduce by 26.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. Hearing House images are well optimized though.
Potential reduce by 2.8 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.
Number of requests can be reduced by 12 (43%)
28
16
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hearing House. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
www.hearinghouse.co.nz
68 ms
originTrials.41d7301a.bundle.min.js
33 ms
minified.js
37 ms
focus-within-polyfill.js
36 ms
polyfill.min.js
32 ms
thunderbolt-commons.24e46262.bundle.min.js
132 ms
main.8752ee81.bundle.min.js
132 ms
lodash.min.js
119 ms
react.production.min.js
132 ms
react-dom.production.min.js
136 ms
siteTags.bundle.min.js
147 ms
wix-perf-measure.umd.min.js
147 ms
xfbml.customerchat.js
222 ms
Asset%204-01.png
240 ms
bundle.min.js
70 ms
6f9a29_8ac8fff892204f7fbcefff43f37daa3f~mv2.jpg
411 ms
6f9a29_acdf0b894ad94366b13e28154229606d~mv2.png
382 ms
6f9a29_ccf93584753a4dca89fdb42c3a02f852~mv2.jpg
372 ms
6f9a29_ccf93584753a4dca89fdb42c3a02f852~mv2.jpg
328 ms
6f9a29_d0714a8c696942959d86a4ead265b23a~mv2.png
364 ms
6f9a29_95793b5f4a3b47acb7566a2dd7d439a6~mv2.png
320 ms
6f9a29_05c1d0f3130d41a19fc64202e8a2c3a4~mv2.jpg
531 ms
6f9a29_05c1d0f3130d41a19fc64202e8a2c3a4~mv2.jpg
534 ms
Your%20paragraph%20text.png
545 ms
The%20Hearing%20House%20Social%20Creatives%20(Client%20pics%20need%20approval%20for%20reusage)).png
517 ms
148 ms
150 ms
143 ms
149 ms
146 ms
144 ms
194 ms
189 ms
202 ms
202 ms
186 ms
198 ms
61bd362e-7162-46bd-b67e-28f366c4afbe.woff
9 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
8 ms
file.woff
341 ms
file.woff
352 ms
file.woff
444 ms
50 ms
123 ms
deprecation-en.v5.html
7 ms
bolt-performance
76 ms
deprecation-style.v5.css
33 ms
right-arrow.svg
56 ms
WixMadeforDisplay_W_Bd.woff
18 ms
WixMadeforText_W_Bd.woff
16 ms
WixMadeforText_W_Rg.woff
17 ms
hearinghouse.co.nz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
hearinghouse.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
hearinghouse.co.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hearinghouse.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 Hearinghouse.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.
hearinghouse.co.nz
Open Graph data is detected on the main page of Hearing House. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: