Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

doublekey.de

DKEY – LOVE WHAT YOU DO

Page Load Speed

840 ms in total

First Response

370 ms

Resources Loaded

380 ms

Page Rendered

90 ms

doublekey.de screenshot

About Website

Welcome to doublekey.de homepage info - get ready to check Doublekey best content right away, or after learning these important things about doublekey.de

Visit doublekey.de

Key Findings

We analyzed Doublekey.de page load time and found that the first response time was 370 ms and then it took 470 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster. This domain responded with an error, which can significantly jeopardize Doublekey.de rating and web reputation

Performance Metrics

doublekey.de performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,940 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value20.1 s

2/100

10%

Network Requests Diagram

doublekey.de

370 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Doublekey.de and no external sources were called. The less responsive or slowest element that took the longest time to load (370 ms) belongs to the original domain Doublekey.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.4 kB (5%)

Content Size

355.1 kB

After Optimization

335.7 kB

In fact, the total size of Doublekey.de main page is 355.1 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 297.3 kB which makes up the majority of the site volume.

HTML Optimization

-19%

Potential reduce by 40 B

  • Original 206 B
  • After minification 205 B
  • After compression 166 B

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 40 B or 19% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

  • Original 297.3 kB
  • After minification 296.1 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. Doublekey images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 14.8 kB

  • Original 53.6 kB
  • After minification 50.5 kB
  • After compression 38.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 14.8 kB or 28% of the original size.

CSS Optimization

-84%

Potential reduce by 3.4 kB

  • Original 4.0 kB
  • After minification 2.9 kB
  • After compression 636 B

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. Doublekey.de needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

doublekey.de accessibility score

86

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-*] attributes do not match their roles

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

[id] attributes on active, focusable elements are not unique

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

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

Best Practices

doublekey.de best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

doublekey.de SEO score

83

Search Engine Optimization Advices

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doublekey.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Doublekey.de main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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