6.6 sec in total
626 ms
5.5 sec
429 ms
Visit hhg.co.nz now to see the best up-to-date HHG content for New Zealand and also check out these interesting facts you probably never knew about hhg.co.nz
Trusted Investment Advisors for over 100 years. Get started on the road to financial freedom - talk to a Hamilton Hindin Greene advisor today.
Visit hhg.co.nzWe analyzed Hhg.co.nz page load time and found that the first response time was 626 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
hhg.co.nz performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value9.0 s
1/100
25%
Value9.6 s
11/100
10%
Value40 ms
100/100
30%
Value0.002
100/100
15%
Value8.8 s
35/100
10%
626 ms
1059 ms
209 ms
410 ms
597 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 70% of them (45 requests) were addressed to the original Hhg.co.nz, 28% (18 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Hhg.co.nz.
Page size can be reduced by 169.3 kB (49%)
345.4 kB
176.1 kB
In fact, the total size of Hhg.co.nz main page is 345.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. 65% of websites need less resources to load. HTML takes 202.1 kB which makes up the majority of the site volume.
Potential reduce by 169.3 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 169.3 kB or 84% of the original size.
Potential reduce by 0 B
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. HHG images are well optimized though.
Number of requests can be reduced by 30 (79%)
38
8
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HHG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for CSS and as a result speed up the page load time.
hhg.co.nz
626 ms
www.hhg.co.nz
1059 ms
theme.min.css
209 ms
custom-frontend.min.css
410 ms
general.min.css
597 ms
eael-35.css
605 ms
style.css
604 ms
frontend.css
607 ms
theme.css
611 ms
style.min.css
633 ms
header-footer.min.css
794 ms
all.min.css
1001 ms
v4-shims.min.css
805 ms
public.css
812 ms
eael-7.css
808 ms
jet-elements.css
1059 ms
jet-elements-skin.css
998 ms
elementor-icons.min.css
1009 ms
swiper.min.css
1008 ms
post-113.css
1010 ms
custom-pro-frontend.min.css
1609 ms
jet-tricks-frontend.css
1199 ms
all.min.css
1211 ms
v4-shims.min.css
1217 ms
global.css
1411 ms
post-7.css
1267 ms
post-22.css
1420 ms
post-35.css
1422 ms
post-48.css
1421 ms
fontawesome.min.css
1475 ms
solid.min.css
1616 ms
brands.min.css
1612 ms
css
44 ms
smush-lazy-load.min.js
1633 ms
HHG-250-logo.svg
233 ms
NZX-logo.svg
236 ms
HHG-Home.jpg
596 ms
hhg-divider.svg
239 ms
hhg-divider_1-gold.svg
238 ms
financialbg-scaled.jpg
405 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
37 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
55 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
55 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
54 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
54 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
55 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
59 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
59 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
59 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
59 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
59 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
60 ms
fa-solid-900.woff
684 ms
fa-solid-900.woff
703 ms
fa-regular-400.woff
299 ms
fa-regular-400.woff
334 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
63 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexQ.ttf
63 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf
64 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf
59 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf
63 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf
63 ms
fa-brands-400.woff
702 ms
fa-brands-400.woff
701 ms
hhg.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.
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
No form fields have multiple labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
hhg.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
Page has valid source maps
hhg.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Hhg.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 Hhg.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.
hhg.co.nz
Open Graph data is detected on the main page of HHG. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: