7 sec in total
825 ms
6.1 sec
137 ms
Visit kenkako.jp now to see the best up-to-date Kenkako content for Japan and also check out these interesting facts you probably never knew about kenkako.jp
兵庫県立加古川医療センターは28科353床を有する東播磨地域の中核病院です。
Visit kenkako.jpWe analyzed Kenkako.jp page load time and found that the first response time was 825 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
kenkako.jp performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value5.6 s
17/100
25%
Value7.7 s
24/100
10%
Value910 ms
31/100
30%
Value0.002
100/100
15%
Value11.5 s
18/100
10%
825 ms
635 ms
499 ms
515 ms
530 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that all of those requests were addressed to Kenkako.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Kenkako.jp.
Page size can be reduced by 178.2 kB (22%)
825.4 kB
647.2 kB
In fact, the total size of Kenkako.jp main page is 825.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. 35% of websites need less resources to load. Images take 611.9 kB which makes up the majority of the site volume.
Potential reduce by 16.2 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.6 kB, which is 27% 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 16.2 kB or 78% of the original size.
Potential reduce by 21.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. Kenkako images are well optimized though.
Potential reduce by 100.6 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 100.6 kB or 68% of the original size.
Potential reduce by 40.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. Kenkako.jp needs all CSS files to be minified and compressed as it can save up to 40.1 kB or 87% of the original size.
Number of requests can be reduced by 25 (33%)
76
51
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kenkako. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
kenkako.jp
825 ms
base.css
635 ms
base_a.css
499 ms
java_ro.js
515 ms
skitter.styles.css
530 ms
jquery-1.6.3.min.js
1268 ms
jquery.easing.1.3.js
469 ms
jquery.animate-colors-min.js
627 ms
jquery.skitter.min.js
994 ms
newmark.js
684 ms
styleswitcher.js
704 ms
mnb01_off.gif
161 ms
mnb01_on.gif
159 ms
mnb02_off.gif
214 ms
mnb02_onf.gif
239 ms
mnb03_off.gif
316 ms
mnb03_on.gif
319 ms
mnb04_off.gif
386 ms
mnb04_on.gif
414 ms
mnb05_off.gif
472 ms
mnb05_on.gif
477 ms
mnb06_off.gif
519 ms
mnb06_on.gif
555 ms
mnb07_off.gif
588 ms
mnb07_on.gif
652 ms
mnb08_off.gif
651 ms
mnb08_on.gif
684 ms
mnb09_off.gif
724 ms
mnb09_on.gif
762 ms
mnb10_off.gif
804 ms
mnb10_on.gif
783 ms
mnb11_off.gif
794 ms
mnb11_on.gif
851 ms
mnb12_off.gif
896 ms
mnb12_on.gif
937 ms
mnb13_off.gif
940 ms
mnb13_on.gif
953 ms
mnb14_off.gif
986 ms
mnb14_on.gif
1018 ms
mnb15_off.gif
1069 ms
mnb15_on.gif
1113 ms
mnb16_off.gif
1098 ms
mnb16_on.gif
1111 ms
mnb17_off.gif
1133 ms
mnb17_on.gif
1132 ms
mnb18_off.gif
1092 ms
mnb18_on.gif
1103 ms
mnb19_off.gif
1066 ms
mnb19_on.gif
1060 ms
mnb20_off.gif
1044 ms
mnb20_on.gif
1043 ms
mnb21_off.gif
1084 ms
mnb21_on.gif
1048 ms
mnb22_off.gif
1026 ms
mnb22_on.gif
1003 ms
mnb23_off.gif
1068 ms
mnb23_on.gif
1010 ms
mnb24_off.gif
1039 ms
mnb24_on.gif
1015 ms
mnb25_off.gif
948 ms
mnb25_on.gif
995 ms
mnb26_off.gif
1013 ms
mnb26_on.gif
1045 ms
mnb27_off.gif
1032 ms
mnb27_on.gif
996 ms
mnb28_off.gif
988 ms
mnb28_on.gif
1024 ms
mnb29_off.gif
1055 ms
mnb29_on.gif
1079 ms
mnb30_off.gif
1018 ms
mnb30_on.gif
980 ms
mnb31_off.gif
1001 ms
mnb31_on.gif
1047 ms
mnb32_off.gif
1041 ms
mnb32_on.gif
1053 ms
mnb33_off.gif
1008 ms
mnb33_on.gif
1121 ms
mnb34_off.gif
1002 ms
mnb34_on.gif
1062 ms
mnb35_off.gif
1025 ms
mnb35_on.gif
1150 ms
mnb36_off.gif
1099 ms
mnb36_on.gif
1031 ms
mnb37_off.gif
1080 ms
mnb37_on.gif
1185 ms
mnb38_off.gif
1156 ms
mnb38_on.gif
1104 ms
mnb39_off.gif
1172 ms
mnb39_on.gif
1176 ms
mnb40_off.gif
1097 ms
mnb40_on.gif
1162 ms
mnb41_off.gif
1226 ms
mnb41_on.gif
1152 ms
mnb42_off.gif
1119 ms
mnb42_on.gif
1261 ms
mnb43_off.gif
1166 ms
mnb43_on.gif
1160 ms
mnb44_off.gif
1185 ms
mnb44_on.gif
1268 ms
mnb45_off.gif
1162 ms
mnb45_on.gif
1273 ms
mnb46_off.gif
1206 ms
mnb46_on.gif
1194 ms
mnb47_off.gif
1316 ms
mnb47_on.gif
1275 ms
mnb48_off.gif
1233 ms
mnb48_on.gif
1345 ms
mnb49_off.gif
1232 ms
mnb49_on.gif
1303 ms
mnb50_off.gif
1294 ms
mnb50_on.gif
1363 ms
bana01.gif
1383 ms
spacer.gif
1247 ms
06.jpg
1796 ms
09.jpg
1846 ms
07.jpg
1779 ms
11.jpg
1408 ms
gnavnew01_off.png
1259 ms
gnavnew02_off.png
1406 ms
gnavnew03_off.png
1401 ms
gnavnew04_off.png
1405 ms
gnavnew05_off.png
1454 ms
gnavnew06_off.png
1403 ms
gnavnew07_off.png
1501 ms
gnavnew08_off.png
1473 ms
title_riyou.gif
1513 ms
title_iryokikan.gif
1517 ms
bana_mobile.gif
1478 ms
h2_osirase.gif
1492 ms
icon_new_l.gif
1451 ms
bana_renkei_yoyaku.gif
1467 ms
taitle_kyujin.gif
1495 ms
line02.gif
1468 ms
bana_jcqhc.gif
1466 ms
line01.gif
1449 ms
bg_submenu01.gif
1383 ms
bg_list_osirase.gif
1392 ms
bg_submenu03.gif
1467 ms
bg_footer.gif
1470 ms
prev.png
1364 ms
next.png
1346 ms
ajax-loader.gif
1361 ms
base_b.css
161 ms
base_c.css
161 ms
kenkako.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
kenkako.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
kenkako.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kenkako.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 Kenkako.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.
kenkako.jp
Open Graph description is not detected on the main page of Kenkako. 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: