4.6 sec in total
823 ms
3.3 sec
448 ms
Visit blog.travelgenio.de now to see the best up-to-date Blog Travelgenio content for Germany and also check out these interesting facts you probably never knew about blog.travelgenio.de
Visit blog.travelgenio.deWe analyzed Blog.travelgenio.de page load time and found that the first response time was 823 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
blog.travelgenio.de performance score
823 ms
281 ms
372 ms
193 ms
199 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 60% of them (55 requests) were addressed to the original Blog.travelgenio.de, 10% (9 requests) were made to W.sharethis.com and 5% (5 requests) were made to Sd.sharethis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Blog.travelgenio.de.
Page size can be reduced by 597.0 kB (33%)
1.8 MB
1.2 MB
In fact, the total size of Blog.travelgenio.de main page is 1.8 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. 45% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 42.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 7.8 kB, which is 15% 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 42.7 kB or 80% of the original size.
Potential reduce by 89.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. Blog Travelgenio images are well optimized though.
Potential reduce by 407.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 407.3 kB or 71% of the original size.
Potential reduce by 57.8 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. Blog.travelgenio.de needs all CSS files to be minified and compressed as it can save up to 57.8 kB or 83% of the original size.
Number of requests can be reduced by 29 (33%)
88
59
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Travelgenio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
blog.travelgenio.de
823 ms
style.css
281 ms
modernizr-2.5.3.js
372 ms
widget.css
193 ms
pagenavi-css.css
199 ms
buttons.js
11 ms
loader.js
12 ms
followme.js
279 ms
jquery-1.8.1.min.js
498 ms
acordeon.js
286 ms
wp-embed.min.js
286 ms
conversion.js
20 ms
ga.js
68 ms
wp-emoji-release.min.js
186 ms
travelgenio.png
187 ms
buttonmid.gif
185 ms
twitter.png
188 ms
googleplus.png
190 ms
facebook.png
556 ms
luxemburgo-travelgenio.jpg
836 ms
Madrid-Travelgenio.jpg
831 ms
Francia-Travelgenio.jpg
780 ms
hoteles-tematicos-travelgenio.jpg
556 ms
Invierno-Travelgenio.jpg
829 ms
Tailandia-Travelgenio.jpg
1016 ms
ulan-bator-travelgenio.jpg
1168 ms
pekin-travelgenio.jpg
1360 ms
de-470x257-2.jpg
1298 ms
Desierto-Travelgenio.jpg
1204 ms
payment_methods.png
1112 ms
list.png
1180 ms
facebook.png
1284 ms
es1.png
1332 ms
fr1.png
1366 ms
de1.png
1369 ms
ku1.png
1461 ms
pt1.png
1469 ms
it1.png
1516 ms
nl1.png
1518 ms
se1.png
1557 ms
no1.png
1555 ms
sw1.png
1662 ms
at1.png
1652 ms
fi1.png
1714 ms
dk1.png
1714 ms
be1.png
1767 ms
ie1.png
1764 ms
sg1.png
1835 ms
__utm.gif
13 ms
ar1.png
1710 ms
br1.png
1745 ms
nz1.png
1751 ms
au1.png
1775 ms
us1.png
1778 ms
297 ms
getAllAppDefault.esi
188 ms
tr1.png
1512 ms
gr1.png
1510 ms
in1.png
1559 ms
39 ms
getSegment.php
174 ms
checkOAuth.esi
6 ms
ca1.png
1346 ms
mx1.png
1318 ms
arrow_up_footer.png
1324 ms
t.dhj
7 ms
t.dhj
11 ms
cm
16 ms
x35248
104 ms
s-3271.xgi
12 ms
hbpix
26 ms
12 ms
pixel
18 ms
xrefid.xgi
10 ms
9 ms
2981
25 ms
hoverbuttons.6eab8de2ee93b309873157b6d3f977fe.css
23 ms
hoverbuttons.035267d71d894482eb413e5bea488ff5.js
24 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
32 ms
buttons.ab966a004186897711de4a5ed256c924.css
20 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
12 ms
st.1188278743c14064d5e8ae56c8ada29c.js
17 ms
__utm.gif
29 ms
mini_Top_Cap.png
24 ms
facebook_32.png
12 ms
mini_BG.png
10 ms
mini_Bottom_Cap.png
11 ms
twitter_32.png
12 ms
email_32.png
11 ms
sharethis_32.png
11 ms
pinterest_32.png
12 ms
blog.travelgenio.de SEO score
DE
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.travelgenio.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 Spanish language. Our system also found out that Blog.travelgenio.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.
blog.travelgenio.de
Open Graph description is not detected on the main page of Blog Travelgenio. 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: