9.8 sec in total
800 ms
8.8 sec
177 ms
Visit jssf.jp now to see the best up-to-date Jssf content and also check out these interesting facts you probably never knew about jssf.jp
日本足の外科学会は、外反母趾、扁平足、リウマチ足などを扱う「足の外科」の発展を通して、国民の健康・福祉に貢献することを目指しています。
Visit jssf.jpWe analyzed Jssf.jp page load time and found that the first response time was 800 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
jssf.jp performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value3.9 s
52/100
25%
Value9.2 s
13/100
10%
Value1,250 ms
19/100
30%
Value0.112
86/100
15%
Value10.3 s
24/100
10%
800 ms
982 ms
397 ms
992 ms
367 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 97% of them (62 requests) were addressed to the original Jssf.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Jssf.jp.
Page size can be reduced by 95.4 kB (16%)
614.0 kB
518.6 kB
In fact, the total size of Jssf.jp main page is 614.0 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. 15% of websites need less resources to load. Images take 488.5 kB which makes up the majority of the site volume.
Potential reduce by 10.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 2.0 kB, which is 14% 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 10.4 kB or 73% of the original size.
Potential reduce by 6.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. Jssf images are well optimized though.
Potential reduce by 28.2 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 28.2 kB or 54% of the original size.
Potential reduce by 50.4 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. Jssf.jp needs all CSS files to be minified and compressed as it can save up to 50.4 kB or 86% of the original size.
Number of requests can be reduced by 29 (47%)
62
33
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jssf. 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 CSS and as a result speed up the page load time.
jssf.jp
800 ms
www.jssf.jp
982 ms
import2.css
397 ms
common.js
992 ms
log.php
367 ms
base_reset.css
363 ms
base_body2.css
368 ms
base_layout_body.css
380 ms
base_layout.css
785 ms
base_contents.css
1074 ms
base_basic.css
1084 ms
ga.js
33 ms
top_background.gif
912 ms
header_logo.gif
375 ms
fontsize_title.gif
360 ms
fontsize_btn_01.gif
369 ms
fontsize_btn_02-over.gif
394 ms
fontsize_btn_03.gif
396 ms
header_english.gif
722 ms
header_navi_03.gif
726 ms
header_navi_02.gif
766 ms
header_navi_01.gif
772 ms
global_navi_01.gif
976 ms
global_navi_02.gif
1304 ms
global_navi_03.gif
1314 ms
global_navi_04.gif
1157 ms
top_main.jpg
2978 ms
top_bar.gif
1303 ms
top_btn.gif
1341 ms
top_list_line.gif
1528 ms
member_btn_01.gif
1878 ms
local_banner_01.gif
1896 ms
local_banner_02.gif
1903 ms
local_banner_03.gif
1890 ms
local_banner_04.gif
2117 ms
jssf2016_banner.jpg
2798 ms
6th_affas_banner.jpg
2674 ms
pagetop.gif
2287 ms
footer_line.gif
2299 ms
footer_back.gif
2474 ms
count_foot.gif
2673 ms
footer_navi_01.gif
2868 ms
footer_navi_02.gif
3044 ms
copyright.gif
3071 ms
__utm.gif
10 ms
import1.css
200 ms
base_body1.css
200 ms
import3.css
374 ms
base_body3.css
392 ms
print.css
391 ms
header_english-over.gif
359 ms
header_navi_03-over.gif
359 ms
header_navi_02-over.gif
363 ms
header_navi_01-over.gif
377 ms
global_navi_01-over.gif
584 ms
global_navi_02-over.gif
589 ms
global_navi_03-over.gif
914 ms
global_navi_04-over.gif
751 ms
member_btn_01-over.gif
942 ms
local_banner_01-over.gif
974 ms
local_banner_02-over.gif
1142 ms
local_banner_03-over.gif
1172 ms
local_banner_04-over.gif
1315 ms
pagetop-over.gif
1291 ms
jssf.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
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
<object> elements do not have alternate text
jssf.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
jssf.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jssf.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 Jssf.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.
jssf.jp
Open Graph description is not detected on the main page of Jssf. 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: