10.3 sec in total
1 sec
9.1 sec
132 ms
Welcome to jsmo.or.jp homepage info - get ready to check Jsmo best content for Japan right away, or after learning these important things about jsmo.or.jp
日本臨床腫瘍学会公式WEBサイトでは、患者・家族、国民、がんの研究者・医療者に対し、がんあるいはがん医療に関する国内外の情報を発信しております。
Visit jsmo.or.jpWe analyzed Jsmo.or.jp page load time and found that the first response time was 1 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
jsmo.or.jp performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value5.2 s
23/100
25%
Value6.1 s
45/100
10%
Value110 ms
98/100
30%
Value0
100/100
15%
Value6.0 s
64/100
10%
1033 ms
316 ms
327 ms
1206 ms
349 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 97% of them (119 requests) were addressed to the original Jsmo.or.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Jsmo.or.jp.
Page size can be reduced by 174.6 kB (43%)
404.2 kB
229.7 kB
In fact, the total size of Jsmo.or.jp main page is 404.2 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. 20% of websites need less resources to load. Images take 154.2 kB which makes up the majority of the site volume.
Potential reduce by 41.8 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 41.8 kB or 82% of the original size.
Potential reduce by 1.1 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. Jsmo images are well optimized though.
Potential reduce by 79.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 79.8 kB or 58% of the original size.
Potential reduce by 51.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. Jsmo.or.jp needs all CSS files to be minified and compressed as it can save up to 51.8 kB or 84% of the original size.
Number of requests can be reduced by 89 (74%)
121
32
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jsmo. 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 from 11 to 1 for CSS and as a result speed up the page load time.
jsmo.or.jp
1033 ms
import.css
316 ms
medium.css
327 ms
jquery-1.6.1.min.js
1206 ms
jquery.swap.js
349 ms
jquery.thickbox.js
370 ms
jquery.acordion.js
659 ms
jquery.corner.js
659 ms
jquery.tab.js
691 ms
jquery.setActive.js
688 ms
styleswitcher.js
900 ms
heightLine.js
993 ms
jquery.linkIconImg.js
840 ms
brand
38 ms
brand
48 ms
reset.css
710 ms
define.css
726 ms
common.css
1219 ms
contents.css
1025 ms
home.css
1040 ms
thickbox.css
186 ms
ga.js
30 ms
wrap_inner_bg.gif
311 ms
header_bg.gif
315 ms
site_title.gif
329 ms
header_bt_login_off.gif
339 ms
header_bt_en_off.gif
348 ms
header_text_size_tx.gif
348 ms
header_text_size_bt_s_off.gif
630 ms
header_text_size_bt_m_over.gif
635 ms
header_text_size_bt_l_off.gif
658 ms
header_search_bg.gif
672 ms
header_search_input_bg.gif
691 ms
header_search_bt_off.gif
706 ms
index_h2.gif
945 ms
common_ic_new.png
983 ms
common_ic_imp.png
972 ms
common_ic_att.png
999 ms
btn_hokkaido_off.gif
1020 ms
btn_aomori_off.gif
1018 ms
btn_iwate_off.gif
1300 ms
btn_miyagi_off.gif
1289 ms
btn_akita_off.gif
1306 ms
btn_yamagata_off.gif
1348 ms
btn_fukushima_off.gif
1361 ms
btn_ibaragi_off.gif
1381 ms
btn_tochigi_off.gif
1634 ms
btn_gunma_off.gif
1636 ms
btn_saitama_off.gif
1644 ms
btn_chiba_off.gif
1665 ms
btn_tokyo_off.gif
1730 ms
btn_kanagawa_off.gif
1747 ms
btn_niigata_off.gif
1954 ms
btn_toyama_off.gif
1962 ms
btn_ishikawa_off.gif
1994 ms
btn_fukui_off.gif
2010 ms
btn_yamanashi_off.gif
2039 ms
btn_nagano_off.gif
2068 ms
__utm.gif
24 ms
btn_gifu_off.gif
1988 ms
btn_shizuoka_off.gif
2006 ms
btn_aichi_off.gif
1998 ms
btn_mie_off.gif
2029 ms
btn_shiga_off.gif
2017 ms
btn_kyoto_off.gif
2101 ms
btn_osaka_off.gif
2006 ms
btn_hyogo_off.gif
1996 ms
btn_nara_off.gif
2007 ms
btn_wakayama_off.gif
2016 ms
btn_tottori_off.gif
2053 ms
btn_shimane_off.gif
2098 ms
btn_okayama_off.gif
2001 ms
btn_hiroshima_off.gif
2013 ms
btn_yamaguchi_off.gif
2010 ms
btn_tokushima_off.gif
2056 ms
btn_kagawa_off.gif
2071 ms
btn_ehime_off.gif
2126 ms
btn_kochi_off.gif
2003 ms
btn_fukuoka_off.gif
2006 ms
btn_saga_off.gif
1993 ms
btn_nagasaki_off.gif
2029 ms
btn_kumamoto_off.gif
2094 ms
btn_oita_off.gif
2107 ms
btn_miyazaki_off.gif
1964 ms
btn_kagoshima_off.gif
1994 ms
btn_okinawa_off.gif
2015 ms
btn_kaigai_off.gif
2076 ms
pdf_box_img.gif
2070 ms
index_info_bt_off.gif
2059 ms
main_navi_member_off.gif
1993 ms
common_ic_member.png
2006 ms
main_navi_about_off.gif
2007 ms
main_navi_authorize_off.gif
2075 ms
main_navi_assembly_off.gif
2106 ms
main_navi_news_off.gif
2062 ms
main_navi_link_off.gif
1980 ms
jsmo2016.jpg
1969 ms
sub_column_img_01.gif
2014 ms
Annals-teeny-banner-Japanese-Author.png
2033 ms
sub_column_bn_news1.gif
2120 ms
sub_column_bn_news2.gif
2049 ms
sub_column_bn_ESMO.jpg
1994 ms
sub_column_bn_KACO.jpg
1989 ms
sub_column_bn_CSCO.jpg
2023 ms
sub_column_bn_MOGA.jpg
2052 ms
sub_column_bn_SSO.jpg
2062 ms
sub_column_bn_cael.gif
2034 ms
common_bl_01.gif
1988 ms
index_key_visual.jpg
3003 ms
common_bl_04.gif
2003 ms
tab_bl.gif
2042 ms
footer_bg.gif
2057 ms
common_bl_03.gif
2013 ms
loadingAnimation.gif
2018 ms
common_ic_pdf.gif
2038 ms
common_ic_word.gif
2156 ms
common_ic_xls.gif
2120 ms
common_ic_page.gif
2071 ms
tab_arrow.png
2164 ms
tab_bg.gif
2086 ms
small.css
164 ms
large.css
351 ms
print.css
390 ms
jsmo.or.jp accessibility score
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
jsmo.or.jp 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
jsmo.or.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jsmo.or.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 Jsmo.or.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.
jsmo.or.jp
Open Graph description is not detected on the main page of Jsmo. 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: