Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

wien.at

Stadt Wien - Offizielle & aktuelle Infos und Services der Wiener Stadtverwaltung

Page Load Speed

4.3 sec in total

First Response

355 ms

Resources Loaded

3.6 sec

Page Rendered

354 ms

wien.at screenshot

About Website

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

Das offizielle Internetportal der Stadt Wien mit Informationen, Services, Nachrichten, Veranstaltungen und vielem mehr

Visit wien.at

Key Findings

We analyzed Wien.at page load time and found that the first response time was 355 ms and then it took 3.9 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

wien.at performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value27.1 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.436

21/100

15%

TTI (Time to Interactive)

Value13.7 s

10/100

10%

Network Requests Diagram

wien.at

355 ms

wien.at

456 ms

www.wien.gv.at

860 ms

vie-resp.css

209 ms

responsive2.css

313 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Wien.at, 94% (59 requests) were made to Wien.gv.at and 3% (2 requests) were made to Ssl-wiengvat.oewabox.at. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Wien.gv.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.5 kB (13%)

Content Size

603.9 kB

After Optimization

523.3 kB

In fact, the total size of Wien.at main page is 603.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 307.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 33.1 kB

  • Original 44.9 kB
  • After minification 43.7 kB
  • After compression 11.8 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 33.1 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 5.3 kB

  • Original 307.7 kB
  • After minification 302.4 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. Wien images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 22.4 kB

  • Original 185.8 kB
  • After minification 185.8 kB
  • After compression 163.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 22.4 kB or 12% of the original size.

CSS Optimization

-30%

Potential reduce by 19.7 kB

  • Original 65.5 kB
  • After minification 65.5 kB
  • After compression 45.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. Wien.at needs all CSS files to be minified and compressed as it can save up to 19.7 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (61%)

Requests Now

59

After Optimization

23

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

Accessibility Review

wien.at accessibility score

87

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

wien.at best practices score

75

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

wien.at SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wien.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 Wien.at main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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