4.9 sec in total
428 ms
3.7 sec
776 ms
Welcome to clinique.be homepage info - get ready to check Clinique best content for Belgium right away, or after learning these important things about clinique.be
Shop the official Clinique website for skin care, makeup, fragrances and gifts. Read reviews & get Free Shipping today. Allergy Tested. 100% Fragrance Free.
Visit clinique.beWe analyzed Clinique.be page load time and found that the first response time was 428 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
clinique.be performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value12.5 s
0/100
25%
Value13.0 s
2/100
10%
Value5,080 ms
0/100
30%
Value0.05
99/100
15%
Value20.7 s
2/100
10%
428 ms
211 ms
206 ms
161 ms
353 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 94% of them (120 requests) were addressed to the original Clinique.be, 2% (2 requests) were made to Connect.facebook.net and 1% (1 request) were made to Js.sentry-cdn.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Clinique.be.
Page size can be reduced by 3.5 MB (61%)
5.7 MB
2.2 MB
In fact, the total size of Clinique.be main page is 5.7 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. Only a small number of websites need less resources to load. CSS take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 472.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. 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 472.6 kB or 80% of the original size.
Potential reduce by 492 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. Clinique images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 60% of the original size.
Potential reduce by 2.0 MB
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.be needs all CSS files to be minified and compressed as it can save up to 2.0 MB or 91% of the original size.
Number of requests can be reduced by 91 (74%)
123
32
The browser has sent 123 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 85 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.clinique.be
428 ms
css_cfOMT6XIniXXja2kUbvROl_YTvTHblxAnbZLoM8dI3U2.css
211 ms
css_ZIsat4uy0C3kvlimVfr2RyDieXMcKBqtRS5a_z_jvek2.css
206 ms
css_ODEZt9SQDvsJmEyMeYjqB9Ow1TcVbMgeEd3TRAxKV3U2.css
161 ms
css_qftzPCDyfX8IpZxpCZ8YH1xLjRGWnYC0C3a2_EdwJdw2.css
353 ms
css_COAVvUKBp2z94qB0KPnyfq8L3XzxSDlaIV8Eg9VTMRc2.css
123 ms
css_q3Mn88meyOyoO7qWz053rWAp2yNH_hMPXXcUo4RCAjY2.css
207 ms
css_ZvemF0WqDsNbXV2CyrpeM756v_WCNT1_EoUnqWgpl402.css
190 ms
9ac4aa2e0a0745a787b46b8dfd989629.min.js
25 ms
js_boot.js
273 ms
bundle.js
273 ms
bundle.js
271 ms
bundle.js
271 ms
bundle.js
273 ms
bundle.js
274 ms
bundle.js
277 ms
bundle.js
276 ms
bundle.js
274 ms
bundle.js
277 ms
bundle.js
282 ms
bundle.js
278 ms
bundle.js
278 ms
bundle.js
281 ms
bundle.js
283 ms
bundle.js
278 ms
bundle.js
279 ms
bundle.js
282 ms
bundle.js
284 ms
bundle.js
286 ms
bundle.js
283 ms
bundle.js
284 ms
bundle.js
286 ms
bundle.js
288 ms
bundle.js
305 ms
bundle.js
287 ms
js_c8LbWbHV1txem3q8oAzuadnL-HiBShaQH_WRviNqT_g.js
397 ms
js_sBujRWCEqi2OucT4DdSpsg7UPCFyROtSuWO6kUin9w0.js
388 ms
bundle.js
26 ms
jquery.colorbox-min.js
356 ms
js_LavUiS10ZOi5cqyiFcbweAukI0jpQHYE3OpJ9431l4I.js
241 ms
js_ZhxAQLAT7Zu1gEXU_6JywLz5yDSnL7KTV7hnhVNXPbc.js
226 ms
add_cart_button.min.js
272 ms
js_zVD5w-vJUJHH5F3gs3rj80FW2m_iELtX5JWRsZ61NCQ.js
229 ms
lang-toggle.min.js
250 ms
js_b2P72P-MYtSCyNzoSfd1bJcO9QJw8UWH3bfkrg0GB4g.js
192 ms
sd_perlgem_notify_me_hybrid_modal.min.js
195 ms
jsonrpc.min.js
288 ms
js_RVm2-DNQXYnhxc5e4WtolpLVi0GDfxRLJxVu_vV4ZTE.js
322 ms
js_M0g5P9sxNA39Vplc2w9Z8wEPoIYTFkruzmYn2pNqZ_A.js
269 ms
bundle.min.js
263 ms
js_SC15stfQfC3xIw3z5ZHvLxHzQMoFki8uhC-ruLDGdqw.js
281 ms
ELC.TealiumLoader.js
310 ms
ELC.DataLayer.js
339 ms
ELC.Analytics.js
339 ms
ELC.AnalyticsConnector.js
355 ms
ELC.ContentModules-Tracking.js
582 ms
ELC.BambuserAnalytics.js
476 ms
ELC.PixleeEvent.js
391 ms
ELC.PowerReviews.js
422 ms
ELC.GlobalNavigationTracking.js
412 ms
analytics.min.js
458 ms
js_zUwxBw8UHCSNOiFL7pVURMU7pF4MHtFa9igsyV9li98.js
478 ms
mount_skeleton.min.js
492 ms
js_48gfQBlT3F5d53BtKqN0oCB-ii6RYuMVvW0gvkny1ho.js
518 ms
js_dQsgnQsp2N6-vQzfX1qTGJYqGBDhYyRMGzozbf0zHpU.js
652 ms
js_AUv49zComSZM5PRwsTHnp_g8SwQhaiUwO1YNIAHmdVg.js
565 ms
js_Aw5tGzL79Av6eUGZyjF3dW5YPweu6r5p6UVs2xFuxUU.js
550 ms
facebook_login.min.js
553 ms
js_ess-IbUJNAYi6NnlSswils4wxJCNiBwE5p2eSJbn2-Q.js
623 ms
js_b6Eex6HUQ1PNd_XStnvFkQpO2z9sJ2smWdQF3V4UGZM.js
622 ms
cart.min.js
610 ms
bundle.es5.min.js
14 ms
js_GiVVLkoxCDIDayYQGW3xMclevvsxJfsP-UE5C8061Eo.js
537 ms
refinements.min.js
673 ms
js_rLx22s-bctNuib78F3uUcsU0HcQ332CtamNfoMwI-qY.js
683 ms
elc_sd_search_gnav_input_field_v1.js
671 ms
js_qknWI6vI0O-gF2-yin3C_6x8zE7vS9KvZFP13nh_r9Q.js
657 ms
phone_order.js
621 ms
js_wmzB5HruIlsIE_Ny_UvhjHjaUm46jMdrO-yOt4fTnxc.js
632 ms
perlgem_favorites_events.min.js
597 ms
perlgem_cart_hook.min.js
664 ms
perlgem_store_inventory_hook.min.js
636 ms
perlgem_apptbooking_token_hook.min.js
717 ms
perlgem_notify_me_hook.min.js
665 ms
perlgem_is_auth_hook.min.js
570 ms
perlgem_user_auth_state_hook.min.js
577 ms
perlgem_vto_hook.min.js
667 ms
js_XD7T_3RXAEUJlzLZ-hcsV6NYWsnjRNx7vWZWcfS1UNk.js
618 ms
ELC.liveperson.js
692 ms
wby96OgQ
603 ms
9YDT7-2D4WH-QYY8G-FW647-SCCY7
110 ms
search-icon.svg
311 ms
SP24_WeddingGuestLooksTrend_BMW_dt_1.jpg
396 ms
gnav_trend_peach.jpg
400 ms
gnav_trend_winterglow.jpg
553 ms
gnav_trend_sunkissed.jpg
575 ms
gnav_trend_bh.jpg
434 ms
gnav_trend_hifi.jpg
616 ms
primers_bmw1.5x.jpg
884 ms
PH_neu&trendig.jpg
1136 ms
cldays_teasing_ms100h-1.png
1005 ms
GNAV-Tout_jumbo.jpg
740 ms
may_monthly_gwp_LMW_m.gif
994 ms
CL_New_GNAV_FY24_Lifestyle-Jan_Lower_GWP.jpg
791 ms
gnav_tout_sets.jpg
1021 ms
SP24_WeddingGuestLooksTrend_LMW_dt.jpg
1103 ms
SP24_WeddingGuestLooksTrend_BMW_dt_2.jpg
953 ms
SP24_WeddingGuestLooksTrend_BMW_dt_3.jpg
1136 ms
cl_sku_V82P01_600x750_0.png
1131 ms
cl_sku_V17515_600x750_0.png
1157 ms
HelveticaNeue-Bold.woff2
990 ms
js_qknWI6vI0O-gF2-yin3C_6x8zE7vS9KvZFP13nh_r9Q.js
184 ms
HelveticaNeue-Regular.woff2
998 ms
HelveticaNeue-Light.woff2
1033 ms
cl_sku_VATM03_600x750_0.png
1290 ms
cl_sku_635906_600x750_0.png
1330 ms
may_monthly_gwp_MPPtout_dt.gif
1408 ms
FA23_BH-PH_LMW_A_dt.jpg
1202 ms
config.json
554 ms
FY23_ATFF_SlimTout_dt_nl.jpg
1177 ms
icon1_fs@2x_v2.png
1848 ms
icon2_samples@2x_v2.png
1274 ms
01_Icon3_Services_d.jpg
1250 ms
icon4_smart@2x_v2.png
1269 ms
sdk.js
92 ms
ajax-loader.gif
1113 ms
sdk.js
6 ms
css_8MdvY4NL4O25UbWho2tFZPQkRQGGS4yNvSQPb_9KPX82.css
150 ms
clinique.be 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
clinique.be 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
Page has valid source maps
clinique.be 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 uses legible font sizes
Tap targets are not sized appropriately
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Clinique.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Clinique.be 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.be
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: