Tools & Wizards About Us
e-sangyo.jp screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 63

    SEO

    Google-friendlier than
    24% of websites

e-sangyo.jp

ネオジウム磁石、強力磁石を全国対応で販売

Page Load Speed

5.3 sec in total

First Response

516 ms

Resources Loaded

4.4 sec

Page Rendered

417 ms

e-sangyo.jp screenshot

About Website

Visit e-sangyo.jp now to see the best up-to-date E Sangyo content for Japan and also check out these interesting facts you probably never knew about e-sangyo.jp

ネオジウム磁石を1個から買える株式会社サンギョウサプライです。強力磁石・ネオジウム磁石を全国対応で販売し、当日発送します。ご購入3,000円以上は送料無料の販売店です。大量在庫なので、ダイソーさんやホームセンターさんより便利です。

Visit e-sangyo.jp

Key Findings

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

Performance Metrics

e-sangyo.jp performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.096

91/100

15%

TTI (Time to Interactive)

Value18.3 s

3/100

10%

Network Requests Diagram

e-sangyo.jp

516 ms

www.e-sangyo.jp

684 ms

sps_common.css

171 ms

default.css

341 ms

jquery.min.js

18 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 95% of them (80 requests) were addressed to the original E-sangyo.jp, 1% (1 request) were made to Ajax.googleapis.com and 1% (1 request) were made to Cdn02.estore.jp. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Apay-up-banner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 124.5 kB (12%)

Content Size

1.1 MB

After Optimization

950.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-sangyo.jp main page is 1.1 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. 35% of websites need less resources to load. Images take 889.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 50.8 kB

  • Original 62.7 kB
  • After minification 60.0 kB
  • After compression 11.9 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 50.8 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 26.4 kB

  • Original 889.4 kB
  • After minification 863.0 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 Sangyo images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 42.2 kB

  • Original 100.6 kB
  • After minification 100.6 kB
  • After compression 58.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 42.2 kB or 42% of the original size.

CSS Optimization

-22%

Potential reduce by 5.0 kB

  • Original 22.7 kB
  • After minification 22.7 kB
  • After compression 17.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. E-sangyo.jp needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 22% of the original size.

Requests Breakdown

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

Requests Now

82

After Optimization

68

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e-sangyo.jp

e-sangyo.jp

516 ms

www.e-sangyo.jp

www.e-sangyo.jp

684 ms

sps_common.css

sps_common.css

171 ms

default.css

default.css

341 ms

jquery.min.js

jquery.min.js

18 ms

jquery.tile.js

jquery.tile.js

491 ms

jquery.distile.js

jquery.distile.js

496 ms

floating_menu.js

floating_menu.js

499 ms

pcsmpflg.js

pcsmpflg.js

511 ms

cal.js

cal.js

508 ms

estore_beacon.js

estore_beacon.js

30 ms

01_Amazon_Pay_BBP_728x90.png

01_Amazon_Pay_BBP_728x90.png

2117 ms

header_bg.gif

header_bg.gif

169 ms

logo01.png

logo01.png

168 ms

txt_tel01.png

txt_tel01.png

172 ms

gNavi01_off.jpg

gNavi01_off.jpg

168 ms

gNavi07_off.jpg

gNavi07_off.jpg

187 ms

gNavi05_off.jpg

gNavi05_off.jpg

170 ms

gNavi03_off.jpg

gNavi03_off.jpg

333 ms

gNavi02_off.jpg

gNavi02_off.jpg

334 ms

gNavi06_off.jpg

gNavi06_off.jpg

335 ms

maining01.png

maining01.png

997 ms

tit_main01.png

tit_main01.png

343 ms

txt_main01.png

txt_main01.png

364 ms

txt_main02.png

txt_main02.png

497 ms

img_main01.jpg

img_main01.jpg

501 ms

img_main02.jpg

img_main02.jpg

500 ms

img_main03.jpg

img_main03.jpg

515 ms

img_main04.jpg

img_main04.jpg

541 ms

img_main05.jpg

img_main05.jpg

661 ms

txt_main03.png

txt_main03.png

668 ms

txt_main04.png

txt_main04.png

666 ms

img_main06.jpg

img_main06.jpg

686 ms

img_main07.jpg

img_main07.jpg

719 ms

img_main08.jpg

img_main08.jpg

826 ms

tit_main02.png

tit_main02.png

833 ms

img_main09.jpg

img_main09.jpg

834 ms

img_main10.jpg

img_main10.jpg

858 ms

tit_main03.png

tit_main03.png

897 ms

txt_main05.png

txt_main05.png

990 ms

img_main11.jpg

img_main11.jpg

1001 ms

img_main12.jpg

img_main12.jpg

1000 ms

txt_main06.png

txt_main06.png

1028 ms

img_main13.jpg

img_main13.jpg

1074 ms

tit_main04.png

tit_main04.png

1167 ms

img_main14.jpg

img_main14.jpg

1168 ms

img_greeting01.jpg

img_greeting01.jpg

1169 ms

btn_side01.jpg

btn_side01.jpg

1168 ms

tag.js

tag.js

202 ms

btn_side06.jpg

btn_side06.jpg

1036 ms

btn_side02.jpg

btn_side02.jpg

1087 ms

tit_side01.png

tit_side01.png

1165 ms

btn_side03.jpg

btn_side03.jpg

1169 ms

btn_side04.jpg

btn_side04.jpg

1169 ms

btn_side05.jpg

btn_side05.jpg

1153 ms

tit_side02.png

tit_side02.png

1041 ms

tit_before01.png

tit_before01.png

1097 ms

stit_before01.png

stit_before01.png

1162 ms

img_credit01.png

img_credit01.png

1163 ms

stit_before02.png

stit_before02.png

1143 ms

stit_before03.png

stit_before03.png

1009 ms

stit_before04.png

stit_before04.png

1044 ms

stit_before05.png

stit_before05.png

1108 ms

stit_before06.png

stit_before06.png

1146 ms

img_before01.png

img_before01.png

1131 ms

stit_before07.png

stit_before07.png

1010 ms

stit_before08.png

stit_before08.png

1005 ms

pagetop.gif

pagetop.gif

1049 ms

bg_gNavi01.jpg

bg_gNavi01.jpg

1100 ms

gNavi01_on.jpg

gNavi01_on.jpg

1105 ms

gNavi07_on.jpg

gNavi07_on.jpg

1013 ms

gNavi05_on.jpg

gNavi05_on.jpg

1006 ms

gNavi03_on.jpg

gNavi03_on.jpg

1006 ms

gNavi02_on.jpg

gNavi02_on.jpg

1030 ms

gNavi06_on.jpg

gNavi06_on.jpg

1065 ms

tracking.php

tracking.php

1008 ms

bg_greeting01.jpg

bg_greeting01.jpg

1011 ms

bg_guide01.jpg

bg_guide01.jpg

1006 ms

bg_contact01.jpg

bg_contact01.jpg

1007 ms

BGline-scolumn.gif

BGline-scolumn.gif

1030 ms

Title-scolumn_calendar.gif

Title-scolumn_calendar.gif

1066 ms

calendar_pleft.gif

calendar_pleft.gif

1005 ms

calendar_pright.gif

calendar_pright.gif

1006 ms

pageTop_off.png

pageTop_off.png

1005 ms

Accessibility Review

e-sangyo.jp accessibility score

82

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

Image elements do not have [alt] attributes

Best Practices

e-sangyo.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

e-sangyo.jp SEO score

63

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 doesn't use 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 E-sangyo.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-sangyo.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

e-sangyo.jp

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