7.5 sec in total
619 ms
6.7 sec
190 ms
Click here to check amazing Hedgerow content. Otherwise, check out these important facts you probably never knew about hedgerow.co.nz
Hedgerow is a Remuera institution with a 25 year history. A carefully curated selection of high quality and stylish gifts and homewares for those you love and you! Hedgerow prides itself on being a be...
Visit hedgerow.co.nzWe analyzed Hedgerow.co.nz page load time and found that the first response time was 619 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
hedgerow.co.nz performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value8.1 s
2/100
25%
Value3.4 s
90/100
10%
Value560 ms
53/100
30%
Value0.01
100/100
15%
Value9.1 s
33/100
10%
619 ms
1233 ms
205 ms
391 ms
793 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 79% of them (34 requests) were addressed to the original Hedgerow.co.nz, 14% (6 requests) were made to Use.typekit.net and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Hedgerow.co.nz.
Page size can be reduced by 241.3 kB (30%)
810.2 kB
568.9 kB
In fact, the total size of Hedgerow.co.nz main page is 810.2 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. 35% of websites need less resources to load. Images take 471.6 kB which makes up the majority of the site volume.
Potential reduce by 17.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 4.3 kB, which is 19% 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 17.7 kB or 77% of the original size.
Potential reduce by 7.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. Hedgerow images are well optimized though.
Potential reduce by 179.6 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 179.6 kB or 66% of the original size.
Potential reduce by 36.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. Hedgerow.co.nz needs all CSS files to be minified and compressed as it can save up to 36.1 kB or 81% of the original size.
Number of requests can be reduced by 12 (32%)
37
25
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hedgerow. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
hedgerow.co.nz
619 ms
www.hedgerow.co.nz
1233 ms
css.php
205 ms
modernizr-2.5.3-min.js
391 ms
js.php
793 ms
oij2nyp.js
208 ms
icn_cart.gif
196 ms
logo_hedgerow.gif
196 ms
home-icon.gif
197 ms
dropdown_top.png
385 ms
btn_search.gif
388 ms
586 ms
794 ms
602 ms
795 ms
1335 ms
774 ms
854
783 ms
addtoshoppingbag.png
793 ms
256
3583 ms
226
981 ms
1133
1008 ms
1517
1001 ms
1000
995 ms
1019
1181 ms
730
1194 ms
1394
1198 ms
facebook.gif
1202 ms
footer_paymentoptions.png
1374 ms
arrow_left.png
1370 ms
arrow_right.png
1372 ms
ga.js
55 ms
www.hedgerow.co.nz
202 ms
__utm.gif
13 ms
xpZLtTKBTfirWnJM5s4w6B4Azc3vEzndzQD8_qssMbSffHPsgsMmeMJ6Mk6f5Mb.woff
29 ms
gkXG-lWRRqN5mRrPbz5slnVGS-XX9sJtpzbccZ0a2n9ffH-sgsMmeMJ6Mk6f5Mj.woff
57 ms
prIMHwO-dhQ6m5OV5oixxOeSqWf6dssBqfTRS7HLOCwffHAsgsMmeMJ6Mk6f5Mt.woff
85 ms
1JXrqEeVY6TvC1ZSGJSHJH94bqGK9pLZhO4qIxIGJQGffHpsgsMmeMJ6Mk6f5gM.woff
113 ms
p.gif
125 ms
print.css
195 ms
drop-shadow.png
196 ms
zoomout.cur
194 ms
loader.white.gif
196 ms
hedgerow.co.nz accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
hedgerow.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hedgerow.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hedgerow.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Hedgerow.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.
hedgerow.co.nz
Open Graph description is not detected on the main page of Hedgerow. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: