6.4 sec in total
1.1 sec
5.1 sec
190 ms
Visit erklaerbaeren.de now to see the best up-to-date Erklaerbaeren content and also check out these interesting facts you probably never knew about erklaerbaeren.de
Die Idee zum Kegelclub “Erklärbären” entstand auf einem sagenumwogenen Männerabend Anfang des Jahres 2001.Wie es weiterging erfährst du hier!
Visit erklaerbaeren.deWe analyzed Erklaerbaeren.de page load time and found that the first response time was 1.1 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
erklaerbaeren.de performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
1050 ms
213 ms
319 ms
215 ms
218 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 46% of them (42 requests) were addressed to the original Erklaerbaeren.de, 27% (25 requests) were made to Static.xx.fbcdn.net and 21% (19 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Erklaerbaeren.de.
Page size can be reduced by 441.7 kB (51%)
865.9 kB
424.2 kB
In fact, the total size of Erklaerbaeren.de main page is 865.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. 65% of websites need less resources to load. Images take 520.3 kB which makes up the majority of the site volume.
Potential reduce by 15.7 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.3 kB, which is 11% 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 15.7 kB or 76% of the original size.
Potential reduce by 191.8 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, Erklaerbaeren needs image optimization as it can save up to 191.8 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 176.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 176.7 kB or 69% of the original size.
Potential reduce by 57.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. Erklaerbaeren.de needs all CSS files to be minified and compressed as it can save up to 57.4 kB or 84% of the original size.
Number of requests can be reduced by 57 (63%)
90
33
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Erklaerbaeren. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
www.erklaerbaeren.de
1050 ms
style.css
213 ms
jquery.js
319 ms
jquery-migrate.min.js
215 ms
jquery.prettyPhoto.js
218 ms
jquery.nivo.slider.pack.js
220 ms
jqueryslidemenu.js
215 ms
jquery.kwicks.min.js
411 ms
jquery.tools.tabs.min.js
403 ms
functions.js
409 ms
prettyPhoto.css
583 ms
nivo-slider.css
580 ms
kwicks.css
596 ms
custom_style.php
1059 ms
plugin.css
619 ms
datatables.css
627 ms
comment-reply.min.js
792 ms
wp-embed.min.js
793 ms
reset.css
587 ms
grid.css
611 ms
jqueryslidemenu.css
622 ms
wp-emoji-release.min.js
205 ms
eb-logo-original1.gif
303 ms
timthumb.php
744 ms
arrow_grey.png
303 ms
timthumb.php
356 ms
likebox.php
884 ms
vertical-line2.png
198 ms
topwrapper.png
206 ms
mainwrapper.png
217 ms
bgheader.jpg
658 ms
topmenu.png
385 ms
bg-dropdown.png
398 ms
button-right.png
402 ms
button-left.png
412 ms
bgboximg2.png
582 ms
sidebartop.png
596 ms
sidebarmain.png
610 ms
bgheading.png
607 ms
arrow.png
743 ms
sidebarbottom.png
965 ms
bottomwrapper.png
964 ms
bg-copyright.png
964 ms
analytics.js
102 ms
collect
13 ms
ebiMDO3r-8l.css
31 ms
wakJkBioHgT.css
32 ms
6qHpHChjY_J.css
39 ms
ztINr5qMqM_.css
41 ms
uVjHKJ0glvg.css
60 ms
HMnVPFsQWIQ.css
47 ms
ZY-3seVVf0G.css
49 ms
q68gy-v_YMF.js
69 ms
FJmpeSpHpjS.js
85 ms
0wM5s1Khldu.js
84 ms
1bNoFZUdlYZ.js
83 ms
njO1TPvGzoR.js
95 ms
1QuX41zDRrx.js
95 ms
Oagsvfb4VWi.js
98 ms
LTv6ZK-5zxz.js
102 ms
1FCa-btixu2.js
97 ms
394389_345357435510884_23417468_n.jpg
133 ms
static_map.php
265 ms
safe_image.php
36 ms
11223694_982163931830228_8499307147578266469_n.jpg
57 ms
12119046_882155898534048_4931041522560996144_n.jpg
70 ms
12439243_741297816003289_2790074094761515042_n.jpg
65 ms
11351162_10203416571129992_5318086365172639500_n.jpg
45 ms
11988547_10207349405524372_8552444836179529992_n.jpg
33 ms
1901251_1412707592315875_629873359_n.jpg
41 ms
12688352_206286633058647_8572384168954282807_n.jpg
108 ms
12645165_1966100943614995_7930404172495523723_n.jpg
45 ms
10676297_845537655508114_8309910227008488535_n.jpg
49 ms
10505301_597821920337981_757918823673883664_n.jpg
58 ms
10731193_801381219929554_1730059780619857309_n.jpg
66 ms
11050667_839868542769444_7541803879246688532_n.jpg
67 ms
601114_343671219068320_1623742416_n.jpg
97 ms
1098154_376499979144736_2061184642_n.jpg
134 ms
12799328_1056831254363495_7642855511315975551_n.jpg
107 ms
1209218_397788387015344_16249599_n.png
91 ms
12646983_1044997898880164_6633551709407267076_n.jpg
139 ms
12650836_1043191985727422_3751153644124231113_n.jpg
463 ms
wL6VQj7Ab77.png
20 ms
s7jcwEQH7Sx.png
22 ms
sSwLTfB7PfP.png
19 ms
QDwYpIaRyfG.png
20 ms
yDaBsYcc9pr.png
19 ms
01TjtkIxVPt.png
21 ms
K00K-UgnsKu.png
25 ms
I6-MnjEovm5.js
7 ms
pQrUxxo5oQp.js
2 ms
erklaerbaeren.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
Document doesn't have a <title> element
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
erklaerbaeren.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
erklaerbaeren.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Erklaerbaeren.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 Erklaerbaeren.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.
erklaerbaeren.de
Open Graph data is detected on the main page of Erklaerbaeren. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: