Tools & Wizards About Us
blinkeye.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

blinkeye.com

Home | Eye Tracking Software & Eye Tracking Technology | Blink

Page Load Speed

3.7 sec in total

First Response

150 ms

Resources Loaded

2.7 sec

Page Rendered

833 ms

blinkeye.com screenshot

About Website

Visit blinkeye.com now to see the best up-to-date Blink Eye content and also check out these interesting facts you probably never knew about blinkeye.com

Blink creates the ultimate interaction between your eyes & the world around you with our eye tracking software & eye tracking technology.

Visit blinkeye.com

Key Findings

We analyzed Blinkeye.com page load time and found that the first response time was 150 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

blinkeye.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value2,110 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

blinkeye.com

150 ms

blinkeye.com

1938 ms

hu-banner.min.js

46 ms

style.min.css

12 ms

styles.css

29 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 66% of them (33 requests) were addressed to the original Blinkeye.com, 12% (6 requests) were made to Unpkg.com and 10% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Blinkeye.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 308.3 kB (19%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blinkeye.com main page is 1.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. 70% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 58.9 kB

  • Original 74.3 kB
  • After minification 69.1 kB
  • After compression 15.3 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 58.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 1.9 kB

  • Original 1.0 MB
  • After minification 1.0 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. Blink Eye images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 227.1 kB

  • Original 416.8 kB
  • After minification 416.8 kB
  • After compression 189.7 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 227.1 kB or 54% of the original size.

CSS Optimization

-30%

Potential reduce by 20.4 kB

  • Original 67.7 kB
  • After minification 67.7 kB
  • After compression 47.2 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. Blinkeye.com needs all CSS files to be minified and compressed as it can save up to 20.4 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (63%)

Requests Now

38

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blinkeye.com

blinkeye.com

150 ms

blinkeye.com

blinkeye.com

1938 ms

hu-banner.min.js

hu-banner.min.js

46 ms

style.min.css

style.min.css

12 ms

styles.css

styles.css

29 ms

aos.css

aos.css

73 ms

keel.css

keel.css

28 ms

main.css

main.css

24 ms

all.css

all.css

26 ms

jquery.min.js

jquery.min.js

27 ms

jquery-migrate.min.js

jquery-migrate.min.js

41 ms

aos.js

aos.js

215 ms

js

js

82 ms

index.js

index.js

32 ms

index.js

index.js

31 ms

navigation.js

navigation.js

31 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

33 ms

libraries.js

libraries.js

37 ms

footer.js

footer.js

36 ms

api.js

api.js

69 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

35 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

35 ms

wp-polyfill.min.js

wp-polyfill.min.js

37 ms

index.js

index.js

67 ms

hhj6kcg.css

hhj6kcg.css

73 ms

aos.css

aos.css

22 ms

aos.css

aos.css

11 ms

p.css

p.css

20 ms

aos.js

aos.js

11 ms

aos.js

aos.js

11 ms

BackgroundHeader.jpg

BackgroundHeader.jpg

109 ms

Blink_TV.jpg

Blink_TV.jpg

89 ms

patrick-tomasso-fMntI8HAAB8-unsplash.jpg

patrick-tomasso-fMntI8HAAB8-unsplash.jpg

86 ms

video2.jpg

video2.jpg

87 ms

omar-prestwich-0TQa-Ur6Zqg-unsplash.jpg

omar-prestwich-0TQa-Ur6Zqg-unsplash.jpg

87 ms

bianca-castillo-iAGPCmxKbls-unsplash.jpg

bianca-castillo-iAGPCmxKbls-unsplash.jpg

88 ms

Oren-Yogev.jpg

Oren-Yogev.jpg

92 ms

Gilad-Drozdov.jpg

Gilad-Drozdov.jpg

89 ms

Artyom-Borzin.jpg

Artyom-Borzin.jpg

90 ms

Tsahi-Mizrahi.jpg

Tsahi-Mizrahi.jpg

90 ms

PHOTO-2021-06-29-10-14-05.jpg

PHOTO-2021-06-29-10-14-05.jpg

91 ms

PP-Headshot.jpg

PP-Headshot.jpg

92 ms

js

js

103 ms

analytics.js

analytics.js

148 ms

d

d

96 ms

d

d

146 ms

d

d

146 ms

icomoon.ttf

icomoon.ttf

39 ms

d

d

193 ms

fa-brands-400.woff

fa-brands-400.woff

146 ms

Accessibility Review

blinkeye.com accessibility score

96

Accessibility Issues

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

Links do not have a discernible name

Best Practices

blinkeye.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

blinkeye.com SEO score

86

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

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 Blinkeye.com 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 Blinkeye.com 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

blinkeye.com

Open Graph data is detected on the main page of Blink Eye. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: