3.8 sec in total
298 ms
3.2 sec
364 ms
Visit reisegeier.de now to see the best up-to-date Reisegeier content for Germany and also check out these interesting facts you probably never knew about reisegeier.de
Traumreisen zu Tiefpreisen! | reisegeier.de
Visit reisegeier.deWe analyzed Reisegeier.de page load time and found that the first response time was 298 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
reisegeier.de performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value7.4 s
4/100
25%
Value10.6 s
7/100
10%
Value620 ms
48/100
30%
Value0.001
100/100
15%
Value12.7 s
14/100
10%
298 ms
464 ms
293 ms
387 ms
400 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Reisegeier.de, 18% (12 requests) were made to Www3.reisegeier.de and 13% (9 requests) were made to Css.rgei.de. The less responsive or slowest element that took the longest time to load (805 ms) relates to the external source Jpg.rgei.de.
Page size can be reduced by 551.5 kB (35%)
1.6 MB
1.0 MB
In fact, the total size of Reisegeier.de main page is 1.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 819.5 kB which makes up the majority of the site volume.
Potential reduce by 26.0 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 5.3 kB, which is 16% 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 26.0 kB or 80% of the original size.
Potential reduce by 22.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. Reisegeier images are well optimized though.
Potential reduce by 185.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 185.3 kB or 57% of the original size.
Potential reduce by 317.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. Reisegeier.de needs all CSS files to be minified and compressed as it can save up to 317.4 kB or 82% of the original size.
Number of requests can be reduced by 29 (45%)
64
35
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reisegeier. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
reisegeier.de
298 ms
www.reisegeier.de
464 ms
qf1_12_05_31.css
293 ms
ss_13_12_19.css
387 ms
reisegeier.css
400 ms
standard_14_07_08.css
295 ms
jquery-1.7.2.min.js
411 ms
jquery-ui-1.8.20.min.js
400 ms
s_14_08_04.js
477 ms
reisegeier_14_06_18.js
401 ms
conversion.js
15 ms
bodyBg1.jpg
729 ms
sprite-head-foot1.png
540 ms
startform
566 ms
navi4.png
520 ms
newsletter
778 ms
hotline.png
208 ms
boxes3.png
578 ms
spriteIcons2.png
530 ms
promo2_11_08_15.jpg
612 ms
reiseveranstalter5.png
805 ms
ga.js
36 ms
adition.js
365 ms
secure_tag_head_ad1_adfarm1.js
368 ms
61 ms
activityi;src=4389083;type=pausc0;cat=reise0;ord=8266235992778.093
48 ms
__utm.gif
19 ms
__utm.gif
28 ms
36 ms
index2012Cat_rb33100b.css
499 ms
uid.html
89 ms
js
176 ms
586 ms
291 ms
indexCat_rb33100b.css
415 ms
ua.js
312 ms
banner
174 ms
splitprocessing.php
165 ms
655 ms
282 ms
215 ms
display.js
89 ms
reisegeierSprite_rb33100b.png
589 ms
uid.js
216 ms
display-iframe.html
247 ms
srp.js
368 ms
preloaderBack_rb33100b.png
136 ms
15 ms
117 ms
2016,2017
265 ms
lastbooking
160 ms
startImg_rb33100b.jpg
411 ms
spriteIcons_rb33100b.png
485 ms
9cx59x0x0x68x3h.png
86 ms
dcx7hx0xkx68x3h.jpg
171 ms
9cx59x0x0x68x3h.jpg
192 ms
9cx59x0x0x68x3h.jpg
170 ms
js
194 ms
ci.html
281 ms
rc
218 ms
102 ms
checkuser
160 ms
ibeLoad.gif
138 ms
banner
177 ms
1x1.gif
87 ms
nlBar_rb33100b.png
229 ms
s
178 ms
i
281 ms
reisegeier.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.
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 IDs are not unique
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
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
<object> elements do not have alternate text
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
reisegeier.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
reisegeier.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document uses plugins
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reisegeier.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 Reisegeier.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.
reisegeier.de
Open Graph description is not detected on the main page of Reisegeier. 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: