3.6 sec in total
336 ms
3 sec
232 ms
Welcome to bahnhof.de homepage info - get ready to check Bahnhof best content for Germany right away, or after learning these important things about bahnhof.de
Ihre Plattform rund um die Personenbahnhöfe in Deutschland. Erhalten Sie schnell und einfach einen Überblick über die Abfahrts- und Ankunftszeiten, die Bahnhofsausstattung, Informationen zur Barrieref...
Visit bahnhof.deWe analyzed Bahnhof.de page load time and found that the first response time was 336 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
bahnhof.de performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value7.7 s
3/100
25%
Value8.5 s
18/100
10%
Value1,430 ms
15/100
30%
Value0.299
40/100
15%
Value12.7 s
14/100
10%
336 ms
217 ms
338 ms
202 ms
214 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 94% of them (51 requests) were addressed to the original Bahnhof.de, 2% (1 request) were made to Code.etracker.com and 2% (1 request) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (689 ms) belongs to the original domain Bahnhof.de.
Page size can be reduced by 63.5 kB (72%)
88.7 kB
25.2 kB
In fact, the total size of Bahnhof.de main page is 88.7 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. 35% of websites need less resources to load. Javascripts take 51.5 kB which makes up the majority of the site volume.
Potential reduce by 30.2 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 30.2 kB or 81% of the original size.
Potential reduce by 33.3 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 33.3 kB or 65% of the original size.
Number of requests can be reduced by 34 (68%)
50
16
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bahnhof. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.bahnhof.de
336 ms
217 ms
layout2010-common,fbf9fcf773b667a6f20c6c83d269db91f9b5ffbd.css
338 ms
theme_default.css.css
202 ms
bahnhof-styles.css
214 ms
dbsearch.autocomplete.css.css
216 ms
modernizr-2.5.3.js
315 ms
swfobject.js.js
213 ms
jquery-1.7.1.js
638 ms
jquery.easing.js.js
315 ms
jquery.json-2.3.js
315 ms
typeAhead.js
316 ms
global-header-utils.js
423 ms
sliderStage.js.js
419 ms
AutocompleteFragment.js
429 ms
disableSearchHighlight.js
418 ms
jquery-custom-plugins.js
348 ms
jquery-ui-1.8.18.custom.min.js
653 ms
jquery.accessible.tabs-1.9.4.custom.js
433 ms
jquery.syncheight.js.js
435 ms
shadowbox.js.js
593 ms
jquery.cookie.js.js
450 ms
global-bottom-utils.js
542 ms
cookieBanner.js
537 ms
data.png
107 ms
data.gif
104 ms
data.png
106 ms
img4.jpg
203 ms
img4.jpg
104 ms
img4.jpg
183 ms
data.png
301 ms
img4.jpg
205 ms
img4.jpg
206 ms
data.gif
206 ms
data.png
268 ms
data.jpg
286 ms
data.png
289 ms
data.jpg
290 ms
data.gif
289 ms
data.png
368 ms
data.png
384 ms
data.png
384 ms
t.js
672 ms
data.woff
340 ms
data.woff
344 ms
cnt_js.php
196 ms
piwik.js
490 ms
flashImg1.jpg
689 ms
flashImg1.jpg
494 ms
flashImg1.jpg
592 ms
data.png
103 ms
data.png
106 ms
data.png
105 ms
data.png
203 ms
bahnhof.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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
bahnhof.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
bahnhof.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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bahnhof.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Bahnhof.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.
bahnhof.de
Open Graph description is not detected on the main page of Bahnhof. 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: