Tools & Wizards About Us
luzern.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

luzern.org

Lucerne Tourism - Luzern Tourismus

Page Load Speed

3.2 sec in total

First Response

391 ms

Resources Loaded

2.5 sec

Page Rendered

276 ms

luzern.org screenshot

About Website

Welcome to luzern.org homepage info - get ready to check Luzern best content right away, or after learning these important things about luzern.org

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

Key Findings

We analyzed Luzern.org page load time and found that the first response time was 391 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

luzern.org performance score

0

Network Requests Diagram

luzern.org

391 ms

www.luzern.org

392 ms

www.luzern.com

417 ms

208 ms

jquery-1.5.1.min.js

358 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Luzern.org, 54% (40 requests) were made to Luzern.com and 28% (21 requests) were made to Images.pxlpartner.ch.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (739 ms) relates to the external source Images.pxlpartner.ch.s3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 418.2 kB (34%)

Content Size

1.2 MB

After Optimization

824.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Luzern.org 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 692.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 57.2 kB

  • Original 68.2 kB
  • After minification 67.6 kB
  • After compression 11.0 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 57.2 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 20.2 kB

  • Original 692.8 kB
  • After minification 672.6 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.org 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

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

luzern.org

luzern.org

391 ms

www.luzern.org

www.luzern.org

392 ms

www.luzern.com

www.luzern.com

417 ms

208 ms

jquery-1.5.1.min.js

jquery-1.5.1.min.js

358 ms

modernizr-1.7.min.js

modernizr-1.7.min.js

180 ms

style.css

style.css

180 ms

style_resize.css

style_resize.css

182 ms

jquery-ui-1.8.14.custom.css

jquery-ui-1.8.14.custom.css

182 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

181 ms

leaflet.css

leaflet.css

268 ms

responsive-table.css

responsive-table.css

268 ms

ui.datepicker-en.js

ui.datepicker-en.js

394 ms

plusone.js

plusone.js

98 ms

cufon-yui.js

cufon-yui.js

270 ms

Helvetica_Neue_Light_Condensed_300.font.js

Helvetica_Neue_Light_Condensed_300.font.js

392 ms

Helvetica_Neue_Condensed_400-Helvetica_Neue_Condensed_700.font.js

Helvetica_Neue_Condensed_400-Helvetica_Neue_Condensed_700.font.js

392 ms

Helvetica_Neue_Medium_Condensed_500.font.js

Helvetica_Neue_Medium_Condensed_500.font.js

444 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

391 ms

jquery-ui.min.js

jquery-ui.min.js

62 ms

jquery.tools.min.js

jquery.tools.min.js

391 ms

script.js

script.js

442 ms

dc.js

dc.js

29 ms

webcam.png

webcam.png

177 ms

460500

460500

187 ms

460501

460501

186 ms

stadtportait.png

stadtportait.png

206 ms

broschueren.png

broschueren.png

225 ms

kontakt.png

kontakt.png

215 ms

newsletter.png

newsletter.png

214 ms

mobilitaet.png

mobilitaet.png

214 ms

apps.png

apps.png

366 ms

home.png

home.png

371 ms

luzern_weihnachten6.jpg

luzern_weihnachten6.jpg

638 ms

luzern_kapellbruecke_winter.jpg

luzern_kapellbruecke_winter.jpg

630 ms

stoos_shooting.jpg

stoos_shooting.jpg

565 ms

kv_weihnachten5-1.jpg

kv_weihnachten5-1.jpg

586 ms

kv_winter2-1.jpg

kv_winter2-1.jpg

527 ms

sonnenuntergang_stoos_fronalpstock_winter.jpg

sonnenuntergang_stoos_fronalpstock_winter.jpg

640 ms

stoerer-social-wall-en-5.png

stoerer-social-wall-en-5.png

614 ms

weggis_winter_schnee.jpg

weggis_winter_schnee.jpg

679 ms

lf_ostern3.jpg

lf_ostern3.jpg

680 ms

news_pauschale.jpg

news_pauschale.jpg

739 ms

region_vierwaldstaettersee.jpg

region_vierwaldstaettersee.jpg

717 ms

bg.png

bg.png

90 ms

logo-luzern_en.png

logo-luzern_en.png

91 ms

facebook_icon.png

facebook_icon.png

91 ms

twitter_icon.png

twitter_icon.png

91 ms

youtube_icon.png

youtube_icon.png

143 ms

instagram_icon.png

instagram_icon.png

144 ms

ajs.php

ajs.php

187 ms

__utm.gif

__utm.gif

11 ms

base_print.css

base_print.css

96 ms

goldblume3-1.png

goldblume3-1.png

543 ms

qqq-rgb-1.png

qqq-rgb-1.png

545 ms

lg.php

lg.php

169 ms

langBG2.png

langBG2.png

165 ms

langBG.png

langBG.png

166 ms

ocButtons.png

ocButtons.png

166 ms

bogenneu.png

bogenneu.png

166 ms

disturberClose.png

disturberClose.png

167 ms

boxHeaderFull-sprite.png

boxHeaderFull-sprite.png

278 ms

quickContentBG.png

quickContentBG.png

195 ms

OV-Ticket.png

OV-Ticket.png

270 ms

spacer.gif

spacer.gif

178 ms

homeNavItem-Sprite.png

homeNavItem-Sprite.png

178 ms

newsItemCornerLB.png

newsItemCornerLB.png

178 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

128 ms

services-ajax.cfc

services-ajax.cfc

227 ms

services-ajax.cfc

services-ajax.cfc

227 ms

calendar.gif

calendar.gif

118 ms

ui-bg_highlight-soft_100_f2f5f7_1x100.png

ui-bg_highlight-soft_100_f2f5f7_1x100.png

118 ms

widget_v2.134.js

widget_v2.134.js

31 ms

1.png

1.png

89 ms

SEO Factors

luzern.org SEO score

0

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

luzern.org

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: