Tools & Wizards About Us
eijinkai.or.jp screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

eijinkai.or.jp

京都 宇治おうばく病院 精神科・心療内科（統合失調症・うつ病・認知症・カウンセリング） 内科（神経内科・糖尿病・リハビリ）専門治療にあたっています

Page Load Speed

6.2 sec in total

First Response

810 ms

Resources Loaded

5.2 sec

Page Rendered

206 ms

eijinkai.or.jp screenshot

About Website

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.jp

Key Findings

We analyzed Eijinkai.or.jp page load time and found that the first response time was 810 ms and then it took 5.4 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

eijinkai.or.jp performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.872

4/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

eijinkai.or.jp

810 ms

style.css

938 ms

font.css

378 ms

top.css

387 ms

jquery-1.8.3.min.js

1316 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 86% of them (49 requests) were addressed to the original Eijinkai.or.jp, 5% (3 requests) were made to Google.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Eijinkai.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 129.4 kB (25%)

Content Size

512.4 kB

After Optimization

383.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-69%

Potential reduce by 13.0 kB

  • Original 18.8 kB
  • After minification 16.7 kB
  • After compression 5.8 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.1 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 13.0 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 951 B

  • Original 293.2 kB
  • After minification 292.3 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. Eijinkai images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 74.1 kB

  • Original 152.0 kB
  • After minification 148.9 kB
  • After compression 77.9 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 74.1 kB or 49% of the original size.

CSS Optimization

-85%

Potential reduce by 41.4 kB

  • Original 48.5 kB
  • After minification 39.1 kB
  • After compression 7.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. Eijinkai.or.jp needs all CSS files to be minified and compressed as it can save up to 41.4 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

54

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 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 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

eijinkai.or.jp

eijinkai.or.jp

810 ms

style.css

style.css

938 ms

font.css

font.css

378 ms

top.css

top.css

387 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1316 ms

jquery.cookie.js

jquery.cookie.js

397 ms

redirect.js

redirect.js

512 ms

main.js

main.js

707 ms

emergency.js

emergency.js

762 ms

swfobject.js

swfobject.js

750 ms

brand

brand

14 ms

brand

brand

35 ms

feed2js.php

feed2js.php

1285 ms

conversion.js

conversion.js

14 ms

ga.js

ga.js

24 ms

body_bg.jpg

body_bg.jpg

188 ms

head_bg.jpg

head_bg.jpg

334 ms

sitetitle.gif

sitetitle.gif

356 ms

navi_sub_bg.gif

navi_sub_bg.gif

377 ms

navi_sub.gif

navi_sub.gif

377 ms

btn_header_search.gif

btn_header_search.gif

442 ms

no_flash.jpg

no_flash.jpg

1887 ms

nayami_ttl.gif

nayami_ttl.gif

684 ms

top_column_pic01.gif

top_column_pic01.gif

702 ms

top_column_pic02.gif

top_column_pic02.gif

710 ms

top_column_pic03.gif

top_column_pic03.gif

768 ms

top_column_pic04.gif

top_column_pic04.gif

798 ms

side_h2_ttl.gif

side_h2_ttl.gif

1037 ms

banner_mentalhealthcare.jpg

banner_mentalhealthcare.jpg

1457 ms

banner_verveneo.jpg

banner_verveneo.jpg

1512 ms

foot_ttl01.gif

foot_ttl01.gif

1169 ms

tel.gif

tel.gif

1170 ms

foot_ttl02.gif

foot_ttl02.gif

1441 ms

kinen.gif

kinen.gif

1516 ms

copyright.gif

copyright.gif

1516 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

54 ms

__utm.gif

__utm.gif

29 ms

navi.jpg

navi.jpg

2301 ms

nayami_bg.gif

nayami_bg.gif

1794 ms

check_btn.gif

check_btn.gif

1825 ms

nayami_btn.gif

nayami_btn.gif

1829 ms

top_column_bg.gif

top_column_bg.gif

1830 ms

top_column_ttl01.gif

top_column_ttl01.gif

2141 ms

t_arrow01.gif

t_arrow01.gif

2182 ms

t_arrow02.gif

t_arrow02.gif

2186 ms

top_column_ttl02.gif

top_column_ttl02.gif

2204 ms

top_column_ttl03.gif

top_column_ttl03.gif

2254 ms

top_column_ttl04.gif

top_column_ttl04.gif

2499 ms

side_h3_bg.gif

side_h3_bg.gif

2538 ms

feed_dotted.gif

feed_dotted.gif

2479 ms

f_dotted.gif

f_dotted.gif

2505 ms

foot_bnr01.gif

foot_bnr01.gif

2552 ms

foot_bnr02.gif

foot_bnr02.gif

2574 ms

33 ms

16 ms

foot_bnr03.gif

foot_bnr03.gif

2824 ms

print.css

print.css

175 ms

Accessibility Review

eijinkai.or.jp accessibility score

79

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

eijinkai.or.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

eijinkai.or.jp SEO score

91

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eijinkai.or.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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: