1.2 sec in total
91 ms
590 ms
532 ms
Welcome to cotonblossom.org homepage info - get ready to check Coton Blossom best content right away, or after learning these important things about cotonblossom.org
Cotton Blossom grew out of a 24 machine startup in 1997.We are a family owned, first generation business that started as a dream to create clothes that look and feel good without compromising on the p...
Visit cotonblossom.orgWe analyzed Cotonblossom.org page load time and found that the first response time was 91 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
cotonblossom.org performance score
name
value
score
weighting
Value2.9 s
51/100
10%
Value21.8 s
0/100
25%
Value8.1 s
21/100
10%
Value440 ms
63/100
30%
Value0.018
100/100
15%
Value13.4 s
11/100
10%
91 ms
30 ms
40 ms
49 ms
78 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 55% of them (42 requests) were addressed to the original Cotonblossom.org, 30% (23 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (229 ms) belongs to the original domain Cotonblossom.org.
Page size can be reduced by 263.4 kB (4%)
6.1 MB
5.8 MB
In fact, the total size of Cotonblossom.org main page is 6.1 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. 85% 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 5.9 MB which makes up the majority of the site volume.
Potential reduce by 23.6 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 3.8 kB, which is 13% 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 23.6 kB or 81% of the original size.
Potential reduce by 182.7 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. Coton Blossom images are well optimized though.
Potential reduce by 24.2 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 24.2 kB or 36% of the original size.
Potential reduce by 32.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. Cotonblossom.org needs all CSS files to be minified and compressed as it can save up to 32.8 kB or 37% of the original size.
Number of requests can be reduced by 26 (49%)
53
27
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Coton Blossom. 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 12 to 1 for CSS and as a result speed up the page load time.
cotonblossom.org
91 ms
jquery-2.2.0.min.js
30 ms
slick.js
40 ms
bootstrap.min.js
49 ms
bootstrap.min.css
78 ms
docs.theme.min.css
169 ms
owl.carousel.min.css
144 ms
owl.theme.default.min.css
139 ms
owl.carousel.js
164 ms
js
84 ms
bootstrap.css
166 ms
style.css
162 ms
nav.css
162 ms
font-awesome.css
166 ms
css
40 ms
css
51 ms
css
53 ms
css
82 ms
responsiveslides.min.js
223 ms
numscroller-1.0.js
224 ms
jquery.flexisel.js
225 ms
move-top.js
226 ms
easing.js
224 ms
classie.js
226 ms
nav.js
227 ms
main.js
228 ms
SmoothScroll.min.js
229 ms
banner2.jpg
129 ms
knowmore.png
102 ms
knowmore_grey.png
125 ms
abbg.jpg
130 ms
logo1.png
129 ms
ic1.png
126 ms
ic2.png
126 ms
ic3.png
127 ms
business_home_shadow.png
146 ms
home_sustain_shadow.png
136 ms
infra_home_shadow.png
138 ms
w1.png
130 ms
w2.png
136 ms
w3.png
135 ms
w4.png
137 ms
w5.png
173 ms
w6.png
174 ms
w7.png
172 ms
mentegoz.png
175 ms
move-up.png
151 ms
banner1.jpg
77 ms
banner3.jpg
80 ms
banner5.jpg
137 ms
banner4.jpg
136 ms
js
65 ms
analytics.js
29 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff
22 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4GLvztg.woff
116 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4GLvztg.woff
116 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLvztg.woff
116 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4GLvztg.woff
56 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff
56 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff
116 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff
116 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff
116 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff
119 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXx-p7K4GLs.woff
120 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXx-p7K4GLvztg.woff
119 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw2aXx-p7K4GLvztg.woff
119 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw9aXx-p7K4GLvztg.woff
120 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw0aXx-p7K4GLvztg.woff
121 ms
PN_xRfK9oXHga0XdZsg5rz7b_g.woff
121 ms
PN_xRfK9oXHga0XdaMg5rz7b_sDa.woff
164 ms
PN_xRfK9oXHga0XdZ8g5rz7b_sDa.woff
126 ms
pxiByp8kv8JHgFVrLDz8Z1xlE92JQEk.woff
120 ms
pxiByp8kv8JHgFVrLDz8Z1JlE92JQEl8qw.woff
126 ms
pxiByp8kv8JHgFVrLDz8Z11lE92JQEl8qw.woff
129 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfY3lC2xcZqT1UA.woff
127 ms
8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfYPlC2xcZqT1UHAS.woff
126 ms
collect
66 ms
cotonblossom.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
cotonblossom.org 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
cotonblossom.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
ZX
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cotonblossom.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed language. Our system also found out that Cotonblossom.org 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.
cotonblossom.org
Open Graph description is not detected on the main page of Coton Blossom. 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: