Tools & Wizards About Us
lancome.es screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    35% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    61% of websites

lancome.es

Belleza, Maquillaje y Tratamientos Antiedad de lujo | Lancôme

Page Load Speed

10.7 sec in total

First Response

2.3 sec

Resources Loaded

5.2 sec

Page Rendered

3.2 sec

lancome.es screenshot

About Website

Click here to check amazing Lancome content for Spain. Otherwise, check out these important facts you probably never knew about lancome.es

Descubra la selección de tratamientos antiedad para la piel y nuestros productos de maquillaje. Consiga una belleza natural para su piel con Lancôme.

Visit lancome.es

Key Findings

We analyzed Lancome.es page load time and found that the first response time was 2.3 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

lancome.es performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value3,950 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.259

47/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

www.lancome.es

2313 ms

otSDKStub.js

82 ms

commons.css

168 ms

pagedesigner.css

162 ms

content.css

111 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 67% of them (18 requests) were addressed to the original Lancome.es, 26% (7 requests) were made to Cdn.cookielaw.org and 4% (1 request) were made to Cdn.cquotient.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Lancome.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (81%)

Content Size

1.9 MB

After Optimization

367.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lancome.es 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. 70% of websites need less resources to load. HTML takes 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 1.5 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 175.7 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 1.5 MB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 9.0 kB
  • After minification 9.0 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. Lancome images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 6.8 kB

  • Original 42.9 kB
  • After minification 42.9 kB
  • After compression 36.1 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 6.8 kB or 16% of the original size.

CSS Optimization

-2%

Potential reduce by 2.9 kB

  • Original 149.6 kB
  • After minification 149.6 kB
  • After compression 146.7 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.es has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (65%)

Requests Now

23

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 23 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 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.lancome.es

www.lancome.es

2313 ms

otSDKStub.js

otSDKStub.js

82 ms

commons.css

commons.css

168 ms

pagedesigner.css

pagedesigner.css

162 ms

content.css

content.css

111 ms

7925c6bd-079d-484f-adc0-41f6dc5d1d9e.json

7925c6bd-079d-484f-adc0-41f6dc5d1d9e.json

420 ms

otBannerSdk.js

otBannerSdk.js

1655 ms

system.js

system.js

567 ms

system.config.js

system.config.js

566 ms

main.js

main.js

565 ms

dwanalytics-22.2.js

dwanalytics-22.2.js

563 ms

dwac-21.7.js

dwac-21.7.js

714 ms

gretel.min.js

gretel.min.js

739 ms

placeholder-2.png

placeholder-2.png

1242 ms

shipping.png

shipping.png

619 ms

samples.png

samples.png

619 ms

easy-checkout_v3.png

easy-checkout_v3.png

618 ms

complimentary-engraving_v3.png

complimentary-engraving_v3.png

705 ms

HelveticaNeue.woff

HelveticaNeue.woff

651 ms

MillerDisplay-Light.woff

MillerDisplay-Light.woff

223 ms

es.json

es.json

183 ms

category.css

category.css

66 ms

otCenterRounded.json

otCenterRounded.json

401 ms

otPcCenter.json

otPcCenter.json

401 ms

otCommonStyles.css

otCommonStyles.css

401 ms

product.css

product.css

414 ms

oct8ne-api-2.3.js

oct8ne-api-2.3.js

546 ms

Accessibility Review

lancome.es accessibility score

92

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 IDs are not unique

Best Practices

lancome.es best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

lancome.es SEO score

86

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

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lancome.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Lancome.es 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.es

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: