7.4 sec in total
1.8 sec
5.3 sec
338 ms
Welcome to tucuna.com.br homepage info - get ready to check Tucuna best content for Brazil right away, or after learning these important things about tucuna.com.br
Visit tucuna.com.brWe analyzed Tucuna.com.br page load time and found that the first response time was 1.8 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tucuna.com.br performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value2.5 s
89/100
25%
Value4.9 s
65/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.5 s
98/100
10%
1816 ms
26 ms
278 ms
272 ms
275 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 50% of them (67 requests) were addressed to the original Tucuna.com.br, 14% (19 requests) were made to Static.xx.fbcdn.net and 10% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Tucuna.com.br.
Page size can be reduced by 801.6 kB (25%)
3.3 MB
2.5 MB
In fact, the total size of Tucuna.com.br main page is 3.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. 75% 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 2.4 MB which makes up the majority of the site volume.
Potential reduce by 43.2 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 43.2 kB or 79% of the original size.
Potential reduce by 164.8 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. Tucuna images are well optimized though.
Potential reduce by 330.2 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 330.2 kB or 63% of the original size.
Potential reduce by 263.5 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. Tucuna.com.br needs all CSS files to be minified and compressed as it can save up to 263.5 kB or 82% of the original size.
Number of requests can be reduced by 65 (51%)
127
62
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tucuna. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
tucuna.com.br
1816 ms
css
26 ms
style.css
278 ms
styles.css
272 ms
responsive-videos.css
275 ms
lightbox.min.css
280 ms
shortcodes.css
419 ms
jquery.fancybox-1.3.4.css
281 ms
page_templates.css
407 ms
jquery.js
822 ms
jquery-migrate.min.js
413 ms
et_shortcodes_frontend.js
414 ms
style.css
912 ms
show_ads.js
9 ms
jquery.cycle.all.min.js
676 ms
jquery.easing.1.3.js
548 ms
superfish.js
551 ms
script.js
1410 ms
functional.css
688 ms
admin-ajax.php
1037 ms
jquery.form.min.js
810 ms
scripts.js
836 ms
wp-lightbox-2.min.js
959 ms
jquery.easing-1.3.pack.js
959 ms
jquery.fancybox-1.3.4.pack.js
1029 ms
et-ptemplates-frontend.js
1057 ms
slideshow.min.js
1133 ms
track
19 ms
dc.js
54 ms
f.png
2182 ms
tu.png
491 ms
flash.jpg
1270 ms
Sem-T%C3%ADtulo-1.jpg
1485 ms
teste.jpg
1231 ms
flash-272888_49x49.jpg
570 ms
Sem-T%C3%ADtulo-1-338408_49x49.jpg
632 ms
teste-344582_49x49.jpg
746 ms
cadastro.png
816 ms
isca1-223522_292x155.jpg
895 ms
2-396262_292x155.jpg
1169 ms
0000000546-111334_292x155.jpg
1166 ms
0000000358-98591_292x155.jpg
1228 ms
11258466_10205140055238489_8897279655474454199_n-117681_292x155.jpg
1283 ms
california-108528_292x155.jpg
1434 ms
lo1.png
1383 ms
lo2.png
1411 ms
map.png
1428 ms
lo3.png
1508 ms
lo4.png
1553 ms
cc.png
1572 ms
saint.png
1576 ms
joga.png
1629 ms
lo6.png
1647 ms
asss.png
1696 ms
YARINHA.png
1853 ms
PURINHA.png
1723 ms
lo8.png
1774 ms
ca-pub-1418825338050065.js
208 ms
zrt_lookup.html
202 ms
show_ads_impl.js
127 ms
lo7.png
1744 ms
deph.png
1794 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
78 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
75 ms
22.jpg
1814 ms
__utm.gif
31 ms
ajax-loader.gif
1824 ms
JEgcALMEMhM
141 ms
featured-left.png
1823 ms
controller-bg-active.png
1845 ms
ads
283 ms
osd.js
10 ms
likebox.php
285 ms
controller-bg.png
1780 ms
www-embed-player-vflfNyN_r.css
45 ms
www-embed-player.js
69 ms
base.js
96 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
92 ms
ad_status.js
96 ms
m_js_controller.js
145 ms
abg.js
154 ms
featured-right.png
1520 ms
hDvwL1_H7g-.css
210 ms
56WNbrUYLbL.css
246 ms
yZ--Yu0PDbV.css
317 ms
QD6_ejUFoCN.css
361 ms
q68gy-v_YMF.js
361 ms
FJmpeSpHpjS.js
394 ms
0wM5s1Khldu.js
344 ms
1bNoFZUdlYZ.js
343 ms
njO1TPvGzoR.js
343 ms
1QuX41zDRrx.js
393 ms
Oagsvfb4VWi.js
406 ms
LTv6ZK-5zxz.js
544 ms
1FCa-btixu2.js
392 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
77 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
80 ms
hr2-bg.png
1605 ms
all.js
159 ms
iframe_api
101 ms
footer.png
1523 ms
www-widgetapi.js
9 ms
light-arrows.png
1510 ms
googlelogo_color_112x36dp.png
62 ms
nessie_icon_tiamat_white.png
54 ms
s
42 ms
x_button_blue2.png
33 ms
111 ms
xd_arbiter.php
139 ms
xd_arbiter.php
222 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
31 ms
11081213_946026968755608_7975082136862353332_n.jpg
111 ms
534312_431387120219598_1573532133_n.jpg
124 ms
1918091_168761153510708_7622667215145218514_n.jpg
205 ms
11949451_515421235282788_8671187017892222034_n.jpg
157 ms
12278655_101267890242493_3232111641710080599_n.jpg
159 ms
1463564_1688401138115265_470393921842496725_n.jpg
196 ms
12800320_1044656808929363_5992864989257702991_n.jpg
182 ms
535086_189317874789301_1835174250523772127_n.jpg
157 ms
10590645_1137078022983834_5682116780947215802_n.jpg
192 ms
1005813_1136146003077036_8140329864997429832_n.jpg
190 ms
10435700_1135510606473909_7051715265653297927_n.jpg
190 ms
1175756_1134720953219541_7968628488180065512_n.jpg
216 ms
12799359_1131284526896517_1225662560917642229_n.jpg
209 ms
wL6VQj7Ab77.png
62 ms
s7jcwEQH7Sx.png
63 ms
QDwYpIaRyfG.png
62 ms
K00K-UgnsKu.png
62 ms
I6-MnjEovm5.js
20 ms
pQrUxxo5oQp.js
34 ms
activeview
15 ms
featured-overlay.png
263 ms
lk.png
328 ms
hr-bg.png
322 ms
ui
14 ms
tucuna.com.br accessibility score
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
Document doesn't have a <title> element
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
tucuna.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
tucuna.com.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tucuna.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Tucuna.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.
tucuna.com.br
Open Graph description is not detected on the main page of Tucuna. 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: