Tools & Wizards About Us
dilly.at screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

dilly.at

Wellness Hotel Upper Austria: Hotel in the Austrian Alps - Dilly National Park Resort

Page Load Speed

6.4 sec in total

First Response

1.2 sec

Resources Loaded

4 sec

Page Rendered

1.2 sec

dilly.at screenshot

About Website

Visit dilly.at now to see the best up-to-date Dilly content for Austria and also check out these interesting facts you probably never knew about dilly.at

The ☙ Wellness Hotel Dilly located in the Austrian Alps in Upper Austria is the perfect place to enjoy your holiday. ☝ Book now!

Visit dilly.at

Key Findings

We analyzed Dilly.at page load time and found that the first response time was 1.2 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

dilly.at performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

1-0.html

1168 ms

gtm.js

136 ms

loader.js

72 ms

logo.png

311 ms

dsc09911-hdr.jpg

490 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 30% of them (6 requests) were addressed to the original Dilly.at, 25% (5 requests) were made to Cloud.zeppelin-group.com and 20% (4 requests) were made to App.usercentrics.eu. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Cloud.zeppelin-group.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 450.9 kB (57%)

Content Size

785.7 kB

After Optimization

334.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Dilly.at main page is 785.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. HTML takes 524.3 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 450.9 kB

  • Original 524.3 kB
  • After minification 523.9 kB
  • After compression 73.4 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 450.9 kB or 86% of the original size.

Image Optimization

-7%

Potential reduce by 35 B

  • Original 522 B
  • After minification 487 B

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. Dilly images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 260.9 kB
  • After minification 260.9 kB
  • After compression 260.9 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 5 (31%)

Requests Now

16

After Optimization

11

  • AJAX
  • Images
  • JavaScript

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dilly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

1-0.html

1-0.html

1168 ms

gtm.js

gtm.js

136 ms

loader.js

loader.js

72 ms

logo.png

logo.png

311 ms

dsc09911-hdr.jpg

dsc09911-hdr.jpg

490 ms

SangBleuSunrise-Regular.woff

SangBleuSunrise-Regular.woff

1220 ms

embed.min.js

embed.min.js

116 ms

v131_302_304_329_306_303_314_307_308_331_334_309_343_340_315_305_321_322_327_312_311.js

v131_302_304_329_306_303_314_307_308_331_334_309_343_340_315_305_321_322_327_312_311.js

358 ms

1

1

1983 ms

logo-inv.png

logo-inv.png

545 ms

zeppelin-weiss.png

zeppelin-weiss.png

559 ms

SpeziaWide-Book.woff

SpeziaWide-Book.woff

1157 ms

SpeziaWide-SemiBold.woff

SpeziaWide-SemiBold.woff

1108 ms

bundle_legacy.js

bundle_legacy.js

39 ms

languages.json

languages.json

121 ms

de.json

de.json

155 ms

cross-domain-bridge.html

cross-domain-bridge.html

6 ms

1px.png

1px.png

17 ms

translations-de.json

translations-de.json

5 ms

gruppe-647.png

gruppe-647.png

164 ms

Accessibility Review

dilly.at accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

dilly.at best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dilly.at SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dilly.at can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Dilly.at 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.

Social Sharing Optimization

dilly.at

Open Graph data is detected on the main page of Dilly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: