3.8 sec in total
221 ms
2.4 sec
1.2 sec
Visit fullflog.com now to see the best up-to-date Fullflog content and also check out these interesting facts you probably never knew about fullflog.com
Post anything (from anywhere!), customize everything, and find and follow what you love. Create your own Tumblr blog today.
Visit fullflog.comWe analyzed Fullflog.com page load time and found that the first response time was 221 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fullflog.com performance score
221 ms
70 ms
127 ms
42 ms
72 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fullflog.com, 8% (12 requests) were made to Static.xx.fbcdn.net and 6% (10 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (562 ms) relates to the external source 2.bp.blogspot.com.
Page size can be reduced by 541.3 kB (38%)
1.4 MB
882.2 kB
In fact, the total size of Fullflog.com main page is 1.4 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 626.2 kB which makes up the majority of the site volume.
Potential reduce by 81.5 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 81.5 kB or 73% of the original size.
Potential reduce by 11.2 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. Fullflog images are well optimized though.
Potential reduce by 246.0 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 246.0 kB or 57% of the original size.
Potential reduce by 202.7 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. Fullflog.com needs all CSS files to be minified and compressed as it can save up to 202.7 kB or 79% of the original size.
Number of requests can be reduced by 88 (68%)
129
41
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fullflog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.bloguinda.com
221 ms
3645911276-widget_css_bundle.css
70 ms
authorization.css
127 ms
plusone.js
42 ms
plusone.js
72 ms
brand
46 ms
show_ads.js
34 ms
widgets.js
37 ms
counter.js
32 ms
counter_xhtml.js
33 ms
3731899860-widgets.js
100 ms
brand
24 ms
cb=gapi.loaded_0
178 ms
ga.js
180 ms
all.js
177 ms
cb=gapi.loaded_1
171 ms
google_top_exp.js
169 ms
icon18_wrench_allbkg.png
170 ms
bloguinda-logo.png
160 ms
ca-pub-8822809618062357.js
277 ms
zrt_lookup.html
387 ms
show_ads_impl.js
265 ms
axonema-comentarios.png
257 ms
icon18_edit_allbkg.gif
305 ms
bloguinda-revisar-host-sitio-web.png
432 ms
bloguinda-facebook-logo-blue.jpg
345 ms
small.js
363 ms
t.php
383 ms
t.php
368 ms
benjamin-gonzalez-instituto-nacional-4to-medio.jpg
370 ms
bloguinda-line-up-lollapalooza-chile-2013.jpg
562 ms
bloguinda-pronostico-fin-del-mundo-21-dec.jpg
310 ms
bloguinda-ver-festival-lollapalooza-vivo-online.jpg
481 ms
axonema-etiquetas.png
187 ms
bloguindafb.png
236 ms
bloguinda-eliminar-cuenta-facebook.png
524 ms
axonema-proxima.png
385 ms
axonema-logo.png
385 ms
google_custom_search_watermark.gif
309 ms
load
323 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
232 ms
blank.html
147 ms
navbar.g
190 ms
__utm.gif
145 ms
ads
368 ms
osd.js
58 ms
172 ms
xd_arbiter.php
79 ms
xd_arbiter.php
131 ms
ads
316 ms
ads
331 ms
like.php
198 ms
blogger_index.js
113 ms
5OKR9RJB_vo
147 ms
ads
277 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.es.html
40 ms
icons_orange.png
124 ms
platform:gapi.iframes.style.common.js
66 ms
arrows-blue.png
133 ms
43 ms
info.json
162 ms
like.php
160 ms
like.php
157 ms
like.php
151 ms
like.php
162 ms
like.php
189 ms
like.php
202 ms
axonema-side.png
29 ms
dpx.js
24 ms
tpid=1EE704451E77EB56280395360284A18C
22 ms
count.js
72 ms
cb=gapi.loaded_0
11 ms
p
4 ms
dpx
35 ms
www-embed-player-vflfNyN_r.css
157 ms
www-embed-player.js
197 ms
base.js
278 ms
fastbutton
94 ms
aol
18 ms
qeKvIRsJabD.js
91 ms
LVx-xkvaJ0b.png
84 ms
count-data.js
160 ms
mapuser
25 ms
cb=gapi.loaded_0
15 ms
cb=gapi.loaded_1
21 ms
abg.js
36 ms
728.html
310 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
47 ms
jot
226 ms
63 ms
y_match
4 ms
match_redirect
3 ms
29931
32 ms
match_redirect
122 ms
tc.js
396 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
19 ms
ad_status.js
47 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
8 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
14 ms
tpid=C629559E1E77EB56D1234EAE02C81623
28 ms
lr
5 ms
tags.js
28 ms
150318.js
103 ms
lr.gif
6 ms
match_redirect
3 ms
sync
6 ms
match_redirect
3 ms
C629559E1E77EB56D1234EAE02C81623
36 ms
match_redirect
3 ms
ProfilesEngineServlet
8 ms
ProfilesEngineServlet
19 ms
tap.php
6 ms
exelate
4 ms
15 ms
38 ms
p
43 ms
16 ms
st
45 ms
spotx_match
3 ms
v2
48 ms
imp
95 ms
dpx
5 ms
ca.png
180 ms
xrefid.xgi
9 ms
fb_match
3 ms
u.php
76 ms
52154.gif
8 ms
c768cca1d7b9a390e883acc2085d8ad6.jpg
38 ms
an
3 ms
setuid
12 ms
lj_match
4 ms
merge
4 ms
cw_match
3 ms
rtset
28 ms
rb_match
3 ms
tap.php
4 ms
ox_match
3 ms
sd
5 ms
pm_match
3 ms
Pug
47 ms
pixel
26 ms
g_match
3 ms
match_redirect
6 ms
pixel
30 ms
aa_px
4 ms
306752634-lightbox_bundle.css
19 ms
4235943703-lbx__es.js
45 ms
page.php
111 ms
Ezryo55Cca5.css
6 ms
q68gy-v_YMF.js
4 ms
YvxwM8R7ol8.js
23 ms
ihptErjAmMX.js
22 ms
1526397_10153255079574170_2362136280888972700_n.png
62 ms
11133672_10153255071239170_6511267717525564628_n.png
28 ms
wL6VQj7Ab77.png
6 ms
s7jcwEQH7Sx.png
26 ms
R9a_DtVRZgv.js
6 ms
cUDgRFxaoIk.js
7 ms
0JBr1QHp8Gi.js
2 ms
kDOzhTr2W91.js
3 ms
fullflog.com SEO score
![]()
EN
![]()
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fullflog.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Fullflog.com 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.
fullflog.com
Open Graph description is not detected on the main page of Fullflog. 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: