Tools & Wizards About Us
musical.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

musical.com

STARLIGHT EXPRESS - Das rasanteste Musical im Universum - STARLIGHT EXPRESS - Live in Bochum

Page Load Speed

4.5 sec in total

First Response

1 sec

Resources Loaded

3.2 sec

Page Rendered

294 ms

musical.com screenshot

About Website

Visit musical.com now to see the best up-to-date Musical content and also check out these interesting facts you probably never knew about musical.com

Das rasanteste Musical im Universum mit bisher über 17 Millionen Besuchern in Bochum. Eine Show für Jung und Alt, Groß und Klein, Paare, Freunde, Familien u.v.m.

Visit musical.com

Key Findings

We analyzed Musical.com page load time and found that the first response time was 1 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

musical.com performance score

0

Network Requests Diagram

www.musical.com

1045 ms

normalize.css

189 ms

style.min.css

417 ms

prettyPhoto.css

282 ms

grid.css

202 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 86% of them (54 requests) were addressed to the original Musical.com, 6% (4 requests) were made to S7.addthis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Musical.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 810.6 kB (46%)

Content Size

1.8 MB

After Optimization

960.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Musical.com main page is 1.8 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. 45% of websites need less resources to load. Javascripts take 942.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 51.7 kB

  • Original 73.0 kB
  • After minification 70.0 kB
  • After compression 21.3 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 51.7 kB or 71% of the original size.

Image Optimization

-1%

Potential reduce by 6.8 kB

  • Original 614.0 kB
  • After minification 607.2 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. Musical images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 633.7 kB

  • Original 942.1 kB
  • After minification 877.5 kB
  • After compression 308.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 633.7 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 118.3 kB

  • Original 141.6 kB
  • After minification 126.2 kB
  • After compression 23.3 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. Musical.com needs all CSS files to be minified and compressed as it can save up to 118.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (69%)

Requests Now

61

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Musical. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.musical.com

www.musical.com

1045 ms

normalize.css

normalize.css

189 ms

style.min.css

style.min.css

417 ms

prettyPhoto.css

prettyPhoto.css

282 ms

grid.css

grid.css

202 ms

jquery-ui-1.10.3.custom.min.css

jquery-ui-1.10.3.custom.min.css

307 ms

mappress.css

mappress.css

206 ms

lightbox.min.css

lightbox.min.css

285 ms

jquery-1.7.min.js

jquery-1.7.min.js

505 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

880 ms

modernizr.js

modernizr.js

375 ms

superfish.js

superfish.js

380 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

409 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

563 ms

uCarousel.js

uCarousel.js

475 ms

tms-0.4.1.js

tms-0.4.1.js

614 ms

jquery.tools.min.js

jquery.tools.min.js

516 ms

jquery.tinycarousel.min.js

jquery.tinycarousel.min.js

571 ms

jquery.loader.js

jquery.loader.js

605 ms

swfobject.js

swfobject.js

605 ms

jquery.cycle.all.js

jquery.cycle.all.js

660 ms

jquery.twitter.js

jquery.twitter.js

666 ms

jquery.flickrush.js

jquery.flickrush.js

706 ms

audio.js

audio.js

701 ms

jquery.color.js

jquery.color.js

717 ms

custom.js

custom.js

755 ms

jquery.ui.datepicker.min.custom.js

jquery.ui.datepicker.min.custom.js

855 ms

jquery.equalheights.js

jquery.equalheights.js

797 ms

addthis.js

addthis.js

807 ms

addthis_widget.js

addthis_widget.js

9 ms

core.min.js

core.min.js

735 ms

comment-reply.min.js

comment-reply.min.js

765 ms

wp-lightbox-2.min.js

wp-lightbox-2.min.js

846 ms

wp-embed.min.js

wp-embed.min.js

848 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

510 ms

body-bg.jpg

body-bg.jpg

480 ms

core086.js

core086.js

45 ms

logo1.png

logo1.png

158 ms

erlebnislive-630x225

erlebnislive-630x225

159 ms

banner-koenig-der-loewen.jpg

banner-koenig-der-loewen.jpg

157 ms

stage-entertainment-siegel.png

stage-entertainment-siegel.png

158 ms

banner-disneys-musical-tarzan.jpg

banner-disneys-musical-tarzan.jpg

156 ms

banner-blue-man-group.jpg

banner-blue-man-group.jpg

195 ms

banner-das-phantom-der-oper.jpg

banner-das-phantom-der-oper.jpg

197 ms

banner-hinterm-horizont.jpg

banner-hinterm-horizont.jpg

205 ms

banner-heisse-ecke.jpg

banner-heisse-ecke.jpg

223 ms

banner-starlight-express.jpg

banner-starlight-express.jpg

215 ms

banner-das-wunder-von-bern.jpg

banner-das-wunder-von-bern.jpg

288 ms

ga.js

ga.js

15 ms

header-tail.gif

header-tail.gif

276 ms

search-tail.gif

search-tail.gif

290 ms

search-submit.gif

search-submit.gif

303 ms

row-top-tail.gif

row-top-tail.gif

318 ms

line.png

line.png

369 ms

menu-a-tail.gif

menu-a-tail.gif

370 ms

carousel-control.png

carousel-control.png

392 ms

__utm.gif

__utm.gif

110 ms

footer-color-line.png

footer-color-line.png

379 ms

boost

boost

19 ms

300lo.json

300lo.json

41 ms

de.js

de.js

14 ms

sh.07f0d9bf220d07a763adad1e.html

sh.07f0d9bf220d07a763adad1e.html

28 ms

menu.c646c958f7e380f4e000.js

menu.c646c958f7e380f4e000.js

5 ms

SEO Factors

musical.com SEO score

0

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 Musical.com 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 Musical.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

musical.com

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