3.6 sec in total
110 ms
2.7 sec
841 ms
Welcome to juanfrank.com homepage info - get ready to check Juanfrank best content right away, or after learning these important things about juanfrank.com
Experto en comunicación estratégica y marketing digital conmás de 10 años de experiencia
Visit juanfrank.comWe analyzed Juanfrank.com page load time and found that the first response time was 110 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
juanfrank.com performance score
110 ms
116 ms
45 ms
94 ms
51 ms
Our browser made a total of 176 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Juanfrank.com, 10% (18 requests) were made to Um.simpli.fi and 7% (13 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (708 ms) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 962.8 kB (22%)
4.4 MB
3.4 MB
In fact, the total size of Juanfrank.com main page is 4.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. 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 3.3 MB which makes up the majority of the site volume.
Potential reduce by 240.4 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 240.4 kB or 79% of the original size.
Potential reduce by 269.0 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. Juanfrank images are well optimized though.
Potential reduce by 453.4 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 453.4 kB or 56% of the original size.
Potential reduce by 79 B
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. Juanfrank.com has all CSS files already compressed.
Number of requests can be reduced by 74 (51%)
146
72
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Juanfrank. 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 7 to 1 for CSS and as a result speed up the page load time.
juanfrank.com
110 ms
www.juanfrank.com
116 ms
3645911276-widget_css_bundle.css
45 ms
authorization.css
94 ms
css
51 ms
recent_comments_widget.js
111 ms
element.js
52 ms
pagenavigation.txt.js
32 ms
addthis_widget.js
32 ms
claim.js
45 ms
memo.php
151 ms
3226477086-widgets.js
35 ms
plusone.js
69 ms
headbg.jpg
44 ms
logo%2B3.png
49 ms
all.js
307 ms
sprites.png
38 ms
freelance.jpg
70 ms
estrategia%2Bde%2Bventas%2Bonline.jpg
84 ms
05-12-2014%2B09-00-32%2Bp.m..png
66 ms
BENEFICIOS-DEL-MEGAPUBLICADOR%2Btrafico%2Bgratis.png
202 ms
grafico-de-comisiones%2Bmegapublicador.png
239 ms
728-x-90.jpg
37 ms
work-from-home%2B(1).jpg
84 ms
Negocios-Multinivel.jpg
198 ms
multinivel%2Bmlm%2Brobert%2Bkiyosaki.png
65 ms
large-getaccessnow.png
85 ms
LPM-demos1200.gif
68 ms
megapublicador-1024x745.png
188 ms
19-09-2014%2B12-06-29%2Ba.m..png
74 ms
14-10-2014%2B11-45-04%2Bp.m..png
170 ms
21-10-2014%2B02-42-22%2Bp.m..png
195 ms
icon18_wrench_allbkg.png
26 ms
ganar-dinero-con-facebook.jpg
38 ms
boton-quiero-saber-mas.png
46 ms
facebook%2Btornado.png
154 ms
300-x-6001.jpg
66 ms
fb%2Btornado.png
69 ms
large-getaccessnow.png
45 ms
19-01-2014%2B05-48-33%2Bmod%2Bp.m..png
170 ms
reporte%2Bgratis.jpg
49 ms
banner%2Bvertical%2Bkalatu.png
171 ms
trafico%2Bfacebook.jpg
53 ms
PAYONEER-Banner-tarjeta.gif
62 ms
noavatar92.png
158 ms
dc.js
62 ms
translateelement.css
179 ms
main.js
216 ms
avatar92.jpg
154 ms
avatar92.jpg
152 ms
avatar92.jpg
161 ms
blogger_index.js
149 ms
88x31.png
149 ms
__utm.gif
33 ms
cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff
24 ms
MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff
43 ms
xkvoNo9fC8O2RDydKj12b73hpw3pgy2gAi-Ip7WPMi0.woff
65 ms
-_Ctzj9b56b8RgXW8FArib3hpw3pgy2gAi-Ip7WPMi0.woff
65 ms
count.js
54 ms
classic.js
208 ms
sprite.png
25 ms
widgets.js
209 ms
summary
85 ms
xjAJXh38I15wypJXxuGMBrrIa-7acMAeDBVuclsi6Gc.woff
19 ms
cb=gapi.loaded_0
7 ms
count-data.js
167 ms
element_main.js
63 ms
106 ms
xd_arbiter.php
305 ms
xd_arbiter.php
510 ms
1653531643.js
70 ms
css
41 ms
8 ms
dpx.js
33 ms
tpid=1DE70445C908EE562B03153702A0BDA6
30 ms
note0.png
96 ms
p
6 ms
fKV8XYuRNNagXr38eqbRf8-ortBJrX8dG4H9Ox7zsWc.woff
6 ms
load
512 ms
300lo.json
27 ms
dpx
6 ms
sh.8e5f85691f9aaa082472a194.html
32 ms
aol
9 ms
layers.e5ea973510bf60b3db41.js
12 ms
like_box.php
208 ms
mapuser
43 ms
pixel
53 ms
48 ms
pixel
25 ms
rs
7 ms
match-result
46 ms
y_match
5 ms
tc.js
8 ms
match_redirect
7 ms
p
64 ms
ebiMDO3r-8l.css
289 ms
jGc-59L_9lo.css
357 ms
q68gy-v_YMF.js
496 ms
FJmpeSpHpjS.js
626 ms
0wM5s1Khldu.js
493 ms
1bNoFZUdlYZ.js
494 ms
29931
18 ms
match_redirect
3 ms
tpid=DA29559EC908EE56CB48DD0402B8BC4A
52 ms
translate_24dp.png
32 ms
l
53 ms
lr
5 ms
v2
49 ms
lr.gif
7 ms
sync
21 ms
match_redirect
4 ms
DA29559EC908EE56CB48DD0402B8BC4A
36 ms
dpx
4 ms
xrefid.xgi
9 ms
ca.png
167 ms
exelate
2 ms
44 ms
36 ms
34 ms
spotx_match
3 ms
fb_match
4 ms
u.php
14 ms
an
4 ms
lj_match
3 ms
merge
5 ms
cw_match
4 ms
52154.gif
5 ms
rtset
19 ms
rb_match
2 ms
tap.php
7 ms
ox_match
3 ms
sd
24 ms
pm_match
6 ms
Pug
45 ms
pixel
80 ms
12802900_956152251121805_5218268215796433786_n.png
503 ms
12803033_956160744454289_2912456712538318727_n.png
566 ms
1395383_10153453249665403_1632719281_n.jpg
634 ms
10295749_757956720902122_1319585233025712836_n.jpg
701 ms
10371970_100726003659018_5264708749732529786_n.jpg
702 ms
12239689_1668671346710223_3032090978647348797_n.jpg
708 ms
1621660_595103043951702_1209367466237183144_n.jpg
706 ms
10471184_10153264296741723_7456039787418354100_n.jpg
704 ms
wL6VQj7Ab77.png
176 ms
s7jcwEQH7Sx.png
175 ms
g_match
131 ms
views2.json
211 ms
widgets.js
184 ms
fastbutton
163 ms
match_redirect
98 ms
cb=gapi.loaded_0
64 ms
cb=gapi.loaded_1
66 ms
xZQOmYg4x3YaWkTJi1kErvesZW2xOQ-xsNqO47m55DA.woff
163 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
61 ms
pixel
166 ms
ganar-dinero-con-facebook.jpg
74 ms
14-10-2014%2B11-45-04%2Bp.m..png
200 ms
megapublicador-1024x745.png
198 ms
BIMLatino2.jpg
74 ms
share_button.php
125 ms
share_button.php
145 ms
share_button.php
137 ms
share_button.php
140 ms
share_button.php
131 ms
share_button.php
127 ms
share_button.php
134 ms
share_button.php
163 ms
share_button.php
158 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
72 ms
share_button.php
130 ms
aa_px
48 ms
qeKvIRsJabD.js
273 ms
LVx-xkvaJ0b.png
69 ms
jot.html
28 ms
I6-MnjEovm5.js
123 ms
pQrUxxo5oQp.js
124 ms
juanfrank.com SEO score
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Juanfrank.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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 Juanfrank.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.
juanfrank.com
Open Graph description is not detected on the main page of Juanfrank. 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: