5.1 sec in total
292 ms
4.5 sec
326 ms
Visit spruengli.com now to see the best up-to-date Spruengli content and also check out these interesting facts you probably never knew about spruengli.com
For over 175 years, Confiserie Sprüngli has been spoiling customers worldwide with its creations made from Swiss chocolate or the unique Luxemburgerli.
Visit spruengli.comWe analyzed Spruengli.com page load time and found that the first response time was 292 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
spruengli.com performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value8.6 s
1/100
25%
Value19.5 s
0/100
10%
Value2,300 ms
5/100
30%
Value0.055
98/100
15%
Value18.9 s
3/100
10%
292 ms
1713 ms
30 ms
98 ms
193 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Spruengli.com, 81% (65 requests) were made to Spruengli.ch and 5% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Spruengli.ch.
Page size can be reduced by 185.1 kB (4%)
4.3 MB
4.1 MB
In fact, the total size of Spruengli.com main page is 4.3 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. 70% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 124.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 17.2 kB, which is 11% 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 124.5 kB or 83% of the original size.
Potential reduce by 323 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. Spruengli images are well optimized though.
Potential reduce by 50.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. This website has mostly compressed JavaScripts.
Potential reduce by 10.1 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. Spruengli.com needs all CSS files to be minified and compressed as it can save up to 10.1 kB or 27% of the original size.
Number of requests can be reduced by 51 (74%)
69
18
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spruengli. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
spruengli.com
292 ms
en
1713 ms
mkz5zoo.js
30 ms
content.css
98 ms
gzip.php
193 ms
stylesheet.css
382 ms
override.css
291 ms
font-awesome.min.css
289 ms
template.css
292 ms
cpnb-style.min.css
291 ms
gzip.php
297 ms
gzip.php
401 ms
gzip.php
1396 ms
qlsmoothscroll.js
401 ms
gzip.php
485 ms
gzip.php
401 ms
gzip.php
584 ms
gzip.php
483 ms
gzip.php
1484 ms
bootstrap.min.js
491 ms
common.js
578 ms
cookies-policy-notification-bar.min.js
580 ms
uikit2-9454d4e2.js
589 ms
wk-scripts-459ab169.js
675 ms
gzip.php
683 ms
gzip.php
790 ms
gzip.php
926 ms
social.js
770 ms
autocomplete.js
779 ms
search.js
867 ms
tooltip.js
875 ms
sticky.js
886 ms
theme.js
962 ms
jquery.color.js
970 ms
jquery.easing.1.3.js
992 ms
spr_popup.js
1021 ms
intlTelInput.js
1154 ms
telephone.js
1065 ms
autoComplete.js
22 ms
css
46 ms
smartslider.min.css
1085 ms
n2.min.js
1027 ms
smartslider-frontend.min.js
1075 ms
ss-simple.min.js
898 ms
w-bullet.min.js
937 ms
gtm.js
199 ms
gtm.js
199 ms
css
35 ms
css
52 ms
arrow-m-down.png
182 ms
minus-circle.svg
177 ms
logo.svg
178 ms
spruengli-amaretti-startseite.jpeg
815 ms
spruengli-bruchschokoladen-staengeli-startseite.jpeg
738 ms
spruengli-standorte-titelbild-startseite-komprimiert.jpg
396 ms
handelsverband-siegel.svg
242 ms
logo.svg
199 ms
d
130 ms
d
203 ms
nav-search.svg
138 ms
Gold.svg
226 ms
nav-account.svg
228 ms
standorte.jpg
617 ms
neuheiten-events.jpg
617 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
71 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
72 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
118 ms
d
547 ms
luna.woff
548 ms
fontawesome-webfont.woff
548 ms
fontawesome-webfont.woff
550 ms
spruengli-startseite-luxemburgerli-winter-2.jpg
495 ms
spruengli-startseite-selection-pralines-truffes-standard.jpg
495 ms
spruengli-startseite-widget-cafe-und-restaurant_2.jpg
495 ms
hochzeitstorte-luxemburgerli-traum.jpg
435 ms
firmenkunden.jpg
435 ms
globe.svg
399 ms
check-m-white.svg
403 ms
White.svg
98 ms
p.gif
29 ms
spruengli.com 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
spruengli.com 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
Missing source maps for large first-party JavaScript
spruengli.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spruengli.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Spruengli.com 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.
spruengli.com
Open Graph description is not detected on the main page of Spruengli. 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: