3.6 sec in total
258 ms
3.1 sec
219 ms
Welcome to chantecaille.com homepage info - get ready to check Chantecaille best content for United States right away, or after learning these important things about chantecaille.com
Discover the full collection of Chantecaille luxury botanical skincare, makeup & fragrance. Sophisticated botanical skincare, vegan makeup and cruelty-free give-back beauty. Chantecaille is proud to p...
Visit chantecaille.comWe analyzed Chantecaille.com page load time and found that the first response time was 258 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
chantecaille.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value36.8 s
0/100
25%
Value36.4 s
0/100
10%
Value5,460 ms
0/100
30%
Value0.123
83/100
15%
Value58.9 s
0/100
10%
258 ms
126 ms
35 ms
69 ms
155 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 70% of them (63 requests) were addressed to the original Chantecaille.com, 4% (4 requests) were made to Fast.fonts.net and 2% (2 requests) were made to V2.zopim.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Yhp.mxptint.net.
Page size can be reduced by 1.2 MB (46%)
2.6 MB
1.4 MB
In fact, the total size of Chantecaille.com main page is 2.6 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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 51.0 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 7.9 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 51.0 kB or 81% of the original size.
Potential reduce by 3.1 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. Chantecaille images are well optimized though.
Potential reduce by 792.9 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 792.9 kB or 74% of the original size.
Potential reduce by 363.6 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. Chantecaille.com needs all CSS files to be minified and compressed as it can save up to 363.6 kB or 84% of the original size.
Number of requests can be reduced by 59 (78%)
76
17
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chantecaille. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.chantecaille.com
258 ms
d0dc1292-e65b-4eb3-9f3e-aeb68d453195.css
126 ms
jquery-ui.css
35 ms
jquery.mCustomScrollbar.css
69 ms
styles.css
155 ms
widgets.css
99 ms
amshopby.css
102 ms
style-newssubscribers.css
105 ms
styles.css
99 ms
glyphicons.css
106 ms
styles.css
133 ms
mediaelementplayer.min.css
138 ms
files.css
130 ms
bootstrap-responsive.css
144 ms
jquery.fancybox.css
163 ms
carousel.css
166 ms
menu.css
164 ms
prototype.js
207 ms
ccard.js
169 ms
validation.js
170 ms
builder.js
169 ms
effects.js
193 ms
dragdrop.js
194 ms
controls.js
200 ms
slider.js
201 ms
js.js
202 ms
form.js
230 ms
menu.js
231 ms
translate.js
233 ms
cookies.js
234 ms
amlanding.js
234 ms
jquery-1.8.2.min.js
274 ms
jquery-noconflict.js
256 ms
mediaelement-and-player.min.js
296 ms
jquery.easing.1.3.js
264 ms
carousel.js
268 ms
jquery.mousewheel.min.js
269 ms
banner2.css
294 ms
camera.css
278 ms
jquery.custom-scrollbar.css
243 ms
jquery.accordion.js
214 ms
jquery.fancybox.js
219 ms
jquery.ddslick.min.js
224 ms
script.js
229 ms
dmscript.js
232 ms
jquery.mobile.customized.min.js
214 ms
camera.js
266 ms
jquery.custom-scrollbar.js
213 ms
jquery.mCustomScrollbar.js
197 ms
analytics.js
164 ms
MasterTMS.min.js
71 ms
fbevents.js
419 ms
prum.min.js
159 ms
mini-cart.jpg
66 ms
logo.png
66 ms
mobile_-_Magnolia.jpg
220 ms
ajax-loader.gif
66 ms
2a004a53-ac5c-43b3-9eeb-9f74ae4c1609.woff
148 ms
btn_search.gif
50 ms
banner-bg.png
138 ms
3fbbd6b1-cfa7-4ff0-97ea-af1b2c489f15.woff
154 ms
9aa32a81-1124-4c43-b3db-15bfb1f7aed2.woff
191 ms
activityi;src=4563514;type=count0;cat=homep0;ord=384051376022.3985
169 ms
tags
97 ms
esns_dark2.png
60 ms
banner-left-arrow.png
61 ms
banner-right-arrow.png
60 ms
camera-loader.gif
60 ms
Desktop_Magnolia.jpg
336 ms
fontawesome-webfont.woff
243 ms
collect
37 ms
collect
178 ms
u
123 ms
tags
120 ms
widget_v2.132.js
30 ms
163 ms
secimg.vmmpxl.com
159 ms
AD
53 ms
Pug
60 ms
118 ms
LusterGlide-Earth_HP.jpg
370 ms
avatar_simple_visitor.png
144 ms
aL63HcygAAVYuCCsAAA==
1 ms
yahoo.ashx
1213 ms
print.css
33 ms
blank.gif
34 ms
pixel
38 ms
adex.ashx
199 ms
1
49 ms
roundtrip.js
34 ms
chantecaille.com 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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
chantecaille.com 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
chantecaille.com 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
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chantecaille.com 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 Chantecaille.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.
chantecaille.com
Open Graph description is not detected on the main page of Chantecaille. 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: