5.2 sec in total
736 ms
4.1 sec
309 ms
Click here to check amazing Jshem content for United States. Otherwise, check out these important facts you probably never knew about jshem.or.jp
一般社団法人日本血液学会公式サイト
Visit jshem.or.jpWe analyzed Jshem.or.jp page load time and found that the first response time was 736 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
jshem.or.jp performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value6.1 s
12/100
25%
Value3.2 s
91/100
10%
Value100 ms
98/100
30%
Value0
100/100
15%
Value3.3 s
93/100
10%
736 ms
346 ms
532 ms
355 ms
97 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 95% of them (55 requests) were addressed to the original Jshem.or.jp, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Jshem.or.jp.
Page size can be reduced by 298.2 kB (20%)
1.5 MB
1.2 MB
In fact, the total size of Jshem.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. 25% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 25.5 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 10.6 kB, which is 33% 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 25.5 kB or 80% of the original size.
Potential reduce by 95.2 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. Jshem images are well optimized though.
Potential reduce by 153.1 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 153.1 kB or 69% of the original size.
Potential reduce by 24.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. Jshem.or.jp needs all CSS files to be minified and compressed as it can save up to 24.4 kB or 83% of the original size.
Number of requests can be reduced by 5 (9%)
56
51
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jshem. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
jshem.or.jp
736 ms
default.css
346 ms
base.css
532 ms
mosaic.css
355 ms
jquery.min.js
97 ms
common.js
373 ms
jquery.belatedPNG.min.js
974 ms
jquery-ui.min.js
1387 ms
mosaic.1.0.1.min.js
518 ms
global_bg1.png
886 ms
logo.png
180 ms
bg-util-nav.png
188 ms
unav-home.png
178 ms
unav-eng.png
199 ms
unav-sitemap.png
188 ms
unav-office.png
354 ms
input.gif
531 ms
btn-search.gif
374 ms
bg-tabs.png
375 ms
slider_winter.jpg
396 ms
slider01.jpg
706 ms
slider02.jpg
1495 ms
slider_78pr.jpg
937 ms
slider_7th_pr.jpg
791 ms
ui-tabs-off.jpg
707 ms
tabs_info.png
1060 ms
btn-info.jpg
883 ms
h2-wn-list.jpg
989 ms
bg-fade.png
1041 ms
memu-meeting.png
1416 ms
menu-society.png
1125 ms
menu-prize.png
1189 ms
menu-fellow.png
1219 ms
menu-regist.png
1411 ms
menu-trial.png
1500 ms
menu-info.png
1390 ms
menu-patient.png
1397 ms
menu-seminar.png
1590 ms
menu-coi.png
1574 ms
menu-local.png
1765 ms
menu-link.png
1768 ms
bnr-member.png
1676 ms
bnr-procedures.png
1686 ms
bnr-memberinfo.png
1749 ms
bnr-credit.png
1786 ms
ga.js
37 ms
__utm.gif
18 ms
bnr-facility.png
1696 ms
bnr-guideline.png
1707 ms
bnr-target.png
1749 ms
bnr-enews.png
1762 ms
bnr_coi_guideline.png
1756 ms
bnr-statement.png
1641 ms
h3-journal.png
1685 ms
cover-ijh_2016.jpg
1698 ms
btn-more.png
1714 ms
cover-rinketsu.png
1601 ms
btn_pagetop.png
1426 ms
jshem.or.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.
jshem.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
jshem.or.jp SEO score
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
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jshem.or.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jshem.or.jp main page’s claimed encoding is shift_jis. 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.
jshem.or.jp
Open Graph description is not detected on the main page of Jshem. 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: