DILLY.AT Wellnesshotel in Oberösterreich, Windischgarsten - Wellnesshotel Dilly 4****S


dilly.at website information.

dilly.at domain name is registered by .AT top-level domain registry. See the other sites registred in .AT domain zone.

Following name servers are specified for dilly.at domain:

  • ns1037.ui-dns.de
  • ns1037.ui-dns.com
  • ns1037.ui-dns.org
  • ns1037.ui-dns.biz

and probably website dilly.at is hosted by CLOUDFLARENET - Cloudflare, Inc., US web hosting company. Check the complete list of other most popular websites hosted by CLOUDFLARENET - Cloudflare, Inc., US hosting company.

According to Alexa traffic rank the highest website dilly.at position was 10369 (in the world). The lowest Alexa rank position was 999562. Now website dilly.at ranked in Alexa database as number 775412 (in the world).

Website dilly.at Desktop speed measurement score (89/100) is better than the results of 87.7% of other sites and shows that the page is performing great on desktop computers.

dilly.at Mobile usability score (94/100) is better than the results of 36.81% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of dilly.at (76/100) is better than the results of 85.22% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-30-2024 775,412-20,726
Nov-29-2024 754,686591
Nov-28-2024 755,277-5,238
Nov-27-2024 750,0395,311
Nov-26-2024 755,3502,084
Nov-25-2024 757,4342,752
Nov-24-2024 760,1863,858

Advertisement

dilly.at Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



dilly.at whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


% Copyright (c)2022 by NIC.AT (1)
%
% Restricted rights.
%
% Except for agreed Internet operational purposes, no part of this
% information may be reproduced, stored in a retrieval system, or
% transmitted, in any form or by any means, electronic, mechanical,
% recording, or otherwise, without prior permission of NIC.AT on behalf
% of itself and/or the copyright holders. Any use of this material to
% target advertising or similar activities is explicitly forbidden and
% can be prosecuted.
%
% It is furthermore strictly forbidden to use the Whois-Database in such
% a way that jeopardizes or could jeopardize the stability of the
% technical systems of NIC.AT under any circumstances. In particular,
% this includes any misuse of the Whois-Database and any use of the
% Whois-Database which disturbs its operation.
%
% Should the user violate these points, NIC.AT reserves the right to
% deactivate the Whois-Database entirely or partly for the user.
% Moreover, the user shall be held liable for any and all damage
% arising from a violation of these points.

% Quota exceeded

dilly.at server information

Servers Location

IP Address
37.186.138.155
Country
Italy
Region
Trentino-Alto Adige
City
Bolzano

dilly.at desktop page speed rank

Last tested: 2019-11-07


Desktop Speed Good
89/100

dilly.at Desktop Speed Test Quick Summary


priority - 5 Reduce server response time

In our test, your server responded in 0.68 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

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

Your page has 1 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.

Optimize CSS Delivery of the following:

https://www.dilly.at/(cms)/module/pass/5/combine/e…8944d86.1572517818.css

priority - 1 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:

https://customer.kunleisys.com/widget/default.css (expiration not specified)
https://customer.kunleisys.com/widget/default.png (expiration not specified)
https://fonts-api.viomassl.com/css?family=Roboto|Roboto+Condensed (60 minutes)

priority - 0 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 3.1KiB (21% reduction).

Compressing https://customer.kunleisys.com/widget/default.png could save 1.5KiB (22% reduction).
Compressing https://www.dilly.at/media/48304/service-newsletter-1455631.png could save 336B (31% reduction).
Compressing https://www.dilly.at/media/48304/service-360-1455636.png could save 316B (17% reduction).
Compressing https://www.dilly.at/media/48304/service-dillys-world-1455634.png could save 285B (16% reduction).
Compressing https://www.dilly.at/media/48304/servicer-last-minute-1455635.png could save 265B (23% reduction).
Compressing https://www.dilly.at/media/48304/service-bonus-1455630.png could save 239B (19% reduction).
Compressing https://www.dilly.at/media/48304/service-star-1455633.png could save 181B (24% reduction).

priority - 0 Minify JavaScript

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

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

Minifying https://www.dilly.at/(cms)/module/static/customer/…a/js/social_media.js?3 could save 710B (34% reduction) after compression.
Minifying https://www.dilly.at/(cms)/module/static/default/content/libs/js/general.js could save 209B (13% reduction) after compression.

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 122B (25% reduction).

Minifying https://customer.kunleisys.com/widget/default.css could save 122B (25% reduction) after compression.

dilly.at Desktop Resources

Total Resources49
Number of Hosts6
Static Resources43
JavaScript Resources4
CSS Resources4

dilly.at Desktop Resource Breakdown

dilly.at mobile page speed rank

Last tested: 2017-05-16


Mobile Speed Medium
76/100

dilly.at Mobile Speed Test Quick Summary


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

Your page has 7 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.

Optimize CSS Delivery of the following:

http://www.dilly.at/(cms)/module/pass/5/combine/eJ…b97ef09.1494847092.css
http://fonts.googleapis.com/css?family=Roboto|Roboto+Condensed
http://hotel-dilly2.clients.clearingstation.de/cus…css?version=1494953510
http://www.dilly.at/(cms)/module/static/customer/2…_media/css/default.css
http://www.dilly.at/(cms)/module/static/customer/2…almedia-moz-webkit.css
http://www.dilly.at/(cms)/module/static/customer/2…default-buttons.css?v1
http://www.dilly.at/(cms)/module/static/customer/2…gal/css/legal-hint.css

priority - 4 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:

https://static.doubleclick.net/instream/ad_status.js (15 minutes)
http://connect.facebook.net/de_DE/all.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/1260822940666996?v=2.7.9 (20 minutes)
http://www.google-analytics.com/plugins/ua/ecommerce.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
https://hotel-barometer.com/wellness-golf-ski-fami…=1&width=192&details=1 (8.6 hours)

priority - 1 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 12.2KiB (22% reduction).

Compressing https://hotel-barometer.com/wellness-golf-ski-fami…=1&width=192&details=1 could save 3.2KiB (14% reduction).
Compressing http://www.dilly.at/media/0/dilly-logo-1455485.png could save 2KiB (25% reduction).
Compressing http://www.dilly.at/media/34388/golf-logo-1009146.png could save 1.6KiB (38% reduction).
Compressing http://www.dilly.at/media/34388/spa-logo-1009166.png could save 1.4KiB (41% reduction).
Compressing http://www.dilly.at/media/34388/famillotel-logo-1009145.png could save 1.4KiB (38% reduction).
Compressing http://www.tripadvisor.at/img/cdsi/img2/awards/CoE…idgetAsset-14348-2.png could save 1.3KiB (21% reduction).
Compressing https://www.tripadvisor.at/img/cdsi/img2/awards/Co…idgetAsset-14348-2.png could save 1.3KiB (22% reduction).

priority - 0 Minify JavaScript

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

Minify JavaScript for the following resources to reduce their size by 4KiB (37% reduction).

Minifying http://www.dilly.at/(cms)/module/static/customer/2….socialshareprivacy.js could save 2KiB (36% reduction) after compression.
Minifying https://www.tripadvisor.at/WidgetEmbed-certificate…tionId=565539&uniq=357 could save 1.3KiB (40% reduction) after compression.
Minifying http://www.dilly.at/(cms)/module/static/customer/2…a/js/social_media.js?3 could save 710B (34% reduction) after compression.

priority - 0 Reduce server response time

In our test, your server responded in 0.22 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 739B (18% reduction).

Minifying http://hotel-dilly2.clients.clearingstation.de/cus…css?version=1494953510 could save 739B (18% reduction) after compression.

dilly.at Mobile Resources

Total Resources94
Number of Hosts25
Static Resources59
JavaScript Resources23
CSS Resources10

dilly.at Mobile Resource Breakdown

dilly.at mobile page usability

Last tested: 2017-05-16


Mobile Usability Good
94/100

dilly.at Mobile Usability Test Quick Summary


priority - 3 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 541 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <li class="slide">Pfingstferien…Kooperationen</li> falls outside the viewport.

priority - 2 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 <a href="/de/hotel/">4* Superior Ho…indischgarsten</a> is close to 1 other tap targets.
The tap target <a href="/de/hotel/anreise-lage/">Lage &amp; Anfahrt</a> and 9 others are close to other tap targets.
The tap target <a href="https://www.tr…r_Austria.html">Dilly&#39;s Wellness Hotel</a> is close to 1 other tap targets.
The tap target <a href="/de/">© 2014 Dilly&#39;s…nesshotel GmbH</a> is close to 1 other tap targets.
The tap target <a href="/de/">© 2014 Dilly&#39;s…nesshotel GmbH</a> is close to 1 other tap targets.
The tap target <a href="/de/hotel/pressebereich/">Presse</a> and 2 others are close to other tap targets.

dilly.at similar domains

Similar domains:
www.dilly.com
www.dilly.net
www.dilly.org
www.dilly.info
www.dilly.biz
www.dilly.us
www.dilly.mobi
www.illy.at
www.dilly.at
www.xilly.at
www.dxilly.at
www.xdilly.at
www.silly.at
www.dsilly.at
www.sdilly.at
www.eilly.at
www.deilly.at
www.edilly.at
www.rilly.at
www.drilly.at
www.rdilly.at
www.filly.at
www.dfilly.at
www.fdilly.at
www.cilly.at
www.dcilly.at
www.cdilly.at
www.dlly.at
www.dully.at
www.diully.at
www.duilly.at
www.djlly.at
www.dijlly.at
www.djilly.at
www.dklly.at
www.diklly.at
www.dkilly.at
www.dolly.at
www.diolly.at
www.doilly.at
www.dily.at
www.diply.at
www.dilply.at
www.diplly.at
www.dioly.at
www.diloly.at
www.dikly.at
www.dilkly.at
www.dilpy.at
www.dillpy.at
www.diloy.at
www.dilloy.at
www.dilky.at
www.dillky.at
www.dill.at
www.dillt.at
www.dillyt.at
www.dillty.at
www.dillg.at
www.dillyg.at
www.dillgy.at
www.dillh.at
www.dillyh.at
www.dillhy.at
www.dillu.at
www.dillyu.at
www.dilluy.at

dilly.at Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


dilly.at TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.