6.5 sec in total
631 ms
5.3 sec
547 ms
Click here to check amazing Schnapshaeusle content. Otherwise, check out these important facts you probably never knew about schnapshaeusle.de
Feine Auswahl an Obstbränden, Schnaps, Likör, Spirituosen bei uns im Shop ✔ Sicher online kaufen mit SSL ✔ Schnelle Lieferung
Visit schnapshaeusle.deWe analyzed Schnapshaeusle.de page load time and found that the first response time was 631 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
schnapshaeusle.de performance score
631 ms
321 ms
443 ms
317 ms
334 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Schnapshaeusle.de, 13% (10 requests) were made to Gepruefter-webshop.de and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Schnapshaeusle.com.
Page size can be reduced by 765.2 kB (44%)
1.7 MB
965.3 kB
In fact, the total size of Schnapshaeusle.de main page is 1.7 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. 35% of websites need less resources to load. Images take 724.5 kB which makes up the majority of the site volume.
Potential reduce by 43.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. This page needs HTML code to be minified as it can gain 14.9 kB, which is 29% 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 43.5 kB or 84% of the original size.
Potential reduce by 14.9 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. Schnapshaeusle images are well optimized though.
Potential reduce by 402.0 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 402.0 kB or 69% of the original size.
Potential reduce by 304.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. Schnapshaeusle.de needs all CSS files to be minified and compressed as it can save up to 304.7 kB or 81% of the original size.
Number of requests can be reduced by 34 (47%)
73
39
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Schnapshaeusle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.schnapshaeusle.com
631 ms
framework.css
321 ms
style.css
443 ms
colors.css
317 ms
plugins.css
334 ms
enrichments.css
316 ms
emotion.css
450 ms
emotion_brown.css
644 ms
paypal.css
632 ms
jquery-1.7.2.min.js
763 ms
jquery.shopware.js
873 ms
jquery.emotion.js
777 ms
background_wood.png
423 ms
hotjar-153873.js
215 ms
ga.js
104 ms
Gepruefter-Webshop-Siegel.png
690 ms
top_background.png
300 ms
bg_arrow_search.gif
346 ms
ico_ajax-loader.gif
343 ms
logo.jpg
340 ms
ico_myaccount.png
339 ms
ico_notes.png
493 ms
ico_info.png
615 ms
cart.png
655 ms
ico_basket.png
655 ms
schnapshaeusle_banner_start539d98def1d3d.png
1078 ms
selection_teaser.png
974 ms
aggstein_teaser_ready.png
1121 ms
sale_banner.png
934 ms
neu_im_sortiment_banner.png
971 ms
obstschnaps_teaser_small.png
1185 ms
blog_banner.png
1247 ms
anfahrt_oeffnung_banner.png
1290 ms
ship_logo.png
1294 ms
payment_banner.png
1395 ms
oekostrom.png
1451 ms
ssl.png
1499 ms
facebook_sh.png
1566 ms
gplus_sh.png
1603 ms
twitter_sh.png
1608 ms
pinterest_sh.png
1709 ms
sprite_listing_2.png
1752 ms
sprite_stars.png
1800 ms
itswoodka_scheibel_188x230.png
2071 ms
button_prod.png
1903 ms
heart_back.png
1907 ms
ico_pseudo.png
2010 ms
absinth_aggstein_188x230.jpg
2066 ms
inlaender_rum_38_05_188x230.jpg
2116 ms
tiroler_zirbenschnaps_188x230.jpg
2224 ms
tiroler_zirbenlikoer_05_neu_188x230.jpg
2223 ms
814 ms
__utm.gif
14 ms
collect
54 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
48 ms
zwetschge_05_sh_188x230.jpg
2112 ms
marille_05_sh_188x230.jpg
2073 ms
marillenlimes_05_188x230.jpg
2121 ms
background_detail.png
2324 ms
wrapper_sprite.png
2218 ms
arrow_right.png
2235 ms
ico_closebutton.png
2113 ms
visit-data
224 ms
sprite-banner-slider.png
2114 ms
css
58 ms
css
73 ms
gepruefter-webshop-iframe.css
331 ms
ccm.base.css
336 ms
jquery.js
454 ms
ccm.base.js
338 ms
jquery.raty.js
340 ms
whitey.png
662 ms
gw-logo-iframe.png
319 ms
star-on.png
335 ms
print.css
167 ms
schnapshaeusle.de SEO score
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Schnapshaeusle.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 Schnapshaeusle.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.
schnapshaeusle.de
Open Graph description is not detected on the main page of Schnapshaeusle. 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: