7.4 sec in total
1.6 sec
5.6 sec
193 ms
Click here to check amazing Catylesca content. Otherwise, check out these important facts you probably never knew about catylesca.com
Welcome to Caty Lesca, your creative happiness fashion! Enter in an ethnic and unstructured universe.
Visit catylesca.comWe analyzed Catylesca.com page load time and found that the first response time was 1.6 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
catylesca.com performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value3.1 s
74/100
25%
Value2.8 s
96/100
10%
Value30 ms
100/100
30%
Value0.139
79/100
15%
Value3.0 s
96/100
10%
1557 ms
557 ms
653 ms
206 ms
208 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 83% of them (44 requests) were addressed to the original Catylesca.com, 6% (3 requests) were made to S.ytimg.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Catylesca.com.
Page size can be reduced by 927.2 kB (78%)
1.2 MB
266.4 kB
In fact, the total size of Catylesca.com main page is 1.2 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. CSS take 649.2 kB which makes up the majority of the site volume.
Potential reduce by 20.8 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 4.7 kB, which is 18% 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 20.8 kB or 80% of the original size.
Potential reduce by 804 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. Catylesca images are well optimized though.
Potential reduce by 356.6 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 356.6 kB or 70% of the original size.
Potential reduce by 549.0 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. Catylesca.com needs all CSS files to be minified and compressed as it can save up to 549.0 kB or 85% of the original size.
Number of requests can be reduced by 37 (76%)
49
12
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Catylesca. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
1557 ms
bootstrap.css
557 ms
global.css
653 ms
highdpi.css
206 ms
responsive-tables.css
208 ms
uniform.default.css
214 ms
jquery.fancybox.css
294 ms
blocklanguages.css
310 ms
blockcart.css
311 ms
blockcontact.css
327 ms
blockuserinfo.css
396 ms
blocknewsletter.css
413 ms
blockcategories.css
414 ms
hooks.css
433 ms
bootstrap-modal-bs3patch.css
498 ms
bootstrap-modal.css
516 ms
video.css
517 ms
jquery-1.11.0.min.js
754 ms
jquery-migrate-1.2.1.min.js
601 ms
jquery.easing.js
619 ms
tools.js
620 ms
global.js
644 ms
10-bootstrap.min.js
704 ms
15-jquery.total-storage.min.js
723 ms
15-jquery.uniform-modified.js
824 ms
jquery.fancybox.js
738 ms
products-comparison.js
746 ms
ajax-cart.js
806 ms
jquery.scrollTo.js
832 ms
jquery.serialScroll.js
833 ms
jquery.bxslider.js
839 ms
blocknewsletter.js
859 ms
treeManagement.js
907 ms
index.js
925 ms
css
24 ms
YYDv9qZTFcY
121 ms
caty-lesca-paris-logo-1424216895.jpg
109 ms
518d96cd6f0470b450f807f4106238b21b1f26d0_caty.gif
554 ms
boutique-en-ligne.gif
308 ms
newsletter2.gif
103 ms
lookbook.gif
207 ms
vitrines.gif
190 ms
vitrines2.gif
288 ms
vitrines3.gif
311 ms
video.gif
658 ms
fontawesome-webfont.woff
355 ms
www-embed-player-vflfNyN_r.css
100 ms
www-embed-player.js
119 ms
base.js
213 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
26 ms
ad_status.js
67 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
75 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
85 ms
catylesca.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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
catylesca.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
catylesca.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 doesn't use legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Catylesca.com 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 Catylesca.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.
catylesca.com
Open Graph description is not detected on the main page of Catylesca. 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: