7.9 sec in total
1.6 sec
5.9 sec
447 ms
Visit g-geschichte.de now to see the best up-to-date G GESCHICHTE content for Germany and also check out these interesting facts you probably never knew about g-geschichte.de
G/Geschichte ist das Magazin für Geschichte
Visit g-geschichte.deWe analyzed G-geschichte.de page load time and found that the first response time was 1.6 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
g-geschichte.de performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value2.3 s
93/100
25%
Value2.4 s
98/100
10%
Value40 ms
100/100
30%
Value0.172
70/100
15%
Value3.2 s
94/100
10%
1555 ms
318 ms
218 ms
222 ms
320 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 83% of them (49 requests) were addressed to the original G-geschichte.de, 10% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain G-geschichte.de.
Page size can be reduced by 888.4 kB (25%)
3.6 MB
2.7 MB
In fact, the total size of G-geschichte.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. 40% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 48.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. 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 48.6 kB or 79% of the original size.
Potential reduce by 72.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. G GESCHICHTE images are well optimized though.
Potential reduce by 307.3 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 307.3 kB or 72% of the original size.
Potential reduce by 459.7 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. G-geschichte.de needs all CSS files to be minified and compressed as it can save up to 459.7 kB or 88% of the original size.
Number of requests can be reduced by 33 (66%)
50
17
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G GESCHICHTE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.g-geschichte.de
1555 ms
wp-emoji-release.min.js
318 ms
styles.css
218 ms
style.css
222 ms
font-awesome.css
320 ms
et-icons.css
222 ms
et-line.css
315 ms
style.min.css
428 ms
lightbox.min.css
333 ms
css
27 ms
css
41 ms
style.css
333 ms
shortcodes.css
431 ms
shortcodes_responsive.css
430 ms
magnific_popup.css
425 ms
jquery.js
688 ms
jquery-migrate.min.js
446 ms
main.js
534 ms
ion.sound.min.js
532 ms
jquery.doubletap.js
535 ms
mtiFontTrackingCode.js
539 ms
microkids-related-posts-default.css
555 ms
frontend-builder-global-functions.js
552 ms
jquery.form.min.js
554 ms
scripts.js
553 ms
wp-lightbox-2.min.js
459 ms
comment-reply.min.js
474 ms
custom.js
557 ms
jquery.fitvids.js
554 ms
waypoints.min.js
557 ms
jquery.magnific-popup.js
570 ms
frontend-builder-scripts.js
692 ms
wp-embed.min.js
604 ms
salvattore.min.js
659 ms
style.css
747 ms
ga.js
215 ms
logo.png
230 ms
GGesch_04_2016_Windsors.jpg
770 ms
GGesch_Rhein.jpg
947 ms
iStock_000023438j751_Small.jpg
429 ms
Dom.jpg
768 ms
Kogge2.jpg
660 ms
IMG_2866.jpg
856 ms
GGE1604_Plus_iStock_ilbusca.jpg
656 ms
GGE1604_Plus_Margaret_Beitragsbild-400x250.jpg
776 ms
Kugel2-400x250.jpg
779 ms
001_Xolotl.jpg
1122 ms
wikinger-vorschau.jpg
2206 ms
GGE1308_Viktoria.jpg
1332 ms
ODelI1aHBYDBqgeIAH2zlDLXPPWpYIJRcQ99gLLWTOQ.woff
18 ms
toadOcfmlt9b38dHJxOBGOHJdKliW2M9IhUT0esa8kM.woff
19 ms
toadOcfmlt9b38dHJxOBGEzfSP8PFPIaW8d4wHl9LSw.woff
20 ms
toadOcfmlt9b38dHJxOBGNF2eBBnhZOFf_rblGEjGiI.woff
19 ms
toadOcfmlt9b38dHJxOBGBgDywzySrQSFSEUM6OqW_g.woff
20 ms
toadOcfmlt9b38dHJxOBGA589pgrPwd9yeXZfWcyCTM.woff
19 ms
ETmodules_v2_4.ttf
1250 ms
62100580-a2d1-4d98-bb14-d4c4c3f1a5ba.woff
780 ms
MinionPro-Regular.otf
1176 ms
__utm.gif
21 ms
g-geschichte.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
g-geschichte.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
g-geschichte.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
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 G-geschichte.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 G-geschichte.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.
g-geschichte.de
Open Graph data is detected on the main page of G GESCHICHTE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: