Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

luzern.com

The Official Lucerne & Lake Lucerne Region Guide | Luzern.com

Page Load Speed

2.7 sec in total

First Response

393 ms

Resources Loaded

2 sec

Page Rendered

291 ms

luzern.com screenshot

About Website

Click here to check amazing Luzern content for Switzerland. Otherwise, check out these important facts you probably never knew about luzern.com

Spend your holidays in the city of Lucerne and discover the diversity of the Lucerne-Lake Lucerne Region. The City. The Lake. The Mountains.

Visit luzern.com

Key Findings

We analyzed Luzern.com page load time and found that the first response time was 393 ms and then it took 2.3 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

luzern.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value1,800 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value25.1 s

0/100

10%

Network Requests Diagram

luzern.com

393 ms

www.luzern.com

322 ms

179 ms

jquery-1.5.1.min.js

270 ms

modernizr-1.7.min.js

190 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 56% of them (41 requests) were addressed to the original Luzern.com, 29% (21 requests) were made to Images.pxlpartner.ch.s3.amazonaws.com and 3% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (696 ms) relates to the external source Images.pxlpartner.ch.s3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 414.6 kB (33%)

Content Size

1.2 MB

After Optimization

831.5 kB

In fact, the total size of Luzern.com main page is 1.2 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. Images take 696.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 56.3 kB

  • Original 67.2 kB
  • After minification 66.6 kB
  • After compression 10.9 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 56.3 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 17.5 kB

  • Original 696.9 kB
  • After minification 679.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. Luzern images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 231.9 kB

  • Original 352.3 kB
  • After minification 347.6 kB
  • After compression 120.4 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 231.9 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 108.9 kB

  • Original 129.8 kB
  • After minification 103.0 kB
  • After compression 20.9 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. Luzern.com needs all CSS files to be minified and compressed as it can save up to 108.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (54%)

Requests Now

68

After Optimization

31

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

Accessibility Review

luzern.com accessibility score

79

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

luzern.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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

luzern.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

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 Luzern.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 Luzern.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 Luzern. 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: