Tools & Wizards About Us
vbw.at screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

vbw.at

VBW - Die offizielle Seite der Vereinigten Bühnen Wien - Alle Infos, Termine und Tickets

Page Load Speed

6.2 sec in total

First Response

329 ms

Resources Loaded

5.2 sec

Page Rendered

680 ms

vbw.at screenshot

About Website

Click here to check amazing VBW content for Austria. Otherwise, check out these important facts you probably never knew about vbw.at

Tickets, Infos, Bilder und Videos zum Unternehmen und allen Produktionen der VEREINIGTEN BÜHNEN WIEN im RAIMUND THEATER, RONACHER und THEATER AN DER WIEN

Visit vbw.at

Key Findings

We analyzed Vbw.at page load time and found that the first response time was 329 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

vbw.at performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value22.0 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.651

9/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

vbw.at

329 ms

home

1136 ms

truendo_cmp.pid.js

75 ms

568 ms

332 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 93% of them (28 requests) were addressed to the original Vbw.at, 3% (1 request) were made to Cdn.priv.center and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Vbw.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 616.8 kB (11%)

Content Size

5.7 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Vbw.at main page is 5.7 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. 15% of websites need less resources to load. Images take 5.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 27.8 kB

  • Original 34.7 kB
  • After minification 29.6 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 5.2 kB, which is 15% 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 27.8 kB or 80% of the original size.

Image Optimization

-11%

Potential reduce by 586.6 kB

  • Original 5.6 MB
  • After minification 5.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. Obviously, VBW needs image optimization as it can save up to 586.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 2.4 kB

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

Requests Breakdown

Number of requests can be reduced by 9 (33%)

Requests Now

27

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vbw.at

vbw.at

329 ms

home

home

1136 ms

truendo_cmp.pid.js

truendo_cmp.pid.js

75 ms

568 ms

332 ms

452 ms

gtm.js

gtm.js

114 ms

logo-vbw.png

logo-vbw.png

362 ms

icon-nav-arrow.png

icon-nav-arrow.png

362 ms

icon-search-anchor.png

icon-search-anchor.png

361 ms

icon-nav-anchor.png

icon-nav-anchor.png

363 ms

VBW_SeatBadge_desktop.png

VBW_SeatBadge_desktop.png

689 ms

21808.jpg

21808.jpg

1237 ms

21950.jpg

21950.jpg

1456 ms

21951.jpg

21951.jpg

1564 ms

1158.jpg

1158.jpg

1126 ms

21743.jpg

21743.jpg

798 ms

21880.jpg

21880.jpg

1676 ms

icon-share-facebook-2019.png

icon-share-facebook-2019.png

1127 ms

x-logo-white.png

x-logo-white.png

1783 ms

icon-share-whatsapp.png

icon-share-whatsapp.png

1457 ms

icon-share-linkedin.png

icon-share-linkedin.png

1566 ms

icon-mail.png

icon-mail.png

1787 ms

icon-scrolltop.png

icon-scrolltop.png

1787 ms

logo-agrana.png

logo-agrana.png

1896 ms

logo-wiener-staedtische.png

logo-wiener-staedtische.png

2004 ms

logo-wienholding-50jahre.jpg

logo-wienholding-50jahre.jpg

2004 ms

logo-wienkultur.png

logo-wienkultur.png

2111 ms

icon-navclose-anchor.png

icon-navclose-anchor.png

2113 ms

SourceSansPro-Light.ttf

SourceSansPro-Light.ttf

2410 ms

Accessibility Review

vbw.at accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

vbw.at best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

vbw.at SEO score

87

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

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 Vbw.at 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 Vbw.at 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

vbw.at

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