3 sec in total
468 ms
2.3 sec
250 ms
Click here to check amazing Eyedentify content for New Zealand. Otherwise, check out these important facts you probably never knew about eyedentify.co.nz
The platform for retailers focused on improving safety, productivity, and profitability. Auror is used by leading Loss Prevention teams in thousands of stores.
Visit eyedentify.co.nzWe analyzed Eyedentify.co.nz page load time and found that the first response time was 468 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
eyedentify.co.nz performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value3.6 s
60/100
25%
Value2.9 s
95/100
10%
Value160 ms
94/100
30%
Value0.099
90/100
15%
Value3.8 s
89/100
10%
468 ms
210 ms
30 ms
110 ms
115 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Eyedentify.co.nz, 92% (44 requests) were made to Auror.co and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (950 ms) relates to the external source Auror.co.
Page size can be reduced by 1.4 MB (47%)
2.9 MB
1.6 MB
In fact, the total size of Eyedentify.co.nz main page is 2.9 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. 30% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 53.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. 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 53.7 kB or 77% of the original size.
Potential reduce by 535 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. Eyedentify images are well optimized though.
Potential reduce by 529.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 529.8 kB or 71% of the original size.
Potential reduce by 778.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. Eyedentify.co.nz needs all CSS files to be minified and compressed as it can save up to 778.0 kB or 89% of the original size.
Number of requests can be reduced by 37 (82%)
45
8
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eyedentify. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
eyedentify.co.nz
468 ms
www.auror.co
210 ms
webfont.js
30 ms
wp-emoji-release.min.js
110 ms
styles.css
115 ms
settings.css
117 ms
style.css
115 ms
js_composer.css
266 ms
shortcodes.css
229 ms
responsive.css
177 ms
form-basic.min.css
170 ms
jquery.js
228 ms
jquery-migrate.min.js
175 ms
jquery.themepunch.tools.min.js
291 ms
jquery.themepunch.revolution.min.js
293 ms
custom_js.js
259 ms
mediaelementplayer.min.css
290 ms
wp-mediaelement.css
303 ms
jquery.form.min.js
329 ms
scripts.js
330 ms
jquery.easing.min.js
343 ms
waypoints.min.js
348 ms
waypoints-sticky.min.js
349 ms
prettyPhoto.js
390 ms
isotope.pkgd.min.js
409 ms
functions.js
409 ms
flexslider.min.js
373 ms
comment-reply.min.js
376 ms
wp-embed.min.js
374 ms
js_composer_front.js
438 ms
mediaelement-and-player.min.js
523 ms
wp-mediaelement.js
430 ms
owl.carousel.min.js
432 ms
forms-api.min.js
446 ms
style.css
402 ms
ga.js
20 ms
logo-header.png
206 ms
logo-header-white.png
205 ms
logo-header-retina.png
206 ms
logo-header-retina-white.png
203 ms
shutterstock_v4847042.oggtheora.png
950 ms
transparent.png
203 ms
icons-marketing-website_03.png
206 ms
icons-marketing-website_05.png
206 ms
icons-marketing-website_07.png
206 ms
icomoon.ttf
190 ms
__utm.gif
164 ms
gridtile.png
72 ms
eyedentify.co.nz accessibility score
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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
eyedentify.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
eyedentify.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
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyedentify.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 Eyedentify.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.
eyedentify.co.nz
Open Graph description is not detected on the main page of Eyedentify. 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: