Tools & Wizards About Us
ebiya.ne.jp screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

ebiya.ne.jp

原料問屋ゑびや｜漢方卸から個人様へ

Page Load Speed

16 sec in total

First Response

529 ms

Resources Loaded

15.1 sec

Page Rendered

322 ms

ebiya.ne.jp screenshot

About Website

Welcome to ebiya.ne.jp homepage info - get ready to check Ebiya best content for Japan right away, or after learning these important things about ebiya.ne.jp

高麗人参(紅参)はじめ漢方粉末の卸通販、サプリメントに加工前の原料粉末(100％)を年間2万人に通販利用いただいています。お求めやすい価格と素材の選定力が原料問屋ゑびや、ショールームでは店頭販売、高麗人参の試食もどうぞ。

Visit ebiya.ne.jp

Key Findings

We analyzed Ebiya.ne.jp page load time and found that the first response time was 529 ms and then it took 15.5 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

ebiya.ne.jp performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value19.5 s

0/100

25%

SI (Speed Index)

Value17.4 s

0/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.09

92/100

15%

TTI (Time to Interactive)

Value20.7 s

2/100

10%

Network Requests Diagram

ebiya.ne.jp

529 ms

www.ebiya.ne.jp

1890 ms

reset.css

499 ms

core.css

671 ms

content.css

676 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 93% of them (100 requests) were addressed to the original Ebiya.ne.jp, 3% (3 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (7.5 sec) belongs to the original domain Ebiya.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 336.7 kB (8%)

Content Size

4.4 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ebiya.ne.jp main page is 4.4 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. 55% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 37.2 kB

  • Original 46.8 kB
  • After minification 40.0 kB
  • After compression 9.5 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 6.8 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 37.2 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 34.4 kB

  • Original 4.0 MB
  • After minification 3.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. Ebiya images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 160.5 kB

  • Original 225.9 kB
  • After minification 191.5 kB
  • After compression 65.4 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 160.5 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 104.6 kB

  • Original 121.7 kB
  • After minification 93.3 kB
  • After compression 17.1 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. Ebiya.ne.jp needs all CSS files to be minified and compressed as it can save up to 104.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (31%)

Requests Now

106

After Optimization

73

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ebiya.ne.jp

ebiya.ne.jp

529 ms

www.ebiya.ne.jp

www.ebiya.ne.jp

1890 ms

reset.css

reset.css

499 ms

core.css

core.css

671 ms

content.css

content.css

676 ms

top.css

top.css

517 ms

material.css

material.css

861 ms

eecfed6be7858ad256de84cdd196e294.js

eecfed6be7858ad256de84cdd196e294.js

679 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

1705 ms

jquery.easing.js

jquery.easing.js

1017 ms

slideshow.js

slideshow.js

1173 ms

script_top.js

script_top.js

1181 ms

script.js

script.js

1190 ms

blank.js

blank.js

1378 ms

pagetop.js

pagetop.js

1517 ms

jquery.bxslider.js

jquery.bxslider.js

2052 ms

logo.gif

logo.gif

186 ms

img_tel.gif

img_tel.gif

597 ms

gnav_com_globalnavi_monozukuri.gif

gnav_com_globalnavi_monozukuri.gif

589 ms

gnav_com_globalnavi_yojo.gif

gnav_com_globalnavi_yojo.gif

595 ms

gnav_com_globalnavi_product.gif

gnav_com_globalnavi_product.gif

592 ms

gnav_com_globalnavi_safety.gif

gnav_com_globalnavi_safety.gif

593 ms

gnav_com_globalnavi_desire.gif

gnav_com_globalnavi_desire.gif

756 ms

img_top_visual01.jpg

img_top_visual01.jpg

3403 ms

img_top_visual06.jpg

img_top_visual06.jpg

2632 ms

img_top_visual07.jpg

img_top_visual07.jpg

2430 ms

img_top_visual03.jpg

img_top_visual03.jpg

2677 ms

img_top_visual04.jpg

img_top_visual04.jpg

3023 ms

gnav_com_globalnavi_material.gif

gnav_com_globalnavi_material.gif

1254 ms

_1.jpg

_1.jpg

2881 ms

_1.png

_1.png

2953 ms

6.png

6.png

3138 ms

_1.jpg

_1.jpg

3536 ms

_1.jpg

_1.jpg

3741 ms

_1.jpg

_1.jpg

3810 ms

_1.jpg

_1.jpg

4519 ms

_1.png

_1.png

3636 ms

JAS.png

JAS.png

3919 ms

_1.jpg

_1.jpg

4398 ms

_1.jpg

_1.jpg

4493 ms

_1.jpg

_1.jpg

4585 ms

_1.jpg

_1.jpg

5355 ms

2.png

2.png

4440 ms

_1.png

_1.png

4900 ms

_1.jpg

_1.jpg

5442 ms

_1.jpg

_1.jpg

5158 ms

_1.jpg

_1.jpg

5852 ms

_1.png

_1.png

5101 ms

21.png

21.png

5404 ms

_1.jpg

_1.jpg

5933 ms

_1.jpg

_1.jpg

6020 ms

gtm.js

gtm.js

109 ms

_1.jpg

_1.jpg

6203 ms

tag.js

tag.js

401 ms

js

js

66 ms

analytics.js

analytics.js

27 ms

destination

destination

231 ms

_1.jpg

_1.jpg

6225 ms

collect

collect

169 ms

collect

collect

245 ms

ga-audiences

ga-audiences

84 ms

_1.png

_1.png

5364 ms

_1.png

_1.png

5767 ms

_1.png

_1.png

5869 ms

_1.png

_1.png

5876 ms

_1.png

_1.png

5932 ms

1.png

1.png

7547 ms

2.png

2.png

6322 ms

_1.gif

_1.gif

4494 ms

_1.gif

_1.gif

4339 ms

bh_top_mainright_info.gif

bh_top_mainright_info.gif

4293 ms

img_com_footer_logo.gif

img_com_footer_logo.gif

4169 ms

img_com_footer_contact.gif

img_com_footer_contact.gif

4471 ms

footer_categoryL01.gif

footer_categoryL01.gif

4463 ms

footer_categoryL01-s04.gif

footer_categoryL01-s04.gif

4348 ms

footer_categoryL01-s02.gif

footer_categoryL01-s02.gif

4172 ms

footer_categoryL01-s01.gif

footer_categoryL01-s01.gif

4389 ms

footer_categoryL02.gif

footer_categoryL02.gif

4347 ms

footer_categoryL02-s01.gif

footer_categoryL02-s01.gif

4244 ms

footer_categoryL02-s03.gif

footer_categoryL02-s03.gif

4261 ms

footer_categoryL02-s02.gif

footer_categoryL02-s02.gif

4173 ms

footer_categoryL03.gif

footer_categoryL03.gif

4027 ms

footer_categoryL01-s03.gif

footer_categoryL01-s03.gif

4044 ms

sprite_top-tab.png

sprite_top-tab.png

4014 ms

bg_tabcontents.png

bg_tabcontents.png

4050 ms

img_topsk-logo01.png

img_topsk-logo01.png

4174 ms

bg_top_summy.png

bg_top_summy.png

4086 ms

bg_top-summy-h3.png

bg_top-summy-h3.png

3823 ms

icon_linlk00.gif

icon_linlk00.gif

3850 ms

img_top_mainright_ginsen.gif

img_top_mainright_ginsen.gif

3656 ms

img_top_mainright_carrot.gif

img_top_mainright_carrot.gif

3671 ms

img_top_mainright_worm.gif

img_top_mainright_worm.gif

3833 ms

img_top_mainright_bee.gif

img_top_mainright_bee.gif

3589 ms

img_top_mainright_seberianginsen.gif

img_top_mainright_seberianginsen.gif

3552 ms

img_top_mainright_tian.gif

img_top_mainright_tian.gif

3576 ms

img_top_mainright_desertcarrot.gif

img_top_mainright_desertcarrot.gif

3507 ms

img_top_mainright_silkworm.gif

img_top_mainright_silkworm.gif

3379 ms

img_top_mainright_blackant.gif

img_top_mainright_blackant.gif

3422 ms

img_top_mainright_leech.gif

img_top_mainright_leech.gif

3554 ms

img_top_mainright_sugata.png

img_top_mainright_sugata.png

3696 ms

btn_com_footer_pagetop.gif

btn_com_footer_pagetop.gif

3564 ms

bg_footer.gif

bg_footer.gif

3513 ms

icon_footer-list01.gif

icon_footer-list01.gif

3174 ms

icon_list_news.gif

icon_list_news.gif

3328 ms

icon_link_news.gif

icon_link_news.gif

3512 ms

gnav_com_globalnavi_monozukuri_o.gif

gnav_com_globalnavi_monozukuri_o.gif

3485 ms

gnav_com_globalnavi_yojo_o.gif

gnav_com_globalnavi_yojo_o.gif

3136 ms

print.css

print.css

254 ms

Accessibility Review

ebiya.ne.jp accessibility score

95

Accessibility Issues

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

ebiya.ne.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

ebiya.ne.jp SEO score

95

Search Engine Optimization Advices

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ebiya.ne.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 Ebiya.ne.jp 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

ebiya.ne.jp

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