5.5 sec in total
439 ms
4.8 sec
283 ms
Visit smartcity.wien.gv.at now to see the best up-to-date Smart City Wien content for Austria and also check out these interesting facts you probably never knew about smartcity.wien.gv.at
Visit smartcity.wien.gv.atWe analyzed Smartcity.wien.gv.at page load time and found that the first response time was 439 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
smartcity.wien.gv.at performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value11.1 s
0/100
25%
Value9.8 s
10/100
10%
Value490 ms
59/100
30%
Value0.005
100/100
15%
Value10.6 s
23/100
10%
439 ms
449 ms
401 ms
119 ms
236 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 78% of them (57 requests) were addressed to the original Smartcity.wien.gv.at, 14% (10 requests) were made to Maps.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.7 sec) relates to the external source Maps.wien.gv.at.
Page size can be reduced by 725.8 kB (45%)
1.6 MB
879.3 kB
In fact, the total size of Smartcity.wien.gv.at main page is 1.6 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. 30% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 67.4 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 67.4 kB or 83% of the original size.
Potential reduce by 362.3 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, Smart City Wien needs image optimization as it can save up to 362.3 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 209.0 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 209.0 kB or 70% of the original size.
Potential reduce by 87.2 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. Smartcity.wien.gv.at needs all CSS files to be minified and compressed as it can save up to 87.2 kB or 82% of the original size.
Number of requests can be reduced by 43 (63%)
68
25
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smart City 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 12 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
smartcity.wien.gv.at
439 ms
smartcity.wien.gv.at
449 ms
en
401 ms
layout.css
119 ms
colorbox.css
236 ms
style.css
328 ms
socialshareprivacy-min.css
432 ms
jquery.js
456 ms
jquery-migrate.min.js
345 ms
jquery-sc.js
332 ms
jquery-wat.js
349 ms
respond.min.js
442 ms
jquery.colorbox-min.js
448 ms
leaflet.css
461 ms
social_bookmarks-min.js
473 ms
jsapi
35 ms
leaflet.js
682 ms
show_map.js
576 ms
structure.css
473 ms
formats.css
565 ms
images.css
475 ms
extensions.css
473 ms
style.css
367 ms
wienat.png
120 ms
lock.png
116 ms
logoSCneu.png
131 ms
twitter.png
119 ms
facebook.png
122 ms
rss.png
120 ms
topmenubg_h.png
1195 ms
searchbg.png
1195 ms
search.png
1195 ms
topmenubg.png
1196 ms
topmenuactive.png
1195 ms
topmenubg2.png
1196 ms
topmenubottom.png
1195 ms
Foto-Titelbild-200x300.jpg
1206 ms
commentblob.png
1206 ms
haeupl01.jpg
1414 ms
stadtwienlogo_en.png
1204 ms
en
1467 ms
js
69 ms
1116.png
1723 ms
1116.png
857 ms
1115.png
842 ms
1117.png
838 ms
1115.png
838 ms
1117.png
845 ms
1114.png
1039 ms
1118.png
1051 ms
1114.png
1158 ms
1118.png
1157 ms
zoom-in.png
188 ms
zoom-out.png
189 ms
bigcity.png
188 ms
marker-shadow.png
187 ms
busstop.png
188 ms
communitycentre.png
335 ms
recycle.png
315 ms
villa.png
316 ms
zoom.png
316 ms
hospital-building.png
322 ms
piwik.js
1130 ms
undefined
918 ms
socialshareprivacy_on_off.png
419 ms
sprite-de_DE.png
409 ms
socialshareprivacy_info.png
409 ms
overlay.png
429 ms
blank.gif
102 ms
layouttablet.css
177 ms
layoutmobile.css
123 ms
piwik.php
298 ms
print.css
118 ms
smartcity.wien.gv.at accessibility score
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
smartcity.wien.gv.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
smartcity.wien.gv.at SEO score
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 uses legible font sizes
Tap targets are not sized appropriately
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Smartcity.wien.gv.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Smartcity.wien.gv.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.
smartcity.wien.gv.at
Open Graph description is not detected on the main page of Smart City 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: