Tools & Wizards About Us
ekey.net screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ekey.net

ekey - Europas Nr. 1 bei Fingerprint-Zutrittslösungen

Page Load Speed

9.1 sec in total

First Response

409 ms

Resources Loaded

8.4 sec

Page Rendered

337 ms

ekey.net screenshot

About Website

Click here to check amazing Ekey content for Germany. Otherwise, check out these important facts you probably never knew about ekey.net

Freiheit genießen Kein Schlüssel mehr, Ihr Finger ist immer dabei. Tür auf, Tür zu, einfach raus! Aussperren unmöglich Zutrittsberechtigungen via App vergeben und Ihr Finger wird zum Schlüssel! Smarte...

Visit ekey.net

Key Findings

We analyzed Ekey.net page load time and found that the first response time was 409 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

ekey.net performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.771

5/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

ekey.net

409 ms

minify.css

1943 ms

modernizr-2.6.2.min.js

633 ms

jquery-1.11.1.min.js

7 ms

minify.js

4362 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 93% of them (54 requests) were addressed to the original Ekey.net, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Ekey.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 581.5 kB (33%)

Content Size

1.8 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ekey.net 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. 25% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 23.7 kB

  • Original 31.6 kB
  • After minification 29.2 kB
  • After compression 7.8 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 23.7 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 62.3 kB

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

JavaScript Optimization

-67%

Potential reduce by 333.5 kB

  • Original 500.3 kB
  • After minification 499.8 kB
  • After compression 166.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 333.5 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 162.0 kB

  • Original 193.2 kB
  • After minification 190.7 kB
  • After compression 31.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. Ekey.net needs all CSS files to be minified and compressed as it can save up to 162.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (31%)

Requests Now

55

After Optimization

38

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ekey.net

ekey.net

409 ms

minify.css

minify.css

1943 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

633 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

7 ms

minify.js

minify.js

4362 ms

preloader.gif

preloader.gif

1808 ms

logo-small-2x.png

logo-small-2x.png

798 ms

logo-top.png

logo-top.png

786 ms

icn-search.png

icn-search.png

576 ms

navArrowSprite.png

navArrowSprite.png

318 ms

flag_de.png

flag_de.png

634 ms

flag_en.png

flag_en.png

893 ms

flag_it_IT.png

flag_it_IT.png

943 ms

flag_fr_FR.png

flag_fr_FR.png

1105 ms

flag_de_CH.png

flag_de_CH.png

1103 ms

flag_fr_CH.png

flag_fr_CH.png

1261 ms

flag_sl_SI.png

flag_sl_SI.png

1422 ms

flag_cs_CZ.png

flag_cs_CZ.png

1421 ms

logo.png

logo.png

1575 ms

logo768.png

logo768.png

1737 ms

navBg.png

navBg.png

1630 ms

Header_Einstieg_2016_02.jpg

Header_Einstieg_2016_02.jpg

4796 ms

Header_Einstieg_2016_03.jpg

Header_Einstieg_2016_03.jpg

3843 ms

Header_Einstieg_2016_01.jpg

Header_Einstieg_2016_01.jpg

3108 ms

Home_Automation_teaser.jpg

Home_Automation_teaser.jpg

2318 ms

Messeeinladung_frontale.jpg

Messeeinladung_frontale.jpg

2830 ms

Messeeinladung-light.jpg

Messeeinladung-light.jpg

2638 ms

IN_BT_RFID.jpg

IN_BT_RFID.jpg

2655 ms

Glasrahmen.jpg

Glasrahmen.jpg

3059 ms

garantie.png

garantie.png

2973 ms

die_zukunft.jpg

die_zukunft.jpg

3463 ms

app-03.jpg

app-03.jpg

3289 ms

anwedungsbereich_schalter.jpg

anwedungsbereich_schalter.jpg

3376 ms

app-01.jpg

app-01.jpg

3425 ms

app-04.jpg

app-04.jpg

3607 ms

socialMediaSprite.png

socialMediaSprite.png

3695 ms

ekey_channel_sprite.png

ekey_channel_sprite.png

3741 ms

icn-arrow-link.png

icn-arrow-link.png

3673 ms

worldmap.png

worldmap.png

3922 ms

GillSansMT.woff

GillSansMT.woff

4770 ms

analytics.js

analytics.js

63 ms

sprite.png

sprite.png

1806 ms

blank.gif

blank.gif

1437 ms

bx_loader.gif

bx_loader.gif

1533 ms

Home_Automation_teaser.jpg

Home_Automation_teaser.jpg

2572 ms

Messeeinladung_frontale.jpg

Messeeinladung_frontale.jpg

1748 ms

Messeeinladung-light.jpg

Messeeinladung-light.jpg

2805 ms

IN_BT_RFID.jpg

IN_BT_RFID.jpg

2117 ms

Glasrahmen.jpg

Glasrahmen.jpg

2972 ms

garantie.png

garantie.png

2589 ms

icn-arrow-left-blue.png

icn-arrow-left-blue.png

2525 ms

icn-arrow-right-blue.png

icn-arrow-right-blue.png

2735 ms

app-03.jpg

app-03.jpg

2887 ms

anwedungsbereich_schalter.jpg

anwedungsbereich_schalter.jpg

3419 ms

app-01.jpg

app-01.jpg

3051 ms

app-04.jpg

app-04.jpg

3058 ms

collect

collect

12 ms

collect

collect

57 ms

Accessibility Review

ekey.net accessibility score

73

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

[lang] attributes do not have a valid value

Best Practices

ekey.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

ekey.net 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

Image elements do not have [alt] attributes

High

Document doesn't have a valid hreflang

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

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ekey.net can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Ekey.net 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

ekey.net

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