6.6 sec in total
304 ms
5.9 sec
387 ms
Visit funpark-hannover.de now to see the best up-to-date Funpark Hannover content for Germany and also check out these interesting facts you probably never knew about funpark-hannover.de
Visit funpark-hannover.deWe analyzed Funpark-hannover.de page load time and found that the first response time was 304 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
funpark-hannover.de performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value4.0 s
51/100
25%
Value9.8 s
10/100
10%
Value610 ms
48/100
30%
Value0.192
64/100
15%
Value7.7 s
45/100
10%
304 ms
3638 ms
848 ms
462 ms
567 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 76% of them (28 requests) were addressed to the original Funpark-hannover.de, 22% (8 requests) were made to Scontent.xx.fbcdn.net and 3% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Funpark-hannover.de.
Page size can be reduced by 319.3 kB (26%)
1.2 MB
889.0 kB
In fact, the total size of Funpark-hannover.de main page is 1.2 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. 30% of websites need less resources to load. Images take 815.6 kB which makes up the majority of the site volume.
Potential reduce by 20.4 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 20.4 kB or 76% of the original size.
Potential reduce by 9.4 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. Funpark Hannover images are well optimized though.
Potential reduce by 150.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 150.4 kB or 74% of the original size.
Potential reduce by 139.0 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. Funpark-hannover.de needs all CSS files to be minified and compressed as it can save up to 139.0 kB or 86% of the original size.
Number of requests can be reduced by 9 (27%)
33
24
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funpark Hannover. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
funpark-hannover.de
304 ms
www.funpark-hannover.de
3638 ms
bootstrap.css
848 ms
yamm.css
462 ms
funpark.css
567 ms
jquery-1.10.2.min.js
819 ms
jquery.mb.browser.min.js
532 ms
bootstrap.js
703 ms
utils.js
602 ms
jquery.fancybox-1.3.4.js
819 ms
jquery.fancybox-1.3.4.css
696 ms
all.js
269 ms
swfobject.js
726 ms
12747416_1260275303988272_1920890820565677924_o.jpg
95 ms
bgIm.jpg
208 ms
bg_big.jpg
875 ms
headerBg.jpg
207 ms
logo.png
273 ms
facebook_top.png
276 ms
youtube_top.png
186 ms
mail_top.png
284 ms
wrapper.png
433 ms
beispielimage_index.png
432 ms
spacer.gif
509 ms
banner2.jpg
622 ms
to_thetop.png
476 ms
12771569_1266667356682400_1332231176554215059_o.jpg
48 ms
12715930_1254420997907036_1341726459975836463_o.jpg
46 ms
12783713_1267948596554276_8757954778364187194_o.jpg
50 ms
azoft-sans.ttf
953 ms
azoft-sans.otf
1075 ms
azoft-sans-bold.ttf
927 ms
azoft-sans-bold.otf
1091 ms
12705315_1260275303988272_1920890820565677924_n.jpg
6 ms
12705728_1254420997907036_1341726459975836463_n.jpg
3 ms
12804882_1267937013222101_4589285349009754789_n.jpg
3 ms
12790850_1267948596554276_8757954778364187194_n.jpg
6 ms
funpark-hannover.de accessibility score
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
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
funpark-hannover.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
funpark-hannover.de SEO score
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 Funpark-hannover.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 Funpark-hannover.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.
funpark-hannover.de
Open Graph description is not detected on the main page of Funpark Hannover. 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: