8.2 sec in total
230 ms
5.3 sec
2.6 sec
Visit tankcoffee.com now to see the best up-to-date Tank Coffee content and also check out these interesting facts you probably never knew about tankcoffee.com
Coffee beans online delivered free in handy 400g boxes to fit the letterbox. Order beans or ground and enjoy quality ethically sourced coffee in your home.
Visit tankcoffee.comWe analyzed Tankcoffee.com page load time and found that the first response time was 230 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
tankcoffee.com performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value3.9 s
53/100
25%
Value2.8 s
95/100
10%
Value90 ms
98/100
30%
Value0.009
100/100
15%
Value6.3 s
61/100
10%
230 ms
51 ms
298 ms
297 ms
326 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 55% of them (46 requests) were addressed to the original Tankcoffee.com, 37% (31 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 121.8 kB (17%)
727.9 kB
606.0 kB
In fact, the total size of Tankcoffee.com main page is 727.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 273.1 kB which makes up the majority of the site volume.
Potential reduce by 96.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 96.1 kB or 81% of the original size.
Potential reduce by 20.6 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. Tank Coffee images are well optimized though.
Potential reduce by 5.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. This website has mostly compressed JavaScripts.
Potential reduce by 25 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. Tankcoffee.com has all CSS files already compressed.
Number of requests can be reduced by 35 (70%)
50
15
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tank Coffee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and as a result speed up the page load time.
www.tankcoffee.com
230 ms
webfontloader.min.js
51 ms
jquery.min.js
298 ms
jquery-migrate.min.js
297 ms
embed.js
326 ms
js
785 ms
fv.js
1098 ms
style.min.js
301 ms
jquery.blockUI.min.js
316 ms
add-to-cart.min.js
344 ms
js.cookie.min.js
790 ms
woocommerce.min.js
340 ms
cart-fragments.min.js
339 ms
mailchimp-woocommerce-public.min.js
338 ms
underscore.min.js
347 ms
wp-util.min.js
347 ms
add-to-cart-variation.min.js
665 ms
yith-wccl.min.js
349 ms
imagesloaded.min.js
349 ms
astra-addon-6323b7c9632596-93746710.js
768 ms
single-product-ajax-cart.min.js
659 ms
ywsbs-frontend.min.js
765 ms
webpack-pro.runtime.min.js
767 ms
webpack.runtime.min.js
767 ms
frontend-modules.min.js
767 ms
jquery.sticky.min.js
769 ms
frontend.min.js
770 ms
waypoints.min.js
780 ms
core.min.js
787 ms
swiper.min.js
783 ms
share-link.min.js
779 ms
dialog.min.js
783 ms
frontend.min.js
784 ms
preloaded-elements-handlers.min.js
784 ms
preloaded-modules.min.js
786 ms
css
320 ms
0390aa472cc7b54e37096de78ca999a6.css
52 ms
aeab82ee6d3e8bcd2704ef4fa.js
1557 ms
S6uyw4BMUTPHjx4wWA.woff
1547 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
1556 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
1554 ms
KFOmCnqEu92Fr1Mu4mxM.woff
1555 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
1554 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
1555 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
1555 ms
KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff
1643 ms
KFOjCnqEu92Fr1Mu51TjASc6CsI.woff
1643 ms
KFOkCnqEu92Fr1Mu51xIIzQ.woff
1560 ms
KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff
1627 ms
KFOjCnqEu92Fr1Mu51TzBic6CsI.woff
1545 ms
KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff
1626 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDJZ9xdv.woff
3388 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDNZ9xdv.woff
3386 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTajNZ9xdv.woff
3388 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDNZ9xdv.woff
3386 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTBjNZ9xdv.woff
3386 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT6jRZ9xdv.woff
3385 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT0zRZ9xdv.woff
3388 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDRZ9xdv.woff
3397 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTnTRZ9xdv.woff
3395 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HCBsidrD0k.woff
3399 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HABsydrD0k.woff
3397 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HDfsydrD0k.woff
3398 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HCBsydrD0k.woff
3408 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HCzsydrD0k.woff
3406 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HBftCdrD0k.woff
3405 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HBmtCdrD0k.woff
3408 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HABtCdrD0k.woff
3402 ms
k3k8o8UDI-1M0wlSfdzyIEkpwTM29hr-8mTYIRyOSVz60_PG_HAotCdrD0k.woff
3406 ms
analytics.js
2766 ms
astra.woff
253 ms
star.woff
249 ms
collect
13 ms
tankcoffee_logo-Overlay.png
12 ms
Retail-comparison-22.jpg
17 ms
Kenya-AA-200x200.jpg
13 ms
Rwandan-Rukira-decaf-200x200.png
175 ms
Kenya-peaberry-Webpage-Pic-200x200.png
15 ms
Yirgacheffe-Webpage-Pic-2-200x200.png
187 ms
ESWD-200x200.jpg
35 ms
kickstartBox-200x200.jpg
21 ms
sidamoBox-200x200.jpg
35 ms
espressoBox-200x200.jpg
86 ms
gloryBox-200x200.jpg
46 ms
tankcoffee.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
Links do not have a discernible name
tankcoffee.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
tankcoffee.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 Tankcoffee.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 Tankcoffee.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.
tankcoffee.com
Open Graph data is detected on the main page of Tank Coffee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: