Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

veranda.at

Gut Guntrams | Naturhotels bei Wien - Kristallgarten - Veranda mit Shop

Page Load Speed

2.1 sec in total

First Response

20 ms

Resources Loaded

1.9 sec

Page Rendered

171 ms

veranda.at screenshot

About Website

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

Naturhotels bei Wien - Kristallgarten - Veranda mit Shop

Visit veranda.at

Key Findings

We analyzed Veranda.at page load time and found that the first response time was 20 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

veranda.at performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

veranda.at

20 ms

guntrams11.at

507 ms

gutguntrams.at

499 ms

script.js

17 ms

styles.css

98 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Veranda.at, 93% (37 requests) were made to Gutguntrams.at and 3% (1 request) were made to Guntrams11.at. The less responsive or slowest element that took the longest time to load (902 ms) relates to the external source Gutguntrams.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 191.1 kB (13%)

Content Size

1.4 MB

After Optimization

1.2 MB

In fact, the total size of Veranda.at main page is 1.4 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 36.9 kB

  • Original 43.0 kB
  • After minification 42.9 kB
  • After compression 6.1 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 36.9 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.1 MB
  • After minification 1.1 MB

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

JavaScript Optimization

-64%

Potential reduce by 154.0 kB

  • Original 240.3 kB
  • After minification 240.3 kB
  • After compression 86.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 154.0 kB or 64% of the original size.

CSS Optimization

-1%

Potential reduce by 244 B

  • Original 17.4 kB
  • After minification 17.4 kB
  • After compression 17.2 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. Veranda.at has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (43%)

Requests Now

37

After Optimization

21

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

Accessibility Review

veranda.at accessibility score

95

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.

Best Practices

veranda.at best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

veranda.at SEO score

97

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Veranda.at 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 Veranda.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

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