Tools & Wizards About Us
stadtsaal.com screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

stadtsaal.com

STADTSAAL - stadtsaal.com

Page Load Speed

8.2 sec in total

First Response

3.2 sec

Resources Loaded

4.6 sec

Page Rendered

309 ms

stadtsaal.com screenshot

About Website

Welcome to stadtsaal.com homepage info - get ready to check STADTSAAL best content for Austria right away, or after learning these important things about stadtsaal.com

Visit stadtsaal.com

Key Findings

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

Performance Metrics

stadtsaal.com performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.545

13/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

stadtsaal.com

3243 ms

default.css

196 ms

webform.css

206 ms

popup.js

209 ms

jquery-1.9.0.min.js

316 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 79% of them (15 requests) were addressed to the original Stadtsaal.com, 11% (2 requests) were made to Staticxx.facebook.com and 5% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Stadtsaal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (57%)

Content Size

1.8 MB

After Optimization

749.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stadtsaal.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. 25% of websites need less resources to load. HTML takes 894.0 kB which makes up the majority of the site volume.

HTML Optimization

-99%

Potential reduce by 888.4 kB

  • Original 894.0 kB
  • After minification 19.5 kB
  • After compression 5.7 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. This page needs HTML code to be minified as it can gain 874.5 kB, which is 98% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 888.4 kB or 99% of the original size.

Image Optimization

-6%

Potential reduce by 41.2 kB

  • Original 748.8 kB
  • After minification 707.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. STADTSAAL images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 60.1 kB

  • Original 93.4 kB
  • After minification 93.3 kB
  • After compression 33.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 60.1 kB or 64% of the original size.

CSS Optimization

-81%

Potential reduce by 11.7 kB

  • Original 14.4 kB
  • After minification 11.1 kB
  • After compression 2.8 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. Stadtsaal.com needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 81% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stadtsaal.com

stadtsaal.com

3243 ms

default.css

default.css

196 ms

webform.css

webform.css

206 ms

popup.js

popup.js

209 ms

jquery-1.9.0.min.js

jquery-1.9.0.min.js

316 ms

logo_stadtsaal_hd.png

logo_stadtsaal_hd.png

307 ms

ico_youtube_hd.png

ico_youtube_hd.png

206 ms

ico_twitter_hd.png

ico_twitter_hd.png

207 ms

ico_facebook_hd.png

ico_facebook_hd.png

106 ms

ico_instagram_hd.png

ico_instagram_hd.png

244 ms

haderspielthader1.jpg

haderspielthader1.jpg

1016 ms

raiffeisen_hd.jpg

raiffeisen_hd.jpg

410 ms

derstandard_doppellogo.jpg

derstandard_doppellogo.jpg

450 ms

all.js

all.js

268 ms

arrow_right_hd.png

arrow_right_hd.png

256 ms

192 ms

xd_arbiter.php

xd_arbiter.php

212 ms

xd_arbiter.php

xd_arbiter.php

420 ms

print.css

print.css

103 ms

Accessibility Review

stadtsaal.com accessibility score

84

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

stadtsaal.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

stadtsaal.com SEO score

72

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stadtsaal.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Stadtsaal.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

stadtsaal.com

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