5.3 sec in total
1.2 sec
3.2 sec
878 ms
Welcome to cubedcherry.co.za homepage info - get ready to check Cubed Cherry best content for South Africa right away, or after learning these important things about cubedcherry.co.za
Visit cubedcherry.co.zaWe analyzed Cubedcherry.co.za page load time and found that the first response time was 1.2 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
cubedcherry.co.za performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value15.5 s
0/100
25%
Value6.6 s
37/100
10%
Value340 ms
74/100
30%
Value0.003
100/100
15%
Value6.8 s
55/100
10%
1218 ms
233 ms
415 ms
307 ms
308 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 82% of them (45 requests) were addressed to the original Cubedcherry.co.za, 15% (8 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 (1.2 sec) belongs to the original domain Cubedcherry.co.za.
Page size can be reduced by 556.7 kB (61%)
909.3 kB
352.6 kB
In fact, the total size of Cubedcherry.co.za main page is 909.3 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. 50% of websites need less resources to load. Javascripts take 509.8 kB which makes up the majority of the site volume.
Potential reduce by 107.9 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 107.9 kB or 84% 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. Cubed Cherry images are well optimized though.
Potential reduce by 305.7 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 305.7 kB or 60% of the original size.
Potential reduce by 143.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. Cubedcherry.co.za needs all CSS files to be minified and compressed as it can save up to 143.2 kB or 55% of the original size.
Number of requests can be reduced by 39 (87%)
45
6
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cubed Cherry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
www.cubedcherry.co.za
1218 ms
grid-system.css
233 ms
style.css
415 ms
header-perma-transparent.css
307 ms
element-fancy-box.css
308 ms
element-scrolling-text.css
309 ms
element-post-grid.css
309 ms
css
31 ms
responsive.css
351 ms
flickity.css
408 ms
select2.css
409 ms
skin-material.css
411 ms
menu-dynamic.css
421 ms
js_composer.min.css
469 ms
salient-dynamic-styles.css
613 ms
style.css
397 ms
css
19 ms
jquery.min.js
512 ms
jquery-migrate.min.js
397 ms
font-awesome.min.css
398 ms
style-non-critical.css
471 ms
jquery.fancybox.css
510 ms
core.css
511 ms
slide-out-right-material.css
510 ms
slide-out-right-hover.css
602 ms
jquery.easing.min.js
603 ms
jquery.mousewheel.min.js
603 ms
priority.js
700 ms
transit.min.js
701 ms
waypoints.js
716 ms
imagesLoaded.min.js
714 ms
hoverintent.min.js
715 ms
jquery.fancybox.js
715 ms
anime.min.js
715 ms
nectar-text-inline-images.js
716 ms
flickity.js
834 ms
stickkit.js
834 ms
superfish.js
834 ms
init.js
910 ms
touchswipe.min.js
651 ms
select2.min.js
651 ms
js_composer_front.min.js
736 ms
logoCubedCherry-1-White.png
403 ms
logoCubedCherry-1-Black.png
402 ms
scroll-down-light-2-1.png
402 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpmJxAct.ttf
80 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuJJmJxAct.ttf
115 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuSJmJxAct.ttf
139 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuyJ6JxAct.ttf
138 ms
L0xjDF02iFML4hGCyOCpRdycFsGxSrqDFRkvEZmv.ttf
137 ms
L0xjDF02iFML4hGCyOCpRdycFsGxSrqDLBkvEZmv.ttf
137 ms
L0xjDF02iFML4hGCyOCpRdycFsGxSrqD-R4vEZmv.ttf
139 ms
H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFiNTc7Nq6A.ttf
135 ms
fontawesome-webfont.svg
419 ms
fontawesome-webfont.woff
124 ms
cubedcherry.co.za accessibility score
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
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.
cubedcherry.co.za 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
cubedcherry.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 Cubedcherry.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 Cubedcherry.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.
cubedcherry.co.za
Open Graph description is not detected on the main page of Cubed Cherry. 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: