Tools & Wizards About Us
lancome.com.hk screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

lancome.com.hk

維持青春肌膚秘密 | 護膚產品 | Lancôme香港

Page Load Speed

7 sec in total

First Response

506 ms

Resources Loaded

6.3 sec

Page Rendered

184 ms

lancome.com.hk screenshot

About Website

Visit lancome.com.hk now to see the best up-to-date Lancome content for Hong Kong and also check out these interesting facts you probably never knew about lancome.com.hk

探索皇牌產品及最新人氣推薦產品。立即登入品牌網站，了解更多維持青春肌膚的秘密。

Visit lancome.com.hk

Key Findings

We analyzed Lancome.com.hk page load time and found that the first response time was 506 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

lancome.com.hk performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value3,820 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.427

22/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

lancome.com.hk

506 ms

index.aspx

458 ms

index.aspx

1175 ms

common.css

423 ms

header.css

442 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 97% of them (72 requests) were addressed to the original Lancome.com.hk, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Lancome.com.hk.

Page Optimization Overview & Recommendations

Page size can be reduced by 290.8 kB (13%)

Content Size

2.2 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lancome.com.hk main page is 2.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. 35% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 45.7 kB

  • Original 57.4 kB
  • After minification 51.6 kB
  • After compression 11.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 45.7 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 15.3 kB

  • Original 1.8 MB
  • After minification 1.8 MB

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. Lancome images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 213.5 kB

  • Original 300.7 kB
  • After minification 275.6 kB
  • After compression 87.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 213.5 kB or 71% of the original size.

CSS Optimization

-81%

Potential reduce by 16.3 kB

  • Original 20.1 kB
  • After minification 13.6 kB
  • After compression 3.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. Lancome.com.hk needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (63%)

Requests Now

70

After Optimization

26

  • Images
  • JavaScript
  • CSS

The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lancome. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lancome.com.hk

lancome.com.hk

506 ms

index.aspx

index.aspx

458 ms

index.aspx

index.aspx

1175 ms

common.css

common.css

423 ms

header.css

header.css

442 ms

footer.css

footer.css

451 ms

popin.css

popin.css

456 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

1143 ms

jquery.bgiframe.min.js

jquery.bgiframe.min.js

630 ms

jquery-ui-1.7.2.custom.min.js

jquery-ui-1.7.2.custom.min.js

876 ms

loreal.tools.js

loreal.tools.js

876 ms

loreal.loc.js.axd

loreal.loc.js.axd

682 ms

loreal.js

loreal.js

1128 ms

homepage.css

homepage.css

845 ms

swfobject.js

swfobject.js

905 ms

dynamic_common.css.axd

dynamic_common.css.axd

644 ms

dynamic_header.css.axd

dynamic_header.css.axd

669 ms

dynamic_footer.css.axd

dynamic_footer.css.axd

651 ms

dynamic_popin.css.axd

dynamic_popin.css.axd

683 ms

dynamic_homepage.css

dynamic_homepage.css

222 ms

HEADER_SIGN_IN_POPIN_CLOSE.gif

HEADER_SIGN_IN_POPIN_CLOSE.gif

222 ms

HEADER_SIGN_IN_POPIN_LOGIN.gif

HEADER_SIGN_IN_POPIN_LOGIN.gif

231 ms

HEADER_SIGN_IN_OFF.gif

HEADER_SIGN_IN_OFF.gif

212 ms

HEADER_REGISTER_OFF.gif

HEADER_REGISTER_OFF.gif

226 ms

HEADER_FULL_LOGO.gif

HEADER_FULL_LOGO.gif

226 ms

HEADER_MY_BASKET.gif

HEADER_MY_BASKET.gif

221 ms

HEADER_VIEW_OFF.gif

HEADER_VIEW_OFF.gif

425 ms

HEADER_BAG_OPEN_BASKET_LAYER.gif

HEADER_BAG_OPEN_BASKET_LAYER.gif

442 ms

bouton_close.gif

bouton_close.gif

439 ms

headerb_btn_ViewBskt_OFF.gif

headerb_btn_ViewBskt_OFF.gif

450 ms

headerb_bottom.png

headerb_bottom.png

451 ms

HEADER_BAG_CLOSE_BASKET_LAYER.gif

HEADER_BAG_CLOSE_BASKET_LAYER.gif

457 ms

HEADER_MN_SRCH_ICN_GLASS_OFF.GIF

HEADER_MN_SRCH_ICN_GLASS_OFF.GIF

640 ms

300413_s.jpg

300413_s.jpg

876 ms

btn_see_off.gif

btn_see_off.gif

660 ms

HF5607000_s.jpg

HF5607000_s.jpg

673 ms

253019_s.jpg

253019_s.jpg

674 ms

160216a_s.jpg

160216a_s.jpg

686 ms

022055_s.jpg

022055_s.jpg

906 ms

201211_s.jpg

201211_s.jpg

879 ms

PT_Section1_Item66.jpg

PT_Section1_Item66.jpg

2483 ms

PT_Section1_Item68.jpg

PT_Section1_Item68.jpg

2704 ms

PT_Section1_Item69_1.jpg

PT_Section1_Item69_1.jpg

2287 ms

PT_Section1_Item71.jpg

PT_Section1_Item71.jpg

2407 ms

PT_Section1_Item70.jpg

PT_Section1_Item70.jpg

2240 ms

FOOTER_JOIN_NOW_OFF.gif

FOOTER_JOIN_NOW_OFF.gif

1115 ms

HEADER_LOGO_BLACK.gif

HEADER_LOGO_BLACK.gif

1326 ms

POPIN_LOADING.gif

POPIN_LOADING.gif

1537 ms

TLN_SMPL_BTN_Close.png

TLN_SMPL_BTN_Close.png

1746 ms

BTN_Rgstr_OFF.png

BTN_Rgstr_OFF.png

1957 ms

BTN_SgnIn_OFF.png

BTN_SgnIn_OFF.png

2167 ms

HEADER_SIGN_IN_POPIN_ON.png

HEADER_SIGN_IN_POPIN_ON.png

2363 ms

HEADER_BTN_SIGNIN.png

HEADER_BTN_SIGNIN.png

2448 ms

HEADER_BTN_REGISTER.png

HEADER_BTN_REGISTER.png

2499 ms

HEADER_BAG_INPUT_TEXT_ROUND_BORDER_LEFT.gif

HEADER_BAG_INPUT_TEXT_ROUND_BORDER_LEFT.gif

2574 ms

HEADER_MN_SRCH_BG.gif

HEADER_MN_SRCH_BG.gif

2610 ms

ga.js

ga.js

58 ms

__utm.gif

__utm.gif

12 ms

interstate.woff

interstate.woff

2482 ms

HEADER_BAG_INPUT_TEXT_ROUND_BORDER_RIGHT.gif

HEADER_BAG_INPUT_TEXT_ROUND_BORDER_RIGHT.gif

2491 ms

FACEBOOK_LOGO.png

FACEBOOK_LOGO.png

2529 ms

HEADER_TAB_MENU_FULL.png

HEADER_TAB_MENU_FULL.png

2582 ms

FOOTER_MENU_CONTENT_BOTTOM.gif

FOOTER_MENU_CONTENT_BOTTOM.gif

2625 ms

FOOTER_BODY_CONTENT_BOTTOM.gif

FOOTER_BODY_CONTENT_BOTTOM.gif

2685 ms

FOOTER_IMG_PRODUCTS.png

FOOTER_IMG_PRODUCTS.png

2510 ms

FOOTER_IMG_ACCOUNT.png

FOOTER_IMG_ACCOUNT.png

2497 ms

FOOTER_IMG_COMMITMENTS.png

FOOTER_IMG_COMMITMENTS.png

2541 ms

FOOTER_IMG_CONTACT.png

FOOTER_IMG_CONTACT.png

2566 ms

FOOTER_IMG_KEEPMEUPDATED.png

FOOTER_IMG_KEEPMEUPDATED.png

2619 ms

popin_cadre_border_middle_left2.png

popin_cadre_border_middle_left2.png

2679 ms

back-popin-fav.png

back-popin-fav.png

2519 ms

new_account.gif

new_account.gif

2501 ms

btn_rgstr_pop.png

btn_rgstr_pop.png

2535 ms

btn_sgnin.png

btn_sgnin.png

2552 ms

Accessibility Review

lancome.com.hk accessibility score

43

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lancome.com.hk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

lancome.com.hk SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lancome.com.hk can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lancome.com.hk 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.

Social Sharing Optimization

lancome.com.hk

Open Graph description is not detected on the main page of Lancome. 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: