5.9 sec in total
1.3 sec
4 sec
592 ms
Visit headbody.com.br now to see the best up-to-date Head Body content for Brazil and also check out these interesting facts you probably never knew about headbody.com.br
Minha biblioteca de códigos web
Visit headbody.com.brWe analyzed Headbody.com.br page load time and found that the first response time was 1.3 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
headbody.com.br performance score
1289 ms
95 ms
89 ms
135 ms
28 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 26% of them (32 requests) were addressed to the original Headbody.com.br, 16% (19 requests) were made to Static.xx.fbcdn.net and 12% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Headbody.com.br.
Page size can be reduced by 54.2 kB (18%)
303.9 kB
249.6 kB
In fact, the total size of Headbody.com.br main page is 303.9 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. 70% of websites need less resources to load. Javascripts take 139.4 kB which makes up the majority of the site volume.
Potential reduce by 38.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 38.1 kB or 78% of the original size.
Potential reduce by 221 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. Head Body images are well optimized though.
Potential reduce by 15.9 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 15.9 kB or 11% of the original size.
Number of requests can be reduced by 59 (53%)
111
52
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Head Body. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
headbody.com.br
1289 ms
normalize.css
95 ms
style.css
89 ms
font-awesome.min.css
135 ms
css
28 ms
crayon.min.css
134 ms
sublime-text.css
100 ms
monaco.css
109 ms
style.css
104 ms
pagenavi-css.css
149 ms
jquery.js
299 ms
jquery-migrate.min.js
153 ms
crayon.min.js
225 ms
jquery.cookie.js
195 ms
app.css
200 ms
platform.js
69 ms
adsbygoogle.js
24 ms
jquery.min.js
35 ms
scripts.js
105 ms
wp-emoji-release.min.js
67 ms
ga.js
8 ms
__utm.gif
78 ms
Headbody
117 ms
bg-lat.jpg
168 ms
brand.png
116 ms
scroll_to-600x315.jpg
118 ms
instagram-600x315.jpg
162 ms
placeholder-820x461-600x315.jpg
160 ms
jquery-tabs.jpg
160 ms
contact.jpg
365 ms
851577_471200712947914_1651787391_n-600x315.jpg
279 ms
fadein-600x300.png
280 ms
wp3-update-admin-preview-featured-600x315.jpg
279 ms
Categorias-%E2%80%B9-HeadBody-%E2%80%94-WordPress-600x315.png
278 ms
17-checkbox-600x315.jpg
294 ms
widgets.js
8 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
8 ms
PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf
40 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
42 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
42 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
41 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
41 ms
fontawesome-webfont.woff
312 ms
github-btn.html
102 ms
more.png
284 ms
sdk.js
297 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
62 ms
bg.png
190 ms
blogheadbody
190 ms
cb=gapi.loaded_0
57 ms
cb=gapi.loaded_1
120 ms
fastbutton
172 ms
ca-pub-6773427059601663.js
156 ms
zrt_lookup.html
171 ms
show_ads_impl.js
61 ms
likebox.php
280 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
34 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
95 ms
fanclose.png
91 ms
ads
302 ms
postmessageRelay
99 ms
osd.js
50 ms
cb=gapi.loaded_0
39 ms
cb=gapi.loaded_1
39 ms
ads
269 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
31 ms
3193398744-postmessagerelay.js
53 ms
rpc:shindig_random.js
50 ms
85 ms
cb=gapi.loaded_0
6 ms
xd_arbiter.php
249 ms
xd_arbiter.php
434 ms
410ucuAGgaJ.css
330 ms
tSbl8xBI27R.css
385 ms
q68gy-v_YMF.js
525 ms
FJmpeSpHpjS.js
651 ms
0wM5s1Khldu.js
519 ms
1bNoFZUdlYZ.js
520 ms
m_js_controller.js
56 ms
abg.js
73 ms
googlelogo_color_112x36dp.png
83 ms
jot.html
3 ms
12527299028395710327
61 ms
favicon
92 ms
nessie_icon_thin_arrow_big_white.png
49 ms
s
35 ms
x_button_blue2.png
23 ms
redir.html
70 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
8 ms
iframe.html
28 ms
11178330_1445109859115872_1463916521944467647_n.jpg
356 ms
11150631_1445107079116150_431799290228726541_n.jpg
490 ms
11694794_10204326691277505_2908187000803835818_n.jpg
596 ms
11822539_428345737352726_5229650115554962964_n.jpg
559 ms
10277043_687510094630614_2287922637060242790_n.jpg
599 ms
734182_383181245122332_1329407371_n.jpg
584 ms
1910056_1130814323603237_2724487884815644153_n.jpg
559 ms
10665223_277223105809438_6695347517086391993_n.jpg
556 ms
12644954_583844991763256_6296606352953044627_n.jpg
626 ms
10806431_1504231023184116_2595752155477564957_n.jpg
625 ms
1958084_1738764519680351_4532775002559818079_n.jpg
628 ms
320545_299153863434563_1010633506_n.jpg
726 ms
wL6VQj7Ab77.png
77 ms
s7jcwEQH7Sx.png
76 ms
activeview
14 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
136 ms
ui
29 ms
like.php
97 ms
page.php
127 ms
jJhqmvSAXq3.js
289 ms
LVx-xkvaJ0b.png
69 ms
LUdypCgtRlc.css
71 ms
XoqZARH4OJa.js
209 ms
ihptErjAmMX.js
138 ms
11178330_1445109859115872_1463916521944467647_n.jpg
143 ms
10931257_770685929666703_5461902981955258403_n.jpg
69 ms
1928929_976762802406969_4271983412483806714_n.jpg
71 ms
R9a_DtVRZgv.js
71 ms
cUDgRFxaoIk.js
74 ms
0JBr1QHp8Gi.js
71 ms
kDOzhTr2W91.js
72 ms
headbody.com.br SEO score
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Headbody.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Headbody.com.br 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.
headbody.com.br
Open Graph data is detected on the main page of Head Body. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: