3.5 sec in total
332 ms
3 sec
110 ms
Click here to check amazing OHRKA content for Germany. Otherwise, check out these important facts you probably never knew about ohrka.de
Bekannte und beliebte Stimmen wie Anke Engelke oder Katharina Thalbach lesen Hörspiele und Hörbücher für Kinder. Über 80 Stunden anhören. Kostenlos, werbefrei. Auch zum downloaden. Pädi-Gütesiegel 201...
Visit ohrka.deWe analyzed Ohrka.de page load time and found that the first response time was 332 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ohrka.de performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value4.2 s
44/100
25%
Value7.3 s
29/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value4.3 s
84/100
10%
332 ms
875 ms
114 ms
219 ms
304 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 97% of them (69 requests) were addressed to the original Ohrka.de, 3% (2 requests) were made to Matomo.ohrka.de. The less responsive or slowest element that took the longest time to load (933 ms) belongs to the original domain Ohrka.de.
Page size can be reduced by 278.3 kB (64%)
433.9 kB
155.6 kB
In fact, the total size of Ohrka.de main page is 433.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. 25% of websites need less resources to load. Images take 350.0 kB which makes up the majority of the site volume.
Potential reduce by 16.6 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 2.6 kB, which is 12% 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 16.6 kB or 76% of the original size.
Potential reduce by 219.9 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, OHRKA needs image optimization as it can save up to 219.9 kB or 63% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 41.7 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 41.7 kB or 67% of the original size.
Number of requests can be reduced by 49 (71%)
69
20
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OHRKA. 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 10 to 1 for CSS and as a result speed up the page load time.
ohrka.de
332 ms
www.ohrka.de
875 ms
basis.css
114 ms
7015c8c4ac.css
219 ms
navigation.css
304 ms
hoeren.css
309 ms
formular.css
319 ms
infobox.css
321 ms
player.css
317 ms
sm2_button.css
325 ms
jquery-3.2.1.min.js
544 ms
jquery-ui.min.js
682 ms
nb_main.js
426 ms
soundmanager2.js
636 ms
sm2_button.js
432 ms
object2vr_player.js
459 ms
hoeren.js
541 ms
e9e07c5ca0.js
541 ms
jquery-ui.min.css
474 ms
font-awesome.min.css
549 ms
hoeren.png
121 ms
hoeren_act.png
117 ms
fragen.png
113 ms
fragen_act.png
125 ms
suchen.png
115 ms
suchen_act.png
106 ms
bckgr_k.png
323 ms
logo.png
348 ms
flasche.png
389 ms
player_li.png
220 ms
pl_gs_kinderministerium.png
224 ms
kapitel_li.png
231 ms
1.png
325 ms
2.png
328 ms
3.png
340 ms
4.png
434 ms
5.png
432 ms
6.png
433 ms
7.png
448 ms
8.png
457 ms
9.png
499 ms
kapitel_re.png
536 ms
info.png
540 ms
8_pl.png
537 ms
player_re.png
557 ms
player-bckgr.gif
697 ms
play.png
608 ms
fischlinie_player.png
647 ms
fisch_player.png
651 ms
download.png
644 ms
bewerten.png
674 ms
kommentar.png
719 ms
play_gr.png
747 ms
anke.png
933 ms
5_.png
755 ms
8_.png
768 ms
matomo.js
664 ms
reportagen.png
701 ms
slider_re.png
724 ms
1_act.png
750 ms
2_act.png
747 ms
3_act.png
778 ms
4_act.png
797 ms
5_act.png
724 ms
6_act.png
747 ms
7_act.png
736 ms
8_act.png
685 ms
9_act.png
704 ms
linie_weiss_grau.png
713 ms
linie_weiss_blau.png
711 ms
matomo.php
300 ms
ohrka.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
Image elements do not have [alt] attributes
ohrka.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
ohrka.de SEO score
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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ohrka.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 Ohrka.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.
ohrka.de
Open Graph description is not detected on the main page of OHRKA. 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: