7.4 sec in total
784 ms
6.2 sec
404 ms
Visit zeye.in now to see the best up-to-date ZEYE content and also check out these interesting facts you probably never knew about zeye.in
RFID Student Tracking System, Automated Student Attendance System to keep Parents and School Administration informed with SMS Notifications : zEYE. ed.
Visit zeye.inWe analyzed Zeye.in page load time and found that the first response time was 784 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
zeye.in performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value15.0 s
0/100
25%
Value18.9 s
0/100
10%
Value4,920 ms
0/100
30%
Value0.137
79/100
15%
Value22.4 s
1/100
10%
784 ms
62 ms
81 ms
30 ms
198 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 59% of them (49 requests) were addressed to the original Zeye.in, 11% (9 requests) were made to Static.xx.fbcdn.net and 5% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Zeye.in.
Page size can be reduced by 192.4 kB (11%)
1.8 MB
1.6 MB
In fact, the total size of Zeye.in 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 43.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 6.7 kB, which is 12% 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 43.7 kB or 79% of the original size.
Potential reduce by 4.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. ZEYE images are well optimized though.
Potential reduce by 89.4 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 89.4 kB or 33% of the original size.
Potential reduce by 54.3 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. Zeye.in needs all CSS files to be minified and compressed as it can save up to 54.3 kB or 38% of the original size.
Number of requests can be reduced by 51 (67%)
76
25
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ZEYE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.zeye.in
784 ms
css
62 ms
css
81 ms
css
30 ms
genericons.css
198 ms
style.css
574 ms
jquery.js
586 ms
jquery-migrate.min.js
394 ms
bootstrap.css
620 ms
font-awesome.css
401 ms
fontello.css
408 ms
settings.css
612 ms
extralayers.css
629 ms
magnific-popup.css
632 ms
animations.css
761 ms
owl.carousel.css
777 ms
style.css
786 ms
dark_cyan.css
793 ms
custom.css
794 ms
conversion.js
33 ms
functions.js
812 ms
wp-embed.min.js
945 ms
jquery.min.js
967 ms
bootstrap.min.js
972 ms
modernizr.js
978 ms
jquery.themepunch.tools.min.js
1189 ms
jquery.themepunch.revolution.min.js
1219 ms
isotope.pkgd.min.js
1141 ms
owl.carousel.js
1167 ms
jquery.magnific-popup.min.js
1163 ms
jquery.appear.js
1173 ms
jquery.countTo.js
1335 ms
jquery.parallax-1.1.3.js
1356 ms
jquery.validate.js
1372 ms
template.js
1372 ms
custom.js
1387 ms
jquery.validate.min.js
1425 ms
validation.js
1522 ms
analytics.js
29 ms
wp-emoji-release.min.js
1461 ms
collect
33 ms
collect
37 ms
animate.css
817 ms
collect
83 ms
logo.png
269 ms
students.jpg
941 ms
mobile-img.jpg
864 ms
map.jpg
1059 ms
cctv.jpg
940 ms
media.png
1042 ms
boy_01.png
1057 ms
sdk.js
77 ms
222 ms
banner-bg.jpg
978 ms
pattern-2.png
1001 ms
pattern-footer.png
989 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
474 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
582 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
590 ms
fontawesome-webfont.woff
913 ms
sdk.js
471 ms
584 ms
widgets.js
393 ms
app_store.png
1001 ms
fontello.woff
634 ms
widget_iframe.7dae38096d06923d683a2a807172322a.html
301 ms
205 ms
200 ms
settings
101 ms
button.d2f864f87f544dc0c11d7d712a191c1f.js
26 ms
embeds
67 ms
follow_button.7dae38096d06923d683a2a807172322a.en.html
231 ms
like_box.php
395 ms
mH0MryOt2MZ.css
32 ms
4_8X-2u0CDc.css
37 ms
nYa8oQZnpdr.js
54 ms
iiDbYMCPtB3.js
148 ms
WOLN5pzG8JN.js
151 ms
q6VzhXzzuec.js
150 ms
YJojGYumZIr.js
173 ms
299855071_153202813995463_9078991172982587135_n.png
301 ms
UXtr_j2Fwe-.png
112 ms
1lYRIUv3fB9.js
65 ms
zeye.in 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
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
Links do not have a discernible name
zeye.in 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
zeye.in 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 Zeye.in 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 Zeye.in 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.
zeye.in
Open Graph data is detected on the main page of ZEYE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: