9.3 sec in total
1.4 sec
7.7 sec
227 ms
Visit my.vienna.at now to see the best up-to-date My VIENNA content for Austria and also check out these interesting facts you probably never knew about my.vienna.at
Alle Nachrichten aus Wien und den Wiener Bezirken sowie Services rund um die Bundeshauptstadt: Veranstaltungen, Wetter, Kino, Theater uvm.
Visit my.vienna.atWe analyzed My.vienna.at page load time and found that the first response time was 1.4 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
my.vienna.at performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value7.3 s
4/100
25%
Value7.9 s
23/100
10%
Value340 ms
74/100
30%
Value0.017
100/100
15%
Value12.2 s
15/100
10%
1396 ms
850 ms
1014 ms
811 ms
25 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 28% of them (40 requests) were addressed to the original My.vienna.at, 14% (20 requests) were made to Vienna.at and 9% (12 requests) were made to Ad.360yield.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Vienna.at.
Page size can be reduced by 737.8 kB (62%)
1.2 MB
445.9 kB
In fact, the total size of My.vienna.at main page is 1.2 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. 60% of websites need less resources to load. Javascripts take 556.4 kB which makes up the majority of the site volume.
Potential reduce by 145.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. 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 145.7 kB or 82% of the original size.
Potential reduce by 22.8 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. Obviously, My VIENNA needs image optimization as it can save up to 22.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 348.6 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 348.6 kB or 63% of the original size.
Potential reduce by 220.6 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. My.vienna.at needs all CSS files to be minified and compressed as it can save up to 220.6 kB or 83% of the original size.
Number of requests can be reduced by 65 (52%)
125
60
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My VIENNA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
my.vienna.at
1396 ms
wp-emoji-release.min.js
850 ms
703a68e4549c06af577be04c63cca014.css
1014 ms
bc42225935a563be68ceada2e7ec530b.js
811 ms
css
25 ms
adition.js
369 ms
adition.js
608 ms
jquery-ui-1.7.2.custom.min.js
585 ms
jquery.form.js
407 ms
js.php
408 ms
jquery.jrcorner.js
605 ms
css.css
612 ms
challenge
52 ms
999ef85b36d3e4340f677a37da419b9e.js
1511 ms
survey.js
339 ms
widget.js
989 ms
rc
222 ms
analytics.js
41 ms
fbds.js
40 ms
freunde.jpg
484 ms
icondirect.php
216 ms
icondirect.php
216 ms
icondirect.php
215 ms
icondirect.php
213 ms
icondirect.php
480 ms
icondirect.php
481 ms
icondirect.php
481 ms
icondirect.php
483 ms
icondirect.php
481 ms
icondirect.php
636 ms
icondirect.php
637 ms
icondirect.php
636 ms
icondirect.php
640 ms
icondirect.php
640 ms
icondirect.php
638 ms
icondirect.php
824 ms
icondirect.php
829 ms
icondirect.php
834 ms
icondirect.php
858 ms
icondirect.php
860 ms
icondirect.php
858 ms
icondirect.php
1030 ms
icondirect.php
1475 ms
icondirect.php
1045 ms
icondirect.php
1054 ms
icondirect.php
1056 ms
icondirect.php
1055 ms
icondirect.php
1238 ms
icondirect.php
1251 ms
icondirect.php
1261 ms
uid.html
93 ms
VIENNA
237 ms
homepage.png
468 ms
homepage.png
209 ms
logo.png
209 ms
140 ms
collect
44 ms
breadcrumbs.png
226 ms
load_small.gif
1212 ms
SourceSansPro-Bold.svg
4006 ms
SourceSansPro-Bold.ttf.woff
779 ms
SourceSansPro-Semibold.svg
1640 ms
SourceSansPro-Semibold.ttf.woff
1433 ms
SourceSansPro-Regular.svg
3211 ms
SourceSansPro-Regular.ttf.woff
985 ms
SourceSansPro-Light.svg
2602 ms
SourceSansPro-Light.ttf.woff
1409 ms
Texture.png
1615 ms
recaptcha.js
15 ms
iRxeRssL0kc6A33tX3mw_8DXSrt0tz5MqKmNoT12tsY.js
11 ms
logo-medium.png
1469 ms
blank.gif
138 ms
reload
33 ms
image
16 ms
get_theme_config
1210 ms
get_preview_menu
1835 ms
sdk.js
36 ms
cx.js
23 ms
qs.oewabox.at
303 ms
plusone.js
91 ms
js
288 ms
36 ms
p1.html
4 ms
xd_arbiter.php
47 ms
xd_arbiter.php
100 ms
p1.js
18 ms
rep.gif
22 ms
cb=gapi.loaded_0
33 ms
banner
184 ms
script.js
212 ms
js
175 ms
banner
173 ms
nadj
60 ms
1x1.jpg
22 ms
pixel
26 ms
generic
12 ms
js
175 ms
generic
9 ms
match
10 ms
pixel
28 ms
match
10 ms
match
9 ms
match
7 ms
match
8 ms
banner
175 ms
nadj
135 ms
usermatch
72 ms
scheduler.tele.net
1055 ms
match
8 ms
usermatch
23 ms
match
34 ms
xd_arbiter.php
23 ms
casale
12 ms
gr
25 ms
GenericUserSync.ashx
24 ms
match
12 ms
crum
31 ms
rum
22 ms
rum
23 ms
pixel
37 ms
rum
226 ms
rum
117 ms
crum
11 ms
m
59 ms
crum
39 ms
loading.gif
201 ms
navigation.png
398 ms
match
7 ms
crum
13 ms
match
8 ms
logo.png
209 ms
ci
214 ms
layer_background.gif
412 ms
bg_closebutton_a.gif
208 ms
bg_closebutton_span.gif
211 ms
bg_button_a.gif
208 ms
bg_button_span.gif
212 ms
light-bottom.css
1117 ms
chartbeat_pub.js
53 ms
ad
24 ms
ping
14 ms
my.vienna.at accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
my.vienna.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
my.vienna.at SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise My.vienna.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 My.vienna.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.
my.vienna.at
Open Graph description is not detected on the main page of My VIENNA. 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: