14.3 sec in total
5.9 sec
8 sec
400 ms
Click here to check amazing Lgbtamigos content for Colombia. Otherwise, check out these important facts you probably never knew about lgbtamigos.com
$REGISTRANT1 $REGISTRANT2 $REGISTRANT3
Visit lgbtamigos.comWe analyzed Lgbtamigos.com page load time and found that the first response time was 5.9 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lgbtamigos.com performance score
5902 ms
83 ms
28 ms
28 ms
158 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 24% of them (39 requests) were addressed to the original Lgbtamigos.com, 16% (25 requests) were made to Static.xx.fbcdn.net and 7% (11 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Lgbtamigos.com.
Page size can be reduced by 1.4 MB (72%)
2.0 MB
556.2 kB
In fact, the total size of Lgbtamigos.com main page is 2.0 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. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 215.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 215.5 kB or 89% of the original size.
Potential reduce by 16.9 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. Lgbtamigos images are well optimized though.
Potential reduce by 764.1 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 764.1 kB or 74% of the original size.
Potential reduce by 429.1 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. Lgbtamigos.com needs all CSS files to be minified and compressed as it can save up to 429.1 kB or 88% of the original size.
Number of requests can be reduced by 105 (71%)
148
43
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lgbtamigos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
lgbtamigos.com
5902 ms
platform.js
83 ms
analytics.js
28 ms
shareaholic.js
28 ms
wp-emoji-release.min.js
158 ms
styles.css
190 ms
jquery.fancybox.min.css
162 ms
wp.css
193 ms
style.min.css
253 ms
default.min.css
380 ms
jquery.js
445 ms
jquery-migrate.min.js
339 ms
jquery.noconflict.min.js
308 ms
jquery.loadScript.min.js
345 ms
common.min.js
375 ms
collect
13 ms
dff4ba1a6828063b8c8cff4c93db887b.json
39 ms
collect
58 ms
buttons.js
11 ms
jquery.placeholder.min.js
112 ms
jquery.fancybox.pack.min.js
113 ms
jquery.form.min.js
423 ms
scripts.js
421 ms
wp-embed.min.js
341 ms
menus.min.js
419 ms
tooltipster.min.js
419 ms
selectnav.min.js
420 ms
dropkick.min.js
421 ms
jquery-ui-1.10.3.custom.min.js
504 ms
jquery.sharrre-1.3.4.min.js
601 ms
jquery.reveal.min.js
580 ms
countdown.min.js
580 ms
global.min.js
606 ms
collect
17 ms
header1.jpg
770 ms
images-2.jpe
699 ms
images-182x125.png
697 ms
hqdefault-1-182x125.jpg
698 ms
lgbt-182x125.jpeg
698 ms
SACER-182x125.jpg
697 ms
220px-Rainbow_flag_and_blue_skies-182x125.jpg
775 ms
seze-or-182x125.jpg
777 ms
descarga-182x125.jpg
774 ms
sdk.js
12 ms
bg.jpg
770 ms
sidebar-right-bg.png
763 ms
icons.png
827 ms
search-icon.png
832 ms
shrMain.min.js
27 ms
widgets.js
25 ms
76 ms
jquery.min.js
38 ms
xd_arbiter.php
38 ms
xd_arbiter.php
109 ms
pageview.gif
36 ms
partners.js
72 ms
sholic.js
60 ms
beacon.js
17 ms
cms-sh2c.html
57 ms
ping_match.gif
14 ms
eexelate.js
273 ms
323 ms
2964
265 ms
cb=gapi.loaded_0
97 ms
cb=gapi.loaded_1
127 ms
page
556 ms
getAllAppDefault.esi
491 ms
pixel
80 ms
rs
41 ms
ep
49 ms
page.php
116 ms
postmessageRelay
60 ms
75 ms
pixel
20 ms
match-result
54 ms
usermatch
362 ms
3193398744-postmessagerelay.js
37 ms
rpc:shindig_random.js
72 ms
IWXAbM4pe57.css
28 ms
whsuYM0JyRK.css
50 ms
7FmFP_Y-8Cu.css
59 ms
q68gy-v_YMF.js
96 ms
FJmpeSpHpjS.js
89 ms
0wM5s1Khldu.js
84 ms
LTv6ZK-5zxz.js
142 ms
1FCa-btixu2.js
86 ms
7BE0CZr3HTs.js
136 ms
pQrUxxo5oQp.js
134 ms
lbnyQhD5B8P.js
139 ms
Oagsvfb4VWi.js
139 ms
Q4A0UyjU8W2.js
204 ms
1bNoFZUdlYZ.js
207 ms
cm
199 ms
net.php
24 ms
pixel
89 ms
generic
91 ms
cb=gapi.loaded_0
249 ms
generic
210 ms
12311088_747576135346834_940479478857709721_n.jpg
383 ms
490 ms
311 ms
12342324_747572505347197_5230793298094758046_n.jpg
199 ms
wL6VQj7Ab77.png
81 ms
s7jcwEQH7Sx.png
101 ms
b53Ajb4ihCP.gif
98 ms
hbpix
796 ms
371 ms
349 ms
i.gif
343 ms
pixelssl.htm
359 ms
pixel.gif
264 ms
rs=AGLTcCNulDh4eHOSvtK1z1IXYn1IncL21w
110 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
122 ms
rs=AGLTcCMeIFon5rpW0He923g_P01S8K7amQ
158 ms
getSegment.php
262 ms
checkOAuth.esi
227 ms
crum
415 ms
photo.jpg
551 ms
portada-google%252B.jpg
417 ms
gplus-dd4b38-20.png
179 ms
pixel.gif
144 ms
rs=AGLTcCMeIFon5rpW0He923g_P01S8K7amQ
70 ms
xrefid.xgi
60 ms
pxj
77 ms
I6-MnjEovm5.js
71 ms
crum
285 ms
t.dhj
139 ms
rs=AGLTcCMeIFon5rpW0He923g_P01S8K7amQ
58 ms
pixel
32 ms
xrefid.xgi
8 ms
crum
227 ms
m
97 ms
ddcssl.htm
98 ms
crum
235 ms
t.dhj
65 ms
css;base64,
2 ms
mJ3scex-8ho.css
51 ms
eXhc6OJ3pgj.css
42 ms
yYGNrWyPiTw.css
32 ms
njO1TPvGzoR.js
32 ms
1QuX41zDRrx.js
48 ms
crum
205 ms
crum
182 ms
s-3271.xgi
38 ms
cm
43 ms
x35248
152 ms
hbpix
103 ms
12802942_120474835011205_2023805324540794812_n.jpg
65 ms
1480593_183308548723617_2599884558900745827_n.jpg
32 ms
10660096_163153664068213_7594050425573992444_n.jpg
47 ms
1379841_10150004552801901_469209496895221757_n.jpg
47 ms
12742079_824252874388048_3798499006896859012_n.jpg
50 ms
12311088_747576135346834_940479478857709721_n.jpg
167 ms
12342324_747572505347197_5230793298094758046_n.jpg
80 ms
QDwYpIaRyfG.png
29 ms
K00K-UgnsKu.png
24 ms
pixel
25 ms
52154.gif
14 ms
20 ms
2981
24 ms
24 ms
lgbtamigos.com SEO score
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lgbtamigos.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Lgbtamigos.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.
lgbtamigos.com
Open Graph data is detected on the main page of Lgbtamigos. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: