Tools & Wizards About Us
e-why.jp screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

e-why.jp

レーヌクロード へアアクセサリー｜ミザンパージュオンラインショップ

Page Load Speed

4.6 sec in total

First Response

806 ms

Resources Loaded

3.7 sec

Page Rendered

182 ms

e-why.jp screenshot

About Website

Welcome to e-why.jp homepage info - get ready to check E Why best content right away, or after learning these important things about e-why.jp

レーヌクロードの上品で高品質のヘアアクセサリー、レディースファッション小物をリーズナブルに販売中。

Visit e-why.jp

Key Findings

We analyzed E-why.jp page load time and found that the first response time was 806 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

e-why.jp performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.141

78/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

www.e-why.jp

806 ms

index.css

162 ms

top.css

167 ms

jquery.min.js

23 ms

js

67 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 30% of them (9 requests) were addressed to the original E-why.jp, 37% (11 requests) were made to Img21.shop-pro.jp and 13% (4 requests) were made to Img.shop-pro.jp. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Img21.shop-pro.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.6 kB (11%)

Content Size

549.5 kB

After Optimization

490.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-why.jp main page is 549.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 460.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 18.0 kB

  • Original 23.4 kB
  • After minification 20.0 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 3.4 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 18.0 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 25.5 kB

  • Original 460.8 kB
  • After minification 435.2 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. E Why images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 4.1 kB

  • Original 50.6 kB
  • After minification 50.2 kB
  • After compression 46.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-75%

Potential reduce by 10.9 kB

  • Original 14.7 kB
  • After minification 11.4 kB
  • After compression 3.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. E-why.jp needs all CSS files to be minified and compressed as it can save up to 10.9 kB or 75% of the original size.

Requests Breakdown

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

Requests Now

29

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.e-why.jp

www.e-why.jp

806 ms

index.css

index.css

162 ms

top.css

top.css

167 ms

jquery.min.js

jquery.min.js

23 ms

js

js

67 ms

jquery.tile.js

jquery.tile.js

196 ms

jquery.masonry.min.js

jquery.masonry.min.js

198 ms

jquery.bxslider.css

jquery.bxslider.css

195 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

370 ms

cart.js

cart.js

547 ms

async_cart_in.js

async_cart_in.js

537 ms

product_stock.js

product_stock.js

685 ms

js.cookie.js

js.cookie.js

686 ms

favorite_button.js

favorite_button.js

703 ms

acc-track.js

acc-track.js

871 ms

PA01480422.png

PA01480422.png

25 ms

slideshow_img_30d812.jpg

slideshow_img_30d812.jpg

900 ms

slideshow_img_dedce3.jpg

slideshow_img_dedce3.jpg

1175 ms

slideshow_img_1c37d7.jpg

slideshow_img_1c37d7.jpg

1171 ms

172516911_th.jpg

172516911_th.jpg

664 ms

166155042_th.jpg

166155042_th.jpg

792 ms

166154526_th.jpg

166154526_th.jpg

30 ms

166155340_th.jpg

166155340_th.jpg

698 ms

166154527_th.jpg

166154527_th.jpg

1011 ms

header_category_pulldown.png

header_category_pulldown.png

24 ms

icons16.png

icons16.png

2 ms

bx_loader.gif

bx_loader.gif

167 ms

li.php

li.php

176 ms

li.php

li.php

175 ms

li.php

li.php

176 ms

Accessibility Review

e-why.jp accessibility score

92

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.

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

e-why.jp best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

e-why.jp SEO score

92

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-why.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that E-why.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

e-why.jp

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