6.9 sec in total
941 ms
5.7 sec
254 ms
Visit historeo.de now to see the best up-to-date HISTOREO content for Germany and also check out these interesting facts you probably never knew about historeo.de
Historeo ist ein unabhängiges Online-Magazin für Hintergrund-Informationen: Historische und gesellschaftliche Zusammenhänge und Tipps für kritische Köpfe.
Visit historeo.deWe analyzed Historeo.de page load time and found that the first response time was 941 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
historeo.de performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value4.9 s
29/100
25%
Value8.7 s
16/100
10%
Value130 ms
96/100
30%
Value0.041
99/100
15%
Value5.8 s
67/100
10%
941 ms
109 ms
210 ms
213 ms
312 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 53% of them (52 requests) were addressed to the original Historeo.de, 8% (8 requests) were made to Platform.twitter.com and 8% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Historeo.de.
Page size can be reduced by 934.7 kB (44%)
2.1 MB
1.2 MB
In fact, the total size of Historeo.de main page is 2.1 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. 70% of websites need less resources to load. Javascripts take 935.4 kB which makes up the majority of the site volume.
Potential reduce by 155.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. 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 155.7 kB or 78% of the original size.
Potential reduce by 59.1 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. HISTOREO images are well optimized though.
Potential reduce by 632.0 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 632.0 kB or 68% of the original size.
Potential reduce by 87.9 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. Historeo.de needs all CSS files to be minified and compressed as it can save up to 87.9 kB or 68% of the original size.
Number of requests can be reduced by 57 (61%)
94
37
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HISTOREO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.historeo.de
941 ms
style.css
109 ms
style-font.css
210 ms
style-responsive.css
213 ms
widget.css
312 ms
avatars.css
315 ms
imgareaselect.css
416 ms
dashicons.min.css
524 ms
thickbox.css
519 ms
output.css
624 ms
styles.css
627 ms
pagenavi-css.css
728 ms
wpp.css
730 ms
colorbox.css
831 ms
jquery.js
944 ms
jquery-migrate.min.js
937 ms
flexslider.js
1042 ms
external.js
1049 ms
suckerfish.js
1146 ms
suckerfish-cat.js
1152 ms
jquery.mobilemenu.js
1251 ms
default.css
1256 ms
custom.css
1355 ms
addthis_widget.js
15 ms
jquery.imgareaselect.min.js
1384 ms
thickbox.js
1459 ms
jquery.form.min.js
1462 ms
scripts.js
1563 ms
jquery.colorbox.1.5.9.js
1570 ms
css
25 ms
ga.js
6 ms
__utm.gif
12 ms
__utm.gif
28 ms
nav-rss.png
352 ms
historeo-titel.png
449 ms
catnav-bg.png
564 ms
mehmed-der-eroberer-150x150.jpg
780 ms
albigenser-kreuzzug-150x150.jpg
1060 ms
hereroaufstand-1904-gefangene-herero-e1389541720682-150x150.jpg
1303 ms
fabian-window-e1388934400643-150x150.jpg
1321 ms
chlebowski-Bajasid-timur-1878-e1375021164129-150x150.jpg
1527 ms
mehmed-der-eroberer-585x300.jpg
1547 ms
albigenser-kreuzzug-585x300.jpg
1863 ms
hereroaufstand-1904-gefangene-herero-585x300.jpg
1775 ms
fabian-window-585x300.jpg
2363 ms
chlebowski-Bajasid-timur-1878-585x300.jpg
2001 ms
geo-epoche-63-alexander-rezension-e1387048465857-150x150.jpg
1979 ms
geo-epoche-62-piraten-rezension-e1383831846700-150x150.jpg
2118 ms
historeo-doku-logo.png
2105 ms
facebook.png
2210 ms
twitter.png
2222 ms
google-plus.png
2315 ms
feed.png
2327 ms
gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf
9 ms
gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf
22 ms
loading.gif
2428 ms
bullet.png
2419 ms
widgets.js
92 ms
like.php
178 ms
300lo.json
41 ms
de.js
31 ms
counter.5524cceca805eb4b9b2b.js
29 ms
all.js&version=v2.0
110 ms
plusone.js
61 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
207 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
244 ms
loadingAnimation.gif
2215 ms
overlay.png
2284 ms
sh.8e5f85691f9aaa082472a194.html
48 ms
TY3MhkXpWJ-.js
87 ms
LVx-xkvaJ0b.png
109 ms
shares.json
78 ms
layers.e5ea973510bf60b3db41.js
42 ms
cb=gapi.loaded_0
64 ms
cb=gapi.loaded_1
63 ms
fastbutton
122 ms
68 ms
postmessageRelay
77 ms
xd_arbiter.php
46 ms
xd_arbiter.php
69 ms
cb=gapi.loaded_0
38 ms
cb=gapi.loaded_1
38 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
78 ms
3193398744-postmessagerelay.js
41 ms
rpc:shindig_random.js
46 ms
syndication
116 ms
317244300108890112
158 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.de.html
49 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.de.html
69 ms
cb=gapi.loaded_0
28 ms
info.json
87 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
29 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
33 ms
jot.html
31 ms
97db98d7bdf7ee648ba37b837a29ec6a_normal.png
27 ms
jot
28 ms
ping
59 ms
like.php
94 ms
historeo.de accessibility score
historeo.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
historeo.de SEO score
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Historeo.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 Historeo.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.
historeo.de
Open Graph description is not detected on the main page of HISTOREO. 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: