Tools & Wizards About Us
shushi.jp screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    55% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

shushi.jp

Shushi Kato officialsite | 人材育成家・慈善活動家 加藤秀視オフィシャルサイト

Page Load Speed

4.3 sec in total

First Response

1.3 sec

Resources Loaded

2.8 sec

Page Rendered

297 ms

shushi.jp screenshot

About Website

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

人材育成家・慈善活動家の加藤秀視オフィシャルサイト。クライアントはトップアスリートから芸能関係、上場企業、非行少年まで、手がける対象は多岐に渡る。著書『自分を愛する技術』は発売2ヶ月で10万部を超えるベストセラーに。他、著書多数。

Visit shushi.jp

Key Findings

We analyzed Shushi.jp page load time and found that the first response time was 1.3 sec and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

shushi.jp performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.374

28/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

shushi.jp

1272 ms

layout.css

499 ms

top.css

349 ms

jquery.min.js

1052 ms

jquery.easing.compatibility.js

354 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 79% of them (23 requests) were addressed to the original Shushi.jp, 7% (2 requests) were made to Google-analytics.com and 7% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Shushi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 129.8 kB (19%)

Content Size

680.9 kB

After Optimization

551.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Shushi.jp main page is 680.9 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 515.0 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 17.0 kB

  • Original 23.4 kB
  • After minification 22.6 kB
  • After compression 6.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. 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 17.0 kB or 73% of the original size.

Image Optimization

-6%

Potential reduce by 32.6 kB

  • Original 515.0 kB
  • After minification 482.4 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. Shushi images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 73.8 kB

  • Original 134.1 kB
  • After minification 131.1 kB
  • After compression 60.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 73.8 kB or 55% of the original size.

CSS Optimization

-76%

Potential reduce by 6.3 kB

  • Original 8.4 kB
  • After minification 7.2 kB
  • After compression 2.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. Shushi.jp needs all CSS files to be minified and compressed as it can save up to 6.3 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (18%)

Requests Now

28

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shushi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

shushi.jp

shushi.jp

1272 ms

layout.css

layout.css

499 ms

top.css

top.css

349 ms

jquery.min.js

jquery.min.js

1052 ms

jquery.easing.compatibility.js

jquery.easing.compatibility.js

354 ms

jquery.smoothScroll.js

jquery.smoothScroll.js

728 ms

main.js

main.js

475 ms

logo.png

logo.png

738 ms

bt-nav.png

bt-nav.png

573 ms

title-top.png

title-top.png

680 ms

lead-top.png

lead-top.png

528 ms

top.jpg

top.jpg

1361 ms

h4-feature.png

h4-feature.png

748 ms

h2_seminar.png

h2_seminar.png

775 ms

lead_seminar.png

lead_seminar.png

848 ms

h2_selflove.png

h2_selflove.png

882 ms

cover.png

cover.png

1601 ms

lead_selflove.png

lead_selflove.png

955 ms

h2-news.png

h2-news.png

990 ms

h2-blog.png

h2-blog.png

1056 ms

h2-facebook.png

h2-facebook.png

1061 ms

h2-mailseminar.png

h2-mailseminar.png

1118 ms

sdk.js

sdk.js

162 ms

mailseminar.jpg

mailseminar.jpg

591 ms

analytics.js

analytics.js

14 ms

collect

collect

14 ms

45 ms

xd_arbiter.php

xd_arbiter.php

149 ms

xd_arbiter.php

xd_arbiter.php

263 ms

Accessibility Review

shushi.jp accessibility score

71

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

shushi.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

High

Page has valid source maps

SEO Factors

shushi.jp SEO score

85

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

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 Shushi.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 Shushi.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

shushi.jp

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