Tools & Wizards About Us
manontokyo.com screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

manontokyo.com

Manon Mimie

Page Load Speed

14.3 sec in total

First Response

2 sec

Resources Loaded

10.7 sec

Page Rendered

1.6 sec

manontokyo.com screenshot

About Website

Click here to check amazing Manon Tokyo content. Otherwise, check out these important facts you probably never knew about manontokyo.com

Manon Mimie 公式サイト。ラフォーレ原宿にある可愛い好きのためのセレクトショップです♡

Visit manontokyo.com

Key Findings

We analyzed Manontokyo.com page load time and found that the first response time was 2 sec and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

manontokyo.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

www.manontokyo.com

1979 ms

css2

33 ms

cf7msm.css

180 ms

styles.css

356 ms

bootstrap.min.css

692 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 95% of them (42 requests) were addressed to the original Manontokyo.com, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Manontokyo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 390.4 kB (4%)

Content Size

10.6 MB

After Optimization

10.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 23.4 kB

  • Original 27.4 kB
  • After minification 23.3 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 4.1 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.4 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 354.4 kB

  • Original 10.5 MB
  • After minification 10.1 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. Manon Tokyo images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 11.5 kB

  • Original 96.5 kB
  • After minification 93.0 kB
  • After compression 85.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 11.5 kB or 12% of the original size.

CSS Optimization

-3%

Potential reduce by 1.1 kB

  • Original 33.5 kB
  • After minification 33.5 kB
  • After compression 32.4 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. Manontokyo.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (34%)

Requests Now

41

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.manontokyo.com

www.manontokyo.com

1979 ms

css2

css2

33 ms

cf7msm.css

cf7msm.css

180 ms

styles.css

styles.css

356 ms

bootstrap.min.css

bootstrap.min.css

692 ms

aos.css

aos.css

522 ms

swiper.min.css

swiper.min.css

526 ms

lightbox.min.css

lightbox.min.css

526 ms

style.css

style.css

527 ms

jquery.min.js

jquery.min.js

706 ms

jquery-migrate.min.js

jquery-migrate.min.js

698 ms

lightbox.min.js

lightbox.min.js

702 ms

aos.js

aos.js

700 ms

swiper.min.js

swiper.min.js

929 ms

function.js

function.js

868 ms

cf7msm.min.js

cf7msm.min.js

872 ms

scripts.js

scripts.js

879 ms

logo.png

logo.png

177 ms

Manon-Tokyo%E6%A8%AA-scaled.jpg

Manon-Tokyo%E6%A8%AA-scaled.jpg

2394 ms

Manon-Mimie%E6%A8%AA4.jpg

Manon-Mimie%E6%A8%AA4.jpg

1051 ms

Manon-Mimie%E6%A8%AA2.jpg

Manon-Mimie%E6%A8%AA2.jpg

1694 ms

Manon-Mimie%E6%A8%AA3.jpg

Manon-Mimie%E6%A8%AA3.jpg

1852 ms

New-Collection-scaled.jpg

New-Collection-scaled.jpg

2340 ms

IMG_6030-scaled.jpg

IMG_6030-scaled.jpg

858 ms

Brand-info-scaled.jpg

Brand-info-scaled.jpg

2729 ms

IMG_2220-2.jpg

IMG_2220-2.jpg

1757 ms

IMG_2222.jpg

IMG_2222.jpg

2718 ms

IMG_2221.jpg

IMG_2221.jpg

2834 ms

IMG_2223.jpg

IMG_2223.jpg

2692 ms

IMG_2225.jpg

IMG_2225.jpg

3014 ms

IMG_7778.jpg

IMG_7778.jpg

3250 ms

IMG_1665-scaled.jpg

IMG_1665-scaled.jpg

4209 ms

IMG_1472.jpg

IMG_1472.jpg

3569 ms

IMG_1991-scaled.jpg

IMG_1991-scaled.jpg

4095 ms

AD0F5F82-946D-4C05-A5FC-FE38838829A8.jpg

AD0F5F82-946D-4C05-A5FC-FE38838829A8.jpg

6158 ms

43420680-0C10-46BC-B457-94789FD523C9.jpg

43420680-0C10-46BC-B457-94789FD523C9.jpg

4923 ms

IMG_5704.jpg

IMG_5704.jpg

3943 ms

footerlogo.png

footerlogo.png

3745 ms

ahcfv8qz1zt6hCC5G4F_P4ASpUw.ttf

ahcfv8qz1zt6hCC5G4F_P4ASpUw.ttf

32 ms

iconfont.woff

iconfont.woff

3854 ms

prev.png

prev.png

4006 ms

next.png

next.png

4029 ms

loading.gif

loading.gif

4180 ms

close.png

close.png

4180 ms

Accessibility Review

manontokyo.com accessibility score

77

Accessibility Issues

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

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

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

manontokyo.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

manontokyo.com SEO score

84

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

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

manontokyo.com

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