Tools & Wizards About Us
nz.loccitane.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nz.loccitane.com

Page Load Speed

2.7 sec in total

First Response

490 ms

Resources Loaded

2 sec

Page Rendered

253 ms

nz.loccitane.com screenshot

About Website

Visit nz.loccitane.com now to see the best up-to-date Nz Loccitane content for Japan and also check out these interesting facts you probably never knew about nz.loccitane.com

Visit nz.loccitane.com

Key Findings

We analyzed Nz.loccitane.com page load time and found that the first response time was 490 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

nz.loccitane.com performance score

0

Network Requests Diagram

nz.loccitane.com

490 ms

OCMS.css

257 ms

css

26 ms

vendors.min.js

328 ms

OCMS.min.js

205 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 30% of them (21 requests) were addressed to the original Nz.loccitane.com, 44% (31 requests) were made to Img.loccitane.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Img.loccitane.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.9 MB (77%)

Content Size

8.9 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nz.loccitane.com main page is 8.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. 60% of websites need less resources to load. Images take 6.3 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 94.7 kB

  • Original 121.7 kB
  • After minification 118.2 kB
  • After compression 27.0 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 94.7 kB or 78% of the original size.

Image Optimization

-75%

Potential reduce by 4.7 MB

  • Original 6.3 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. Obviously, Nz Loccitane needs image optimization as it can save up to 4.7 MB or 75% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 616.3 kB

  • Original 864.4 kB
  • After minification 853.7 kB
  • After compression 248.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 616.3 kB or 71% of the original size.

CSS Optimization

-90%

Potential reduce by 1.4 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 154.6 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. Nz.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 19 (29%)

Requests Now

66

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nz 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 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

nz.loccitane.com

nz.loccitane.com

490 ms

OCMS.css

OCMS.css

257 ms

css

css

26 ms

vendors.min.js

vendors.min.js

328 ms

OCMS.min.js

OCMS.min.js

205 ms

OCMS.ui.floatingbag.js

OCMS.ui.floatingbag.js

209 ms

OCMS.footer.min.js

OCMS.footer.min.js

90 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

10 ms

KT3KS9Aol4WfR6Vas8kNcg.woff

KT3KS9Aol4WfR6Vas8kNcg.woff

15 ms

wkfQbvfT_02e2IWO3yYueQ.woff

wkfQbvfT_02e2IWO3yYueQ.woff

20 ms

ga.js

ga.js

13 ms

logo.png

logo.png

31 ms

OCC_205420.jpg

OCC_205420.jpg

207 ms

OCC_183383.jpg

OCC_183383.jpg

309 ms

OCC_183372.jpg

OCC_183372.jpg

351 ms

OCC_155213.jpg

OCC_155213.jpg

285 ms

OCC_157985.jpg

OCC_157985.jpg

365 ms

OCC_154673.jpg

OCC_154673.jpg

363 ms

OCC_172293.jpg

OCC_172293.jpg

315 ms

OCC_172450.jpg

OCC_172450.jpg

545 ms

OCC_173908.jpg

OCC_173908.jpg

384 ms

OCC_173919.jpg

OCC_173919.jpg

416 ms

OCC_173920.jpg

OCC_173920.jpg

1057 ms

OCC_173918.jpg

OCC_173918.jpg

548 ms

OCC_155449.jpg

OCC_155449.jpg

473 ms

OCC_155453.jpg

OCC_155453.jpg

486 ms

OCC_155452.jpg

OCC_155452.jpg

505 ms

61557.jpg

61557.jpg

565 ms

61554.jpg

61554.jpg

587 ms

61556.jpg

61556.jpg

598 ms

OCC_205421.jpg

OCC_205421.jpg

111 ms

OCC_205422.jpg

OCC_205422.jpg

42 ms

OCC_178349.jpg

OCC_178349.jpg

288 ms

OCC_206970.jpg

OCC_206970.jpg

571 ms

OCC_206971.jpg

OCC_206971.jpg

371 ms

OCC_207968.jpg

OCC_207968.jpg

505 ms

OCC_206972.jpg

OCC_206972.jpg

358 ms

OCC_206996.jpg

OCC_206996.jpg

1185 ms

OCC_206994.jpg

OCC_206994.jpg

348 ms

OCC_207000.jpg

OCC_207000.jpg

598 ms

OCC_206999.jpg

OCC_206999.jpg

703 ms

home_load.gif

home_load.gif

397 ms

gtm.js

gtm.js

55 ms

search_input.png

search_input.png

420 ms

search_link.png

search_link.png

447 ms

__utm.gif

__utm.gif

18 ms

sprite_info_menu_links_list.png

sprite_info_menu_links_list.png

456 ms

ecomBag_Ajax.aspx

ecomBag_Ajax.aspx

680 ms

basic_border_dark_brown.png

basic_border_dark_brown.png

468 ms

basic_shadow_top.png

basic_shadow_top.png

496 ms

basic_shadow_bottom.png

basic_shadow_bottom.png

507 ms

basic_bg.png

basic_bg.png

521 ms

sprite_mid_service.png

sprite_mid_service.png

529 ms

sprite_footer_site_map.png

sprite_footer_site_map.png

534 ms

sprite_social_media.png

sprite_social_media.png

541 ms

pipe.png

pipe.png

551 ms

sdk.js

sdk.js

192 ms

widgets.js

widgets.js

76 ms

pinit.js

pinit.js

47 ms

platform.js

platform.js

117 ms

sprite_carousel_arrow.png

sprite_carousel_arrow.png

508 ms

nanoscroller_top.png

nanoscroller_top.png

512 ms

nanoscroller_bottom.png

nanoscroller_bottom.png

513 ms

pinit_main.js

pinit_main.js

48 ms

125 ms

157 ms

xd_arbiter.php

xd_arbiter.php

129 ms

xd_arbiter.php

xd_arbiter.php

258 ms

01-10108-radar10.min.js

01-10108-radar10.min.js

17 ms

handshake.js

handshake.js

43 ms

xd_arbiter.php

xd_arbiter.php

82 ms

SEO Factors

nz.loccitane.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

nz.loccitane.com

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