7.1 sec in total
320 ms
6.2 sec
528 ms
Click here to check amazing Coffers content. Otherwise, check out these important facts you probably never knew about coffers.direct
Visit coffers.directWe analyzed Coffers.direct page load time and found that the first response time was 320 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
coffers.direct performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value12.6 s
0/100
25%
Value10.7 s
7/100
10%
Value100 ms
98/100
30%
Value0
100/100
15%
Value9.4 s
31/100
10%
320 ms
3237 ms
220 ms
330 ms
325 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 96% of them (108 requests) were addressed to the original Coffers.direct, 4% (5 requests) were made to Coffers.ajvonidol.si. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Coffers.direct.
Page size can be reduced by 260.4 kB (7%)
3.6 MB
3.3 MB
In fact, the total size of Coffers.direct main page is 3.6 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 2.9 MB which makes up the majority of the site volume.
Potential reduce by 150.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 150.1 kB or 84% of the original size.
Potential reduce by 88.2 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. Coffers images are well optimized though.
Potential reduce by 7.9 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 14.2 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. Coffers.direct has all CSS files already compressed.
Number of requests can be reduced by 88 (82%)
107
19
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Coffers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 58 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
coffers.direct
320 ms
coffers.direct
3237 ms
frontend.css
220 ms
gutenberg-blocks.css
330 ms
styles.css
325 ms
cookieblocker.min.css
328 ms
header-footer-elementor.css
331 ms
custom-frontend-lite.min.css
338 ms
swiper.min.css
336 ms
post-23.css
442 ms
global.css
441 ms
post-1503.css
448 ms
post-3540.css
450 ms
post-701.css
458 ms
frontend.min.css
454 ms
slick.css
556 ms
perfect-scrollbar.min.css
558 ms
custom-theme.css
563 ms
magnific-popup.css
570 ms
feather.css
570 ms
frontend.css
577 ms
style.css
786 ms
slick.css
674 ms
slick-theme.css
675 ms
elementor.css
685 ms
woocommerce.css
688 ms
tooltipster.bundle.min.css
694 ms
style.css
792 ms
jquery.min.js
900 ms
jquery-migrate.min.js
801 ms
jquery.blockUI.min.js
806 ms
add-to-cart.min.js
804 ms
js.cookie.min.js
898 ms
woocommerce.min.js
911 ms
underscore.min.js
920 ms
wp-util.min.js
923 ms
jarallax.js
918 ms
custom-widget-icon-box.min.css
515 ms
custom-widget-icon-list.min.css
518 ms
wc-blocks.css
921 ms
animations.min.css
804 ms
rs6.css
734 ms
post-3723.css
730 ms
index.js
730 ms
index.js
730 ms
rbtools.min.js
908 ms
rs6.min.js
1023 ms
sourcebuster.min.js
710 ms
order-attribution.min.js
710 ms
api-request.min.js
702 ms
wp-polyfill-inert.min.js
710 ms
regenerator-runtime.min.js
822 ms
wp-polyfill.min.js
821 ms
hooks.min.js
720 ms
i18n.min.js
720 ms
url.min.js
794 ms
api-fetch.min.js
808 ms
frontend.min.js
819 ms
add-to-cart-variation.min.js
811 ms
slick.min.js
722 ms
perfect-scrollbar.jquery.min.js
800 ms
jquery.magnific-popup.min.js
792 ms
frontend.js
802 ms
main.js
810 ms
skip-link-focus-fix.min.js
711 ms
search-popup.js
719 ms
text-editor.js
790 ms
nav-mobile.js
789 ms
frontend.js
803 ms
login.js
717 ms
header-cart.min.js
707 ms
tooltipster.bundle.js
727 ms
product-ajax-search.min.js
783 ms
main.min.js
789 ms
Header-3.jpg
700 ms
h3_bg1.png
115 ms
h3_decor1.png
400 ms
quantity.min.js
706 ms
cart-canvas.min.js
716 ms
complianz.min.js
680 ms
frontend.js
701 ms
webpack.runtime.min.js
762 ms
frontend-modules.min.js
771 ms
waypoints.min.js
781 ms
core.min.js
701 ms
frontend.min.js
706 ms
header-group.js
723 ms
products.js
775 ms
jquery-numerator.min.js
671 ms
testimonial.js
680 ms
posts-grid.js
693 ms
forms.js
698 ms
elementor-frontend.js
705 ms
jquery.sticky.js
693 ms
sticky.min.js
696 ms
xocora.woff
803 ms
xocora-sub.woff
698 ms
xocora-icon-1.1.9.woff
813 ms
xocora-Italic.woff
830 ms
Coffers-Logo-Transparent-BG-150x150.png
686 ms
Coffers-Logo-Hosizontal-White-BG.png
912 ms
1-Home3-scaled.jpg
1153 ms
2-Coffees_Colectivo-scaled-450x450.jpg
773 ms
2-Coffees_Caramelo-scaled-450x450.jpg
898 ms
2-Coffees-Microlots-2-scaled-450x450.jpg
798 ms
2-Coffees_Topaz-scaled-450x450.jpg
749 ms
3-Terroir3-684x1024.jpg
909 ms
4-About2-768x1024.jpg
1141 ms
brazil-scenery-with-multiple-coffee-farms-820x580.jpg
956 ms
table-full-of-coffe-and-items-related-to-coffe-pr-2-820x580.jpg
893 ms
ai5-820x580.jpg
989 ms
Newsletter1-630x508.jpg
917 ms
output-onlinepngtools-150x150.png
916 ms
coffers.direct accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
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.
coffers.direct 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
coffers.direct SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Coffers.direct can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Coffers.direct 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.
coffers.direct
Open Graph description is not detected on the main page of Coffers. 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: