4.2 sec in total
583 ms
3.1 sec
542 ms
Welcome to mx.loccitane.com homepage info - get ready to check Mx L Occitane best content for Japan right away, or after learning these important things about mx.loccitane.com
Haz viajar a tus sentidos con L'OCCITANE, productos de cosmética natural de lujo y elegantes perfumes inspirados en la Provenza. ¡Un regalo para tu piel!
Visit mx.loccitane.comWe analyzed Mx.loccitane.com page load time and found that the first response time was 583 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
mx.loccitane.com performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value26.5 s
0/100
25%
Value12.0 s
4/100
10%
Value4,520 ms
0/100
30%
Value0.005
100/100
15%
Value26.6 s
0/100
10%
583 ms
160 ms
24 ms
239 ms
128 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 38% of them (38 requests) were addressed to the original Mx.loccitane.com, 37% (37 requests) were made to Img.loccitane.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Mx.loccitane.com.
Page size can be reduced by 5.1 MB (60%)
8.5 MB
3.4 MB
In fact, the total size of Mx.loccitane.com main page is 8.5 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. Images take 5.9 MB which makes up the majority of the site volume.
Potential reduce by 134.4 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 134.4 kB or 80% of the original size.
Potential reduce by 2.9 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. Obviously, Mx L Occitane needs image optimization as it can save up to 2.9 MB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 616.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 616.0 kB or 70% of the original size.
Potential reduce by 1.4 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. Mx.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.
Number of requests can be reduced by 21 (22%)
94
73
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mx L Occitane. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
mx.loccitane.com
583 ms
OCMS.css
160 ms
css
24 ms
vendors.min.js
239 ms
OCMS.min.js
128 ms
OCMS.ui.floatingbag.js
174 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
34 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
84 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
87 ms
ga.js
75 ms
gtm.js
79 ms
logo.png
74 ms
search_input.png
71 ms
search_link.png
72 ms
sprite_info_menu_links_list.png
69 ms
OCC_70210.jpg
1135 ms
OCC_65424.jpg
746 ms
OCC_135976.jpg
481 ms
OCC_159962.jpg
577 ms
OCC_131073.jpg
480 ms
OCC_113234.jpg
576 ms
OCC_153699.jpg
600 ms
OCC_205899.jpg
614 ms
OCC_205900.jpg
655 ms
OCC_151469.jpg
654 ms
OCC_205904.jpg
707 ms
OCC_205905.jpg
706 ms
OCC_178329.png
1060 ms
OCC_171237.jpg
818 ms
OCC_189945.png
1279 ms
OCC_189946.png
1278 ms
OCC_189947.png
1308 ms
OCC_202700.jpg
2044 ms
OCC_204549.png
1871 ms
OCC_204548.png
2100 ms
OCC_204550.jpg
1444 ms
OCC_100158.jpg
1366 ms
OCC_205854.jpg
1400 ms
OCC_205853.jpg
1635 ms
P.aspx
65 ms
P.aspx
64 ms
OCC_200124.png
474 ms
OCC_201217.jpg
121 ms
OCC_201336.jpg
123 ms
P.aspx
120 ms
OCC_139814.png
474 ms
P.aspx
474 ms
OCC_139807.png
121 ms
P.aspx
124 ms
P.aspx
477 ms
OCC_139802.png
153 ms
P.aspx
476 ms
conversion.js
52 ms
OCMS.footer.min.js
155 ms
OCC_205855.jpg
1699 ms
OCC_200080.jpg
1618 ms
OCC_205852.jpg
1704 ms
OCC_78487.png
1726 ms
OCC_78484.png
1784 ms
OCC_134273.png
1789 ms
OCC_78488.png
1790 ms
OCC_78483.png
1870 ms
OCC_78489.png
1873 ms
OCC_78486.png
1875 ms
P.aspx
458 ms
home_load.gif
556 ms
ecomBag_Ajax.aspx
2038 ms
basic_border_dark_brown.png
539 ms
basic_shadow_top.png
540 ms
basic_shadow_bottom.png
539 ms
basic_bg.png
539 ms
OCC_198396.png
2001 ms
sprite_mid_service.png
514 ms
__utm.gif
22 ms
rate_sprite.png
470 ms
collect
353 ms
339 ms
sprite_footer_site_map.png
435 ms
sprite_social_media.png
433 ms
pipe.png
433 ms
sdk.js
302 ms
widgets.js
449 ms
pinit.js
295 ms
platform.js
420 ms
OCC_90032.gif
525 ms
sprite_carousel_arrow.png
309 ms
sprite_regular_arrow.png
351 ms
nanoscroller_top.png
350 ms
nanoscroller_bottom.png
350 ms
like.php
250 ms
128 ms
pinit_main.js
38 ms
48 ms
49 ms
xd_arbiter.php
47 ms
xd_arbiter.php
90 ms
vpc6VNjRPXV.js
93 ms
LVx-xkvaJ0b.png
101 ms
01-10108-radar10.min.js
194 ms
xd_arbiter.php
39 ms
handshake.js
215 ms
mx.loccitane.com 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
[role]s are not contained by their required parent element
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
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.
mx.loccitane.com 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
mx.loccitane.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mx.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 Mx.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.
mx.loccitane.com
Open Graph data is detected on the main page of Mx L Occitane. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: