14.9 sec in total
419 ms
13.6 sec
882 ms
Welcome to medwatch.jp homepage info - get ready to check Medwatch best content for Japan right away, or after learning these important things about medwatch.jp
病院経営に携わる関係者向けのブログメディアです。急性期病院の経営コンサルティング会社、グローバルヘルスコンサルティング・ジャパンが、病院経営の改善、医療の質向上などに役立つ情報を発信します。
Visit medwatch.jpWe analyzed Medwatch.jp page load time and found that the first response time was 419 ms and then it took 14.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
medwatch.jp performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
419 ms
1841 ms
314 ms
361 ms
365 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 52% of them (70 requests) were addressed to the original Medwatch.jp, 17% (23 requests) were made to Facebook.com and 9% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (8.4 sec) belongs to the original domain Medwatch.jp.
Page size can be reduced by 770.9 kB (18%)
4.3 MB
3.6 MB
In fact, the total size of Medwatch.jp main page is 4.3 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. 65% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 93.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 93.7 kB or 84% of the original size.
Potential reduce by 346.0 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. Medwatch images are well optimized though.
Potential reduce by 234.3 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 234.3 kB or 60% of the original size.
Potential reduce by 96.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. Medwatch.jp needs all CSS files to be minified and compressed as it can save up to 96.8 kB or 77% of the original size.
Number of requests can be reduced by 43 (34%)
128
85
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Medwatch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
medwatch.jp
419 ms
www.medwatch.jp
1841 ms
mwstyle.css
314 ms
medw.js
361 ms
styles.css
365 ms
css
26 ms
genericons.css
553 ms
style.css
952 ms
jquery.fancybox.css
689 ms
wpp.css
692 ms
jquery.js
1281 ms
jquery-migrate.min.js
710 ms
jquery.fancybox.js
1301 ms
style.css
1011 ms
jquery-1.9.1.js
9 ms
jquery.form.min.js
672 ms
scripts.js
700 ms
masonry.min.js
1178 ms
jquery.masonry.min.js
1029 ms
functions.js
1027 ms
jquery.dotdotdot.js
1056 ms
add_bookmark.jquery.js
1260 ms
PIE.js
1460 ms
sdk.js
334 ms
analytics.js
24 ms
head-border.jpg
418 ms
logo.png
444 ms
sidebar-logo_simple.png
456 ms
81378d250c62c2f596f3058e0793858d_s.jpg
1388 ms
75010c2ed7c16ba4bf9c4ce19c636cef_s.jpg
825 ms
IMG_6512.jpg
1097 ms
%E5%8E%9A%E7%94%9F%E5%8A%B4%E5%83%8D%E7%9C%81%E3%82%A4%E3%83%A1%E3%83%BC%E3%82%B8%E5%86%99%E7%9C%9F.jpg
1527 ms
DSC09161.jpg
1335 ms
d235cfb086ef4372f03c04dcffb22229_s.jpg
1736 ms
IMG_6501.jpg
1680 ms
%E3%82%B9%E3%83%A9%E3%82%A4%E3%83%89218.jpg
1628 ms
%E3%82%B9%E3%83%A9%E3%82%A4%E3%83%89124.jpg
2006 ms
%E3%82%B9%E3%83%A9%E3%82%A4%E3%83%89123.jpg
2016 ms
160217nsp10.jpg
2359 ms
fig2.png
2472 ms
bbcd6d61d16289a0a51105e3c26bda15_l.jpg
2304 ms
4eb6c25f92c520c65abdb2dc5377cc5d_s.jpg
3083 ms
167f40062191e3987b54902456d3210b_m.jpg
6605 ms
72c3dcaabcd8878ba3c1396854636b08_s.jpg
3246 ms
%E3%82%B9%E3%83%A9%E3%82%A4%E3%83%89214.jpg
3142 ms
15604486811_4cd49a49d0_o.jpg
3149 ms
%E3%82%B9%E3%83%A9%E3%82%A4%E3%83%8916.jpg
3366 ms
IMG_6488.jpg
3924 ms
go_top.jpg
3467 ms
black_trans.png
3469 ms
pattern-light.svg
3537 ms
collect
32 ms
sidebarbackground.jpg
3728 ms
mw_register_sm.png
3683 ms
facebook_sm.png
3719 ms
twitter_sm.png
3772 ms
gplus_sm.png
4053 ms
feedly_sm.png
4066 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
44 ms
4cKlrioa77J2iqTqBgkRWg.ttf
53 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
118 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
117 ms
rss_sm.png
4069 ms
widgets.js
9 ms
plusone.js
95 ms
collect
16 ms
cb=gapi.loaded_0
98 ms
2016ShinryoH-off.png
3913 ms
mail_magazine.png
4056 ms
77 ms
xd_arbiter.php
325 ms
xd_arbiter.php
555 ms
grey_frame.png
4099 ms
search_btn_off.png
4064 ms
arrow-down.jpg
4076 ms
medwatch.js
155 ms
admin-ajax.php
4690 ms
beacon.gif
224 ms
popin_discovery5-min.js
31 ms
like.php
60 ms
log.gif
320 ms
ck
685 ms
like.php
67 ms
like.php
101 ms
like.php
80 ms
like.php
90 ms
like.php
114 ms
like.php
114 ms
rU2ubZ6l1Q5.js
503 ms
LVx-xkvaJ0b.png
458 ms
like.php
102 ms
like.php
95 ms
like.php
105 ms
like.php
110 ms
like.php
126 ms
like.php
117 ms
ninki_title.png
4291 ms
like.php
86 ms
like.php
70 ms
like.php
84 ms
like.php
89 ms
like.php
100 ms
like.php
106 ms
like.php
105 ms
like.php
112 ms
like_box.php
158 ms
SM3vdxK-TJb.css
210 ms
i4vhyzUs1Dh.css
212 ms
_rx8naC75Dy.js
338 ms
b94UUzHjapV.js
356 ms
0wM5s1Khldu.js
270 ms
TTCre3391I0.js
275 ms
blog-past-botton-off.png
3768 ms
facebook.png
3527 ms
twitter.png
3509 ms
10429846_695538640555659_2712569723039524676_n.jpg
358 ms
10409723_635620326547491_8609536602227626088_n.png
423 ms
10481331_738454842896665_373920475279478031_n.jpg
495 ms
556493_117776648360190_784182221_n.jpg
565 ms
10354686_10150004552801856_220367501106153455_n.jpg
562 ms
10556373_558822017574706_3289661486156270024_n.jpg
563 ms
1979701_259097277607576_1328355600913506765_n.jpg
563 ms
11709719_867692313318990_3550699057332784884_n.jpg
565 ms
wL6VQj7Ab77.png
75 ms
s7jcwEQH7Sx.png
73 ms
uid.html
36 ms
google-plus.png
3649 ms
feedely.png
3565 ms
rss.png
6592 ms
footer-arrow.jpg
6743 ms
I6-MnjEovm5.js
69 ms
f6T91Deal_q.js
138 ms
%E3%82%B9%E3%83%A9%E3%82%A4%E3%83%8911.jpg
8361 ms
head-plus-off.png
7919 ms
medwatch.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.
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
medwatch.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
medwatch.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Medwatch.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 Medwatch.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.
medwatch.jp
Open Graph data is detected on the main page of Medwatch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: