Hotel.Idealo.De receives about 1,896,152 unique visitors and 5,328,187 (2.81 per visitor) page views per day which should earn about $24,574.45/day from advertising revenue. Estimated site value is $17,989,210.45. According to Alexa Traffic Rank is ranked number 1,476 in the world and 0.0418% of global Internet users visit it. Site is hosted in Germany and links to network IP address This server supports HTTPS and doesn't support HTTP/2.

About -

Preisvergleich und Online-Shopping: Bei die günstigsten Preise der Online-Shops finden
Die idealo Hotelsuche findet die besten Preise für Hotelzimmer online. Jetzt die Hotelsuchmaschine starten und Hotels beim Hotel-Preisvergleich Nr. 1 buchen.
Edit Site Info

Technologies used on Website

Currently Not Available Profile

Title: Hotels günstig buchen | idealo Hotelsuche & Hotelvergleich
Keywords: mit können sie hotels weltweit online günstig buchen. der hotel preisvergleich hilft ihnen mit hotelbewertungen bei der suche nach einem luxushotel, wellnesshotel oder tagungshotel.
Last update was 48 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

1.9M daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
1,476 visit alexa
Alexa Reach:
0.0418%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources


Visitors by country

Germany 91.4%92.1%29
Switzerland 1.1%0.7%1006
Austria 0.8%0.4%1022
Luxembourg 0.7%0.4%275
United States 0.6%0.6%43545
Czech Republic 0.6%1.4%900

Where do visitors go on this site?


Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
Last Change Time:
(The last time that the site changed status.)
2018-06-20 16:41:11
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)

Mobile summary

Last Change Time:
(The last time that the site changed status.)
2018-06-20 02:08:18
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)

+ Abusive Experience Report

Root domain:
Last Change Time:
(The last time that the site changed status.)
2018-06-20 16:41:11
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Germany 4,907,260$23,702.07
United States 31,969$366.69
Switzerland 37,297$226.39
Czech Republic 74,595$161.87
Austria 21,313$69.27
Luxembourg 21,313$48.17

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Germany 1,423,105$6,873.60
United States 5,754$66.00
Switzerland 6,714$40.75
Austria 5,541$18.01
Czech Republic 7,459$16.19
Luxembourg 3,197$7.23

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Server Location:

Germany, DE

Other sites hosted on

There are no other sites hosted on this IP

+ How fast does load?

Average Load Time:
(1690 ms) 52 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)1.3s % of loads for this page have a fast (<1s) First Contentful Paint (FCP) 55% 40% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 40% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)335ms 76% of loads for this page have a fast (<100ms) First Input Delay (FID) 76% 16% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 16% 6% of loads for this page have a slow (>300ms) First Input Delay (FID) 6%

Origin Data

All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)1.9s 31% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 31% 61% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 61% 7% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 7%
First Input Delay (FID)337ms % of loads for this page have a fast (<100ms) First Input Delay (FID) 85% 8% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 8% 5% of loads for this page have a slow (>300ms) First Input Delay (FID) 5%

Lab Data

Max Potential First Input Delay 370 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 7.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint (3G) 5190 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 410 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 80 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 3.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 6.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 2.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms119 ms0 KB0 KB301
120 ms414 ms17 KB108 KB200text/htmlDocument
432 ms609 ms2 KB3 KB200application/javascriptScript
432 ms750 ms67 KB413 KB200text/cssStylesheet
432 ms554 ms8 KB19 KB200application/javascriptScript
433 ms598 ms5 KB5 KB200image/pngImage
600 ms617 ms11 KB11 KB200image/pngImage
620 ms690 ms23 KB23 KB200image/pngImage
691 ms708 ms1 KB1 KB200image/pngImage
709 ms872 ms139 KB502 KB200application/javascriptScript
557 ms564 ms11 KB25 KB200text/javascriptScript
566 ms751 ms1 KB1 KB200application/javascriptScript
752 ms757 ms18 KB43 KB200text/javascriptScript
773 ms793 ms27 KB121 KB200application/x-javascriptScript
781 ms800 ms10 KB30 KB200text/javascriptScript
782 ms806 ms8 KB23 KB200application/javascriptScript
782 ms1370 ms9 KB18 KB200application/x-javascriptScript
782 ms889 ms2 KB4 KB200text/cssStylesheet
755 ms774 ms1 KB2 KB200text/cssStylesheet
796 ms870 ms2 KB3 KB200image/svg+xmlImage
796 ms943 ms53 KB190 KB200image/svg+xmlImage
797 ms854 ms1 KB1 KB200image/svg+xmlImage
797 ms855 ms1 KB0 KB200image/svg+xmlImage
797 ms874 ms1 KB1 KB200image/svg+xmlImage
798 ms814 ms1 KB1 KB200image/svg+xmlImage
798 ms873 ms1 KB0 KB200image/svg+xmlImage
798 ms1005 ms1 KB1 KB200image/svg+xmlImage
803 ms897 ms62 KB62 KB200image/pngImage
803 ms1156 ms56 KB56 KB200image/pngImage
803 ms884 ms51 KB50 KB200image/pngImage
803 ms904 ms59 KB59 KB200image/pngImage
804 ms1086 ms45 KB45 KB200image/pngImage
804 ms1149 ms58 KB57 KB200image/pngImage
804 ms975 ms51 KB50 KB200image/pngImage
805 ms1033 ms30 KB29 KB200image/pngImage
805 ms949 ms50 KB50 KB200image/pngImage
806 ms877 ms45 KB45 KB200image/pngImage
807 ms949 ms56 KB56 KB200image/pngImage
807 ms935 ms69 KB68 KB200image/pngImage
810 ms865 ms16 KB16 KB200application/font-woffFont
876 ms885 ms2 KB2 KB200text/javascriptScript<=927&evt=pageLoad&msclkid=N&rn=683418
957 ms1001 ms0 KB0 KB204text/plainImage
1011 ms1028 ms2 KB2 KB200text/javascriptScript
1020 ms1041 ms5 KB11 KB200text/htmlDocument
1021 ms1128 ms2 KB4 KB200text/cssStylesheet
1090 ms1295 ms0 KB0 KB200application/jsonXHR
1092 ms1119 ms109 KB436 KB200application/x-javascriptScript
1127 ms1142 ms1 KB0 KB200image/gifImage
1159 ms1174 ms1 KB0 KB200image/gifImage
1168 ms1186 ms1 KB0 KB200application/jsonFetch
1203 ms1234 ms1 KB0 KB200image/gifImage
1562 ms1571 ms1 KB0 KB302text/html
1571 ms1581 ms1 KB0 KB302text/html
1581 ms1590 ms1 KB0 KB200image/gifImage[DataLayer]=%5B%5D&cd[Meta]=%7B%22title%22%3A%22Hotels%20g%C3%BCnstig%20buchen%20%7C%20idealo%20Hotelsuche%20%26%20Hotelvergleich%22%2C%22meta%3Adescription%22%3A%22Die%20idealo%20Hotelsuche%20findet%20die%20besten%20Preise%20f%C3%BCr%20Hotelzimmer%20online.%20Jetzt%20die%20Hotelsuchmaschine%20starten%20und%20Hotels%20beim%20Hotel-Preisvergleich%20Nr.%201%20buchen.%22%7D&cd[OpenGraph]=%7B%7D&cd[][JSON-LD]=%5B%5D&sw=412&sh=660&v=2.9.14&r=stable&ec=1&o=30&fbp=fb.1.1575799518138.1918821495&it=1575799518030&coo=false&es=automatic&tm=3&rqm=GET
1709 ms1725 ms0 KB0 KB200image/gifImage
2042 ms2090 ms1 KB0 KB302
2090 ms2198 ms1 KB1 KB200application/x-javascriptScript
2204 ms2307 ms0 KB0 KB200text/htmlDocument
Serve static assets with an efficient cache policy - 5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
1200000 ms109 KB
1200000 ms27 KB
7200000 ms18 KB
86400000 ms10 KB
535441000 ms1 KB
Minimize third-party usage - Third-party code blocked the main thread for 70 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

