7.2 sec in total
800 ms
6.2 sec
283 ms
Click here to check amazing Medimedi content for Japan. Otherwise, check out these important facts you probably never knew about medimedi.info
開業医のためのお悩み解決サイト。医院開業に関連した様々な専門家がノウハウをコラム形式で公開しています。
Visit medimedi.infoWe analyzed Medimedi.info page load time and found that the first response time was 800 ms and then it took 6.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.
medimedi.info performance score
name
value
score
weighting
Value1.1 s
99/100
10%
Value1.1 s
100/100
25%
Value0
0/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.1 s
100/100
10%
800 ms
1023 ms
1094 ms
544 ms
563 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 79% of them (74 requests) were addressed to the original Medimedi.info, 12% (11 requests) were made to Web.xaas.jp and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Medimedi.info.
Page size can be reduced by 424.7 kB (70%)
604.6 kB
179.9 kB
In fact, the total size of Medimedi.info main page is 604.6 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. 30% of websites need less resources to load. Javascripts take 263.7 kB which makes up the majority of the site volume.
Potential reduce by 35.4 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 8.0 kB, which is 18% 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 35.4 kB or 80% of the original size.
Potential reduce by 8.7 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. Obviously, Medimedi needs image optimization as it can save up to 8.7 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 182.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 182.3 kB or 69% of the original size.
Potential reduce by 198.3 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. Medimedi.info needs all CSS files to be minified and compressed as it can save up to 198.3 kB or 83% of the original size.
Number of requests can be reduced by 29 (31%)
93
64
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Medimedi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
medimedi.info
800 ms
A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.1FlClNpo4U.css
1023 ms
jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js
1094 ms
ajax_v2016.js.pagespeed.jm.IhMMOvTC75.js
544 ms
jcarousellite_v1.1.js.pagespeed.jm.wtlzVdCKLg.js
563 ms
mousewheel_v3.1.13.js.pagespeed.jm.wBwlG6vk-c.js
566 ms
jscrollpane.js.pagespeed.jm.2wYEC_BNG3.js
756 ms
treeview.js.pagespeed.jm.Ccxdh7coVu.js
745 ms
common_v2016.js.pagespeed.jm.6iGU-6_f5J.js
982 ms
prettyphoto_v3.1.6.js,q20150527.pagespeed.jm.w2fGLjjfmp.js
960 ms
theme.css
300 ms
theme.css
605 ms
widgets.js
5 ms
background.gif
349 ms
original_header_bg.gif
400 ms
logo.gif
406 ms
header_link_bg.gif
477 ms
header_link01.gif
385 ms
header_link02.gif
370 ms
header_link03.gif
720 ms
header_link04.gif
802 ms
header_tab05.gif
755 ms
header_tab02.gif
752 ms
header_tab03.gif
759 ms
header_tab04.gif
840 ms
header_navi01_bg.gif
875 ms
header_navi_btn01.gif
1152 ms
header_navi_btn02.gif
1075 ms
header_navi_btn03.gif
1171 ms
header_navi_btn04.gif
1148 ms
header_navi_btn05.gif
1205 ms
header_navi_btn06.gif
1186 ms
header_navi_btn07.gif
1399 ms
header_navi_btn08.gif
1495 ms
header_navi02_bg.gif
1374 ms
header_navi2_btn01.gif
1527 ms
header_navi2_btn02.gif
1545 ms
header_navi2_btn03.gif
1520 ms
header_navi2_btn04.gif
1786 ms
icon_new.gif
1560 ms
icn_top3.gif
1715 ms
PP-47.jpg
1915 ms
hikaku_bnr.jpg
1882 ms
mm_special05_banner.gif
2240 ms
mm_seminer_banner.gif
1879 ms
voice_banner_top.gif
2104 ms
voice_banner_dc.gif
2142 ms
voice_banner_ct.gif
2200 ms
voice_banner_bottom.gif
2060 ms
page17_bt.png
757 ms
ga.js
29 ms
loading_icon.gif
399 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
47 ms
space.gif
205 ms
__utm.gif
19 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
19 ms
jot
98 ms
side_banner01.gif
1898 ms
h2_column_category01.gif
2117 ms
index_category_line_bg.gif
2122 ms
index_column_category01_bg.gif
2176 ms
index_category_listmark.gif
2236 ms
like.php
276 ms
index_column_category02_bg.gif
2131 ms
index_column_category03_bg.gif
1887 ms
qeKvIRsJabD.js
161 ms
LVx-xkvaJ0b.png
177 ms
index_column_category04_bg.gif
2141 ms
index_column_category05_bg.gif
2148 ms
index_column_category06_bg.gif
2208 ms
index_column_category07_bg.gif
2177 ms
index_column_category08_bg.gif
2126 ms
index_category_bottom.gif
1968 ms
h2_column_category02.gif
2143 ms
index_category_line2_bg.gif
2152 ms
index_column_category09_bg.gif
2146 ms
index_column_category10_bg.gif
2163 ms
index_column_category11_bg.gif
2187 ms
index_column_category12_bg.gif
2142 ms
side_doctorscolumn_icon_more.gif
2244 ms
latest_column_bg.gif
2121 ms
latest_column_title_bg.gif
2249 ms
new_topics_column_bg.gif
2013 ms
side_pickup_bg.gif
2136 ms
h2_side_pickup.gif
2235 ms
side_pickup_listmark01.gif
2393 ms
side_pickup_listmark02.gif
2219 ms
side_pickup_listmark03.gif
2191 ms
side_pickup_listmark04.gif
2138 ms
side_pickup_listmark05.gif
2298 ms
side_qa_box_bg.gif
2220 ms
side_contact_bg.gif
2186 ms
original_footer_bg.gif
2258 ms
btn_pagetop_bg.gif
2046 ms
medimedi.info accessibility score
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
medimedi.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
medimedi.info SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Medimedi.info 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 Medimedi.info 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.
medimedi.info
Open Graph description is not detected on the main page of Medimedi. 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: