14.1 sec in total
2.6 sec
10.9 sec
615 ms
Visit coffeeberry.co.za now to see the best up-to-date Coffeeberry content and also check out these interesting facts you probably never knew about coffeeberry.co.za
Visit coffeeberry.co.zaWe analyzed Coffeeberry.co.za page load time and found that the first response time was 2.6 sec and then it took 11.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
coffeeberry.co.za performance score
name
value
score
weighting
Value10.7 s
0/100
10%
Value17.5 s
0/100
25%
Value19.9 s
0/100
10%
Value70 ms
99/100
30%
Value0.044
99/100
15%
Value14.5 s
9/100
10%
2626 ms
614 ms
31 ms
613 ms
621 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 89% of them (51 requests) were addressed to the original Coffeeberry.co.za, 7% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Coffeeberry.co.za.
Page size can be reduced by 702.9 kB (39%)
1.8 MB
1.1 MB
In fact, the total size of Coffeeberry.co.za main page is 1.8 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. 55% of websites need less resources to load. Images take 813.5 kB which makes up the majority of the site volume.
Potential reduce by 111.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 111.1 kB or 83% of the original size.
Potential reduce by 0 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. Coffeeberry images are well optimized though.
Potential reduce by 57.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 57.1 kB or 31% of the original size.
Potential reduce by 534.7 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. Coffeeberry.co.za needs all CSS files to be minified and compressed as it can save up to 534.7 kB or 79% of the original size.
Number of requests can be reduced by 35 (71%)
49
14
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Coffeeberry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
www.coffeeberry.co.za
2626 ms
style.min.css
614 ms
css
31 ms
cookie-law-info-public.css
613 ms
cookie-law-info-gdpr.css
621 ms
elementor-icons.min.css
891 ms
frontend.min.css
1206 ms
swiper.min.css
904 ms
post-519.css
921 ms
frontend.min.css
1531 ms
all.min.css
928 ms
v4-shims.min.css
1190 ms
global.css
1213 ms
post-7.css
1228 ms
post-670.css
1235 ms
post-165.css
1491 ms
css
29 ms
fontawesome.min.css
1511 ms
solid.min.css
1510 ms
brands.min.css
1541 ms
jquery.min.js
1846 ms
jquery-migrate.min.js
1790 ms
cookie-law-info-public.js
1815 ms
v4-shims.min.js
1816 ms
animations.min.css
1834 ms
cookie-law-info-table.css
1841 ms
style.min.js
2091 ms
jquery.smartmenus.min.js
2119 ms
webpack-pro.runtime.min.js
2120 ms
webpack.runtime.min.js
2140 ms
frontend-modules.min.js
2455 ms
hooks.min.js
2150 ms
i18n.min.js
2390 ms
frontend.min.js
2422 ms
waypoints.min.js
2427 ms
core.min.js
2451 ms
frontend.min.js
2464 ms
elements-handlers.min.js
2691 ms
coffee-berry-icon.jpg
849 ms
coffeeberry-interior-1.jpg
1154 ms
coffeeberr-cafe-800px.png
883 ms
Coffeeberry-Gallery1.jpg
1187 ms
Vibes2.jpg
1500 ms
Food-1.jpg
1405 ms
Legendary-coffee.jpg
1151 ms
Food3.jpg
1496 ms
Kids.jpg
1759 ms
coffeeberry-gallery4-1.jpg
1459 ms
Food2.jpg
1799 ms
Footer.jpg
2589 ms
jizaRExUiTo99u79D0KEww.woff
18 ms
jizfRExUiTo99u79B_mh0O6tKw.woff
35 ms
fa-solid-900.woff
1995 ms
fa-regular-400.woff
1735 ms
jizdRExUiTo99u79D0e8fOydLxUb.woff
48 ms
jizYRExUiTo99u79D0e0x8mO.woff
49 ms
fa-brands-400.woff
1745 ms
coffeeberry.co.za 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
Heading elements are not in a sequentially-descending order
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
coffeeberry.co.za 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
coffeeberry.co.za 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Coffeeberry.co.za 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 Coffeeberry.co.za 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.
coffeeberry.co.za
Open Graph description is not detected on the main page of Coffeeberry. 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: