7.2 sec in total
2.5 sec
4.5 sec
191 ms
Click here to check amazing Hannover Stadtmobil content for Germany. Otherwise, check out these important facts you probably never knew about hannover.stadtmobil.de
CarSharing heißt Autoteilen: Autos flexibel nutzen, ohne eines besitzen müssen. Stadtmobil CarSharing in Berlin, Hannover, Karlsruhe, Rhein-Main, Rhein-Neckar, Rhein-Ruhr und Stuttgart.
Visit hannover.stadtmobil.deWe analyzed Hannover.stadtmobil.de page load time and found that the first response time was 2.5 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
hannover.stadtmobil.de performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value30.9 s
0/100
25%
Value21.5 s
0/100
10%
Value6,340 ms
0/100
30%
Value0.001
100/100
15%
Value37.8 s
0/100
10%
2517 ms
1378 ms
1379 ms
1286 ms
1287 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 95% of them (55 requests) were addressed to the original Hannover.stadtmobil.de, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Hannover.stadtmobil.de.
Page size can be reduced by 269.3 kB (29%)
921.5 kB
652.1 kB
In fact, the total size of Hannover.stadtmobil.de main page is 921.5 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. 20% of websites need less resources to load. Images take 558.8 kB which makes up the majority of the site volume.
Potential reduce by 25.0 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. This page needs HTML code to be minified as it can gain 4.0 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.0 kB or 79% of the original size.
Potential reduce by 42.3 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. Hannover Stadtmobil images are well optimized though.
Potential reduce by 163.2 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 163.2 kB or 58% of the original size.
Potential reduce by 38.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. Hannover.stadtmobil.de needs all CSS files to be minified and compressed as it can save up to 38.8 kB or 82% of the original size.
Number of requests can be reduced by 31 (55%)
56
25
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hannover Stadtmobil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
hannover.stadtmobil.de
2517 ms
stylesheet_e5c40cd2b5.css
1378 ms
iceflavorstyles_206349347iceflavor.css
1379 ms
rggooglemaps.css
1286 ms
main.css
1287 ms
navigation.css
1380 ms
content.css
372 ms
lightbox.css
466 ms
msie.css
561 ms
jquery-1.6.1-1.8.13-1.2.5.js
1035 ms
googlemaps_enhancer.js
1129 ms
carlist.js
1222 ms
checkPasswordInput.js
1315 ms
glossary.js
1373 ms
javascript_93077bb238.js
1373 ms
socialbookmarks.js
1431 ms
tipafriend.js
1462 ms
lightbox.js
1464 ms
jsbn.js
1478 ms
prng4.js
1401 ms
rng.js
1401 ms
rsa.js
1422 ms
base64.js
1473 ms
rsaauth_min.js
1479 ms
powermail_validation.js
1303 ms
ga.js
19 ms
logo.gif
115 ms
buttonback2.gif
131 ms
buttonback.gif
178 ms
rightback.gif
183 ms
loginback.gif
182 ms
de.png
183 ms
gb.png
188 ms
co2ausstoss_klein.png
230 ms
ff4e410073.png
561 ms
c4e4711e45.png
563 ms
5671c6c4fb.png
277 ms
65d8914322.png
658 ms
e6159a1df2.png
281 ms
f1af8e4fd7.png
332 ms
72fc8a7147.png
373 ms
023fc59cc4.jpeg
377 ms
e6ce1e2812.jpg
425 ms
__utm.gif
13 ms
collect
82 ms
mapback.gif
373 ms
f22ed5e230.png
378 ms
741a05798f.png
426 ms
4c50ed26d0.png
468 ms
38d556bc37.png
473 ms
ab73f5363b.png
520 ms
3d7d4fe574.png
558 ms
2a555d6269.png
562 ms
newsicon.png
562 ms
footerback_neu.gif
566 ms
totop.gif
613 ms
print.gif
651 ms
facebook.gif
654 ms
hannover.stadtmobil.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
button, link, and menuitem elements do not have accessible names.
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
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
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.
hannover.stadtmobil.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
hannover.stadtmobil.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hannover.stadtmobil.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 Hannover.stadtmobil.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.
hannover.stadtmobil.de
Open Graph description is not detected on the main page of Hannover Stadtmobil. 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: