2.8 sec in total
637 ms
1.9 sec
257 ms
Welcome to stattbad.net homepage info - get ready to check Stattbad best content for Germany right away, or after learning these important things about stattbad.net
Visit stattbad.netWe analyzed Stattbad.net page load time and found that the first response time was 637 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
stattbad.net performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value3.0 s
79/100
25%
Value5.1 s
62/100
10%
Value510 ms
57/100
30%
Value0
100/100
15%
Value7.4 s
49/100
10%
637 ms
106 ms
26 ms
6 ms
323 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Stattbad.net, 27% (16 requests) were made to Wp.stattbad.net and 23% (14 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (788 ms) relates to the external source Wp.stattbad.net.
Page size can be reduced by 792.6 kB (53%)
1.5 MB
697.4 kB
In fact, the total size of Stattbad.net main page is 1.5 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. 50% of websites need less resources to load. Javascripts take 916.2 kB which makes up the majority of the site volume.
Potential reduce by 11.5 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 11.5 kB or 72% of the original size.
Potential reduce by 14.7 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. Stattbad images are well optimized though.
Potential reduce by 628.7 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 628.7 kB or 69% of the original size.
Potential reduce by 137.7 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. Stattbad.net needs all CSS files to be minified and compressed as it can save up to 137.7 kB or 82% of the original size.
Number of requests can be reduced by 30 (59%)
51
21
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stattbad. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
stattbad.net
637 ms
language-selector.css
106 ms
css
26 ms
font-awesome.min.css
6 ms
styles.css
323 ms
bootstrap-wp.css
344 ms
bootstrap.min.css
430 ms
style.css
323 ms
jquery.js
472 ms
jquery-migrate.min.js
325 ms
bootstrap.min.js
429 ms
bootstrap-wp.js
426 ms
jquery.form.min.js
441 ms
scripts.js
447 ms
skip-link-focus-fix.js
543 ms
sitepress.js
206 ms
wp-emoji-release.min.js
427 ms
embed
170 ms
logo.png
111 ms
icon-fb.png
124 ms
icon-sc.png
143 ms
Robert-Montgomery_Installation-view-Stattbad-Wedding_2012_photo-by-Kai-von-Rabenau_feature1.jpg
788 ms
analytics.js
18 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
29 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
37 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
53 ms
fontawesome-webfont.woff
11 ms
collect
15 ms
js
67 ms
init_embed.js
45 ms
common.js
51 ms
map.js
51 ms
google4.png
74 ms
overlay.js
10 ms
util.js
68 ms
onion.js
68 ms
search_impl.js
69 ms
StaticMapService.GetMapImage
105 ms
stats.js
33 ms
openhand_8_8.cur
41 ms
ViewportInfoService.GetViewportInfo
92 ms
ViewportInfoService.GetViewportInfo
33 ms
kh
85 ms
transparent.png
18 ms
controls.js
13 ms
ViewportInfoService.GetViewportInfo
65 ms
css
92 ms
entity11.png
52 ms
mapcnt6.png
36 ms
vt
96 ms
vt
97 ms
vt
95 ms
vt
110 ms
vt
108 ms
tmapctrl.png
19 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
59 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
73 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
79 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
92 ms
AuthenticationService.Authenticate
18 ms
stattbad.net 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
stattbad.net 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
stattbad.net 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 Stattbad.net 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 Stattbad.net 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.
stattbad.net
Open Graph description is not detected on the main page of Stattbad. 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: