Tools & Wizards About Us
yamato.tokyo.jp screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

yamato.tokyo.jp

清水義久先生の気功ヒーリングセミナー

Page Load Speed

5.2 sec in total

First Response

534 ms

Resources Loaded

4.1 sec

Page Rendered

603 ms

yamato.tokyo.jp screenshot

About Website

Click here to check amazing Yamato content for Japan. Otherwise, check out these important facts you probably never knew about yamato.tokyo.jp

清水義久先生の気功ヒーリングセミナーサイトです。

Visit yamato.tokyo.jp

Key Findings

We analyzed Yamato.tokyo.jp page load time and found that the first response time was 534 ms and then it took 4.7 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

yamato.tokyo.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.793

5/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

yamato.tokyo.jp

534 ms

www.yamato.tokyo.jp

887 ms

default.css

174 ms

design.css

346 ms

jquery.min.js

35 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 66% of them (53 requests) were addressed to the original Yamato.tokyo.jp, 23% (18 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Yamato.tokyo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.9 kB (7%)

Content Size

398.2 kB

After Optimization

371.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yamato.tokyo.jp main page is 398.2 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. 70% of websites need less resources to load. Images take 315.3 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 13.5 kB

  • Original 21.1 kB
  • After minification 19.2 kB
  • After compression 7.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. 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 13.5 kB or 64% of the original size.

Image Optimization

-3%

Potential reduce by 10.5 kB

  • Original 315.3 kB
  • After minification 304.8 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. Yamato images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 50.4 kB
  • After minification 50.4 kB
  • After compression 50.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. This website has mostly compressed JavaScripts.

CSS Optimization

-25%

Potential reduce by 2.8 kB

  • Original 11.5 kB
  • After minification 11.3 kB
  • After compression 8.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. Yamato.tokyo.jp needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (46%)

Requests Now

78

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yamato.tokyo.jp

yamato.tokyo.jp

534 ms

www.yamato.tokyo.jp

www.yamato.tokyo.jp

887 ms

default.css

default.css

174 ms

design.css

design.css

346 ms

jquery.min.js

jquery.min.js

35 ms

conversion.js

conversion.js

113 ms

analytics.js

analytics.js

209 ms

type-top

type-top

783 ms

header.png

header.png

363 ms

logo.png

logo.png

600 ms

link01.png

link01.png

803 ms

link02.png

link02.png

659 ms

home.jpg

home.jpg

1180 ms

home.png

home.png

659 ms

seminar.png

seminar.png

738 ms

textbook.png

textbook.png

822 ms

voice.png

voice.png

825 ms

teacher.png

teacher.png

907 ms

mail-magazine.png

mail-magazine.png

947 ms

articleArea.png

articleArea.png

973 ms

point01.png

point01.png

998 ms

line01.png

line01.png

1002 ms

mail-mag.png

mail-mag.png

1114 ms

text12.png

text12.png

1150 ms

text11.png

text11.png

1148 ms

pdf.png

pdf.png

1175 ms

text01.png

text01.png

1181 ms

button.png

button.png

1294 ms

p1.jpg

p1.jpg

1507 ms

p2.jpg

p2.jpg

1490 ms

p3.jpg

p3.jpg

1528 ms

h2.png

h2.png

1353 ms

crown.png

crown.png

1358 ms

text01.png

text01.png

1475 ms

img01.jpg

img01.jpg

1534 ms

no01.png

no01.png

1538 ms

text02.png

text02.png

1666 ms

img02.jpg

img02.jpg

1661 ms

no02.png

no02.png

1677 ms

text03.png

text03.png

1704 ms

new.png

new.png

1712 ms

text04.png

text04.png

1715 ms

widgets.js

widgets.js

95 ms

text05.png

text05.png

1733 ms

72 ms

collect

collect

36 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

43 ms

js

js

89 ms

62 ms

settings

settings

108 ms

text06.png

text06.png

1493 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

5 ms

shimizuyo_bot

shimizuyo_bot

55 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

14 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

51 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

57 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

54 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

106 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

113 ms

_buildManifest.js

_buildManifest.js

106 ms

_ssgManifest.js

_ssgManifest.js

133 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

22 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

22 ms

text07.png

text07.png

1225 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

8 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

16 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

16 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

18 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

15 ms

book.png

book.png

1233 ms

text08.png

text08.png

1237 ms

button01.png

button01.png

1333 ms

design.css

design.css

1236 ms

new.css

new.css

1242 ms

tw.png

tw.png

1217 ms

text09.png

text09.png

1244 ms

footer.png

footer.png

1170 ms

arrow01.png

arrow01.png

1236 ms

arrow02.png

arrow02.png

1237 ms

arrow03.png

arrow03.png

183 ms

Accessibility Review

yamato.tokyo.jp accessibility score

77

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

Best Practices

yamato.tokyo.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

yamato.tokyo.jp SEO score

100

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

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 Yamato.tokyo.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 Yamato.tokyo.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

yamato.tokyo.jp

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