Tools & Wizards About Us
kyoto-hokenkai.or.jp screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

kyoto-hokenkai.or.jp

公益社団法人京都保健会

Page Load Speed

6.1 sec in total

First Response

594 ms

Resources Loaded

5.3 sec

Page Rendered

206 ms

kyoto-hokenkai.or.jp screenshot

About Website

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

京都保健会は、1956年3月20日に設立し、府内広域に３病院１４診療所（歯科併設２）他に訪問看護ステーション・ヘルパーステーション等の介護施設、看護専門学校を含め３７事業所を運営する公益社団法人です。

Visit kyoto-hokenkai.or.jp

Key Findings

We analyzed Kyoto-hokenkai.or.jp page load time and found that the first response time was 594 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

kyoto-hokenkai.or.jp performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

kyoto-hokenkai.or.jp

594 ms

kyoto-hokenkai.or.jp

888 ms

main.css

175 ms

top.htm

371 ms

menu.htm

539 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 76% of them (64 requests) were addressed to the original Kyoto-hokenkai.or.jp, 21% (18 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Kyoto-hokenkai.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 181.6 kB (24%)

Content Size

752.4 kB

After Optimization

570.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kyoto-hokenkai.or.jp main page is 752.4 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. 65% of websites need less resources to load. Images take 535.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 18.7 kB

  • Original 23.2 kB
  • After minification 17.4 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 5.8 kB, which is 25% 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 18.7 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 22.4 kB

  • Original 535.2 kB
  • After minification 512.7 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. Kyoto Hokenkai images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 110.4 kB

  • Original 159.8 kB
  • After minification 155.3 kB
  • After compression 49.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 110.4 kB or 69% of the original size.

CSS Optimization

-88%

Potential reduce by 30.0 kB

  • Original 34.2 kB
  • After minification 29.4 kB
  • After compression 4.3 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. Kyoto-hokenkai.or.jp needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (28%)

Requests Now

82

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kyoto-hokenkai.or.jp

kyoto-hokenkai.or.jp

594 ms

kyoto-hokenkai.or.jp

kyoto-hokenkai.or.jp

888 ms

main.css

main.css

175 ms

top.htm

top.htm

371 ms

menu.htm

menu.htm

539 ms

show_202101.htm

show_202101.htm

541 ms

menu_2.htm

menu_2.htm

710 ms

info.htm

info.htm

716 ms

top2.gif

top2.gif

842 ms

bn50-2.gif

bn50-2.gif

878 ms

helper.gif

helper.gif

885 ms

fukusi.gif

fukusi.gif

1019 ms

free_no2.gif

free_no2.gif

1033 ms

top1.gif

top1.gif

1050 ms

banner.gif

banner.gif

1058 ms

sdgs1.png

sdgs1.png

1370 ms

free_no.gif

free_no.gif

1214 ms

bn01.gif

bn01.gif

1220 ms

bn03.gif

bn03.gif

1231 ms

bn04.gif

bn04.gif

1397 ms

bn02.gif

bn02.gif

1392 ms

bn05.jpg

bn05.jpg

1405 ms

bn08.gif

bn08.gif

1484 ms

bn09.gif

bn09.gif

1546 ms

bn13.jpg

bn13.jpg

1562 ms

bn14-2.png

bn14-2.png

1579 ms

bn15.png

bn15.png

1577 ms

bn47.gif

bn47.gif

1671 ms

bn48.gif

bn48.gif

1723 ms

bn45.jpg

bn45.jpg

1733 ms

bn43.jpg

bn43.jpg

1750 ms

bn53.png

bn53.png

1761 ms

bn54.png

bn54.png

1859 ms

bn52.gif

bn52.gif

1898 ms

bn12.gif

bn12.gif

1904 ms

shmwl2.gif

shmwl2.gif

1923 ms

poster2022_0.png

poster2022_0.png

2126 ms

widgets.js

widgets.js

13 ms

footer.htm

footer.htm

2049 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

18 ms

settings

settings

100 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

3 ms

kyoto_hokenkai

kyoto_hokenkai

100 ms

kifu.png

kifu.png

2064 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

4 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

32 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

37 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

35 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

34 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

67 ms

_buildManifest.js

_buildManifest.js

36 ms

_ssgManifest.js

_ssgManifest.js

78 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

18 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

15 ms

shmwl.gif

shmwl.gif

1709 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

4 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

8 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

7 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

21 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

6 ms

menu.css

menu.css

1541 ms

camera.css

camera.css

1561 ms

jquery.min.js

jquery.min.js

1926 ms

jquery.mobile.customized.min.js

jquery.mobile.customized.min.js

1542 ms

camera.min.js

camera.min.js

1578 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1395 ms

poster.jpg

poster.jpg

1427 ms

min1.gif

min1.gif

1408 ms

min2.gif

min2.gif

1399 ms

olive2.png

olive2.png

1398 ms

mutei_banner02.gif

mutei_banner02.gif

1437 ms

top2.gif

top2.gif

1376 ms

logo.png

logo.png

1394 ms

logo2.png

logo2.png

1377 ms

home.gif

home.gif

1249 ms

mail.gif

mail.gif

1285 ms

new.gif

new.gif

1366 ms

footer.css

footer.css

734 ms

miniren.png

miniren.png

751 ms

bb03.gif

bb03.gif

712 ms

camera-loader.gif

camera-loader.gif

191 ms

00.png

00.png

563 ms

01.jpg

01.jpg

524 ms

blank.gif

blank.gif

189 ms

Accessibility Review

kyoto-hokenkai.or.jp accessibility score

64

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

kyoto-hokenkai.or.jp best practices score

75

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

SEO Factors

kyoto-hokenkai.or.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 Kyoto-hokenkai.or.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 Kyoto-hokenkai.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

kyoto-hokenkai.or.jp

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