Tools & Wizards About Us
yamatokai.or.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

yamatokai.or.jp

【公式】社会医療法人財団大和会 ウェブサイト

Page Load Speed

6.7 sec in total

First Response

598 ms

Resources Loaded

5.5 sec

Page Rendered

670 ms

yamatokai.or.jp screenshot

About Website

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

東大和市、武蔵村山市を中心に高度先進医療から介護・在宅サービスをシームレスに提供する社会医療法人です。東大和病院／武蔵村山病院／東大和病院附属セントラルクリニック／東大和ケアセンター／在宅サポートセンター

Visit yamatokai.or.jp

Key Findings

We analyzed Yamatokai.or.jp page load time and found that the first response time was 598 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

yamatokai.or.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value27.0 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.189

65/100

15%

TTI (Time to Interactive)

Value20.3 s

2/100

10%

Network Requests Diagram

yamatokai.or.jp

598 ms

www.yamatokai.or.jp

1020 ms

gtm.js

66 ms

style.css

188 ms

roundmenu_3.css

374 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 83% of them (65 requests) were addressed to the original Yamatokai.or.jp, 4% (3 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Yamatokai.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (14%)

Content Size

14.4 MB

After Optimization

12.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yamatokai.or.jp main page is 14.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 14.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 29.1 kB

  • Original 37.4 kB
  • After minification 32.5 kB
  • After compression 8.3 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 4.8 kB, which is 13% 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 29.1 kB or 78% of the original size.

Image Optimization

-14%

Potential reduce by 1.9 MB

  • Original 14.0 MB
  • After minification 12.1 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. Obviously, Yamatokai needs image optimization as it can save up to 1.9 MB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-27%

Potential reduce by 79.9 kB

  • Original 297.7 kB
  • After minification 297.3 kB
  • After compression 217.8 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 79.9 kB or 27% of the original size.

CSS Optimization

-30%

Potential reduce by 22.2 kB

  • Original 74.1 kB
  • After minification 74.1 kB
  • After compression 51.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. Yamatokai.or.jp needs all CSS files to be minified and compressed as it can save up to 22.2 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (42%)

Requests Now

69

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yamatokai.or.jp

yamatokai.or.jp

598 ms

www.yamatokai.or.jp

www.yamatokai.or.jp

1020 ms

gtm.js

gtm.js

66 ms

style.css

style.css

188 ms

roundmenu_3.css

roundmenu_3.css

374 ms

swiper-bundle.min.css

swiper-bundle.min.css

523 ms

copy.png

copy.png

878 ms

hy.png

hy.png

1485 ms

cc.png

cc.png

1114 ms

mm.png

mm.png

1496 ms

care.png

care.png

1723 ms

support.png

support.png

1561 ms

require.js

require.js

1052 ms

jsapi

jsapi

20 ms

jspreadsheet.js

jspreadsheet.js

1227 ms

whatsnew-column.js

whatsnew-column.js

1299 ms

swiper-bundle.min.js

swiper-bundle.min.js

1405 ms

parallax.min.js

parallax.min.js

1485 ms

Notification.min.js

Notification.min.js

1581 ms

greeting_sp.png

greeting_sp.png

1670 ms

magazine.png

magazine.png

1672 ms

yearsbook.png

yearsbook.png

1680 ms

lecture02.png

lecture02.png

1734 ms

interview.png

interview.png

1756 ms

loader.js

loader.js

24 ms

bootstrap.css

bootstrap.css

1678 ms

all.css

all.css

1685 ms

animate.min.css

animate.min.css

1688 ms

css2

css2

30 ms

odometer.css

odometer.css

1731 ms

base.css

base.css

1728 ms

parts.css

parts.css

1750 ms

jquery-3.5.1.js

jquery-3.5.1.js

194 ms

bootstrap.js

bootstrap.js

177 ms

fontawesome.js

fontawesome.js

188 ms

jquery.easeScroll.js

jquery.easeScroll.js

188 ms

smooth_scroll.js

smooth_scroll.js

176 ms

wow.min.js

wow.min.js

219 ms

odometer.min.js

odometer.min.js

352 ms

fade_loading.js

fade_loading.js

352 ms

googleAnalytics.js

googleAnalytics.js

374 ms

js

js

133 ms

tq

tq

256 ms

sky.png

sky.png

748 ms

menu_include.html

menu_include.html

230 ms

recruit_include.html

recruit_include.html

238 ms

footer_column.html

footer_column.html

241 ms

footer.html

footer.html

234 ms

img04.png

img04.png

400 ms

img06_2.png

img06_2.png

1058 ms

img05.png

img05.png

1232 ms

img07_2.png

img07_2.png

947 ms

img03.png

img03.png

569 ms

recruit.jpg

recruit.jpg

594 ms

greeting_pc.png

greeting_pc.png

758 ms

pxiFyp4_v8FCjlI4NLr8f1s.ttf

pxiFyp4_v8FCjlI4NLr8f1s.ttf

291 ms

fa-solid-900.woff

fa-solid-900.woff

675 ms

fa-regular-400.woff

fa-regular-400.woff

826 ms

js

js

58 ms

tqpub

tqpub

318 ms

footer_logo.png

footer_logo.png

720 ms

70th_header_logo_trans.png

70th_header_logo_trans.png

749 ms

facility01.png

facility01.png

884 ms

facility02.png

facility02.png

894 ms

facility03.png

facility03.png

902 ms

facility04.png

facility04.png

942 ms

facility05.png

facility05.png

1001 ms

facility06.png

facility06.png

1071 ms

vertical_logo.png

vertical_logo.png

1080 ms

21632269.js

21632269.js

216 ms

head_office_s.png

head_office_s.png

1085 ms

analytics.js

analytics.js

59 ms

01.png

01.png

1012 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOubAILO5wSiX.ttf

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOubAILO5wSiX.ttf

565 ms

collect

collect

14 ms

ycover.png

ycover.png

861 ms

prcover.png

prcover.png

861 ms

news.png

news.png

942 ms

Accessibility Review

yamatokai.or.jp accessibility score

86

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

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

yamatokai.or.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Page has valid source maps

SEO Factors

yamatokai.or.jp SEO score

92

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

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

    JP

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yamatokai.or.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed language. Our system also found out that Yamatokai.or.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

yamatokai.or.jp

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