1.8 sec in total
236 ms
1.1 sec
433 ms
Welcome to cleo.ca homepage info - get ready to check Cleo best content for Canada right away, or after learning these important things about cleo.ca
Look & Feel Your Best In Today’s Must Haves! Trendy Styles That Offer Versatility, Value And Quality. Available In Petite, Sizes 0-20. Ship To Your Store For $2.
Visit cleo.caWe analyzed Cleo.ca page load time and found that the first response time was 236 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
cleo.ca performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value18.2 s
0/100
25%
Value12.5 s
3/100
10%
Value8,970 ms
0/100
30%
Value0.086
93/100
15%
Value38.0 s
0/100
10%
236 ms
78 ms
122 ms
157 ms
73 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 14% of them (11 requests) were addressed to the original Cleo.ca, 70% (57 requests) were made to Demandware.edgesuite.net and 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (476 ms) relates to the external source Demandware.edgesuite.net.
Page size can be reduced by 1.6 MB (40%)
4.0 MB
2.4 MB
In fact, the total size of Cleo.ca main page is 4.0 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. 75% 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 2.3 MB which makes up the majority of the site volume.
Potential reduce by 64.7 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 17.4 kB, which is 22% 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 64.7 kB or 84% of the original size.
Potential reduce by 216.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. Cleo images are well optimized though.
Potential reduce by 781.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 781.7 kB or 76% of the original size.
Potential reduce by 530.8 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. Cleo.ca needs all CSS files to be minified and compressed as it can save up to 530.8 kB or 86% of the original size.
Number of requests can be reduced by 46 (65%)
71
25
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cleo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.cleo.ca
236 ms
normalize.css
78 ms
jquery.ui.all.css
122 ms
jquery-1.8.3.min.js
157 ms
jquery.cookie.js
73 ms
modernizr.js
147 ms
yepnope.js
74 ms
browserdetect.addbodyclass.js
114 ms
detectmobile.js
115 ms
dwac-14.8.js
115 ms
print.css
170 ms
fonts.css
103 ms
style.css
287 ms
cleo.css
265 ms
jquery.jscrollpane.css
170 ms
jquery.tooltip.css
171 ms
jPushMenu.css
179 ms
jPushMenu.js
176 ms
style-responsive.css
216 ms
cleo-responsive.css
238 ms
responsive.js
218 ms
jquery.rwdImageMaps.min.js
221 ms
conversion.js
16 ms
getseal
38 ms
Resources-Load
37 ms
jquery-ui-1.9.2.js
388 ms
jquery.jcarousel.min.js
186 ms
jquery.tooltip.min.js
211 ms
jquery.ba-hashchange.min.js
240 ms
jquery.validate.min-1.9.0.js
258 ms
app.js
310 ms
app.override.js
258 ms
jquery.mousewheel.js
258 ms
jquery.placeholder.js
279 ms
jquery.jscrollpane.js
288 ms
jquery.ticker.js
289 ms
dwanalytics.js
289 ms
gretel.min.js
26 ms
main-logo.png
72 ms
main-logo-medium.png
90 ms
cc-TN-Feb3-NewArrivals.jpg
120 ms
cc-TN-Feb19-Apparel.jpg
121 ms
cc-TN-Aug12-Petites.jpg
120 ms
cc-TN-Feb29-Jewellery.jpg
134 ms
cc-TN-Feb29-Accessories.jpg
318 ms
cc-TN-Feb10-SA.jpg
319 ms
cc-TN-Feb23-Sale.jpg
321 ms
cc-Jan26-SHIP399.png
318 ms
cc-Jan26-SHIP399-MOBILE.png
320 ms
cc-FEB29-HP.jpg
476 ms
cc-FEB29-HP-MOBILE_01.jpg
329 ms
cc-FEB29-HP-MOBILE_02.jpg
322 ms
cc-FEB29-HP-MOBILE_03.jpg
326 ms
cc-FEB29-HP-MOBILE_04.jpg
327 ms
cc-Aug12-HP-MOBILE-2.jpg
322 ms
MyConnection_Footer-2.png
323 ms
get-involved-2.png
330 ms
63 ms
mini-cart-total.png
315 ms
icon-search.png
315 ms
281C51_4_0.woff
30 ms
281C51_A_0.woff
52 ms
281C51_F_0.woff
98 ms
281C51_7_0.woff
105 ms
281C51_1_0.woff
59 ms
281C51_11_0.woff
270 ms
281C51_0_0.woff
275 ms
signup-popup.png
283 ms
newsletter-submit.png
281 ms
social-links.png
357 ms
48 ms
281C51_13_0.woff
137 ms
getseal
12 ms
ga.js
87 ms
gtm.js
85 ms
email-signup-sprites.png
95 ms
__utm.gif
30 ms
analytics.js
16 ms
ec.js
15 ms
collect
9 ms
collect
60 ms
cleo.ca 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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.
cleo.ca 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
Page has valid source maps
cleo.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Cleo.ca 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 Cleo.ca main page’s claimed encoding is utf-8;. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
cleo.ca
Open Graph description is not detected on the main page of Cleo. 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: