4.8 sec in total
337 ms
4.1 sec
415 ms
Click here to check amazing Oetinger content for Germany. Otherwise, check out these important facts you probably never knew about oetinger.de
Erlebe mit uns spannende Geschichten in Kinder- & Jugendbüchern: Von Pippi Langstrumpf bis Tintenwelt – finde deine Lieblingsgeschichte. Jetzt entdecken!
Visit oetinger.deWe analyzed Oetinger.de page load time and found that the first response time was 337 ms and then it took 4.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.
oetinger.de performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value9.7 s
0/100
25%
Value7.0 s
32/100
10%
Value680 ms
43/100
30%
Value0.503
16/100
15%
Value9.6 s
29/100
10%
337 ms
546 ms
188 ms
192 ms
190 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 97% of them (60 requests) were addressed to the original Oetinger.de, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Oetinger.de.
Page size can be reduced by 212.2 kB (15%)
1.4 MB
1.2 MB
In fact, the total size of Oetinger.de main page is 1.4 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. 20% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 25.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 25.2 kB or 76% of the original size.
Potential reduce by 93.5 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. Oetinger images are well optimized though.
Potential reduce by 49.2 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 49.2 kB or 57% of the original size.
Potential reduce by 44.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. Oetinger.de needs all CSS files to be minified and compressed as it can save up to 44.4 kB or 84% of the original size.
Number of requests can be reduced by 22 (37%)
60
38
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oetinger. 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 11 to 1 for CSS and as a result speed up the page load time.
oetinger.de
337 ms
www.oetinger.de
546 ms
stylesheet_f646f7d0ca.css
188 ms
basic.css
192 ms
oetinger.css
190 ms
extensions.css
193 ms
warenkorb_oetinger.css
195 ms
jquery-1.2.1.pack.js
367 ms
jquery.jqModal.js
372 ms
jquery.form.js
467 ms
advents_kalender.js
376 ms
tx_enetimageguard.js
376 ms
jsfunc.validateform.js
374 ms
javascript_757c080409.js
555 ms
cssstyledcontent.css
367 ms
indexedsearch.css
370 ms
newloginbox.css
372 ms
srfeuserregister.css
374 ms
srsendcard.css
463 ms
adventskalender_2007.css
550 ms
ga.js
39 ms
oetinger_bg.png
187 ms
__utm.gif
24 ms
vlgsgruppe_oe2.gif
189 ms
figuren_oetinger_201311.gif
831 ms
bg_topmenu.gif
187 ms
kleiner_pfeil5.gif
185 ms
vlgsgruppe_oe1.gif
190 ms
hauptnavi_bg.png
370 ms
oetinger_aktiv.png
374 ms
oetinger_oetinger34_out.png
372 ms
oetinger_audio_out.png
374 ms
kinderkino_out.png
376 ms
dressler_out.png
555 ms
ellermann_out.png
558 ms
oetinger_logo_gr.gif
652 ms
content_bg_oetinger.png
749 ms
cb_head_bg.png
763 ms
suchen_button.gif
742 ms
wahrenkorb.png
926 ms
RTEmagicC_oetinger34_2.jpg.jpg
928 ms
RTEmagicC_TigerCreate_2.jpg.jpg
1018 ms
RTEmagicC_TigerBooks_2.jpg.jpg
1140 ms
RTEmagicC_onilo_2.jpg.jpg
1061 ms
RTEmagicC_framily_2_01.jpg.jpg
1194 ms
Thabo_teaser_334x250.jpg
1609 ms
teaser_oster-olchi_334x250.jpg
1488 ms
b1347e1585.jpg
1733 ms
teaser334x250.jpg
1706 ms
Kakadu-Kukuda_Teaser_334x250.jpg
1877 ms
Digby_Teaser_334x250px.jpg
1852 ms
c2ecb04dc3.jpg
2284 ms
Blaubeerhaus.png
2440 ms
facebook.png
2006 ms
youtube.png
2010 ms
googleplus.png
2153 ms
instagram.png
2175 ms
pinterest.png
2286 ms
bg_logomenu.png
2036 ms
atrium-logo.gif
2164 ms
656f13a3a2.png
2185 ms
nord-sued-logo.jpg
2214 ms
oetinger.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-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
oetinger.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
oetinger.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
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oetinger.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 Oetinger.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
oetinger.de
Open Graph description is not detected on the main page of Oetinger. 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: