7.6 sec in total
2.5 sec
4.9 sec
210 ms
Visit cocktailshop.es now to see the best up-to-date Cocktailshop content for Spain and also check out these interesting facts you probably never knew about cocktailshop.es
Shop powered by PrestaShop
Visit cocktailshop.esWe analyzed Cocktailshop.es page load time and found that the first response time was 2.5 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cocktailshop.es performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value10.6 s
0/100
25%
Value9.3 s
13/100
10%
Value1,280 ms
18/100
30%
Value0.201
61/100
15%
Value14.6 s
8/100
10%
2492 ms
216 ms
325 ms
331 ms
327 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 94% of them (67 requests) were addressed to the original Cocktailshop.es, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to App.cookieassistant.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Cocktailshop.es.
Page size can be reduced by 621.1 kB (58%)
1.1 MB
440.8 kB
In fact, the total size of Cocktailshop.es 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 404.8 kB which makes up the majority of the site volume.
Potential reduce by 36.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 5.3 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 36.8 kB or 79% of the original size.
Potential reduce by 12.5 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. Cocktailshop images are well optimized though.
Potential reduce by 289.5 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 289.5 kB or 72% of the original size.
Potential reduce by 282.3 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. Cocktailshop.es needs all CSS files to be minified and compressed as it can save up to 282.3 kB or 85% of the original size.
Number of requests can be reduced by 42 (63%)
67
25
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cocktailshop. 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 21 to 1 for CSS and as a result speed up the page load time.
2492 ms
bootstrap.css
216 ms
jquery.fancybox.css
325 ms
blockbestsellers.css
331 ms
blockpermanentlinks.css
327 ms
blockviewed.css
317 ms
blockcart.css
342 ms
blockcontact.css
322 ms
blockcurrencies.css
429 ms
blockmyaccount.css
430 ms
blockuserinfo.css
425 ms
blocklanguages.css
435 ms
blocksearch.css
438 ms
jquery.autocomplete.css
451 ms
blocknewsletter.css
527 ms
productcomments.css
538 ms
blocktags.css
531 ms
custommenu.css
545 ms
posspecialproduct.css
548 ms
nivo-slider.css
562 ms
paypal.css
629 ms
global_brown.css
748 ms
jquery-1.11.0.min.js
868 ms
jquery-migrate-1.2.1.min.js
651 ms
jquery.easing.js
653 ms
tools.js
671 ms
jquery.fancybox.js
728 ms
ajax-cart.js
778 ms
jquery.scrollTo.js
778 ms
jquery.serialScroll.js
784 ms
jquery.bxslider.js
833 ms
jquery.autocomplete.js
845 ms
treeManagement.js
902 ms
scrolltop.js
902 ms
custommenu.js
903 ms
mobile_menu.js
934 ms
widget.js
43 ms
pos.bxslider.min.js
949 ms
jquery.nivo.slider.pack.js
767 ms
html5shiv.js
682 ms
respond.min.js
682 ms
bootstrap.js
699 ms
bootstrap.min.js
729 ms
cocktailshop-1429691368.jpg
767 ms
4.jpg
785 ms
1.jpg
700 ms
29.jpg
1125 ms
24.jpg
1147 ms
bg-wrapper.png
382 ms
bg-toplink.png
396 ms
arrow.png
438 ms
icon-cart.png
450 ms
border-cart.png
486 ms
bg-footer-top.png
499 ms
icon-search.png
549 ms
bg-menu.png
561 ms
bg-right-menu.png
589 ms
bg-footer-top.png
602 ms
loader.gif
757 ms
bg-header.png
672 ms
bg-follow.png
691 ms
bg-facebook.png
705 ms
bg-twiter.png
771 ms
bg-google.png
781 ms
century.woff
1035 ms
abrahamlincoln.woff
959 ms
back-top.png
821 ms
jquery.min.js
40 ms
analytics.js
37 ms
collect
24 ms
arrows.png
105 ms
cocktailshop.es 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
ARIA IDs 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
No form fields have multiple labels
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
cocktailshop.es 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
cocktailshop.es 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
ES
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cocktailshop.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Cocktailshop.es 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.
cocktailshop.es
Open Graph description is not detected on the main page of Cocktailshop. 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: