4 sec in total
514 ms
3.3 sec
202 ms
Click here to check amazing Hamburgbahn content. Otherwise, check out these important facts you probably never knew about hamburgbahn.de
Home
Visit hamburgbahn.deWe analyzed Hamburgbahn.de page load time and found that the first response time was 514 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
hamburgbahn.de performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value1.7 s
99/100
25%
Value0.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
514 ms
206 ms
767 ms
27 ms
772 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 93% of them (39 requests) were addressed to the original Hamburgbahn.de, 5% (2 requests) were made to Fonts.googleapis.com and 2% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Hamburgbahn.de.
Page size can be reduced by 510.2 kB (21%)
2.4 MB
1.9 MB
In fact, the total size of Hamburgbahn.de main page is 2.4 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. 40% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 15.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 15.2 kB or 74% of the original size.
Potential reduce by 26.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. Hamburgbahn images are well optimized though.
Potential reduce by 298.5 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 298.5 kB or 70% of the original size.
Potential reduce by 169.8 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. Hamburgbahn.de needs all CSS files to be minified and compressed as it can save up to 169.8 kB or 85% of the original size.
Number of requests can be reduced by 25 (63%)
40
15
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hamburgbahn. 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 9 to 1 for CSS and as a result speed up the page load time.
hamburgbahn.de
514 ms
wp-emoji-release.min.js
206 ms
layerslider.css
767 ms
css
27 ms
styles.css
772 ms
swfobject.js
781 ms
jquery.js
1086 ms
jquery-migrate.min.js
779 ms
layerslider.kreaturamedia.jquery.js
407 ms
greensock.js
611 ms
layerslider.transitions.js
714 ms
jquery.cu3er.js
818 ms
style.css
958 ms
primary-red.css
865 ms
secondary-red.css
881 ms
_mobile.css
883 ms
css
35 ms
comment-reply.js
918 ms
custom-main.js
1051 ms
jquery.prettyPhoto.js
1169 ms
jquery.superfish.js
984 ms
jquery.cycle.all.min.js
1020 ms
jquery.easing.1.3.js
1049 ms
jquery.isotope.js
1195 ms
jquery.form.min.js
1168 ms
scripts.js
1168 ms
wp-embed.min.js
1169 ms
bg_bahn.jpg
424 ms
bg-top-aside-shadow.png
129 ms
bg-ui-gradient.png
131 ms
heg-unterseite.png
131 ms
blank.gif
130 ms
shadow-5.png
125 ms
bg-ui-shadow-bottom.png
181 ms
banner-abstract.png
558 ms
-bg-ui-gradient.png
197 ms
sprite.png
605 ms
skin.css
112 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
5 ms
skin.png
104 ms
cargobahn2.png
1134 ms
loading.gif
104 ms
hamburgbahn.de 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
Document doesn't have a <title> element
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
hamburgbahn.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
hamburgbahn.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
N/A
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hamburgbahn.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Hamburgbahn.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.
hamburgbahn.de
Open Graph data is detected on the main page of Hamburgbahn. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: