5.4 sec in total
305 ms
4.7 sec
472 ms
Visit dragonland-radio.de now to see the best up-to-date Dragonland Radio content and also check out these interesting facts you probably never knew about dragonland-radio.de
Alles, was das Radio, das Team und die Webseite betrifft
Visit dragonland-radio.deWe analyzed Dragonland-radio.de page load time and found that the first response time was 305 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster. This domain responded with an error, which can significantly jeopardize Dragonland-radio.de rating and web reputation
dragonland-radio.de performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value10.8 s
0/100
25%
Value4.7 s
69/100
10%
Value310 ms
77/100
30%
Value0.784
5/100
15%
Value10.0 s
26/100
10%
305 ms
945 ms
195 ms
198 ms
198 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 96% of them (74 requests) were addressed to the original Dragonland-radio.de, 1% (1 request) were made to Cdn.jsdelivr.net and 1% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Dragonland-radio.de.
Page size can be reduced by 236.3 kB (35%)
681.9 kB
445.6 kB
In fact, the total size of Dragonland-radio.de main page is 681.9 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. 35% of websites need less resources to load. Images take 464.0 kB which makes up the majority of the site volume.
Potential reduce by 41.0 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 41.0 kB or 81% of the original size.
Potential reduce by 58.4 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. Obviously, Dragonland Radio needs image optimization as it can save up to 58.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 97.6 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 97.6 kB or 82% of the original size.
Potential reduce by 39.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. Dragonland-radio.de needs all CSS files to be minified and compressed as it can save up to 39.2 kB or 82% of the original size.
Number of requests can be reduced by 38 (51%)
74
36
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dragonland Radio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
dragonland-radio.de
305 ms
www.dragonland-radio.de
945 ms
e107.css
195 ms
backcompat.css
198 ms
tooltip.css
198 ms
all.jquery.css
198 ms
prettyPhoto.css
202 ms
divascookies_style_dark_top.css
293 ms
style.css
386 ms
jquery.min.js
53 ms
jquery.once.min.js
46 ms
bootstrap-tooltip.js
386 ms
jquery.raty.js
390 ms
jquery.prettyPhoto.js
400 ms
front.jquery.js
487 ms
all.jquery.js
578 ms
jquery.divascookies-0.6.min.js
582 ms
tsstatus.css
585 ms
nav_menu.css
597 ms
nav_menu.js
649 ms
clock.js
677 ms
blank.png
203 ms
pagebg.jpg
490 ms
header.jpg
385 ms
navtop.png
290 ms
wink.png
247 ms
shy.png
285 ms
shades.png
381 ms
cry.png
443 ms
heart.png
483 ms
amazed.png
486 ms
cheesey.png
578 ms
biglaugh.png
577 ms
smile.png
638 ms
rss2.png
676 ms
rss4.png
681 ms
thumb.php
728 ms
thumb.php
804 ms
nonew_comments.png
771 ms
thumb.php
879 ms
thumb.php
1932 ms
thumb.php
1937 ms
thumb.php
961 ms
thumb.php
1002 ms
thumb.php
2032 ms
thumb.php
1109 ms
16x16_server_green.png
1151 ms
16x16_channel_green.png
1208 ms
16x16_default.png
1305 ms
16x16_channel_red.png
1342 ms
16x16_register.png
1403 ms
16x16_channel_yellow.png
1501 ms
streamcontrol.php
1568 ms
m_top_b.png
1559 ms
m_top_l.png
1652 ms
m_top_r.png
1748 ms
log.php
1767 ms
m_l.png
1717 ms
m_r.png
1757 ms
m_bot_b.png
1817 ms
m_bot_l.png
1811 ms
m_bot_r.png
1745 ms
tbox.png
1748 ms
finfo.png
1757 ms
fhead2.png
1754 ms
fhead3.png
1806 ms
fhead.png
1816 ms
navdown.png
1842 ms
radiologo.png
437 ms
ap_0000005_dlr-drago-145x145.jpg
802 ms
vlcplayer.png
784 ms
winamp.png
816 ms
itunes.png
871 ms
wmp.png
882 ms
flash.png
980 ms
lastplayed.png
1186 ms
wunsch_box.png
997 ms
dragonland-radio.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 progressbar elements do not have accessible names.
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
dragonland-radio.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
dragonland-radio.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
N/A
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dragonland-radio.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 Dragonland-radio.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.
dragonland-radio.de
Open Graph description is not detected on the main page of Dragonland Radio. 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: