14.2 sec in total
459 ms
13.6 sec
151 ms
Visit vmobil.at now to see the best up-to-date VMOBIL content for Austria and also check out these interesting facts you probably never knew about vmobil.at
Bus, Bahn, Fahrrad, Carsharing, Schiff und zu Fuß – mit VMOBIL haben Sie alle Mobilitätsangebote Vorarlbergs auf einen Blick.
Visit vmobil.atWe analyzed Vmobil.at page load time and found that the first response time was 459 ms and then it took 13.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster. This domain responded with an error, which can significantly jeopardize Vmobil.at rating and web reputation
vmobil.at performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value9.4 s
1/100
25%
Value9.1 s
14/100
10%
Value1,120 ms
23/100
30%
Value0.012
100/100
15%
Value9.3 s
32/100
10%
459 ms
905 ms
114 ms
115 ms
222 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 53% of them (49 requests) were addressed to the original Vmobil.at, 26% (24 requests) were made to Fahrplan.vmobil.at and 16% (15 requests) were made to Wetterring.at. The less responsive or slowest element that took the longest time to load (11.4 sec) belongs to the original domain Vmobil.at.
Page size can be reduced by 1.5 MB (69%)
2.2 MB
699.0 kB
In fact, the total size of Vmobil.at main page is 2.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. 50% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 32.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. This page needs HTML code to be minified as it can gain 5.9 kB, which is 14% 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 32.8 kB or 79% of the original size.
Potential reduce by 26.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. VMOBIL images are well optimized though.
Potential reduce by 1.2 MB
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 1.2 MB or 80% of the original size.
Potential reduce by 259.3 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. Vmobil.at needs all CSS files to be minified and compressed as it can save up to 259.3 kB or 86% of the original size.
Number of requests can be reduced by 56 (68%)
82
26
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VMOBIL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
vmobil.at
459 ms
www.vmobil.at
905 ms
efamini.css
114 ms
1455897527_plugins.css
115 ms
_index.css
222 ms
jquery.js
341 ms
jquery.colorbox-min.js
228 ms
colorbox.css
230 ms
mobil_form.js
229 ms
jquery.tabify.js
227 ms
dny
583 ms
all.js
28 ms
efamini.css
221 ms
base.css
119 ms
basemod.css
121 ms
nav_slidingdoor.css
121 ms
nav_vlist.css
120 ms
content.css
222 ms
print_003.css
228 ms
iehacks.css
230 ms
bg-aktuell.gif
116 ms
2015-120-aktuell.jpg
218 ms
10_adgrau.gif
118 ms
10_agelb.gif
120 ms
10_ahblau.gif
121 ms
10_aorange.gif
118 ms
10_adblau.gif
121 ms
10_agrn1.gif
122 ms
10_abraun.gif
222 ms
10_ahgrau.gif
225 ms
10_gruppe1.png
222 ms
10_idgrau.gif
224 ms
10_icongrau.gif
224 ms
searchback.gif
225 ms
sprechomat.gif
331 ms
crop_96_Web_planb_Trolley_Pressekonferenz_Medien.jpg
441 ms
crop_93_StadtbusLandbus_116.jpg
441 ms
78_busland1.png
332 ms
10_Panorama1.jpg
570 ms
78_abusbahn_560x336.jpg
671 ms
bg-aktuell.gif
345 ms
hafas_microsite.css
245 ms
styles.css
372 ms
style.css
255 ms
jsmap.css
259 ms
suggest.css
263 ms
styles.css
261 ms
hafas_microsite.js
614 ms
vmobil-wetter.html
330 ms
2015-120-aktuell.jpg
11398 ms
style.css
122 ms
jquery.min.js
29 ms
footer1.gif
114 ms
ext_link.gif
114 ms
131 ms
piwik.js
113 ms
overlay.png
121 ms
reset.css
104 ms
wetterring.css
199 ms
ie.css
206 ms
xd_arbiter.php
25 ms
xd_arbiter.php
34 ms
footer1.gif
113 ms
piwik.js
152 ms
hafas_lib.js
126 ms
header_left.jpg
97 ms
header_middle.jpg
99 ms
header_right.jpg
98 ms
schneeregen.png
195 ms
logo_transparent.png
283 ms
schneefall.png
190 ms
regen.png
194 ms
schneeschauer.png
193 ms
wolkig.png
194 ms
regenschauer.png
282 ms
piwik.php
114 ms
hafas_gui.js
244 ms
piwik.php
319 ms
OpenLayers.js
785 ms
deprecated.js
374 ms
OpenStreetMap.js
247 ms
AJSMapBaseClass.js
260 ms
CCoord.js
247 ms
AAjaxMap.js
252 ms
AOpenLayerMap.js
262 ms
COLOpenStreetMap.js
253 ms
ajax_load_bar.gif
240 ms
ico_start.png
242 ms
ico_dest.png
259 ms
btn_date_earlier.png
263 ms
btn_date_later.png
265 ms
logo_small.png
265 ms
print.css
115 ms
vmobil.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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
ARIA IDs are not unique
vmobil.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
Missing source maps for large first-party JavaScript
vmobil.at SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses 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 Vmobil.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 Vmobil.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.
vmobil.at
Open Graph description is not detected on the main page of VMOBIL. 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: