6.9 sec in total
177 ms
6.1 sec
572 ms
Welcome to radioplayer.de homepage info - get ready to check Radioplayer best content for Germany right away, or after learning these important things about radioplayer.de
Die besten deutschen Radiosender kostenlos hören. Direkt im Browser, als Mobile-App, auf SmartTVs, via Sonos und BOSE oder Amazon Alexa.
Visit radioplayer.deWe analyzed Radioplayer.de page load time and found that the first response time was 177 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
radioplayer.de performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value24.5 s
0/100
25%
Value9.1 s
14/100
10%
Value2,880 ms
3/100
30%
Value0
100/100
15%
Value12.3 s
15/100
10%
177 ms
175 ms
268 ms
178 ms
269 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 76% of them (35 requests) were addressed to the original Radioplayer.de, 11% (5 requests) were made to Google-analytics.com and 4% (2 requests) were made to Static.radioplayer.de. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Radioplayer.de.
Page size can be reduced by 151.5 kB (16%)
929.1 kB
777.5 kB
In fact, the total size of Radioplayer.de main page is 929.1 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. 55% of websites need less resources to load. Images take 720.6 kB which makes up the majority of the site volume.
Potential reduce by 23.2 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.2 kB or 73% of the original size.
Potential reduce by 13.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. Radioplayer images are well optimized though.
Potential reduce by 115.1 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 115.1 kB or 65% of the original size.
Number of requests can be reduced by 11 (28%)
40
29
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Radioplayer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
index.html
177 ms
merged-8ec582e92a654868f8f119f3ec2c7f39-f4745c50e78fb0914f671a3da07c47d2.css.gzip
175 ms
radioplayer.min-8d58378276bed6e47496a1a1cb10a82b.css.gzip
268 ms
undohtml-1880b85e1c3d2023e72693cabfd3f917.css.gzip
178 ms
screen-4800461d0a2ff275559bc2d160a37701.css.gzip
269 ms
jquery.fancybox-1eae45da976f27d022511322bd399462.css.gzip
180 ms
merged-e2322b42b0bc541b1235d59c46aaf198-d468a059ead9d792079043d9f039cc53.js.gzip
635 ms
merged-69b1b4a5a4376acde2b82d00cae1b82f-f9f49406305212214644389b79c4e944.js.gzip
348 ms
merged-0567532497d951b6f4835cf2b3121559-e92f82934ff4e0fc56854e05bffede30.js.gzip
443 ms
analytics.js
48 ms
bg.jpg
419 ms
sprite.svg
423 ms
logo.svg
418 ms
visualBG.jpg
4314 ms
sprite.png
444 ms
spinner.gif
416 ms
visualLola.png
4318 ms
visualLolaCut.png
4311 ms
store-android.png
441 ms
store-apple.png
441 ms
store-windows.png
443 ms
store-amazon.png
444 ms
store-small-android.png
444 ms
store-small-apple.png
444 ms
store-small-windows.png
479 ms
store-small-amazon.png
479 ms
appweb-sizer600x450.gif
480 ms
devices_tablets_start.png
4311 ms
rp_home_smartphones_wp.png
4315 ms
kreon-bold.woff
4286 ms
kreon-regular.woff
4286 ms
jwpsrv.js
3900 ms
faqClose.svg
3901 ms
linkid.js
28 ms
kreon-light.woff
3831 ms
nearby.json
3785 ms
analytics.html
366 ms
StationList.js
366 ms
faqOpen.svg
90 ms
heart-sprite.png
179 ms
collect
13 ms
collect
69 ms
ga-audiences
38 ms
12
172 ms
ga.js
21 ms
__utm.gif
19 ms
radioplayer.de accessibility score
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
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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
radioplayer.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
radioplayer.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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Radioplayer.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Radioplayer.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.
radioplayer.de
Open Graph data is detected on the main page of Radioplayer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: