5.1 sec in total
566 ms
4.1 sec
442 ms
Welcome to c-notes.jp homepage info - get ready to check C Notes best content for Japan right away, or after learning these important things about c-notes.jp
治療ノートは、治療法を決める際に必要な情報を知ることができる医療情報サイトです。病気の基礎情報や治療法に関する体験談を調べたり、治療法の違いを比較して、あなたにとって最善の治療法を選択してください。
Visit c-notes.jpWe analyzed C-notes.jp page load time and found that the first response time was 566 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
c-notes.jp performance score
566 ms
321 ms
235 ms
46 ms
973 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original C-notes.jp, 19% (22 requests) were made to Static.xx.fbcdn.net and 13% (15 requests) were made to Dt1xp29bjwe6.cloudfront.net. The less responsive or slowest element that took the longest time to load (973 ms) relates to the external source B.st-hatena.com.
Page size can be reduced by 371.2 kB (24%)
1.6 MB
1.2 MB
In fact, the total size of C-notes.jp main page is 1.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 949.3 kB which makes up the majority of the site volume.
Potential reduce by 28.0 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 28.0 kB or 68% of the original size.
Potential reduce by 9.6 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. C Notes images are well optimized though.
Potential reduce by 220.5 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 220.5 kB or 50% of the original size.
Potential reduce by 113.2 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. C-notes.jp needs all CSS files to be minified and compressed as it can save up to 113.2 kB or 84% of the original size.
Number of requests can be reduced by 61 (58%)
106
45
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of C Notes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
c-notes.jp
566 ms
www.c-notes.jp
321 ms
application-e5e1bfcacc5c2285967ed57ae1257a3d8e7668339ae9c1299c4013fb2d110b97.css
235 ms
application-b72b0dde0b66c811f2a4bb388e725128f3286939535f7ead06b0a7d1e4857016.js
46 ms
bookmark_button.js
973 ms
show_ads.js
43 ms
raygun.min.js
46 ms
gtm.js
280 ms
sdk.js
355 ms
widgets.js
595 ms
button-only@2x.png
877 ms
logo-d56933522775f4499d2008fa1aa5f5ec6d5b5d5139b533acde26ae4cd7d37a56.png
220 ms
logo_min-edb6a0e65891b553f33dccd9d2767c8e9cd1c46b594abeb85d74b99708c24584.png
275 ms
woman_70-2a3dff784598c62af4d17c9a5e1cbf29e1646978510cd79fcc154907554efab9.svg
295 ms
woman_50-3a7cb58509422fc2f0036f781c0792af2b7abdf0734d9844ede5fc4266bf765d.svg
277 ms
man_30-cb698cef2705871afed8a1e6851798eafe6f91095d794019e504b77e442ffab7.svg
421 ms
icon_medicine-ac309c73e48a4483763a1eb5f0089d6d81df8daeee44dbbfed11e1b051714be4.svg
590 ms
icon_otcmedicine-44c799b38da96077b9c4f98aec6f6c10c6ce842ae33731eebd9113851668028b.svg
448 ms
icon_news-ae21efbcd5d374669a417220ae0d0720fc177b7c2c2be07084ef48a2817df0e4.svg
301 ms
logo_white-99c0fc3e96e01c4651a679c177d98144338c1de825d2080600959339ad0b27da.png
295 ms
facebook-e4ae541a24a9516a33fd8debce7bb7d671181e5067cd0084f5e27a5491e6aed8.svg
345 ms
main_visual-82b3d4c7a1135e9497bcad8d8ede4a61fbe3ee2620855132933ce4b0f281ceba.png
699 ms
campaign_visual-31bd9a8f2e8d51d1c059c4ad5d61b34b765961134217a86d14f8d4b46cbf4fa9.png
656 ms
ca-pub-8510848482077597.js
110 ms
zrt_lookup.html
389 ms
show_ads_impl.js
251 ms
chiryonote-051e32604efa3b0625ab2c27d49bf0577a069141ba7381969191593016616397.woff
315 ms
mixpanel-2-latest.min.js
472 ms
analytics.js
364 ms
conversion_async.js
422 ms
itm.js
395 ms
320 ms
xd_arbiter.php
281 ms
ads
294 ms
osd.js
92 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
109 ms
collect
55 ms
collect
58 ms
audience
658 ms
40 ms
926 ms
collect
145 ms
86 ms
103 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
52 ms
139 ms
adj
127 ms
beacon
110 ms
104 ms
jot
111 ms
OMEB00527822.gif
208 ms
verify_selector.js
132 ms
blank.gif
157 ms
beacon.js
51 ms
verifyr.js
30 ms
client-verify.adtricity.com
427 ms
0
117 ms
bg.png
51 ms
pixel
53 ms
lidar.js
36 ms
sbhK2lTE.js
56 ms
adchoices.en.png
102 ms
pixel
139 ms
pixel
137 ms
cTrvNaRi.html
70 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
9 ms
gtm.js
46 ms
pageview.js
57 ms
td-1.5.1.js
118 ms
get
613 ms
sd
30 ms
reset.css
169 ms
entry-button.css
336 ms
bbtn-l_v3.png
169 ms
pageviews
27 ms
nr-885.min.js
138 ms
like.php
69 ms
page.php
603 ms
rU2ubZ6l1Q5.js
67 ms
LVx-xkvaJ0b.png
55 ms
c988fbe35f
274 ms
E9-rX0jGnNc.css
10 ms
NHzH-s6-lZM.css
25 ms
MBI28u-arQ9.css
20 ms
MKiDk2JIhZf.css
28 ms
_rx8naC75Dy.js
33 ms
3o1espZ6Mhb.js
17 ms
nfTYZZc0iSn.js
32 ms
SFuJyO56WQT.js
30 ms
pJPDNGWM_rf.js
76 ms
qLkez9vV75x.js
93 ms
g7eQ7KS-feD.js
107 ms
11800460_1607416952847573_1214354553805392629_n.png
306 ms
safe_image.php
320 ms
safe_image.php
331 ms
11760260_1603938843195384_1348329272448415029_n.png
309 ms
12645215_214702848874597_8202161681153443675_n.jpg
291 ms
1459661_505669432880536_987503894_n.jpg
307 ms
10313658_1613493358870262_3092629861196747030_n.jpg
290 ms
12072757_916435791756309_7833921838830200415_n.jpg
326 ms
10456026_649312885138972_842887163219961195_n.jpg
310 ms
11261590_853607168091926_8624475698944653301_n.jpg
311 ms
wL6VQj7Ab77.png
267 ms
s7jcwEQH7Sx.png
267 ms
LT9rONw9UJp.png
267 ms
lRyN50VcaFW.js
26 ms
safe_image.php
85 ms
safe_image.php
85 ms
safe_image.php
101 ms
6GqoI2ZyIrf.png
24 ms
R9a_DtVRZgv.js
12 ms
cUDgRFxaoIk.js
13 ms
0JBr1QHp8Gi.js
11 ms
kDOzhTr2W91.js
12 ms
c-notes.jp SEO score
N/A
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise C-notes.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that C-notes.jp main page’s claimed encoding is iso-8859-1. 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.
c-notes.jp
Open Graph data is detected on the main page of C Notes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: