Tools & Wizards About Us
yoroi.co.jp screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

yoroi.co.jp

甲冑工房丸武産業｜鹿児島県

Page Load Speed

13.5 sec in total

First Response

1.6 sec

Resources Loaded

11.2 sec

Page Rendered

786 ms

yoroi.co.jp screenshot

About Website

Click here to check amazing Yoroi content for Japan. Otherwise, check out these important facts you probably never knew about yoroi.co.jp

鹿児島県薩摩川内市、丸武産業では、実際に武将達が戦で着用した本物の鎧兜の設計どおりに熟練の当職人により、丹精込めて細部に至るまで忠実に再現しています。ドラマ・映画等の着用甲冑の製造、博物館・資料館等の鎧修理・複製なども手掛けております。

Visit yoroi.co.jp

Key Findings

We analyzed Yoroi.co.jp page load time and found that the first response time was 1.6 sec and then it took 11.9 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

yoroi.co.jp performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.659

8/100

15%

TTI (Time to Interactive)

Value20.1 s

2/100

10%

Network Requests Diagram

yoroi.co.jp

1571 ms

style.css

689 ms

jquery.min.js

31 ms

jquery.fullwidthslider.1.0.js

354 ms

imgover.js

363 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 96% of them (78 requests) were addressed to the original Yoroi.co.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Yoroi.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.8 kB (2%)

Content Size

5.9 MB

After Optimization

5.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yoroi.co.jp main page is 5.9 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. 40% of websites need less resources to load. Images take 5.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 18.8 kB

  • Original 24.7 kB
  • After minification 23.1 kB
  • After compression 5.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 18.8 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 390 B

  • Original 5.7 MB
  • After minification 5.7 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. Yoroi images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 95.5 kB

  • Original 158.8 kB
  • After minification 146.2 kB
  • After compression 63.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 95.5 kB or 60% of the original size.

CSS Optimization

-80%

Potential reduce by 16.0 kB

  • Original 19.9 kB
  • After minification 13.7 kB
  • After compression 3.9 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. Yoroi.co.jp needs all CSS files to be minified and compressed as it can save up to 16.0 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

78

After Optimization

68

  • Images
  • JavaScript
  • CSS

The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yoroi. 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

yoroi.co.jp

yoroi.co.jp

1571 ms

style.css

style.css

689 ms

jquery.min.js

jquery.min.js

31 ms

jquery.fullwidthslider.1.0.js

jquery.fullwidthslider.1.0.js

354 ms

imgover.js

imgover.js

363 ms

styles.css

styles.css

365 ms

slimbox2.css

slimbox2.css

368 ms

jquery.js

jquery.js

1357 ms

jquery-migrate.min.js

jquery-migrate.min.js

706 ms

slimbox2.js

slimbox2.js

542 ms

slimbox2_autoload.js

slimbox2_autoload.js

543 ms

scroll.js

scroll.js

219 ms

jquery.form.js

jquery.form.js

753 ms

scripts.js

scripts.js

572 ms

ga.js

ga.js

29 ms

bg_cn.jpg

bg_cn.jpg

172 ms

mainImage.jpg

mainImage.jpg

2562 ms

mainImage2.jpg

mainImage2.jpg

2914 ms

mainImage3.jpg

mainImage3.jpg

2366 ms

mainImage4.jpg

mainImage4.jpg

2698 ms

mainImage5.jpg

mainImage5.jpg

2310 ms

mainnav_6.jpg

mainnav_6.jpg

511 ms

mainnav_5.jpg

mainnav_5.jpg

852 ms

mainnav_4.jpg

mainnav_4.jpg

1194 ms

mainnav_3.jpg

mainnav_3.jpg

1535 ms

mainnav_2.jpg

mainnav_2.jpg

1875 ms

mainnav_1.jpg

mainnav_1.jpg

2216 ms

logo.jpg

logo.jpg

2560 ms

bannerS1.jpg

bannerS1.jpg

2967 ms

bannerS2.jpg

bannerS2.jpg

3269 ms

bannerS3.jpg

bannerS3.jpg

2740 ms

bannerS4.jpg

bannerS4.jpg

3586 ms

bannerS5.jpg

bannerS5.jpg

3425 ms

bannerS6.jpg

bannerS6.jpg

3824 ms

top_ttl1.jpg

top_ttl1.jpg

3093 ms

top_ttl2.jpg

top_ttl2.jpg

3791 ms

IMG_2351-90x90.jpg

IMG_2351-90x90.jpg

3274 ms

defort.jpg

defort.jpg

3449 ms

bannerM1.jpg

bannerM1.jpg

3636 ms

bannerM2.jpg

bannerM2.jpg

4319 ms

bannerM3.jpg

bannerM3.jpg

4536 ms

bannerL2.jpg

bannerL2.jpg

4819 ms

bannerL1.jpg

bannerL1.jpg

4906 ms

bannerSS1.jpg

bannerSS1.jpg

4450 ms

bannerSS2.jpg

bannerSS2.jpg

4670 ms

bannerSS3.jpg

bannerSS3.jpg

5038 ms

bannerSS4.jpg

bannerSS4.jpg

4945 ms

footer_logo.gif

footer_logo.gif

4992 ms

footer_tel.gif

footer_tel.gif

4858 ms

footer_inq.gif

footer_inq.gif

5000 ms

footer_odr.gif

footer_odr.gif

5216 ms

__utm.gif

__utm.gif

11 ms

footer_bnr.gif

footer_bnr.gif

5083 ms

h_bg.jpg

h_bg.jpg

4606 ms

bullet2.gif

bullet2.gif

4928 ms

image

image

4598 ms

bg.png

bg.png

3691 ms

mainnav_6_o.jpg

mainnav_6_o.jpg

198 ms

mainnav_5_o.jpg

mainnav_5_o.jpg

383 ms

mainnav_4_o.jpg

mainnav_4_o.jpg

348 ms

mainnav_3_o.jpg

mainnav_3_o.jpg

371 ms

mainnav_2_o.jpg

mainnav_2_o.jpg

367 ms

mainnav_1_o.jpg

mainnav_1_o.jpg

336 ms

bannerS1_o.jpg

bannerS1_o.jpg

1101 ms

bannerS2_o.jpg

bannerS2_o.jpg

1491 ms

bannerS3_o.jpg

bannerS3_o.jpg

1200 ms

bannerS4_o.jpg

bannerS4_o.jpg

1087 ms

bannerS5_o.jpg

bannerS5_o.jpg

1276 ms

bannerS6_o.jpg

bannerS6_o.jpg

1506 ms

bannerM1_o.jpg

bannerM1_o.jpg

2169 ms

bannerM2_o.jpg

bannerM2_o.jpg

2194 ms

bannerM3_o.jpg

bannerM3_o.jpg

1542 ms

bannerL2_o.jpg

bannerL2_o.jpg

2551 ms

bannerL1_o.jpg

bannerL1_o.jpg

2733 ms

bannerSS1_o.jpg

bannerSS1_o.jpg

1693 ms

bannerSS2_o.jpg

bannerSS2_o.jpg

1714 ms

bannerSS3_o.jpg

bannerSS3_o.jpg

2444 ms

bannerSS4_o.jpg

bannerSS4_o.jpg

1885 ms

footer_inq_o.gif

footer_inq_o.gif

2056 ms

footer_odr_o.gif

footer_odr_o.gif

2228 ms

footer_bnr_o.gif

footer_bnr_o.gif

2626 ms

Accessibility Review

yoroi.co.jp accessibility score

74

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

yoroi.co.jp best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

yoroi.co.jp SEO score

69

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

Image elements do not have [alt] attributes

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 Yoroi.co.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 Yoroi.co.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

yoroi.co.jp

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