7.7 sec in total
542 ms
4.6 sec
2.6 sec
Welcome to yohwakai.com homepage info - get ready to check Yohwakai best content right away, or after learning these important things about yohwakai.com
JR中央線三鷹駅からすぐ。武蔵野市・三鷹市・東京西部・多摩地域の病院といえば武蔵野陽和会病院。内科・外科・整形外科・泌尿器科・リハビリテーション科・放射線科・訪問診療科・専門外来。東京都武蔵野市にある病院です。
Visit yohwakai.comWe analyzed Yohwakai.com page load time and found that the first response time was 542 ms and then it took 7.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.
yohwakai.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value11.2 s
0/100
25%
Value9.3 s
13/100
10%
Value520 ms
56/100
30%
Value0.534
14/100
15%
Value11.7 s
17/100
10%
542 ms
1136 ms
333 ms
500 ms
42 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 40% of them (21 requests) were addressed to the original Yohwakai.com, 25% (13 requests) were made to Maps.googleapis.com and 15% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Yohwakai.com.
Page size can be reduced by 198.3 kB (12%)
1.7 MB
1.5 MB
In fact, the total size of Yohwakai.com main page is 1.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. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 29.5 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 16% 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.5 kB or 80% of the original size.
Potential reduce by 111.2 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. Yohwakai images are well optimized though.
Potential reduce by 29.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 29.9 kB or 23% of the original size.
Potential reduce by 27.6 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. Yohwakai.com needs all CSS files to be minified and compressed as it can save up to 27.6 kB or 83% of the original size.
Number of requests can be reduced by 20 (40%)
50
30
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yohwakai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
yohwakai.com
542 ms
yohwakai.com
1136 ms
style.css
333 ms
style_home.css
500 ms
js
42 ms
jquery-1.10.2.min.js
34 ms
typesquare.js
584 ms
common.js
598 ms
home.js
600 ms
analytics.js
127 ms
embed
296 ms
img_yowakai.png
169 ms
logo.png
1317 ms
banner_recruit.jpg
339 ms
img_tel.png
494 ms
keyvisual.jpg
2215 ms
bg_tile.jpg
565 ms
img_maintop.jpg
1854 ms
img_arrow.png
633 ms
img_maintop.jpg
2524 ms
img_maintop.jpg
1090 ms
img_nursing.jpg
1147 ms
icon_link.png
1342 ms
doctor_nagakura.png
1497 ms
pagetop_text.png
1500 ms
logo_footer.png
1700 ms
collect
13 ms
collect
31 ms
js
47 ms
gen_204
24 ms
init_embed.js
29 ms
common.js
56 ms
util.js
98 ms
map.js
88 ms
overlay.js
72 ms
onion.js
62 ms
search_impl.js
61 ms
StaticMapService.GetMapImage
209 ms
openhand_8_8.cur
51 ms
ViewportInfoService.GetViewportInfo
54 ms
vt
141 ms
vt
144 ms
vt
167 ms
vt
129 ms
vt
122 ms
vt
141 ms
AuthenticationService.Authenticate
20 ms
vt
199 ms
QuotaService.RecordEvent
21 ms
controls.js
6 ms
css
145 ms
css
162 ms
yohwakai.com 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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
yohwakai.com 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
yohwakai.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yohwakai.com 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 Yohwakai.com 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.
yohwakai.com
Open Graph description is not detected on the main page of Yohwakai. 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: