5.2 sec in total
405 ms
4.5 sec
258 ms
Click here to check amazing VAG content for Germany. Otherwise, check out these important facts you probably never knew about vag.de
U-Bahn, Straßenbahn und Bus. Mit öffentlichen Verkehrsmitteln umweltfreundlich im Stadtverkehr Nürnberg unterwegs. Fahrpläne, Fahrkarten, Preise, u.v.m.
Visit vag.deWe analyzed Vag.de page load time and found that the first response time was 405 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
vag.de performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value10.3 s
0/100
25%
Value12.6 s
3/100
10%
Value8,050 ms
0/100
30%
Value0.29
41/100
15%
Value16.3 s
5/100
10%
405 ms
1273 ms
99 ms
199 ms
294 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 94% of them (94 requests) were addressed to the original Vag.de, 4% (4 requests) were made to Etracker.de and 1% (1 request) were made to Static.etracker.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Vag.de.
Page size can be reduced by 1.2 MB (42%)
2.9 MB
1.7 MB
In fact, the total size of Vag.de main page is 2.9 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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 55.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. 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 55.9 kB or 83% of the original size.
Potential reduce by 86.2 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. VAG images are well optimized though.
Potential reduce by 787.1 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 787.1 kB or 72% of the original size.
Potential reduce by 282.0 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. Vag.de needs all CSS files to be minified and compressed as it can save up to 282.0 kB or 85% of the original size.
Number of requests can be reduced by 63 (66%)
95
32
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VAG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
vag.de
405 ms
www.vag.de
1273 ms
stylesheet_70d0d3c156.css
99 ms
jquery-ui-1.8.16.custom.css
199 ms
webfonts.css
294 ms
menue.css
292 ms
supersized.core.css
299 ms
flexslider.css
303 ms
jquery.fancybox.css
296 ms
ext_veranstaltungen.css
299 ms
jquery-ui-1.10.3.custom.min.css
387 ms
jquery.mCustomScrollbar.css
390 ms
tipsy.css
393 ms
socialshareprivacy.css
394 ms
jquery.ui.timepicker.css
391 ms
chosen.min.css
396 ms
ext_geschuetzter_bereich.css
483 ms
animate.css
487 ms
liquid-slider.css
492 ms
smoothDivScroll.css
492 ms
ext_geschichten.css
494 ms
shariff.complete.css
497 ms
global.css
581 ms
stylesheet_e4d01b369c.css
586 ms
jquery-1.6.4.min.js
593 ms
jquery-ui-1.8.16.custom.min.js
588 ms
jquery-1.9.1.js
798 ms
supersized.core.3.2.1.min.js
592 ms
jquery.flexslider-min.js
678 ms
jquery.fancybox.pack.js
678 ms
jquery-ui-1.10.3.custom.min.js
812 ms
jquery.easing.1.3.js
689 ms
jquery.numeric.js
688 ms
ext_veranstaltungen.js
775 ms
jquery.mCustomScrollbar.concat.min.js
776 ms
jquery.marquee.min.js
784 ms
jquery.tipsy.js
787 ms
e.js
381 ms
ext_fahrplansystem.css
867 ms
ext_fahrplaninfo.css
785 ms
startseite2015.css
693 ms
responsive.css
606 ms
iso.js
612 ms
abfahtsmonitor.js
609 ms
jquery.socialshareprivacy.js
677 ms
jquery.ui.timepicker.js
682 ms
chosen.jquery.min.js
685 ms
jquery.kinetic.min.js
606 ms
jquery.mousewheel.min.js
611 ms
jquery.smoothdivscroll-1.3-min.js
611 ms
jquery.touchSwipe.min.js
682 ms
jquery.liquid-slider.min.js
687 ms
jquery.ui.datepicker-de.js
688 ms
jquery.anystretch.min.js
608 ms
jquery.cookie.js
608 ms
global.js
608 ms
cookies.js
674 ms
efa_fontsize.js
683 ms
ext_fahrplansystem.js
681 ms
ext_fahrplaninfo.js
600 ms
shariff.min.js
616 ms
d74de079-587d-4049-9cca-50ba02a536f9.woff
702 ms
jquery-1.8.3.min.js
508 ms
422 ms
t.js
450 ms
meine_vag_03.jpg
128 ms
online_shop_01.png
128 ms
abo-tickets.png
126 ms
nightliner.png
128 ms
aktuelles_01.png
129 ms
infoportal2.png
205 ms
logo_vag.gif
203 ms
20160226_Slider_Natuerlich_blond.jpg
301 ms
Extratour_Aussenansicht_4_680x350_01.jpg
394 ms
csm_icon_ubahn_70_38733b2702.png
210 ms
csm_icon_tram_70_c147645597.png
210 ms
csm_icon_bus_70_07cd7ca2e6.png
288 ms
csm_icon_ubahn_h_193bc5ae8a.png
293 ms
csm_icon_tram_h_7db6a506b1.png
299 ms
csm_icon_bus_h_928f83ab6c.png
300 ms
csm_icon_aufzug_h_820e735401.png
384 ms
weissverlauf.png
386 ms
linkpfeil_weiss.png
391 ms
ui-bg_flat_75_ffffff_40x100.png
368 ms
78cb2356-22e7-4eae-bbb7-f947f2384d4b.woff
373 ms
background_fahrplanauskunft_reiter.png
447 ms
background_headlines.png
452 ms
linkpfeil_weiss_gross.png
453 ms
linkpfeil_teaser.png
451 ms
socialmedia.png
451 ms
5f3f5b96-b77d-497d-a916-d483bc9c6c3f.woff
453 ms
piwik.js
532 ms
background-image.jpg
1238 ms
datepicker_icon.png
477 ms
gelegenheitsfahrer_03.jpg
966 ms
vielfahrer_03.jpg
870 ms
schueler_08.jpg
1170 ms
gruppen_04.jpg
1139 ms
cnt_js.php
101 ms
cntcc
108 ms
vag.de accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Form elements do not have associated labels
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
[lang] attributes do not have a valid value
vag.de 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
vag.de 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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vag.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Vag.de 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.
vag.de
Open Graph description is not detected on the main page of VAG. 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: