3.4 sec in total
424 ms
2.6 sec
331 ms
Visit wehpke.de now to see the best up-to-date Wehpke content and also check out these interesting facts you probably never knew about wehpke.de
Visit wehpke.deWe analyzed Wehpke.de page load time and found that the first response time was 424 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
wehpke.de performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value9.7 s
0/100
25%
Value6.9 s
33/100
10%
Value180 ms
92/100
30%
Value0
100/100
15%
Value8.8 s
35/100
10%
424 ms
107 ms
191 ms
282 ms
318 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 41% of them (31 requests) were addressed to the original Wehpke.de, 17% (13 requests) were made to Maps.googleapis.com and 12% (9 requests) were made to Cdn.website-start.de. The less responsive or slowest element that took the longest time to load (703 ms) belongs to the original domain Wehpke.de.
Page size can be reduced by 640.4 kB (59%)
1.1 MB
452.6 kB
In fact, the total size of Wehpke.de main page is 1.1 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 829.0 kB which makes up the majority of the site volume.
Potential reduce by 21.7 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 21.7 kB or 72% of the original size.
Potential reduce by 7.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. Wehpke images are well optimized though.
Potential reduce by 601.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 601.2 kB or 73% of the original size.
Potential reduce by 10.2 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. Wehpke.de needs all CSS files to be minified and compressed as it can save up to 10.2 kB or 82% of the original size.
Number of requests can be reduced by 32 (46%)
70
38
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wehpke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.wehpke.de
424 ms
layout.css
107 ms
font.css
191 ms
web.css
282 ms
common,shoppingbasket
318 ms
logstate2-css.php
477 ms
logstate-js.php
484 ms
web.js
672 ms
web.bundle.js
275 ms
common,shoppingbasket
487 ms
444 ms
pfcsupport.js
444 ms
8214.js
268 ms
print.css
103 ms
site-bg.gif
113 ms
header_bg.png
95 ms
navi_glow.png
102 ms
passion_fashion_sliced_34.jpg
191 ms
passion_fashion_sliced_03.png
189 ms
passion_fashion_sliced_05.png
193 ms
passion_fashion_sliced_07.png
193 ms
passion_fashion_sliced_08.png
202 ms
passion_fashion_sliced_10.png
205 ms
passion_fashion_sliced_12.png
285 ms
passion_fashion_sliced_14.png
284 ms
passion_fashion_sliced_16.png
286 ms
passion_fashion_sliced_18.png
287 ms
passion_fashion_sliced_20.png
300 ms
passion_fashion_sliced_22.png
307 ms
passion_fashion_sliced_24.png
378 ms
passion_fashion_sliced_25.png
377 ms
passion_fashion_sliced_26.png
380 ms
passion_fashion_sliced_27.png
380 ms
passion_fashion_sliced_28.png
400 ms
passion_fashion_sliced_29.png
410 ms
passion_fashion_sliced_30.png
630 ms
passion_fashion_sliced_31.png
629 ms
passion_fashion_sliced_32.png
629 ms
emotionheader.jpg
628 ms
maps
26 ms
v22-sliced_04.png
703 ms
cache_2411244080.jpg
581 ms
printer.gif
95 ms
logo.gif
113 ms
embed
371 ms
js
57 ms
init_embed.js
31 ms
common.js
58 ms
map.js
86 ms
google4.png
44 ms
overlay.js
41 ms
util.js
86 ms
onion.js
85 ms
search_impl.js
85 ms
StaticMapService.GetMapImage
136 ms
stats.js
32 ms
ViewportInfoService.GetViewportInfo
69 ms
ViewportInfoService.GetViewportInfo
44 ms
transparent.png
42 ms
kh
112 ms
controls.js
31 ms
289 ms
vt
99 ms
vt
92 ms
vt
101 ms
vt
101 ms
vt
95 ms
css
100 ms
entity11.png
64 ms
mapcnt6.png
46 ms
tmapctrl.png
38 ms
AuthenticationService.Authenticate
33 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
39 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
44 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
61 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
59 ms
wehpke.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
wehpke.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
wehpke.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wehpke.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 Wehpke.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.
wehpke.de
Open Graph description is not detected on the main page of Wehpke. 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: