4.9 sec in total
349 ms
4.2 sec
444 ms
Welcome to elbdampfer-hamburg.de homepage info - get ready to check Elbdampfer Hamburg best content for Germany right away, or after learning these important things about elbdampfer-hamburg.de
Jahrzehntelang gehörten die bulligen HADAG-Hafenfähren zu Hamburg. In dieser Web-Doku erfahren Sie alles über ihre packende Geschichte & ihren Verbleib.
Visit elbdampfer-hamburg.deWe analyzed Elbdampfer-hamburg.de page load time and found that the first response time was 349 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
elbdampfer-hamburg.de performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value9.4 s
1/100
25%
Value10.3 s
8/100
10%
Value890 ms
32/100
30%
Value1
2/100
15%
Value11.9 s
16/100
10%
349 ms
916 ms
184 ms
294 ms
322 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 50% of them (53 requests) were addressed to the original Elbdampfer-hamburg.de, 17% (18 requests) were made to Fonts.gstatic.com and 8% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Elbdampfer-hamburg.de.
Page size can be reduced by 286.9 kB (42%)
686.4 kB
399.5 kB
In fact, the total size of Elbdampfer-hamburg.de main page is 686.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 340.6 kB which makes up the majority of the site volume.
Potential reduce by 122.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. 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 122.8 kB or 83% of the original size.
Potential reduce by 1.0 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. Elbdampfer Hamburg images are well optimized though.
Potential reduce by 153.9 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 153.9 kB or 45% of the original size.
Potential reduce by 9.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. Elbdampfer-hamburg.de has all CSS files already compressed.
Number of requests can be reduced by 57 (69%)
83
26
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elbdampfer Hamburg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
elbdampfer-hamburg.de
349 ms
www.elbdampfer-hamburg.de
916 ms
wp-emoji-release.min.js
184 ms
widget.css
294 ms
style.min.css
322 ms
blocks.style.build.css
321 ms
bbpress.min.css
326 ms
front.min.css
324 ms
media-credit.min.css
324 ms
shortcode.css
402 ms
wpp.css
427 ms
jquery-ui.css
19 ms
bootstrap.css
432 ms
font-awesome.min.css
429 ms
theme_plugins.css
435 ms
bkstyle.css
541 ms
woocommerce.css
509 ms
bbpress.css
533 ms
responsive.css
539 ms
style.css
536 ms
front.min.css
537 ms
jquery.min.js
731 ms
jquery-migrate.min.js
638 ms
login-with-ajax.js
642 ms
wpp.min.js
643 ms
jquery-ui.js
21 ms
adsbygoogle.js
64 ms
ads.js
643 ms
css
48 ms
front.min.js
578 ms
shortcode.js
753 ms
core.min.js
756 ms
tabs.min.js
756 ms
accordion.min.js
757 ms
theme_plugins.js
815 ms
onviewport.js
792 ms
module-load-post.js
792 ms
menu.js
797 ms
customjs.js
796 ms
comment-reply.min.js
795 ms
retina.min.js
941 ms
2566c291e59e185c12a331fef1e235f3.css
1097 ms
front.min.js
835 ms
new-tab.js
726 ms
wp-embed.min.js
709 ms
2566c291e59e185c12a331fef1e235f3.js
733 ms
zrt_lookup.html
58 ms
Elbdampfer-logo_2009.png
426 ms
c92f8fcf53451fe3ec1de94c6632bca6
93 ms
HADAG-Neubau-2030-002-350x238.jpg
423 ms
Kehrwieder4-350x238.jpg
643 ms
20170202-bergedorf_1972_1_20120412_1414582270-350x238.jpg
423 ms
hadad_logo_vertikal02_gruen.png
423 ms
24849-featured-80x80.jpg
531 ms
24061-featured-80x80.jpg
642 ms
25984-featured-80x80.jpg
642 ms
no_thumb.jpg
642 ms
29c8246c422804c844a7c5fd626f415b
151 ms
26619299e8a952762b77a64578a80530
151 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf
120 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf
155 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf
194 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf
195 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVcUwaEQXjM.ttf
194 ms
fontawesome-webfont.woff
675 ms
tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvLFG6o3mpNiEr6Aab.ttf
389 ms
tss5ApVBdCYD5Q7hcxTE1ArZ0Zz8oY2KRmwvKhhvy1a6o3mpNiEr6Aab.ttf
390 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2RmV9Su1fah.ttf
215 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2RmV9Su1fah.ttf
390 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2RmV9Su1fah.ttf
213 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2RmV9Su1fah.ttf
390 ms
show_ads_impl.js
175 ms
ajax_load.gif
581 ms
nbpytl
553 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexYMUdjFnmg.ttf
145 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexYMUdjFnmg.ttf
313 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexYMUdjFnmg.ttf
145 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexYMUdjFnmg.ttf
238 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexYMUdjFnmg.ttf
313 ms
analytics.js
302 ms
cookie.js
308 ms
integrator.js
312 ms
ads
581 ms
nbpytl
71 ms
ads
448 ms
collect
48 ms
994f120a8a1049a5db4e9815aa0f2047.js
79 ms
load_preloaded_resource.js
141 ms
5b53d7d5e4c65027251dcefda1e55898.js
106 ms
abg_lite.js
142 ms
window_focus.js
175 ms
qs_click_protection.js
176 ms
rx_lidar.js
174 ms
05878b7632cfc2730fe1a101bdcf9d1c.js
140 ms
14763004658117789537
184 ms
icon.png
170 ms
s
18 ms
css
16 ms
activeview
38 ms
sodar
53 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyzAFyo4d4k.ttf
15 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyzAFyo4d4k.ttf
15 ms
sodar2.js
26 ms
runner.html
15 ms
aframe
20 ms
f36U5LLOSFCl_RQcRb4gz5dtt8ZR3FgOTI7LNXASQxk.js
4 ms
elbdampfer-hamburg.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
elbdampfer-hamburg.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
elbdampfer-hamburg.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
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 Elbdampfer-hamburg.de 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 Elbdampfer-hamburg.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.
elbdampfer-hamburg.de
Open Graph data is detected on the main page of Elbdampfer Hamburg. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: