12.5 sec in total
407 ms
11.7 sec
377 ms
Welcome to dilma.pt homepage info - get ready to check Dilma best content right away, or after learning these important things about dilma.pt
História de Nossa Senhora Aparecida
Visit dilma.ptWe analyzed Dilma.pt page load time and found that the first response time was 407 ms and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
dilma.pt performance score
407 ms
605 ms
182 ms
223 ms
267 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dilma.pt, 66% (67 requests) were made to Static.xx.fbcdn.net and 28% (28 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 251.8 kB (13%)
1.9 MB
1.7 MB
In fact, the total size of Dilma.pt main page is 1.9 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 235.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 235.3 kB or 80% of the original size.
Potential reduce by 16.6 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. Dilma images are well optimized though.
Number of requests can be reduced by 60 (61%)
99
39
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dilma. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
dilma.pt
407 ms
blogdilmabr
605 ms
IWXAbM4pe57.css
182 ms
_WYx8qAOsiF.css
223 ms
whsuYM0JyRK.css
267 ms
wmiz7xzFfqO.css
338 ms
OJcLXXE4bYe.css
305 ms
eDKl-ra6OP1.css
300 ms
aDk70ZHFIl3.css
308 ms
yq2wLTItbV0.css
305 ms
yYGNrWyPiTw.css
358 ms
vR0pLYWj618.css
352 ms
v_An6I20hBD.css
356 ms
h3AvqLq2os9.css
365 ms
eXhc6OJ3pgj.css
360 ms
FubXyyslphg.css
375 ms
BViiCxy-W5p.css
382 ms
UBsaA5Ft-O6.css
379 ms
dcnr_H-EB5r.css
383 ms
q68gy-v_YMF.js
422 ms
LXQaqfwANV7.png
74 ms
event
117 ms
12241450_1104393996289485_5927808852655964058_n.png
542 ms
safe_image.php
244 ms
12507681_1140550416007176_3568579398834486684_n.png
548 ms
10352289_1178468528882031_6070545274296361778_n.png
596 ms
10399952_1174563409272543_1317318460723846084_n.png
648 ms
10347620_1174424385953112_485842312121931500_n.png
647 ms
1914057_1174342689294615_7822718930745841855_n.png
645 ms
3386_1174261242636093_6715135469178172073_n.png
649 ms
64923_1174226992639518_6548650523956910052_n.png
650 ms
12821363_1173360342726183_8283712101326632569_n.png
627 ms
10330315_1173008892761328_458634056259132173_n.png
667 ms
12832354_1172816909447193_4264422117907381297_n.png
724 ms
12720024_1178526955542855_756073814_n.jpg
687 ms
12109365_1178224075573143_743576650_n.jpg
688 ms
12719897_1177355312326686_2106126243_n.jpg
694 ms
1610042_219435774923161_99226127_n.jpg
693 ms
12507681_1140550416007176_3568579398834486684_n.png
706 ms
7677_693493330793106_7527947906847433592_n.png
1002 ms
10351586_1207099665968286_4166584694888362282_n.png
923 ms
10494714_1207061985972054_5083346516646971531_n.png
771 ms
12321273_693387507470355_5843773176003217656_n.png
1013 ms
ZVyMWStefv_.png
51 ms
K00K-UgnsKu.png
51 ms
wL6VQj7Ab77.png
49 ms
ZrLxvLoiUzX.png
48 ms
GsNJNwuI-UM.gif
47 ms
spacer.gif
21 ms
UHNY_g5mVbr.js
42 ms
FJmpeSpHpjS.js
120 ms
hbybLXHu6w1.js
50 ms
Oagsvfb4VWi.js
81 ms
1FCa-btixu2.js
88 ms
remhd19g416.js
50 ms
1bNoFZUdlYZ.js
87 ms
_UYztdBNTjs.js
90 ms
7BE0CZr3HTs.js
148 ms
IjqSyiwKeaX.js
148 ms
RTHSWgdzleR.js
150 ms
eR-qA8bp1RM.js
149 ms
LTv6ZK-5zxz.js
260 ms
VfAud2trIQQ.js
196 ms
-7JBD_ybv4q.js
239 ms
Kt4tkgSRvHH.js
164 ms
pQrUxxo5oQp.js
201 ms
H3EKDTObx05.js
167 ms
J0ZuTxeV0vD.js
206 ms
bh5z0Gfv2P_.js
208 ms
njEKf1WUXml.js
259 ms
1QuX41zDRrx.js
259 ms
yMCR4PoU6B-.js
260 ms
7uWMMev-gdj.js
261 ms
yBzWdmXwoNV.js
374 ms
jn5cerRXiQf.js
375 ms
yXuA_dMgOm6.js
374 ms
c05laeT1OPx.js
375 ms
-sVccfRXDIY.js
377 ms
UiJCRDQUmbL.js
378 ms
450NBOJyjOf.js
377 ms
geAvKyblz0A.png
376 ms
l5aPruN9xMM.png
377 ms
YGgz9e4B0yW.png
376 ms
ZYpT1aFajd7.png
376 ms
MiXXTBbOQzg.png
376 ms
117 ms
F1Xohf2RB95.png
62 ms
12243230_1316111458402381_538832939157167992_n.jpg
259 ms
1936039_1698132363789381_6285559314258974401_n.jpg
277 ms
946787_380566815477206_2097976234295429240_n.jpg
299 ms
12809557_957538734329910_8959533803623469817_n.jpg
319 ms
1928851_10206373754314947_698284175428852248_n.jpg
326 ms
12274199_1683782068501259_6926027922887387036_n.jpg
372 ms
11218470_968282789904578_3824254087093657348_n.jpg
393 ms
10354686_10150004552801856_220367501106153455_n.jpg
365 ms
I6-MnjEovm5.js
41 ms
Dppan5o6UJu.js
44 ms
8v2_hdH4Nfm.js
45 ms
-Tr757ZEtMP.js
122 ms
A0qdgknEnD5.js
45 ms
-PAXP-deijE.gif
47 ms
dilma.pt SEO score
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dilma.pt 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 Dilma.pt 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.
dilma.pt
Open Graph description is not detected on the main page of Dilma. 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: