4.2 sec in total
481 ms
3.5 sec
186 ms
Click here to check amazing Wosis content. Otherwise, check out these important facts you probably never knew about wosis.com
Vienna, coffee, tea, jams, chocolate, accessories, cups, premium, gourmet, 1862, Espresso, beans, capsules, cialde, pods, filter, coldbrew, instant coffee, airline coffee, freshly roasted, sustainable...
Visit wosis.comWe analyzed Wosis.com page load time and found that the first response time was 481 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
wosis.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value9.1 s
1/100
25%
Value5.0 s
63/100
10%
Value1,180 ms
21/100
30%
Value0.327
35/100
15%
Value10.2 s
25/100
10%
481 ms
714 ms
527 ms
525 ms
19 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wosis.com, 88% (138 requests) were made to Shop.meinl.com and 6% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (714 ms) relates to the external source Shop.meinl.com.
Page size can be reduced by 266.1 kB (25%)
1.1 MB
809.3 kB
In fact, the total size of Wosis.com 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. 65% of websites need less resources to load. Images take 430.8 kB which makes up the majority of the site volume.
Potential reduce by 221.8 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 75.9 kB, which is 31% 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 221.8 kB or 92% of the original size.
Potential reduce by 5.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. Wosis images are well optimized though.
Potential reduce by 38.8 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 38.8 kB or 14% of the original size.
Potential reduce by 252 B
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. Wosis.com has all CSS files already compressed.
Number of requests can be reduced by 126 (93%)
135
9
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wosis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 118 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
wosis.com
481 ms
b7cb7356216fadf1f6340121061fc399.min.css
714 ms
styles-l.min.css
527 ms
6e77d0a10fbb41455d9f79c17a75d062.min.js
525 ms
css
19 ms
css
38 ms
css
38 ms
css
44 ms
bootstrap.optimized.min.css
434 ms
animate.optimized.css
434 ms
font-awesome.min.css
30 ms
hotjar-3063936.js
111 ms
gtm.js
131 ms
logo.png
95 ms
JM-Red-Cup-Standard-2023_RZ_Desktop-Tablet_EN.jpg
452 ms
JM-Red-Cup-Standard-2023_RZ_Mobile_EN.jpg
185 ms
euro_en.png
101 ms
euro_de.png
100 ms
jquery.min.js
272 ms
common.min.js
187 ms
dataPost.min.js
187 ms
bootstrap.min.js
284 ms
app.min.js
283 ms
form-key-provider.min.js
284 ms
mage-translation-dictionary.min.js
283 ms
theme.min.js
361 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
15 ms
opensans-400.woff
439 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
15 ms
opensans-300.woff
352 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
21 ms
opensans-600.woff
450 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
21 ms
opensans-700.woff
450 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
20 ms
porto-icons.woff
434 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
19 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
18 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf
19 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
19 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf
20 ms
sw_megamenu.min.js
371 ms
jquery-mixin.min.js
440 ms
pic-meinl-footer-middle.jpg
443 ms
pic-meinl-footer.jpg
448 ms
owl.carousel.min.js
446 ms
weltpixel_quickview.min.js
433 ms
weltpixel_ga4_persistentlayer.min.js
434 ms
weltpixel_ga4_gtm.min.js
512 ms
weltpixel_persistentlayer.min.js
515 ms
weltpixel_gtm.min.js
521 ms
customer-data.min.js
501 ms
customer-data-mixin.min.js
503 ms
domReady.min.js
459 ms
template.min.js
534 ms
confirm.min.js
537 ms
widget.min.js
543 ms
main.min.js
439 ms
bootstrap.min.js
439 ms
text.min.js
440 ms
types.min.js
516 ms
layout.min.js
516 ms
wrapper.min.js
282 ms
jquery.magnific-popup.min.js
272 ms
underscore.min.js
274 ms
local.min.js
415 ms
registry.min.js
416 ms
knockout.min.js
357 ms
section-config.min.js
327 ms
url.min.js
327 ms
storage.min.js
328 ms
storage-wrapper.min.js
327 ms
translate.min.js
276 ms
modal.min.js
288 ms
knockout-es5.min.js
281 ms
js-translation.json
281 ms
version.min.js
281 ms
scripts.min.js
354 ms
engine.min.js
353 ms
bootstrap.min.js
357 ms
observable_array.min.js
361 ms
bound-nodes.min.js
367 ms
main.min.js
289 ms
console-logger.min.js
362 ms
events.min.js
208 ms
js.storage.min.js
210 ms
mage.min.js
174 ms
modal-popup.html
256 ms
modal-slide.html
256 ms
modal-custom.html
257 ms
key-codes.min.js
172 ms
core.min.js
172 ms
z-index.min.js
254 ms
knockout-repeat.min.js
184 ms
knockout-fast-foreach.min.js
185 ms
observable_source.min.js
265 ms
renderer.min.js
265 ms
resizable.min.js
265 ms
i18n.min.js
268 ms
scope.min.js
273 ms
range.min.js
272 ms
mage-init.min.js
356 ms
keyboard.min.js
352 ms
optgroup.min.js
353 ms
after-render.min.js
355 ms
autoselect.min.js
360 ms
datepicker.min.js
360 ms
outer_click.min.js
440 ms
fadeVisible.min.js
442 ms
collapsible.min.js
444 ms
staticChecked.min.js
444 ms
simple-checked.min.js
448 ms
bind-html.min.js
450 ms
tooltip.min.js
529 ms
color-picker.min.js
531 ms
arrays.min.js
527 ms
compare.min.js
529 ms
misc.min.js
532 ms
objects.min.js
532 ms
strings.min.js
549 ms
template.min.js
549 ms
jquery.cookie.min.js
548 ms
logger.min.js
550 ms
entry-factory.min.js
549 ms
console-output-handler.min.js
547 ms
formatter.min.js
549 ms
message-pool.min.js
551 ms
levels-pool.min.js
548 ms
logger-utils.min.js
549 ms
data.min.js
548 ms
disable-selection.min.js
548 ms
focusable.min.js
548 ms
form.min.js
549 ms
ie.min.js
547 ms
keycode.min.js
547 ms
labels.min.js
549 ms
jquery-patch.min.js
548 ms
plugin.min.js
550 ms
safe-active-element.min.js
549 ms
safe-blur.min.js
551 ms
scroll-parent.min.js
546 ms
tabbable.min.js
548 ms
unique-id.min.js
547 ms
class.min.js
553 ms
async.min.js
547 ms
loader.min.js
549 ms
tooltip.html
459 ms
spectrum.min.js
465 ms
tinycolor.min.js
465 ms
cookie-wrapper.min.js
454 ms
entry.min.js
446 ms
moment.min.js
370 ms
dom-observer.min.js
94 ms
bindings.min.js
95 ms
js.cookie.min.js
93 ms
print.min.css
92 ms
wosis.com 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
[role]s do not have all required [aria-*] attributes
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
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
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.
wosis.com 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
Browser errors were logged to the console
wosis.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wosis.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wosis.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.
wosis.com
Open Graph description is not detected on the main page of Wosis. 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: