4 sec in total
381 ms
3.4 sec
165 ms
Visit dai.de now to see the best up-to-date Dai content for Germany and also check out these interesting facts you probably never knew about dai.de
Visit dai.deWe analyzed Dai.de page load time and found that the first response time was 381 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
dai.de performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value12.4 s
0/100
25%
Value6.3 s
42/100
10%
Value290 ms
80/100
30%
Value0.627
9/100
15%
Value7.5 s
48/100
10%
381 ms
516 ms
68 ms
437 ms
453 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 70% of them (26 requests) were addressed to the original Dai.de, 16% (6 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (982 ms) belongs to the original domain Dai.de.
Page size can be reduced by 303.3 kB (61%)
494.7 kB
191.3 kB
In fact, the total size of Dai.de main page is 494.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 184.0 kB which makes up the majority of the site volume.
Potential reduce by 24.5 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 4.1 kB, which is 14% 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 24.5 kB or 81% of the original size.
Potential reduce by 7.0 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. Dai images are well optimized though.
Potential reduce by 128.2 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 128.2 kB or 70% of the original size.
Potential reduce by 143.6 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. Dai.de needs all CSS files to be minified and compressed as it can save up to 143.6 kB or 86% of the original size.
Number of requests can be reduced by 11 (38%)
29
18
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
dai.de
381 ms
516 ms
css
68 ms
8cec4fc1ee31.css
437 ms
b84ca0a372d1.js
453 ms
modernizr-2.6.2.min.js
335 ms
jquery.min.js
68 ms
gumby.min.js
331 ms
jquery.tools.min.js
340 ms
jquery.colorbox-min.js
340 ms
plugins.min.js
682 ms
main.min.js
686 ms
css
16 ms
header_bg.png
181 ms
de.gif
268 ms
dai_logo.png
331 ms
bg-header-mainnav.png
332 ms
wir-ueber-uns-bg.png
613 ms
wir-in-europa-bg.png
624 ms
bg-header-subnav-1.png
514 ms
bg-header-subnav-2.png
599 ms
bg-home-stripes-4cols.png
656 ms
bg-home-whitespace.png
664 ms
icon-kompass-home.png
839 ms
gen-icons.png
922 ms
icon-doctor-home.png
934 ms
icon-presse-home.png
954 ms
slider-sprites.png
982 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
57 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
66 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
79 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
94 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
98 ms
mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf
97 ms
piwik.js
788 ms
piwik.php
403 ms
print.css
325 ms
dai.de accessibility score
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
ARIA input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
dai.de 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
General
Impact
Issue
Detected JavaScript libraries
dai.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dai.de 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 Dai.de 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.
dai.de
Open Graph description is not detected on the main page of Dai. 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: