5.4 sec in total
404 ms
3.4 sec
1.6 sec
Visit dahs.de now to see the best up-to-date Dahs content and also check out these interesting facts you probably never knew about dahs.de
Visit dahs.deWe analyzed Dahs.de page load time and found that the first response time was 404 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
dahs.de performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.8 s
56/100
25%
Value4.4 s
75/100
10%
Value90 ms
99/100
30%
Value0.029
100/100
15%
Value3.8 s
89/100
10%
404 ms
114 ms
516 ms
195 ms
217 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 91% of them (84 requests) were addressed to the original Dahs.de, 7% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Dahs.de.
Page size can be reduced by 493.2 kB (49%)
1.0 MB
513.9 kB
In fact, the total size of Dahs.de main page is 1.0 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. 55% of websites need less resources to load. Images take 437.8 kB which makes up the majority of the site volume.
Potential reduce by 128.9 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 48.0 kB, which is 34% 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 128.9 kB or 91% of the original size.
Potential reduce by 20.8 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. Dahs images are well optimized though.
Potential reduce by 179.5 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 179.5 kB or 77% of the original size.
Potential reduce by 164.0 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. Dahs.de needs all CSS files to be minified and compressed as it can save up to 164.0 kB or 85% of the original size.
Number of requests can be reduced by 25 (30%)
82
57
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dahs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
dahs.de
404 ms
114 ms
516 ms
bootstrap.css
195 ms
jquery.fs.selecter.css
217 ms
scojs.css
225 ms
theme.css
229 ms
font-awesome.css
242 ms
refineslide.css
277 ms
refineslide-theme-dark.css
295 ms
jquery.fs.scroller.css
306 ms
jquery.fs.picker.css
307 ms
default.css
307 ms
jquery.js
531 ms
jquery.fs.selecter.js
313 ms
jquery.fs.picker.js
383 ms
jquery.fs.scroller.js
387 ms
jquery.refineslide.js
388 ms
bootstrap.js
392 ms
theme.js
414 ms
sco.modal.js
474 ms
sco.confirm.js
490 ms
sco.ajax.js
488 ms
sco.collapse.js
487 ms
sco.countdown.js
588 ms
sco.message.js
589 ms
default.js
599 ms
604 ms
css
50 ms
css
62 ms
229 ms
242 ms
250 ms
217 ms
263 ms
219 ms
378 ms
402 ms
363 ms
351 ms
391 ms
371 ms
430 ms
450 ms
443 ms
445 ms
662 ms
531 ms
646 ms
539 ms
666 ms
673 ms
843 ms
683 ms
841 ms
846 ms
848 ms
843 ms
849 ms
958 ms
992 ms
968 ms
884 ms
848 ms
903 ms
802 ms
803 ms
819 ms
1220 ms
873 ms
911 ms
f8OBjBbevvywgbyJOxlO7Q.ttf
106 ms
AwBqWF2kjhlybWamaKMPcaCWcynf_cDxXwCLxiixG1c.ttf
110 ms
yVHpdQrmTj9Kax1tmFSx2qCWcynf_cDxXwCLxiixG1c.ttf
111 ms
TttUCfJ272GBgSKaOaD7KqCWcynf_cDxXwCLxiixG1c.ttf
114 ms
kpI87QY2ce-mk2ZnKb-r0g.ttf
108 ms
1TiHc9yag0wq3lDO9cw0vqCWcynf_cDxXwCLxiixG1c.ttf
116 ms
glyphicons-halflings-regular.woff
909 ms
771 ms
952 ms
942 ms
1097 ms
932 ms
1030 ms
1010 ms
1073 ms
1039 ms
923 ms
937 ms
877 ms
944 ms
fs-selecter-arrow.png
728 ms
dahs.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
dahs.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
dahs.de SEO score
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
N/A
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dahs.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Dahs.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.
dahs.de
Open Graph description is not detected on the main page of Dahs. 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: