Tools & Wizards About Us
jsum.or.jp screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

jsum.or.jp

公益社団法人日本超音波医学会

Page Load Speed

3.5 sec in total

First Response

538 ms

Resources Loaded

2.8 sec

Page Rendered

229 ms

jsum.or.jp screenshot

About Website

Click here to check amazing Jsum content for Japan. Otherwise, check out these important facts you probably never knew about jsum.or.jp

公益社団法人日本超音波医学会

Visit jsum.or.jp

Key Findings

We analyzed Jsum.or.jp page load time and found that the first response time was 538 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

jsum.or.jp performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

jsum.or.jp

538 ms

common.css

166 ms

index.css

330 ms

drawer.css

336 ms

smart.css

338 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 88% of them (51 requests) were addressed to the original Jsum.or.jp, 9% (5 requests) were made to Google.com and 3% (2 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Jsum.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.4 kB (9%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jsum.or.jp main page is 1.5 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 60.3 kB

  • Original 73.4 kB
  • After minification 53.6 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 19.8 kB, which is 27% 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 60.3 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 50.1 kB

  • Original 1.2 MB
  • After minification 1.1 MB

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. Jsum images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 12.5 kB

  • Original 222.1 kB
  • After minification 222.1 kB
  • After compression 209.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-30%

Potential reduce by 8.4 kB

  • Original 28.3 kB
  • After minification 28.3 kB
  • After compression 19.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. Jsum.or.jp needs all CSS files to be minified and compressed as it can save up to 8.4 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (34%)

Requests Now

56

After Optimization

37

  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jsum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

jsum.or.jp

jsum.or.jp

538 ms

common.css

common.css

166 ms

index.css

index.css

330 ms

drawer.css

drawer.css

336 ms

smart.css

smart.css

338 ms

jquery.bxslider.css

jquery.bxslider.css

336 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

514 ms

iscroll.min.js

iscroll.min.js

341 ms

jquery.drawer.js

jquery.drawer.js

494 ms

pagetop.js

pagetop.js

499 ms

jquery.bxslider.js

jquery.bxslider.js

501 ms

jquery.cycle.all.js

jquery.cycle.all.js

503 ms

bg01.jpg

bg01.jpg

166 ms

hamburger.jpg

hamburger.jpg

173 ms

menu.png

menu.png

166 ms

member.jpg

member.jpg

170 ms

h1.png

h1.png

167 ms

98th_banner.png

98th_banner.png

824 ms

20240824-lecture.png

20240824-lecture.png

656 ms

97th_banner.jpg

97th_banner.jpg

657 ms

main_img01.jpg

main_img01.jpg

661 ms

jmu_2000.jpg

jmu_2000.jpg

1185 ms

topics_bar2.jpg

topics_bar2.jpg

511 ms

of_01_2.jpg

of_01_2.jpg

682 ms

of_list.jpg

of_list.jpg

821 ms

daiichi.gif

daiichi.gif

986 ms

philips.gif

philips.gif

991 ms

fujifilm_healthcare.png

fujifilm_healthcare.png

852 ms

ge.png

ge.png

1148 ms

fukuda.gif

fukuda.gif

988 ms

fuji2.gif

fuji2.gif

1023 ms

siemens.gif

siemens.gif

1314 ms

asanuma.gif

asanuma.gif

1155 ms

konicaminolta2.png

konicaminolta2.png

1157 ms

afsumb_2024.jpg

afsumb_2024.jpg

1199 ms

of_02_2.jpg

of_02_2.jpg

1313 ms

info_mark.gif

info_mark.gif

1320 ms

page_top.png

page_top.png

1321 ms

jsum_logo.png

jsum_logo.png

1353 ms

cse.js

cse.js

124 ms

navi01.jpg

navi01.jpg

1248 ms

navi02.jpg

navi02.jpg

1356 ms

navi03.jpg

navi03.jpg

1355 ms

navi04.jpg

navi04.jpg

1363 ms

navi05.jpg

navi05.jpg

1364 ms

navi06.jpg

navi06.jpg

1401 ms

navi07.jpg

navi07.jpg

1416 ms

navi08.jpg

navi08.jpg

1518 ms

of_mark.gif

of_mark.gif

1519 ms

cse_element__ja.js

cse_element__ja.js

21 ms

default+ja.css

default+ja.css

66 ms

default.css

default.css

67 ms

foot_bg.jpg

foot_bg.jpg

1487 ms

bx_loader.gif

bx_loader.gif

1489 ms

controls.png

controls.png

1527 ms

async-ads.js

async-ads.js

29 ms

branding.png

branding.png

14 ms

clear.png

clear.png

6 ms

Accessibility Review

jsum.or.jp accessibility score

87

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

jsum.or.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

jsum.or.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jsum.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 Jsum.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.

Social Sharing Optimization

jsum.or.jp

Open Graph description is not detected on the main page of Jsum. 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: