5.1 sec in total
678 ms
4.2 sec
215 ms
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.jpWe analyzed E-why.jp page load time and found that the first response time was 678 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
e-why.jp performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.5 s
38/100
25%
Value7.0 s
33/100
10%
Value30 ms
100/100
30%
Value0.186
65/100
15%
Value4.5 s
82/100
10%
678 ms
309 ms
335 ms
309 ms
330 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 64% of them (58 requests) were addressed to the original E-why.jp, 16% (14 requests) were made to Gigaplus.makeshop.jp and 13% (12 requests) were made to Why.co.jp. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain E-why.jp.
Page size can be reduced by 146.1 kB (29%)
504.1 kB
357.9 kB
In fact, the total size of E-why.jp main page is 504.1 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. 35% of websites need less resources to load. Images take 352.0 kB which makes up the majority of the site volume.
Potential reduce by 92.3 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 31.0 kB, which is 30% 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 92.3 kB or 90% of the original size.
Potential reduce by 28.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.
Potential reduce by 3.3 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 3.3 kB or 15% of the original size.
Potential reduce by 22.3 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 22.3 kB or 81% of the original size.
Number of requests can be reduced by 39 (44%)
88
49
The browser has sent 88 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 10 to 1 for CSS and as a result speed up the page load time.
e-why.jp
678 ms
import.css
309 ms
script.js
335 ms
check_history.css
309 ms
pager.css
330 ms
shopdetail.css
332 ms
ranking.css
330 ms
basket.css
355 ms
security.css
386 ms
category_menu.css
641 ms
topicpath.css
637 ms
catalog.css
638 ms
login_btn.gif
509 ms
logo.gif
485 ms
count2.makeshop.jp
587 ms
sp_30_30.gif
497 ms
tel_icon.gif
497 ms
tel0366959341.gif
498 ms
500point_btn_150_50.gif
501 ms
top_btn.gif
520 ms
artherapie_btn.gif
802 ms
reineclaude_btn.gif
819 ms
mimipinson_btn.gif
803 ms
guide_btn1.gif
832 ms
line_01.gif
828 ms
information.gif
850 ms
reineclaude2015_base_top.jpg
1176 ms
artherapie2016_03_top_nov.jpg
1218 ms
reine_new_310_80_base.jpg
894 ms
at_new_310_80_base.jpg
900 ms
reine_blog_310_80_base.jpg
909 ms
at_blog_310_80_base.jpg
913 ms
reine_sale_310_80_base.jpg
1058 ms
at_sale_310_80_base.jpg
1066 ms
h5_spacer.gif
542 ms
croche_top_210_82_base.jpg
1077 ms
bananaclip_210_82_base.jpg
1088 ms
gummyclip_top_210_82.jpg
1387 ms
201211top_bananaclip.gif
560 ms
list_title.gif
166 ms
listdot.gif
167 ms
menu_bottom.gif
168 ms
search.gif
309 ms
tel_title.gif
330 ms
telicon.gif
332 ms
trans.gif
475 ms
mailicon.gif
493 ms
tel_bottom.gif
495 ms
gmosp965_gmosp965_why_baner.jpg
646 ms
gmosp965_reineclaude_official.jpg
636 ms
gmosp965_gmosp965_birdie145_35.gif
663 ms
maintitle1.gif
818 ms
0000000043233.jpg
827 ms
iconU.gif
869 ms
mk_main_p_line.gif
956 ms
0000000043223.jpg
968 ms
0000000043213.jpg
1012 ms
0000000042543.jpg
1144 ms
maintitle2.gif
1156 ms
0000000043253.jpg
1155 ms
0000000043243.jpg
1262 ms
0000000043133.jpg
1273 ms
0000000043123.jpg
1338 ms
0000000043113.jpg
1461 ms
0000000043103.jpg
1496 ms
0000000043093.jpg
1505 ms
0000000043083.jpg
1573 ms
0000000043073.jpg
1599 ms
0000000042523.jpg
1689 ms
0000000042443.jpg
1767 ms
0000000042433.jpg
1847 ms
0000000042423.jpg
1855 ms
0000000042413.jpg
1886 ms
0000000042403.jpg
1926 ms
0000000042393.jpg
1986 ms
is_show_gmo_header.html
859 ms
ga.js
12 ms
__utm.gif
11 ms
__utm.gif
12 ms
__utm.gif
12 ms
0000000042373.jpg
1965 ms
0000000042343.jpg
2013 ms
0000000042333.jpg
2024 ms
0000000042283.jpg
1909 ms
info_title.gif
1933 ms
noticedot.gif
2004 ms
20090604.jpg
2113 ms
menu_line.gif
2018 ms
boardbg.gif
2026 ms
mk_main_underline.gif
1934 ms
e-why.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
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.
e-why.jp 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
e-why.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
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.
e-why.jp
Open Graph description is not detected on the main page of E Why. 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: