3.8 sec in total
393 ms
3.3 sec
112 ms
Visit walhedo.de now to see the best up-to-date Walhedo content for Germany and also check out these interesting facts you probably never knew about walhedo.de
Hier kaufen Sie preiswerte Badkeramik, Badarmaturen, Spülkästen, Badheizkörper, Umwälzpumpen, Fittings, Badlüfter und Rückstauklappen!
Visit walhedo.deWe analyzed Walhedo.de page load time and found that the first response time was 393 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
walhedo.de performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value3.4 s
66/100
25%
Value5.2 s
61/100
10%
Value80 ms
99/100
30%
Value0.495
16/100
15%
Value5.7 s
68/100
10%
393 ms
666 ms
160 ms
592 ms
793 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 7% of them (6 requests) were addressed to the original Walhedo.de, 83% (67 requests) were made to Static.my-eshop.info and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (793 ms) relates to the external source Static.my-eshop.info.
Page size can be reduced by 49.9 kB (14%)
349.5 kB
299.6 kB
In fact, the total size of Walhedo.de main page is 349.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. 25% of websites need less resources to load. Javascripts take 193.0 kB which makes up the majority of the site volume.
Potential reduce by 37.9 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 37.9 kB or 80% of the original size.
Potential reduce by 813 B
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. Walhedo images are well optimized though.
Potential reduce by 6.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 4.9 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. Walhedo.de has all CSS files already compressed.
Number of requests can be reduced by 70 (90%)
78
8
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Walhedo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 68 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
walhedo.de
393 ms
walhedo.de
666 ms
160 ms
package-sf.css
592 ms
package-sf.js
793 ms
StorefrontStyle_1670.css
359 ms
addthis_widget.js
18 ms
passwordsecurity.css
511 ms
style-ie.css
99 ms
de-DE.js
121 ms
EUR.js
121 ms
string.js
192 ms
legacy.js
194 ms
tools.js
208 ms
constants.js
290 ms
browser.js
291 ms
scope.js
311 ms
json.js
388 ms
base64.js
389 ms
inject-sec-token.js
403 ms
cookie.js
413 ms
storage.js
415 ms
$pub.js
422 ms
data.js
480 ms
disable-selection.js
481 ms
focusable.js
496 ms
form.js
513 ms
ie.js
508 ms
keycode.js
521 ms
labels.js
577 ms
jquery-1-7.js
578 ms
plugin.js
594 ms
safe-active-element.js
607 ms
safe-blur.js
615 ms
scroll-parent.js
623 ms
tabbable.js
674 ms
unique-id.js
675 ms
version.js
692 ms
mouse.js
704 ms
dialog.js
719 ms
tabs.js
727 ms
slider.js
774 ms
class.js
772 ms
mime.js
789 ms
analytics.js
32 ms
X44765493176B5AFCEB97A72544C110CE.js
410 ms
Logoletzt.png
238 ms
20120903-b2b-de-DE-spotTeaser-300x250-v1.gif
223 ms
ga.js
26 ms
$dict.js
696 ms
$tmpl.js
714 ms
core.js
721 ms
collect
12 ms
inpage_linkid.js
6 ms
js
60 ms
__utm.gif
10 ms
support.js
687 ms
load.js
687 ms
touch.js
691 ms
version.js
622 ms
validate.js
642 ms
de_epages.js
630 ms
cookiemessage.js
589 ms
$ready.js
589 ms
energylabel.js
593 ms
passwordsecurity.js
595 ms
utf8.js
622 ms
button.js
315 ms
draggable.js
346 ms
resizable.js
347 ms
escape-selector.js
359 ms
dict.de.json
297 ms
simpledialog.js
165 ms
dictionary.de.json
135 ms
button.js
128 ms
draggable.js
99 ms
resizable.js
117 ms
controlgroup.js
98 ms
checkboxradio.js
104 ms
controlgroup.js
99 ms
checkboxradio.js
98 ms
walhedo.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.
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.
walhedo.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
walhedo.de SEO score
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 Walhedo.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 Walhedo.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.
walhedo.de
Open Graph description is not detected on the main page of Walhedo. 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: