Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

reichegger.com

Hotel South Tyrol - Hotel Reichegger *** in Uttenheim - Start Page

Page Load Speed

22.3 sec in total

First Response

335 ms

Resources Loaded

21.8 sec

Page Rendered

192 ms

reichegger.com screenshot

About Website

Welcome to reichegger.com homepage info - get ready to check Reichegger best content right away, or after learning these important things about reichegger.com

Our Hotel is situated in the beautiful Uttenheim, 7 km away from the Kronplatz in South Tyrol. Whether you want to hike, explore nature or simply relax, our hotel is the choice for you!

Visit reichegger.com

Key Findings

We analyzed Reichegger.com page load time and found that the first response time was 335 ms and then it took 22 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

reichegger.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

reichegger.com

335 ms

www.reichegger.com

408 ms

www.reichegger.com

562 ms

d6563cc1c3fc.css

112 ms

be2ebe8d7ed4.js

332 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 45% of them (53 requests) were addressed to the original Reichegger.com, 9% (11 requests) were made to Holidaycheck.de and 5% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Tripadvisor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 159.3 kB (22%)

Content Size

724.8 kB

After Optimization

565.5 kB

In fact, the total size of Reichegger.com main page is 724.8 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. Javascripts take 426.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 60.6 kB

  • Original 78.8 kB
  • After minification 69.8 kB
  • After compression 18.2 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 9.0 kB, which is 11% 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 60.6 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 3.9 kB

  • Original 182.3 kB
  • After minification 178.4 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. Reichegger images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 69.1 kB

  • Original 426.0 kB
  • After minification 426.0 kB
  • After compression 356.8 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 69.1 kB or 16% of the original size.

CSS Optimization

-68%

Potential reduce by 25.7 kB

  • Original 37.7 kB
  • After minification 37.7 kB
  • After compression 12.0 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. Reichegger.com needs all CSS files to be minified and compressed as it can save up to 25.7 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (46%)

Requests Now

95

After Optimization

51

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

Accessibility Review

reichegger.com accessibility score

59

Accessibility Issues

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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.

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

High

<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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

reichegger.com best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

reichegger.com SEO score

82

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reichegger.com 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 Reichegger.com 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 description is not detected on the main page of Reichegger. 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: