2.9 sec in total
306 ms
2.4 sec
168 ms
Click here to check amazing StadtRAD Hamburg content for Germany. Otherwise, check out these important facts you probably never knew about stadtrad.hamburg.de
Willkommen bei StadtRAD Hamburg, dem smarten Bikesharing für Hamburg und Umgebung.
Visit stadtrad.hamburg.deWe analyzed Stadtrad.hamburg.de page load time and found that the first response time was 306 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
stadtrad.hamburg.de performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value11.9 s
0/100
25%
Value8.4 s
18/100
10%
Value600 ms
49/100
30%
Value0
100/100
15%
Value11.5 s
18/100
10%
306 ms
107 ms
611 ms
353 ms
211 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 38% of them (26 requests) were addressed to the original Stadtrad.hamburg.de, 32% (22 requests) were made to Maps.google.com and 12% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (883 ms) belongs to the original domain Stadtrad.hamburg.de.
Page size can be reduced by 826.5 kB (47%)
1.8 MB
930.4 kB
In fact, the total size of Stadtrad.hamburg.de main page is 1.8 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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 30.3 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.3 kB or 82% of the original size.
Potential reduce by 19.5 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. StadtRAD Hamburg images are well optimized though.
Potential reduce by 733.4 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 733.4 kB or 69% of the original size.
Potential reduce by 43.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. Stadtrad.hamburg.de needs all CSS files to be minified and compressed as it can save up to 43.3 kB or 86% of the original size.
Number of requests can be reduced by 35 (58%)
60
25
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of StadtRAD 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 28 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
stadtrad.hamburg.de
306 ms
kundenbuchung
107 ms
611 ms
style.css
353 ms
omq510.css
211 ms
iam.js
189 ms
flowplayer-3.1.4.min.js
281 ms
sprintf.js
214 ms
multilangjs.php
216 ms
libhal2kubu.min.js
883 ms
app510.min.js
280 ms
js
29 ms
hal2mapconfig.js
319 ms
libhal2maps.min.js
678 ms
defaultmapinit.js
384 ms
bikesuche.js
384 ms
omq-self-service-min.js
419 ms
json2.js
527 ms
omq-self-service.css
319 ms
get_flash_player.gif
16 ms
verlauf.jpg
107 ms
flagge_de.gif
109 ms
Collage_Website2_HH.jpg
557 ms
090422_02_22_home.jpg
245 ms
tx.io
291 ms
bg_mainnav.jpg
199 ms
bg_teaser.jpg
201 ms
btn_search_bg.jpg
275 ms
icon_link.gif
304 ms
tx.io
172 ms
common.js
28 ms
util.js
30 ms
marker.js
29 ms
geocoder.js
27 ms
controls.js
27 ms
drawing_impl.js
27 ms
map.js
16 ms
infowindow.js
13 ms
loader_medium.gif
114 ms
StaticMapService.GetMapImage
247 ms
onion.js
11 ms
openhand_8_8.cur
39 ms
ViewportInfoService.GetViewportInfo
66 ms
stats.js
26 ms
css
34 ms
transparent.png
33 ms
google4.png
34 ms
mapcnt6.png
48 ms
sv5.png
47 ms
tmapctrl.png
35 ms
tmapctrl4.png
41 ms
imgs8.png
35 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
32 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
34 ms
Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff
41 ms
d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff
41 ms
vt
73 ms
vt
74 ms
vt
69 ms
vt
63 ms
vt
57 ms
vt
69 ms
vt
123 ms
vt
108 ms
vt
120 ms
vt
121 ms
AuthenticationService.Authenticate
113 ms
usage.js
2 ms
stadtrad.hamburg.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
stadtrad.hamburg.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
stadtrad.hamburg.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stadtrad.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 Stadtrad.hamburg.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
stadtrad.hamburg.de
Open Graph description is not detected on the main page of StadtRAD Hamburg. 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: