3.1 sec in total
97 ms
2.7 sec
334 ms
Click here to check amazing Corpo Humano content for Brazil. Otherwise, check out these important facts you probably never knew about corpohumano.org
O seu canal de notícias sobre o Corpo Humano
Visit corpohumano.orgWe analyzed Corpohumano.org page load time and found that the first response time was 97 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.
corpohumano.org performance score
97 ms
201 ms
39 ms
57 ms
67 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Corpohumano.org, 21% (27 requests) were made to Static.xx.fbcdn.net and 12% (16 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (716 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 390.5 kB (29%)
1.3 MB
934.1 kB
In fact, the total size of Corpohumano.org main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 706.8 kB which makes up the majority of the site volume.
Potential reduce by 237.1 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 237.1 kB or 77% of the original size.
Potential reduce by 20.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. Corpo Humano images are well optimized though.
Potential reduce by 51.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 51.8 kB or 26% of the original size.
Potential reduce by 81.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. Corpohumano.org needs all CSS files to be minified and compressed as it can save up to 81.4 kB or 75% of the original size.
Number of requests can be reduced by 74 (63%)
117
43
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Corpo Humano. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
corpohumano.org
97 ms
www.corpohumano.org
201 ms
css
39 ms
css
57 ms
css
67 ms
font-awesome.min.css
6 ms
3375562265-css_bundle_v2.css
50 ms
authorization.css
108 ms
jquery.min.js
58 ms
jquery.flexslider.js
47 ms
jquery.min.js
41 ms
jquery.nivo.slider.pack.js
61 ms
adsbygoogle.js
32 ms
element.js
58 ms
platform.js
84 ms
3226477086-widgets.js
37 ms
plusone.js
189 ms
analytics.js
15 ms
webfont.js
14 ms
collect
24 ms
css
20 ms
icon18_wrench_allbkg.png
45 ms
icon-search.png
39 ms
TCxMVIU.png
71 ms
translateelement.css
70 ms
main.js
88 ms
Banner300x250.jpg
491 ms
r8JSYP0.png
56 ms
bkIsy6t.jpg
38 ms
JLCuEmd.jpg
39 ms
icon_home.png
33 ms
folder_search.png
32 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
33 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
33 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
36 ms
ca-pub-4871722659817120.js
241 ms
zrt_lookup.html
39 ms
show_ads_impl.js
86 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
18 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
15 ms
sdk.js
265 ms
178 ms
element_main.js
166 ms
cb=gapi.loaded_0
80 ms
cb=gapi.loaded_1
77 ms
fastbutton
165 ms
ads
113 ms
likebox.php
329 ms
fontawesome-webfont.woff
100 ms
osd.js
104 ms
cb=gapi.loaded_2
99 ms
follow
319 ms
postmessageRelay
590 ms
cloudflare.min.js
254 ms
combined.css
172 ms
jquery.min.js
172 ms
cb=gapi.loaded_0
240 ms
cb=gapi.loaded_1
262 ms
Cirurgias
212 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
513 ms
ajax-loader.gif
467 ms
summary
186 ms
summary
314 ms
334 ms
kyEKgjk51ZE.css
501 ms
xgj7bXhJNEH.css
586 ms
q68gy-v_YMF.js
642 ms
FJmpeSpHpjS.js
716 ms
0wM5s1Khldu.js
668 ms
1bNoFZUdlYZ.js
661 ms
rs=AGLTcCN9Hbd2l7OmLFEc03gVhW6k3Y2pYw
56 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
63 ms
rs=AGLTcCNPDRRI46HA3uIHFctvm-Ae2vfx-g
106 ms
xd_arbiter.php
394 ms
xd_arbiter.php
573 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
303 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
303 ms
%255Bwww.gj37765.blogspot.com%255Dh1.png
133 ms
3193398744-postmessagerelay.js
139 ms
rpc:shindig_random.js
106 ms
translate_24dp.png
87 ms
l
55 ms
googlelogo_color_42x16dp.png
66 ms
page.php
92 ms
cleardot.gif
78 ms
te_ctrl3.gif
30 ms
googlelogo_color_68x28dp.png
28 ms
loading.gif
43 ms
cb=gapi.loaded_0
15 ms
5IbuNoOZgHx.css
160 ms
VvsfEObxnnn.js
313 ms
LTv6ZK-5zxz.js
333 ms
1FCa-btixu2.js
302 ms
7BE0CZr3HTs.js
302 ms
pQrUxxo5oQp.js
316 ms
lbnyQhD5B8P.js
316 ms
Oagsvfb4VWi.js
319 ms
Q4A0UyjU8W2.js
316 ms
1bNoFZUdlYZ.js
317 ms
te_bk.gif
21 ms
12647143_1662233767349641_594999183708807859_n.jpg
352 ms
12548851_1662233047349713_8127063958469788485_n.png
389 ms
12592207_879090685542858_6110299930307857649_n.jpg
443 ms
12376654_940129689427904_2683799195617130871_n.jpg
470 ms
1947734_963626427062761_4595140186419432021_n.jpg
471 ms
12187662_1633962650189652_403360409819881161_n.jpg
441 ms
12552549_1740142006208542_8411393244350285083_n.jpg
468 ms
246776_193564304354829_4880717187803551791_n.jpg
490 ms
12038096_733005123501343_1146852427795795395_n.jpg
509 ms
12274580_1524950891152205_5095850712535868737_n.jpg
502 ms
12243080_1710376439243225_6680102102866679630_n.jpg
518 ms
12508849_886152884831608_6893869881077836585_n.jpg
536 ms
wL6VQj7Ab77.png
84 ms
s7jcwEQH7Sx.png
85 ms
12647143_1662233767349641_594999183708807859_n.jpg
433 ms
126 ms
115 ms
b53Ajb4ihCP.gif
45 ms
css;base64,
3 ms
Czh0gDTFcBt.css
66 ms
N-k91nHCZS2.css
57 ms
ZeuPykSxSED.css
43 ms
njO1TPvGzoR.js
54 ms
1QuX41zDRrx.js
68 ms
1464619_939852012799787_3415585573494481967_n.jpg
114 ms
12647143_1662233767349641_594999183708807859_n.jpg
136 ms
12548851_1662233047349713_8127063958469788485_n.png
423 ms
QDwYpIaRyfG.png
41 ms
K00K-UgnsKu.png
42 ms
I6-MnjEovm5.js
43 ms
s-6.png
24 ms
corpohumano.org SEO score
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Corpohumano.org can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Corpohumano.org 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.
corpohumano.org
Open Graph description is not detected on the main page of Corpo Humano. 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: