Access lilienberg.ch. Hotel, Restaurant, Konferenz- und Seminarlocation am Bodensee

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value26.1 s

0/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value4,680 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value25.6 s

0/100

10%

lilienberg.ch

303 ms

www.lilienberg.ch

406 ms

colorbox.css

103 ms

base.css

204 ms

skeleton.css

206 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 61% of them (75 requests) were addressed to the original Lilienberg.ch, 21% (26 requests) were made to Maps.googleapis.com and 7% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Lilienberg.ch.

Content Size

2.0 MB

After Optimization

1.0 MB

In fact, the total size of Lilienberg.ch main page is 2.0 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. 65% of websites need less resources to load. Javascripts take 973.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 55.7 kB

Original 69.1 kB
After minification 68.6 kB
After compression 13.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 55.7 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 19.9 kB

Original 720.8 kB
After minification 700.9 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. Lilienberg images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 674.7 kB

Original 973.6 kB
After minification 916.6 kB
After compression 298.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 674.7 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 186.0 kB

Original 219.1 kB
After minification 140.7 kB
After compression 33.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. Lilienberg.ch needs all CSS files to be minified and compressed as it can save up to 186.0 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

<html> element does not have a valid value for its [lang] attribute.

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

High

Document doesn't have a valid hreflang

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/).

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 Lilienberg.ch 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 Lilienberg.ch 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

lilienberg.ch

Open Graph description is not detected on the main page of Lilienberg. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

Hotel, Restaurant, Konferenz- und Seminarlocation am Bodensee

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

lilienberg.ch

www.lilienberg.ch

colorbox.css

base.css

skeleton.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

lilienberg.ch

www.lilienberg.ch

colorbox.css

base.css

skeleton.css

layout.css

dynamiccontent_dynamicformular.css

jquery.fancybox-1.3.4.css

jquery-ui-1.8.12.custom.css

font-awesome.min.css

template_base_print.css

template_all_print.css

jquery.js

jquery.imgr.js

cs_js_lib.js

jquery-ui.js

jquery.easing-1.3.pack.js

jquery.mousewheel.js

jquery.fancybox-1.3.4.pack.js

jquery.fancynavigation.js

jquery.cycle.js

js

gmap3.js

dynamiccontent.css

dynamicformular.css

css

kategorie.css

kopfbilder.css

news.css

veranstaltungen.css

jquery.fancynavigation.css

layout.css

blog.css

download.css

konferenzraum.css

kontakt.css

publikation.css

suche.css

formular.css

analytics.js

lilienberg.svg

g_titelbild30.jpg

g_098.JPG