SizeMain-Thread Blocking Time
137 KB42 ms
18 KB28 ms
19 KB0 ms
16 KB0 ms
8 KB0 ms
2 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
438 ms
9 ms
773 ms
17 ms
799 ms
10 ms
809 ms
61 ms
874 ms
8 ms
884 ms
14 ms
904 ms
15 ms
929 ms
15 ms
947 ms
22 ms
970 ms
8 ms
982 ms
35 ms
1017 ms
7 ms
1024 ms
9 ms
1046 ms
67 ms
1117 ms
30 ms
1149 ms
12 ms
1162 ms
6 ms
1191 ms
33 ms
1397 ms
186 ms
1645 ms
27 ms
1673 ms
24 ms
1723 ms
7 ms
2331 ms
56 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
55 ms
Reduce JavaScript execution time - 1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
1430 ms59 ms10 ms
1340 ms1175 ms32 ms
154 ms119 ms34 ms
113 ms105 ms8 ms
89 ms71 ms18 ms
57 ms47 ms10 ms
Defer offscreen images - Potential savings of 193 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

SizePotential Savings
59 KB59 KB
56 KB50 KB
50 KB50 KB
23 KB23 KB
11 KB11 KB
Properly size images - Potential savings of 3 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
5 KB3 KB
Remove unused CSS - Potential savings of 63 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

SizePotential Savings
67 KB63 KB
Avoids enormous network payloads - Total size was 1,194 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

139 KB
109 KB
69 KB
67 KB
62 KB
59 KB
58 KB
56 KB
56 KB
53 KB
Minimize main-thread work - 3.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
Script Evaluation
1714 ms
561 ms
Style & Layout
462 ms
Garbage Collection
183 ms
Parse HTML & CSS
157 ms
Script Parsing & Compilation
153 ms
133 ms
Serve images in next-gen formats - Potential savings of 366 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

SizePotential Savings
56 KB48 KB
68 KB43 KB
45 KB40 KB
56 KB36 KB
59 KB31 KB
50 KB31 KB
62 KB28 KB
57 KB25 KB
50 KB24 KB
45 KB22 KB
29 KB22 KB
50 KB18 KB
Avoid an excessive DOM size - 931 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 58 requests • 1,194 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
581194 KB
30734 KB
14347 KB
471 KB
322 KB
116 KB
63 KB
00 KB
501163 KB
Eliminate render-blocking resources - Potential savings of 450 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
2 KB180
67 KB1230
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Avoid chaining critical requests - 6 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 290 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:***4aff3654e.css

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 67% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (20 minutes)***513148?v=2.9.14&r=stable (20 minutes) (30 minutes) (60 minutes)******ytics.js (2 hours) (2.5 hours)

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <div class="cc-window cc-f…ide--157421440">Wenn Du unsere…tzerklärung.OK</div> is close to 1 other tap targets .
The tap target <a href="" class="travel-navbar-…etup-img hotel"></a> is close to 1 other tap targets .
The tap target <div id="top-hotels-box1" class="tile col-***s-1…-sm-6 col-md-4">Hotels in Berl…. B. Amsterdam</div> is close to 1 other tap targets .
The tap target <a href="https://hotel.…rdam-s2759794/">Städtetrip z. B. Amsterdam</a> and 9 others are close to other tap targets.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 2.2KiB (16% reduction).

Minifying could save 2.2KiB (16% reduction) after compression.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 250B (22% reduction).

Minifying could save 250B (22% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Optimize images
Your images are optimized. Learn more about optimizing images.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 107.96 KB
Compressed size: 16.28 KB
File reduced by: 91.67 KB (84%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name: *
Issuer: Thawte RSA CA 2018
Valid from: Mar 9 00:00:00 2018 GMT
Valid until: Feb 7 12:00:00 2020 GMT
Authority: Is not a CA
Common Name: Thawte RSA CA 2018
Organization: DigiCert Inc,
Location: US
Issuer: DigiCert Global Root CA
Valid from: Nov 6 12:23:52 2017 GMT
Valid until: Nov 6 12:23:52 2027 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)


+ Http Header

Connection: Keep-Alive
Content-Length: 0

HTTP/1.1 200 OK
Date: Sat, 07 Dec 2019 14:20:59 GMT
Content-Type: text/html; charset=UTF-8
X-Frame-Options: SAMEORIGIN
Content-Encoding: gzip
X-Age: 71042
X-Cache: HIT
X-Cache-Hits: 2159
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 16672
Connection: close
Accept-Ranges: bytes

+ DNS Lookup

Type Ip Target TTL
TXT 263
A 263

+ Whois Lookup

Domain Created:
Domain Age:

whois lookup at
Status: connect
Last update was 48 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

9 secs
1 min
1 min
2 mins
2 mins
3 mins
4 mins
4 mins
4 mins
4 mins
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget