5.9 sec in total
699 ms
4.8 sec
317 ms
Welcome to e2.nz homepage info - get ready to check E 2 best content right away, or after learning these important things about e2.nz
E2 Digital creates more than just websites, we discover your business objectives & help to grow your online presence using our teams digital expertise
Visit e2.nzWe analyzed E2.nz page load time and found that the first response time was 699 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
e2.nz performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value1.2 s
100/100
10%
Value0 ms
100/100
30%
Value0.005
100/100
15%
Value0.6 s
100/100
10%
699 ms
1497 ms
41 ms
288 ms
709 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original E2.nz, 44% (18 requests) were made to E2digital.co.nz and 15% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source E2digital.co.nz.
Page size can be reduced by 172.9 kB (10%)
1.8 MB
1.6 MB
In fact, the total size of E2.nz main page is 1.8 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. 35% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 12.1 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 2.1 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 12.1 kB or 73% of the original size.
Potential reduce by 7.8 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. E 2 images are well optimized though.
Potential reduce by 75.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 75.1 kB or 69% of the original size.
Potential reduce by 78.0 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. E2.nz needs all CSS files to be minified and compressed as it can save up to 78.0 kB or 80% of the original size.
Number of requests can be reduced by 13 (45%)
29
16
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
e2.nz
699 ms
e2digital.co.nz
1497 ms
css
41 ms
lnv2zfc.js
288 ms
bootstrap.min.css
709 ms
main.css
692 ms
text.css
477 ms
font-awesome.min.css
39 ms
slick.min.css
23 ms
slick-theme.css
474 ms
jquery.min.js
22 ms
imagesloaded.pkgd.min.js
477 ms
slick.min.js
25 ms
main.js
501 ms
conversion.js
28 ms
e2digital.co.nz
94 ms
analytics.js
90 ms
e2-logo.png
250 ms
home-e2-landing.jpg
962 ms
home-slide-macpac.jpg
1418 ms
home-gough.jpg
1373 ms
home-versatile.jpg
1186 ms
home-maintainance.jpg
1546 ms
home-birkenstock.jpg
1202 ms
home-alpine-group.jpg
1908 ms
careers.jpg
1669 ms
6GxWk1GDRqVp9G5KxliyKyyzHyTOidYX5MSCeSCdXl9ffwWJgsMdeMJ6Mk6g5MsfbeZcZRBy5Q6oFQS3ZAJXFDsK5ewkwcwuFhFRFDIo5A9hwh4cjDi85QIUjRSuw2IhFAb3wQqowRItZRgKFh9ajhw.woff
263 ms
RUXNaCEamaGXiq9SPgo_a5c_Y4s0x213sIPljKCqlQGffOdJgsMdeMJ6Mk6g5MifbeZcZRBy5Q6oFQS3ZAJXFDsK5ewkwcwuFhFRFDIo5A9hwh4cjDi85QIUjRSuw2IhFAb3wQqowRItZRgKFh9ajhw.woff
404 ms
UUu1lKiy4hRmBWk599VL1f4EjSn3AhEwRmBJ9NDhg68.ttf
26 ms
JzRrPKdwEnE8F1TDmDLMUhxcROG_7vu2ubkyRjqgeRY.ttf
25 ms
BGP4cfYUTrhlzv32AHmp_5P_WoKfhsqDVvwlmM42AsqffODJgsMdeMJ6Mk6g5MofbeZcZRBy5Q6oFQS3ZAJXFDsK5ewkwcwuFhFRFDIo5A9hwh4cjDi85QIUjRSuw2IhFAb3wQqowRItZRgKFh9ajhw.woff
425 ms
Jc757llyfhNrssmik2grmKgfjVvW7kol7q_yzI8NY7tffOLJgsMdeMJ6Mk6g5gBfbeZcZRBy5Q6oFQS3ZAJXFDsK5ewkwcwuFhFRFDIo5A9hwh4cjDi85QIUjRSuw2IhFAb3wQqowRItZRgKFh9ajhw.woff
486 ms
collect
139 ms
136 ms
collect
88 ms
ajax-loader.gif
1209 ms
fontawesome-webfont.woff
9 ms
slick.woff
1363 ms
57 ms
ga-audiences
21 ms
p.gif
132 ms
e2.nz accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
e2.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
e2.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E2.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 E2.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.
e2.nz
Open Graph description is not detected on the main page of E 2. 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: