Tools & Wizards About Us
philharmonie.wien screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

philharmonie.wien

Home | Philharmonie der Universität Wien

Page Load Speed

4.7 sec in total

First Response

527 ms

Resources Loaded

3.7 sec

Page Rendered

446 ms

philharmonie.wien screenshot

About Website

Click here to check amazing Philharmonie content. Otherwise, check out these important facts you probably never knew about philharmonie.wien

Die Philharmonie der Universität Wien besteht aus ca. 900 MusikerInnen und SängerInnen aller Niveaus und Altersgruppen.

Visit philharmonie.wien

Key Findings

We analyzed Philharmonie.wien page load time and found that the first response time was 527 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

philharmonie.wien performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

philharmonie.wien

527 ms

philharmonie.wien

670 ms

css

37 ms

font-awesome.min.css

34 ms

main.css

428 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 78% of them (21 requests) were addressed to the original Philharmonie.wien, 7% (2 requests) were made to Maxcdn.bootstrapcdn.com and 7% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Philharmonie.wien.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.0 kB (5%)

Content Size

1.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Philharmonie.wien main page is 1.1 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. 25% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 29.0 kB

  • Original 35.4 kB
  • After minification 32.2 kB
  • After compression 6.5 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 29.0 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 24.5 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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. Philharmonie images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 75 B

  • Original 40.4 kB
  • After minification 40.4 kB
  • After compression 40.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-21%

Potential reduce by 1.4 kB

  • Original 6.8 kB
  • After minification 6.8 kB
  • After compression 5.4 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. Philharmonie.wien needs all CSS files to be minified and compressed as it can save up to 1.4 kB or 21% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

22

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Philharmonie. According to our analytics all requests are already optimized.

Network Requests Diagram

philharmonie.wien

philharmonie.wien

527 ms

philharmonie.wien

philharmonie.wien

670 ms

css

css

37 ms

font-awesome.min.css

font-awesome.min.css

34 ms

main.css

main.css

428 ms

logo.png

logo.png

425 ms

foto1-1280x640-crop-q80.jpg

foto1-1280x640-crop-q80.jpg

1060 ms

pop-2-web-1280x640-crop-q80.jpg

pop-2-web-1280x640-crop-q80.jpg

1272 ms

x-2-cb-1280x640-crop-q80.jpg

x-2-cb-1280x640-crop-q80.jpg

1168 ms

genshin-q-300x200-crop-q80.jpg

genshin-q-300x200-crop-q80.jpg

464 ms

80s-q-300x200-crop-q80.jpg

80s-q-300x200-crop-q80.jpg

848 ms

beethoven-q-300x200-crop-q80.jpg

beethoven-q-300x200-crop-q80.jpg

955 ms

bruckner-q-300x200-crop-q80.jpg

bruckner-q-300x200-crop-q80.jpg

854 ms

orchester-q-300x200-crop-q80.jpg

orchester-q-300x200-crop-q80.jpg

1272 ms

vocal-q-300x200-crop-q80.jpg

vocal-q-300x200-crop-q80.jpg

1277 ms

traditionfrancaise-q-300x200-crop-q80.jpg

traditionfrancaise-q-300x200-crop-q80.jpg

1379 ms

africacalling-q-300x200-crop-q80.jpg

africacalling-q-300x200-crop-q80.jpg

1591 ms

verdi-q-300x200-crop-q80.jpg

verdi-q-300x200-crop-q80.jpg

1589 ms

anime.min.js

anime.min.js

1695 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

1698 ms

marlene-bild-2-1248x832-crop.jpg

marlene-bild-2-1248x832-crop.jpg

2121 ms

univie-160x.png

univie-160x.png

1804 ms

univiesiegel.png

univiesiegel.png

1683 ms

font

font

20 ms

font

font

22 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

12 ms

piwik.js

piwik.js

786 ms

Accessibility Review

philharmonie.wien accessibility score

89

Accessibility Issues

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

philharmonie.wien best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

philharmonie.wien SEO score

90

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

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Philharmonie.wien 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 Philharmonie.wien 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

philharmonie.wien

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