6.5 sec in total
2.1 sec
4.2 sec
247 ms
Visit weinkoenig.de now to see the best up-to-date Weinkoenig content and also check out these interesting facts you probably never knew about weinkoenig.de
Alkoholfreie Weine & Zubehör ✓gesunde Alternative zu Sekt & Wein ✓höchste Qualität ✓hervorragender Geschmack
Visit weinkoenig.deWe analyzed Weinkoenig.de page load time and found that the first response time was 2.1 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
weinkoenig.de performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value7.1 s
5/100
25%
Value5.9 s
48/100
10%
Value140 ms
95/100
30%
Value0.082
94/100
15%
Value7.1 s
52/100
10%
2112 ms
369 ms
186 ms
186 ms
242 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 96% of them (90 requests) were addressed to the original Weinkoenig.de, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Static.shopgate.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Weinkoenig.de.
Page size can be reduced by 69.6 kB (73%)
95.4 kB
25.8 kB
In fact, the total size of Weinkoenig.de main page is 95.4 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. 45% of websites need less resources to load. HTML takes 49.1 kB which makes up the majority of the site volume.
Potential reduce by 40.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. This page needs HTML code to be minified as it can gain 6.2 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 40.4 kB or 82% of the original size.
Potential reduce by 29.1 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 29.1 kB or 63% of the original size.
Number of requests can be reduced by 27 (30%)
90
63
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weinkoenig. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.weinkoenig.de
2112 ms
styles.css
369 ms
css3.css
186 ms
custom.css
186 ms
widget.css
242 ms
stock_indicator.css
189 ms
trustedrating.css
270 ms
prototype.js
643 ms
validation.js
376 ms
builder.js
282 ms
effects.js
451 ms
dragdrop.js
468 ms
controls.js
530 ms
slider.js
457 ms
js.js
460 ms
form.js
543 ms
menu.js
550 ms
translate.js
551 ms
cookies.js
562 ms
jquery.latest.js
819 ms
imgpreview.js
634 ms
jquery.pop.js
658 ms
cufon.js
658 ms
font.js
746 ms
fancybox.js
727 ms
slider.js
732 ms
jcarousel.js
733 ms
custom.js
736 ms
12705.js
11 ms
print.css
95 ms
header_bg.jpg
144 ms
header_bg.gif
102 ms
search_bg.gif
101 ms
search_btn.gif
100 ms
logo.gif
101 ms
Deutsch.png
165 ms
English.png
187 ms
HP_UMZUG1.jpg
275 ms
ROSE_12.jpg
374 ms
teaser1.jpg
192 ms
teaser2.jpg
232 ms
teaser3.jpg
254 ms
teaser4.jpg
276 ms
teaser5.jpg
289 ms
Logo_Dennree.gif
414 ms
Naturian_L.gif
345 ms
bodan.gif
366 ms
KontaktM.jpg
366 ms
401_14.jpg
384 ms
405_2015_hp.jpg
437 ms
752_4er_rose_web.jpg
458 ms
407_12_web.jpg
460 ms
gren.jpg
466 ms
143_breit_web.jpg
482 ms
420_2015_1hp.jpg
504 ms
403_2015_hp_1.jpg
528 ms
145_1.jpg
549 ms
140z.jpg
551 ms
400_2015_hp.jpg
559 ms
404_15_hp.jpg
577 ms
705.jpg
596 ms
409_romance_en_rose_web.jpg
620 ms
144z.jpg
640 ms
714_1.jpg
643 ms
402_15_hps.jpg
652 ms
ga.js
35 ms
__utm.gif
17 ms
430_15_hp.jpg
583 ms
cockt_2.jpg
597 ms
bitter_250ml_hp.jpg
619 ms
410_15_hp.jpg
639 ms
141_breit.jpg
639 ms
collect
60 ms
431_web.jpg
612 ms
755_rotwein_web.jpg
616 ms
barbesteck1.jpg
602 ms
curac.jpg
619 ms
906.jpg
600 ms
709a.jpg
582 ms
barmass_2.jpg
575 ms
k-g_impuls_1er.jpg
603 ms
logo_footer.gif
592 ms
basket_ico.gif
558 ms
leftbgtop.jpg
558 ms
leftbgbottom.jpg
563 ms
rightbgtop.jpg
572 ms
rightbgmid.jpg
590 ms
rightbgmidbottom.jpg
559 ms
rightbgbottom.jpg
559 ms
weinkoenig-woman-footer.gif
558 ms
newsletter_bg.gif
560 ms
bg_carousel.gif
570 ms
prev-horizontal.png
582 ms
next-horizontal.png
566 ms
weinkoenig.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.
[role]s are not contained by their required parent element
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
Some elements have a [tabindex] value greater than 0
weinkoenig.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
weinkoenig.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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weinkoenig.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 Weinkoenig.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.
weinkoenig.de
Open Graph description is not detected on the main page of Weinkoenig. 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: