8.2 sec in total
1.5 sec
6.2 sec
397 ms
Visit eijinkai.or.jp now to see the best up-to-date Eijinkai content for Japan and also check out these interesting facts you probably never knew about eijinkai.or.jp
栄仁会 宇治おうばく病院のHPです。精神科・心療内科・リハビリテーション科・内科などの専門診療とともに、うつ病や統合失調症、認知症(もの忘れ・痴呆疾患)の治療に早くから取り組み、カウンセリングセンターも併設しています。
Visit eijinkai.or.jpWe analyzed Eijinkai.or.jp page load time and found that the first response time was 1.5 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
eijinkai.or.jp performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value19.4 s
0/100
25%
Value7.7 s
25/100
10%
Value130 ms
96/100
30%
Value0.518
15/100
15%
Value11.6 s
18/100
10%
1505 ms
1043 ms
64 ms
170 ms
675 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 82% of them (64 requests) were addressed to the original Eijinkai.or.jp, 9% (7 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Eijinkai.or.jp.
Page size can be reduced by 160.0 kB (6%)
2.7 MB
2.5 MB
In fact, the total size of Eijinkai.or.jp main page is 2.7 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. 45% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 19.0 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 2.6 kB, which is 11% 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 19.0 kB or 78% of the original size.
Potential reduce by 652 B
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. Eijinkai images are well optimized though.
Potential reduce by 96.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 96.6 kB or 57% of the original size.
Potential reduce by 43.8 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. Eijinkai.or.jp needs all CSS files to be minified and compressed as it can save up to 43.8 kB or 85% of the original size.
Number of requests can be reduced by 32 (47%)
68
36
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eijinkai. 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 4 to 1 for CSS and as a result speed up the page load time.
eijinkai.or.jp
1505 ms
www.eijinkai.or.jp
1043 ms
gtm.js
64 ms
slick.css
170 ms
common.css
675 ms
home.css
494 ms
jquery.1.8.3.min.js
1159 ms
slick.min.js
834 ms
jquery-auto-height.js
514 ms
script.js
516 ms
mv_season01_pc.jpg
2109 ms
mv_01_pc.jpg
1195 ms
mv_02_pc.jpg
1532 ms
mv_season02_pc.jpg
1891 ms
card_01_pc.jpg
1330 ms
card_02_pc.jpg
1488 ms
card_03_pc.jpg
1532 ms
card_04_pc.jpg
1662 ms
card_05_pc.jpg
1818 ms
card_06_pc.jpg
1867 ms
card_07_pc.jpg
1701 ms
card_08_pc.jpg
1828 ms
card_09_pc.jpg
2038 ms
card_10_pc.jpg
1983 ms
notosansjapanese.css
27 ms
subject_1.png
1295 ms
subject_2.png
1336 ms
subject_3.png
1359 ms
subject_4.png
1449 ms
subject_5.png
1462 ms
card_arrow.png
1504 ms
bg_news.jpg
1508 ms
news_arrow.png
1528 ms
btn-1_arrow.png
1568 ms
NotoSansJP-Bold.woff
32 ms
NotoSansJP-Black.woff
71 ms
NotoSansJP-Medium.woff
106 ms
NotoSansJP-Regular.woff
109 ms
NotoSansJP-DemiLight.woff
109 ms
NotoSansJP-Light.woff
108 ms
NotoSansJP-Thin.woff
106 ms
analytics.js
33 ms
header.html
1129 ms
footer.html
1149 ms
info.php
1332 ms
info.php
1365 ms
arrow_left.png
1205 ms
arrow_right.png
1237 ms
collect
12 ms
brand
29 ms
logo.png
167 ms
close.png
177 ms
access.png
248 ms
sitemap.png
271 ms
contact.png
331 ms
recruit.png
342 ms
search.png
367 ms
navidial.png
402 ms
hamburger.png
416 ms
about.png
430 ms
outpatient.png
495 ms
hospitalization.png
506 ms
rehabilitation.png
535 ms
home_service.png
570 ms
group.png
583 ms
icon_contact.png
590 ms
bnr5.jpg
643 ms
bnr6.jpg
654 ms
bnr_01.jpg
686 ms
bnr_02.jpg
722 ms
bnr_03.jpg
737 ms
bnr_04.jpg
735 ms
bnr_contact.jpg
809 ms
bnr_netanswer2023.jpg
820 ms
building.jpg
1356 ms
totop.png
890 ms
brandjs.js
15 ms
branding.png
4 ms
eijinkai.or.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eijinkai.or.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
eijinkai.or.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Eijinkai.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 Eijinkai.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.
eijinkai.or.jp
Open Graph description is not detected on the main page of Eijinkai. 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: