3 sec in total
36 ms
1.8 sec
1.1 sec
Welcome to clinique.in homepage info - get ready to check Clinique best content for India right away, or after learning these important things about clinique.in
Explore Clinique's wide range of skincare, makeup and fragrance. Find products that fit your skin and routine. Free samples | 10% off on first purchase
Visit clinique.inWe analyzed Clinique.in page load time and found that the first response time was 36 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
clinique.in performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value8.9 s
1/100
25%
Value14.9 s
1/100
10%
Value10,650 ms
0/100
30%
Value0.601
10/100
15%
Value37.6 s
0/100
10%
36 ms
64 ms
146 ms
146 ms
18 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 81% of them (56 requests) were addressed to the original Clinique.in, 6% (4 requests) were made to S.btstatic.com and 3% (2 requests) were made to Esteelauder.d1.sc.omtrdc.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Clinique.in.
Page size can be reduced by 1.4 MB (75%)
1.9 MB
480.7 kB
In fact, the total size of Clinique.in main page is 1.9 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. Javascripts take 816.7 kB which makes up the majority of the site volume.
Potential reduce by 148.1 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 148.1 kB or 81% of the original size.
Potential reduce by 24.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. Obviously, Clinique needs image optimization as it can save up to 24.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 630.0 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 630.0 kB or 77% of the original size.
Potential reduce by 647.1 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. Clinique.in needs all CSS files to be minified and compressed as it can save up to 647.1 kB or 86% of the original size.
Number of requests can be reduced by 30 (53%)
57
27
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Clinique. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
clinique.in
36 ms
www.clinique.in
64 ms
css_t7ohJgpZGxVr-rkd5bgUBHdOjmGZJkFhY_pTzEPYezI.css
146 ms
css_BYgUzaq4LuhTj556vvnzLBoaHYO6f1svdFmwuiE1ETg.css
146 ms
css_mJO6luxxhz6BNJSc-wZ-XKtSFFWTLpZ1zNMcAyPQtFA.css
18 ms
css_lIy6wv32m3QYIYBrI7Hp80nvZP7HUJp3Zblb2idZEWA.css
1013 ms
css_wWyuR5kxgvUm4xczZ9vAEAYSTPdak-QTBRd-_ZlfYJo.css
44 ms
js_uRFF9Ou7qmZIm1xTbtWmZCXrQJ6kStuSQtTk92BG2uk.js
146 ms
js_v3cvd2C6jx5E9rEbJn3nPcUWDQ6W1YHXYzXYkOske_E.js
144 ms
js_yaW3jhkBGce7oUKJLNIm03JW08P3aD0AgeeHx6vDF9w.js
147 ms
js_PR4-dIOAHingEeAfPvL1-fPD883HXdYV2rpSKwlCkc0.js
147 ms
drupal_js_features.tmpl
419 ms
js_IVgS69Kes2KtLOzF2FHjdQNJeL1pj3wAiLsjP5V2wWE.js
147 ms
analytics.js
416 ms
js_qs2fhefHMGcNoS0-txSzztjYiVZ_I0e3w5XJ0PabRuA.js
151 ms
js_qzIC15r0WXGsYzbCOyM4dK3mQZvoSczguEl96CBeUz4.js
147 ms
js_ofEMQcSDgc1l8x3E2PioWhNZkUczT_sQUCLqQ26KKJE.js
150 ms
client_detect.js
145 ms
conversion.js
137 ms
js_eDCg5E8bOthWK6hcF-CXV_szeNCVMHYiuP77HpKg38U.js
140 ms
js_t5eOVk7jLXaKJntlxVs1ZpYM1AIioq4HpH3ubTRTjuM.js
142 ms
js_s6BCeFFMZrQacAtx5ocls1zidMrbVL3f1MOEeYp8E4I.js
140 ms
js
78 ms
index.tmpl
163 ms
tag.js
116 ms
trackingCode.js
180 ms
toolbar-bg.png
88 ms
site-logo.png
90 ms
newt.png
78 ms
Homepage_LMWnew-1.jpg
85 ms
blank_960x406.png
77 ms
HP_pop_lgo-1.jpg
81 ms
pep_start.jpg
91 ms
CL_Modules_Module1231.jpg
78 ms
S16_DCircle_website_home_image.jpg
81 ms
blank_960x406.png
81 ms
bg-product-content-grid.png
90 ms
clq_75X3_181x209.png
83 ms
clq_749K01_181x209.png
81 ms
clq_ZEK208_181x209.png
83 ms
clq_6G0R_181x209.png
90 ms
clq_60MK_181x209.png
88 ms
clq_6KN9_181x209.png
113 ms
clq_6121_181x209.png
91 ms
clq_7JHT_181x209.png
113 ms
clq_7T5_181x209.png
84 ms
clq_Z512_181x209.png
84 ms
icon-facebook.png
86 ms
clinique-sm.png
86 ms
530dee22-e3c1-4e9f-bf62-c31d510d9656.woff
24 ms
bcf54343-d033-41ee-bbd7-2b77df3fe7ba.woff
51 ms
60be5c39-863e-40cb-9434-6ebafb62ab2b.woff
24 ms
tag
34 ms
css_lmK5h5VWA6Mq9o8lYsDN-twPpfgCU_uo8L7G5MrxZCo.css
20 ms
f45edf6f1e0b72127834fe1390a5b42af6963fe2.js
21 ms
690da3f3fdeffe9a8f26714d8f4bcf4989ad5c6d.js
6 ms
dd93765545eeb8d0eb69a78a63025032fc86d8c8.js
9 ms
i.js
229 ms
240 ms
overlay.png
177 ms
interstitial.tmpl
195 ms
id
56 ms
border.png
40 ms
controls.png
34 ms
toc-up.png
35 ms
toc-down.png
34 ms
fontawesome-webfont.woff
85 ms
95 ms
s134895376507265027
26 ms
clinique.in accessibility score
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-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
ARIA input fields do not have accessible names
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
Form elements do not have associated labels
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.
clinique.in 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
clinique.in 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 Clinique.in 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 Clinique.in 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.
clinique.in
Open Graph description is not detected on the main page of Clinique. 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: