Tools & Wizards About Us
safeeye.in screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

safeeye.in

Safeeye | Best Security System Accessories in Delhi, India

Page Load Speed

8.4 sec in total

First Response

2.4 sec

Resources Loaded

5.3 sec

Page Rendered

769 ms

safeeye.in screenshot

About Website

Welcome to safeeye.in homepage info - get ready to check Safeeye best content right away, or after learning these important things about safeeye.in

Safeeye offers you the best security system accessories in Delhi, India. Dealing with Biometric Attendance System, Hybrid Biometric Machine, Electrical Panel Manufacturing, standalone device manufactu...

Visit safeeye.in

Key Findings

We analyzed Safeeye.in page load time and found that the first response time was 2.4 sec and then it took 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.

Performance Metrics

safeeye.in performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value26.8 s

0/100

25%

SI (Speed Index)

Value20.2 s

0/100

10%

TBT (Total Blocking Time)

Value11,410 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value32.3 s

0/100

10%

Network Requests Diagram

safeeye.in

2408 ms

analytics.js

298 ms

wp-emoji-release.min.js

150 ms

style.min.css

270 ms

styles.css

147 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 77% of them (59 requests) were addressed to the original Safeeye.in, 6% (5 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Safeeye.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 985.8 kB (27%)

Content Size

3.6 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Safeeye.in main page is 3.6 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 87.8 kB

  • Original 109.0 kB
  • After minification 104.9 kB
  • After compression 21.2 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 87.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 8.8 kB

  • Original 2.2 MB
  • After minification 2.2 MB

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. Safeeye images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 450.9 kB

  • Original 773.8 kB
  • After minification 724.1 kB
  • After compression 322.9 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 450.9 kB or 58% of the original size.

CSS Optimization

-85%

Potential reduce by 438.3 kB

  • Original 517.6 kB
  • After minification 479.4 kB
  • After compression 79.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. Safeeye.in needs all CSS files to be minified and compressed as it can save up to 438.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (61%)

Requests Now

66

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Safeeye. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

safeeye.in

safeeye.in

2408 ms

analytics.js

analytics.js

298 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

150 ms

style.min.css

style.min.css

270 ms

styles.css

styles.css

147 ms

settings.css

settings.css

324 ms

style.css

style.css

144 ms

base.css

base.css

310 ms

layout.css

layout.css

418 ms

shortcodes.css

shortcodes.css

369 ms

animations.min.css

animations.min.css

261 ms

jquery.ui.all.css

jquery.ui.all.css

340 ms

jplayer.blue.monday.css

jplayer.blue.monday.css

342 ms

responsive.css

responsive.css

518 ms

css

css

132 ms

css

css

132 ms

style.css

style.css

405 ms

jquery.js

jquery.js

491 ms

jquery-migrate.min.js

jquery-migrate.min.js

508 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

489 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

489 ms

svgxuse.js

svgxuse.js

452 ms

default.css

default.css

482 ms

scripts.js

scripts.js

952 ms

core.min.js

core.min.js

987 ms

widget.min.js

widget.min.js

987 ms

mouse.min.js

mouse.min.js

982 ms

sortable.min.js

sortable.min.js

984 ms

tabs.min.js

tabs.min.js

997 ms

accordion.min.js

accordion.min.js

980 ms

plugins.js

plugins.js

990 ms

menu.js

menu.js

1004 ms

animations.min.js

animations.min.js

983 ms

jplayer.min.js

jplayer.min.js

1130 ms

translate3d.js

translate3d.js

1006 ms

scripts.js

scripts.js

1242 ms

comment-reply.min.js

comment-reply.min.js

1004 ms

wp-embed.min.js

wp-embed.min.js

1007 ms

collect

collect

100 ms

safeeye.png

safeeye.png

164 ms

7321cfbaf80f45ef1ffd58f82239ab4e.jpg

7321cfbaf80f45ef1ffd58f82239ab4e.jpg

475 ms

b1.jpg

b1.jpg

257 ms

di3.jpg

di3.jpg

832 ms

di2.jpg

di2.jpg

469 ms

di1.jpg

di1.jpg

847 ms

hj-1.jpg

hj-1.jpg

468 ms

hs.jpg

hs.jpg

469 ms

abgt-1.png

abgt-1.png

900 ms

testimonials-placeholder.png

testimonials-placeholder.png

527 ms

1.gif

1.gif

521 ms

0.gif

0.gif

521 ms

embed

embed

577 ms

fancy_heading_hr.png

fancy_heading_hr.png

568 ms

kjl.jpg

kjl.jpg

668 ms

box_shadow_button.png

box_shadow_button.png

555 ms

textline.png

textline.png

587 ms

blockquote.png

blockquote.png

642 ms

symbol-defs.svg

symbol-defs.svg

583 ms

init.js

init.js

800 ms

default

default

366 ms

box_shadow.png

box_shadow.png

383 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

59 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

339 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

317 ms

mfn-icons.woff

mfn-icons.woff

358 ms

KFOkCnqEu92Fr1Mu51xIIzQ.woff

KFOkCnqEu92Fr1Mu51xIIzQ.woff

316 ms

ZXuke1cDvLCKLDcimxB44_lo.woff

ZXuke1cDvLCKLDcimxB44_lo.woff

316 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

337 ms

revolution.extension.navigation.min.js

revolution.extension.navigation.min.js

331 ms

js

js

433 ms

loader.gif

loader.gif

164 ms

revicons.woff

revicons.woff

205 ms

init.js

init.js

611 ms

init_embed.js

init_embed.js

89 ms

common.js

common.js

134 ms

util.js

util.js

259 ms

map.js

map.js

255 ms

Accessibility Review

safeeye.in accessibility score

83

Accessibility Issues

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

High

ARIA input fields do not have accessible names

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

safeeye.in best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

safeeye.in SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Safeeye.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 Safeeye.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.

Social Sharing Optimization

safeeye.in

Open Graph description is not detected on the main page of Safeeye. 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: