4.7 sec in total
996 ms
3.4 sec
351 ms
Visit humanbody.jp now to see the best up-to-date Humanbody content for Japan and also check out these interesting facts you probably never knew about humanbody.jp
ヒューマンボディ。ヒューマンボディでは、人体ダミー、生体力学試験材料、人体模型、医療シミュレーター、解剖モデル、標本など世界中の2000種類以上の製品を販売しています。株式会社アヴィス
Visit humanbody.jpWe analyzed Humanbody.jp page load time and found that the first response time was 996 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
humanbody.jp performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value7.0 s
6/100
25%
Value6.0 s
47/100
10%
Value390 ms
69/100
30%
Value0.007
100/100
15%
Value6.0 s
64/100
10%
996 ms
582 ms
584 ms
5 ms
105 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 77% of them (57 requests) were addressed to the original Humanbody.jp, 11% (8 requests) were made to Apis.google.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Humanbody.jp.
Page size can be reduced by 45.6 kB (14%)
315.4 kB
269.9 kB
In fact, the total size of Humanbody.jp main page is 315.4 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. 40% of websites need less resources to load. Images take 237.7 kB which makes up the majority of the site volume.
Potential reduce by 23.3 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 23.3 kB or 75% of the original size.
Potential reduce by 0 B
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. Humanbody images are well optimized though.
Potential reduce by 6.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 6.1 kB or 21% of the original size.
Potential reduce by 16.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. Humanbody.jp needs all CSS files to be minified and compressed as it can save up to 16.2 kB or 87% of the original size.
Number of requests can be reduced by 21 (29%)
73
52
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Humanbody. 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 as a result speed up the page load time.
humanbody.jp
996 ms
normalize.css
582 ms
main1.css
584 ms
widgets.js
5 ms
plusone.js
105 ms
dc.js
79 ms
nv-humanbody.jpg
203 ms
nv-cart.jpg
204 ms
nv-faq.jpg
194 ms
nv-contact.jpg
391 ms
nv-map.jpg
391 ms
nv-category.jpg
392 ms
nv-guide.jpg
397 ms
nv-simulator.jpg
394 ms
nv-human.jpg
404 ms
nv-dummy.jpg
573 ms
nv-zoology.jpg
579 ms
nv-botany.jpg
579 ms
nv-orthopaedic.jpg
585 ms
t-humanbody.jpg
1200 ms
ttc-26-8.jpg
793 ms
ttc-6101.jpg
952 ms
ttc-6102.jpg
772 ms
ttc-6110.jpg
769 ms
ttc-6109.jpg
968 ms
ttc-6108.jpg
961 ms
ttc-6103.jpg
962 ms
ttc-6105.jpg
1183 ms
ttc-6106.jpg
1141 ms
ttc-6107.jpg
1156 ms
ttc-24-5.jpg
1154 ms
box.gif
1157 ms
hbd0115-00.jpg
1521 ms
SAW3403-sum.jpg
1348 ms
BCBC073-sum.jpg
1348 ms
A290-sum.jpg
1349 ms
SAW1352-sum.jpg
1377 ms
KY11326-000-sum.jpg
1386 ms
ttc-24-4.jpg
1539 ms
hatena2.gif
1540 ms
iebm.gif
1540 ms
hsm01.jpg
1525 ms
cb=gapi.loaded_0
39 ms
cb=gapi.loaded_1
93 ms
fastbutton
106 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
55 ms
inpage_linkid.js
60 ms
hsm02.jpg
1390 ms
hsm30.jpg
1520 ms
hsm41.jpg
1533 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
48 ms
cb=gapi.loaded_0
86 ms
cb=gapi.loaded_1
87 ms
__utm.gif
41 ms
postmessageRelay
48 ms
3193398744-postmessagerelay.js
60 ms
rpc:shindig_random.js
72 ms
hsm42.jpg
1354 ms
hsm43.jpg
1353 ms
hsm44.jpg
1388 ms
hsm45.jpg
1387 ms
hsm46.jpg
1516 ms
hsm47.jpg
1527 ms
cb=gapi.loaded_0
11 ms
jot
92 ms
hsm99.jpg
1554 ms
fota01.jpg
1356 ms
fota02.jpg
1396 ms
fota03.jpg
1388 ms
fota04.jpg
1331 ms
i03.jpg
1354 ms
hsm00.jpg
1335 ms
i01.jpg
1214 ms
hsm40.jpg
1207 ms
humanbody.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.
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
Form elements do not have associated labels
Links do not have a discernible name
humanbody.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
humanbody.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Humanbody.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 Humanbody.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.
humanbody.jp
Open Graph description is not detected on the main page of Humanbody. 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: