Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

Page Load Speed

4 sec in total

First Response

633 ms

Resources Loaded

2.8 sec

Page Rendered

608 ms

es.loccitane.com screenshot

About Website

Welcome to es.loccitane.com homepage info - get ready to check Es Loccitane best content for Japan right away, or after learning these important things about es.loccitane.com

Descubre lo último en cosmética, tratamiento facial y perfumes en la Página de L'Occitane. Entrega gratuita por tu primer pedido.

Visit es.loccitane.com

Key Findings

We analyzed Es.loccitane.com page load time and found that the first response time was 633 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

es.loccitane.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value16,260 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value33.0 s

0/100

10%

Network Requests Diagram

es.loccitane.com

633 ms

OCMS.css

174 ms

css

26 ms

vendors.min.js

261 ms

OCMS.min.js

132 ms

Our browser made a total of 140 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Es.loccitane.com, 45% (63 requests) were made to Img.loccitane.com and 6% (9 requests) were made to Mmtro.com. The less responsive or slowest element that took the longest time to load (696 ms) relates to the external source Js.sddan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (54%)

Content Size

4.6 MB

After Optimization

2.1 MB

In fact, the total size of Es.loccitane.com main page is 4.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. 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. CSS take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 170.1 kB

  • Original 224.8 kB
  • After minification 221.9 kB
  • After compression 54.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 170.1 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 30.3 kB

  • Original 1.6 MB
  • After minification 1.6 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. Es Loccitane images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 856.8 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 364.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 856.8 kB or 70% of the original size.

CSS Optimization

-90%

Potential reduce by 1.4 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 155.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. Es.loccitane.com needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 90% of the original size.

Requests Breakdown

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

Requests Now

129

After Optimization

66

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

Accessibility Review

es.loccitane.com accessibility score

86

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

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

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

High

Links do not have a discernible name

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

es.loccitane.com best practices score

83

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

Page has valid source maps

SEO Factors

es.loccitane.com SEO score

91

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Es.loccitane.com 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 Es.loccitane.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.

Social Sharing Optimization

Open Graph data is detected on the main page of Es Loccitane. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: