4.5 sec in total
822 ms
3.4 sec
277 ms
Click here to check amazing Health content for Japan. Otherwise, check out these important facts you probably never knew about health.ne.jp
健康、病気のことなら「HelC(ヘルシー)」。ヘルシーでは、病名、最寄駅などさまざまな条件から探せる病院検索やお薬検索のほか、健康法や病気の解説、用語解説、医師への健康相談など、日常生活に役立つ情報満載のサイトです。
Visit health.ne.jpWe analyzed Health.ne.jp page load time and found that the first response time was 822 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
health.ne.jp performance score
822 ms
539 ms
565 ms
414 ms
435 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 78% of them (69 requests) were addressed to the original Health.ne.jp, 4% (4 requests) were made to Platform.twitter.com and 3% (3 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Health.ne.jp.
Page size can be reduced by 214.6 kB (34%)
631.4 kB
416.9 kB
In fact, the total size of Health.ne.jp main page is 631.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. 40% of websites need less resources to load. Images take 358.3 kB which makes up the majority of the site volume.
Potential reduce by 33.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. 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 33.4 kB or 75% of the original size.
Potential reduce by 31.4 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. Health images are well optimized though.
Potential reduce by 107.8 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 107.8 kB or 60% of the original size.
Potential reduce by 41.9 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. Health.ne.jp needs all CSS files to be minified and compressed as it can save up to 41.9 kB or 86% of the original size.
Number of requests can be reduced by 39 (44%)
88
49
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Health. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
health.ne.jp
822 ms
phn.css
539 ms
top_renew.css
565 ms
phn.js
414 ms
top_renew.js
435 ms
spacer.gif
189 ms
head_sitemap.gif
185 ms
head_about.gif
211 ms
headLogo.gif
188 ms
submitBtn.gif
209 ms
h2Tit_theme.jpg
365 ms
top_bipolar_141201.gif
548 ms
top_dlb_150713.gif
370 ms
top_pollen_150316.jpg
720 ms
h2Tit_found.jpg
405 ms
140911.jpg
407 ms
140431.jpg
520 ms
suppleH4.gif
551 ms
sesamin.jpg
600 ms
fnc_hightv.jpg
607 ms
h2Tit_study.jpg
719 ms
160251.jpg
728 ms
new_entry01.gif
735 ms
pickup_lib.gif
801 ms
new_words.gif
867 ms
leftH301.gif
869 ms
leftBtn01.jpg
868 ms
leftBtn06.jpg
909 ms
leftBtn04.jpg
913 ms
leftBtn02.jpg
991 ms
leftBtn03.jpg
1002 ms
leftBtn05.jpg
1035 ms
leftH302.gif
1022 ms
banner.jpg
1090 ms
rightH301.gif
1094 ms
rightH302.gif
1185 ms
right_doctorBtn.gif
1200 ms
h2Tit_lib.jpg
1187 ms
h2Tit_service.jpg
1232 ms
fLogo.gif
1272 ms
gpt.js
5 ms
pubads_impl_81.js
12 ms
container.html
22 ms
bgHead.gif
1230 ms
ads
82 ms
widgets.js
90 ms
ga.js
4 ms
__utm.gif
24 ms
14190161774241427733
96 ms
ads
398 ms
osd.js
19 ms
bgContents.gif
1211 ms
arw_s01.gif
1183 ms
rss.gif
1226 ms
searchHeadBtm.gif
1236 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
126 ms
searchHead.gif
1247 ms
syndication
94 ms
311359675830517760
215 ms
searchBg.gif
1104 ms
dotted01.gif
1170 ms
arw01.gif
1187 ms
h3Img01.gif
1205 ms
bgTokuho_02.gif
1320 ms
bgTokuho_03.gif
1104 ms
arw02.gif
1104 ms
15491532398886047327
148 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
32 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
133 ms
bgLeftBoxHead.gif
1104 ms
bgLeftBoxBtm.gif
1180 ms
twitter_icon__normal.png
248 ms
bgLeftBox.gif
1093 ms
bglibDt02.gif
1111 ms
bgRightBox.gif
1109 ms
bgRightBox_inner.gif
1138 ms
bgRightBoxBtm.gif
1116 ms
liQ.gif
1141 ms
bglibDt.gif
1143 ms
i_lib_disease.gif
1148 ms
i_lib_symptom.gif
1127 ms
i_lib_medical.gif
1126 ms
i_lib_life.gif
1188 ms
i_lib_nutrition.gif
1204 ms
i_lib_age.gif
1171 ms
bgDot01.gif
1165 ms
jot
40 ms
activeview
13 ms
activeview
13 ms
health.ne.jp SEO score
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Health.ne.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 Health.ne.jp main page’s claimed encoding is euc-jp. 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.
health.ne.jp
Open Graph description is not detected on the main page of Health. 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: