4.4 sec in total
323 ms
3.4 sec
662 ms
Welcome to inforadio.de homepage info - get ready to check Inforadio best content for Germany right away, or after learning these important things about inforadio.de
Jederzeit umfassend informiert über das Geschehen in Berlin und Brandenburg, Deutschland und der Welt. Live-Hören per mp3, auch für mobile Anwendungen. Aktuelle Interviews, Reportagen, Berichte, Meinu...
Visit inforadio.deWe analyzed Inforadio.de page load time and found that the first response time was 323 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
inforadio.de performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value5.7 s
17/100
25%
Value11.4 s
5/100
10%
Value1,940 ms
8/100
30%
Value0.161
73/100
15%
Value15.1 s
7/100
10%
323 ms
684 ms
639 ms
555 ms
215 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 83% of them (90 requests) were addressed to the original Inforadio.de, 6% (7 requests) were made to Pbs.twimg.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Inforadio.de.
Page size can be reduced by 1.1 MB (30%)
3.6 MB
2.5 MB
In fact, the total size of Inforadio.de main page is 3.6 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. 60% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 150.4 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 150.4 kB or 82% of the original size.
Potential reduce by 130.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. Inforadio images are well optimized though.
Potential reduce by 432.4 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 432.4 kB or 69% of the original size.
Potential reduce by 395.4 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. Inforadio.de needs all CSS files to be minified and compressed as it can save up to 395.4 kB or 85% of the original size.
Number of requests can be reduced by 33 (32%)
102
69
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inforadio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
inforadio.de
323 ms
www.inforadio.de
684 ms
f=css.css
639 ms
f=css2.css
555 ms
property_1.css
215 ms
f=jshead.js
541 ms
property_3.js.js
109 ms
f=js.js
759 ms
jquery.socialshareprivacy.min.js
317 ms
hotfix.js
214 ms
wallpaper.jpg
312 ms
spr_logo.png
106 ms
logo_red.png
109 ms
ico_search.png
108 ms
320000.png
111 ms
330100.png
216 ms
110000.png
209 ms
330000.png
215 ms
120000.png
210 ms
bg_topnav_shadow.png
314 ms
img.png
317 ms
img.png
321 ms
bg_nav_level1_full.png
322 ms
size=470x264.jpg
545 ms
size=470x264.jpg
556 ms
size=470x264.jpg
546 ms
size=470x264.jpg
548 ms
size=470x264.jpg
550 ms
size=470x264.jpg
551 ms
size=470x264.jpg
554 ms
size=470x264.jpg
555 ms
size=470x264.jpg
557 ms
size=98x55.jpg
558 ms
size=98x55.jpg
575 ms
size=98x55.jpg
624 ms
size=98x55.jpg
623 ms
size=98x55.jpg
626 ms
size=98x55.jpg
633 ms
size=98x55.jpg
634 ms
size=98x55.jpg
679 ms
size=98x55.jpg
727 ms
expandableArrows.png
727 ms
livestream_inf.gif
729 ms
ico_livestream.gif
736 ms
widgets.js
94 ms
ico_plusminus.png
688 ms
b850db31-9043-48a9-9105-f6215999635a-3.woff
810 ms
3d6b9143-eb88-4451-80b0-7d05bd58b8a1-3.woff
857 ms
RBB-Icon-Font.woff
727 ms
ico_traffic_plus.png
729 ms
ico_traffic_minus.png
654 ms
321000.png
654 ms
320030.png
751 ms
rendition=tisch%2520975.jpg.jpg
1041 ms
rendition=kinosaal%25202%2520breit.jpg.jpg
965 ms
rendition=rolls_royce__blankenfelde9%2520breit.jpg.jpg
752 ms
rendition=revolte%2520breit.jpg.jpg
1099 ms
img.jpg
737 ms
rendition=ingo_kahle___sigmar%2520breit.jpg.jpg
934 ms
iam.js
401 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
125 ms
MobileMainNav.js
624 ms
MobileContentNav.js
628 ms
GallerySlider.js
714 ms
GalleryThumblist.js
727 ms
ReloadContent.js
809 ms
Slider.js
809 ms
FooterLinks.js
823 ms
rendition=buecherdiebin%2520breit.jpg.jpg
936 ms
rendition=kirchgaenger%2520breit.jpg.jpg
1032 ms
img.jpg
1009 ms
rendition=podium_forum_harald.jpg.jpg
1211 ms
size=98x55.jpg
899 ms
size=98x55.jpg
895 ms
size=98x55.jpg
950 ms
size=98x55.jpg
961 ms
size=98x55.jpg
990 ms
size=98x55.jpg
1037 ms
syndication
91 ms
611463095811186688
193 ms
size=98x55.jpg
1000 ms
hit.xiti
226 ms
size=98x55.jpg
966 ms
size=98x55.jpg
968 ms
size=98x55.jpg
999 ms
spr_topnav_shadow.png
1046 ms
ico_rss.png
1046 ms
tx.io
205 ms
bg_overlay.png
966 ms
bg_footer.jpg
946 ms
logo_footer.png
972 ms
spr_footer_expand.png
1025 ms
spr_footer_logos.png
957 ms
size=470x264.jpg
927 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
43 ms
size=470x264.jpg
907 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
50 ms
tx.io
96 ms
oZnbRxRt_normal.jpeg
100 ms
ZYF2LkHu_normal.png
77 ms
CcYE4y7W0AAkRBL.jpg
47 ms
CcYBtpAWwAE_xGq.jpg
97 ms
CcXuiUuW4AAeCrG.jpg
47 ms
CcXSkDxWEAAg0_K.jpg
48 ms
CcTMJcjWAAEMXs9.jpg
48 ms
jot
26 ms
Logging.js
556 ms
print.css
108 ms
inforadio.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
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.
inforadio.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
inforadio.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Inforadio.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 Inforadio.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.
inforadio.de
Open Graph description is not detected on the main page of Inforadio. 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: