8.6 sec in total
134 ms
5.6 sec
3 sec
Welcome to complexogeek.com homepage info - get ready to check Complexo Geek best content for Brazil right away, or after learning these important things about complexogeek.com
Desperte o Geek dentro de você!
Visit complexogeek.comWe analyzed Complexogeek.com page load time and found that the first response time was 134 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
complexogeek.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value27.6 s
0/100
25%
Value13.8 s
1/100
10%
Value2,810 ms
3/100
30%
Value0.025
100/100
15%
Value23.1 s
1/100
10%
134 ms
20 ms
54 ms
88 ms
90 ms
Our browser made a total of 208 requests to load all elements on the main page. We found that 13% of them (26 requests) were addressed to the original Complexogeek.com, 10% (21 requests) were made to Apis.google.com and 9% (19 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Adclient.siga.uol.com.br.
Page size can be reduced by 991.7 kB (20%)
5.0 MB
4.0 MB
In fact, the total size of Complexogeek.com main page is 5.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. 85% 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.5 MB which makes up the majority of the site volume.
Potential reduce by 88.1 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 88.1 kB or 82% of the original size.
Potential reduce by 25.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. Complexo Geek images are well optimized though.
Potential reduce by 413.8 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 413.8 kB or 53% of the original size.
Potential reduce by 464.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. Complexogeek.com needs all CSS files to be minified and compressed as it can save up to 464.1 kB or 83% of the original size.
Number of requests can be reduced by 94 (47%)
198
104
The browser has sent 198 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Complexo Geek. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 69 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
complexogeek.com
134 ms
webfont.js
20 ms
fbstyle.css
54 ms
pagenavi-css.css
88 ms
style.css
90 ms
style.css
88 ms
jquery.js
153 ms
jquery-migrate.min.js
103 ms
graphene.js
103 ms
adsbygoogle.js
8 ms
adwup.js
146 ms
embed.js
24 ms
css
25 ms
gTHiwyxi6S7iiHpqAoiE3NqQynqKV_9Plp7mupa0S4g.ttf
98 ms
widgets.js
100 ms
plusone.js
191 ms
ga.js
79 ms
all.js
145 ms
lt3WUtq9kIs
184 ms
9HBTeP22nkA
268 ms
nkQ-ij3LTTM
301 ms
444 ms
tRAD3UT.jpg
96 ms
5uwbS1B.jpg
96 ms
b6z7XYn.png
130 ms
DvXiU.png
170 ms
Vuled.jpg
169 ms
JcJks.png
168 ms
7xTlWcn.png
169 ms
naDt7.png
196 ms
Scx44.png
168 ms
SN4fNSY.jpg
250 ms
mHbf4.jpg
195 ms
GfTDU.png
195 ms
lDKdI.png
249 ms
Background-21.jpg
443 ms
Header.png
1033 ms
sprite_h.png
94 ms
sprite_master.png
94 ms
Hist%C3%B3ria-Casal-Pra-Sempre.jpg
811 ms
XcomScum.jpg
1034 ms
Enguia.jpg
727 ms
N%C3%A3o-Intendo.jpg
166 ms
ahnegao.jpg
246 ms
Fail-Wars.jpg
291 ms
insoonia.jpg
441 ms
Rock-n-Tech.jpg
506 ms
nao-pode-rir-2.png
507 ms
Amigos-do-F%C3%B3rum.png
579 ms
Cotovelo-de-Formiga.jpg
566 ms
blogdoBraian.jpg
829 ms
otaku-cabeludo.png
810 ms
ca-pub-2841862043605093.js
170 ms
zrt_lookup.html
167 ms
show_ads_impl.js
70 ms
likebox.php
234 ms
__utm.gif
53 ms
ads
317 ms
osd.js
67 ms
89 ms
xd_arbiter.php
131 ms
xd_arbiter.php
282 ms
www-embed-player-vflZsBgOl.css
142 ms
www-embed-player.js
282 ms
base.js
426 ms
cb=gapi.loaded_0
50 ms
cb=gapi.loaded_1
80 ms
fastbutton
121 ms
fastbutton
117 ms
fastbutton
109 ms
fastbutton
172 ms
fastbutton
171 ms
fastbutton
173 ms
postmessageRelay
243 ms
roNeOY-tz5Y.css
256 ms
UHhaxo8Cs3k.css
299 ms
_rx8naC75Dy.js
529 ms
x5F9OMjKyLw.js
571 ms
ICDbTSzjQEg.js
564 ms
TTCre3391I0.js
564 ms
www-embed-player-vflQrT_sR.css
200 ms
www-embed-player.js
228 ms
base.js
441 ms
rs=AGLTcCNqicBbTRy2Ny4TeyhsrBuZucE7Kg
71 ms
cb=gapi.loaded_0
115 ms
cb=gapi.loaded_1
110 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
149 ms
sas-browser.js
646 ms
api.js
37 ms
core:rpc:shindig.random:shindig.sha1.js
328 ms
2536007149-postmessagerelay.js
223 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
234 ms
ad_status.js
234 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
125 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
125 ms
12717905_1269209863096212_6310414856785050323_n.png
186 ms
385138_363012123715995_322502749_n.jpg
205 ms
10710620_594860550646580_6971103096469532743_n.jpg
290 ms
10264_655425517931191_7349530376043327119_n.jpg
365 ms
12019896_810573635728491_5177839833482737748_n.jpg
259 ms
1916735_613129435505774_4188089983783669448_n.jpg
234 ms
11811396_1663402887236309_3749671496315248285_n.jpg
263 ms
12592777_1549890345302211_8018585018045855749_n.jpg
302 ms
wL6VQj7Ab77.png
43 ms
s7jcwEQH7Sx.png
42 ms
sas-dom.js
1001 ms
I6-MnjEovm5.js
24 ms
vlXaquuXMrr.js
17 ms
sas-banner-2.2.js
619 ms
teste.html
313 ms
iframe.html
302 ms
platform.js
290 ms
_.gif
284 ms
bb_viewability.min.js
88 ms
list
236 ms
teste.html
81 ms
uolaf.js
705 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
65 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
65 ms
cb=gapi.loaded_2
85 ms
page
129 ms
graph.facebook.com
370 ms
syndication
380 ms
565687691803889666
524 ms
like.php
69 ms
share_button.php
68 ms
share_button.php
145 ms
like.php
319 ms
share_button.php
139 ms
like.php
326 ms
like.php
323 ms
share_button.php
315 ms
tweet_button.6a78875565a912489e9aef879c881358.pt.html
102 ms
like.php
299 ms
share_button.php
299 ms
share_button.php
353 ms
like.php
360 ms
rs=AGLTcCOIysoEmtW85aiKIBLdKHmHc4_EPw
83 ms
rs=AGLTcCOP6COjm_DFOSfBgSnJyl5PUX2hyw
114 ms
rs=AGLTcCNX5-cl7K4LC02TMdakqhaXIV0yHA
149 ms
L70CG02Crze.js
307 ms
LVx-xkvaJ0b.png
100 ms
L70CG02Crze.js
270 ms
beacon.js
84 ms
tm11750.js
443 ms
user_sync.html
275 ms
widget.css
239 ms
embed_enabler.min.js
248 ms
photo.jpg
478 ms
Shingeki.jpg
478 ms
L70CG02Crze.js
247 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
180 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
195 ms
rs=AGLTcCNX5-cl7K4LC02TMdakqhaXIV0yHA
100 ms
L70CG02Crze.js
230 ms
L70CG02Crze.js
247 ms
L70CG02Crze.js
240 ms
bbbeacon-icon-transparent.png
240 ms
300x250.html
355 ms
showad.js
196 ms
rs=AGLTcCNX5-cl7K4LC02TMdakqhaXIV0yHA
222 ms
L70CG02Crze.js
240 ms
L70CG02Crze.js
303 ms
PugMaster
139 ms
format9_g.html
682 ms
format9_g.html
1085 ms
format9_g.html
1083 ms
format9_g.html
1086 ms
format9_g.html
1082 ms
format9_g.html
1082 ms
universalpixel.js
85 ms
usr
122 ms
pixel
65 ms
Pug
59 ms
usersync.aspx
67 ms
221F214E-26C9-4582-AAA7-3E3C7E56989E
70 ms
runtime.js
138 ms
embed_triggers.min.js
57 ms
UPug
84 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
42 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
49 ms
Pug
69 ms
Pug
50 ms
Pug
51 ms
_.gif
66 ms
IAiiNniL_normal.jpeg
187 ms
req
147 ms
PWl_sGVB_normal.jpg
208 ms
CcZ3RSwWIAEVBNh.jpg:small
247 ms
CcZcMdcW8AEWLCT.jpg:small
278 ms
CcZIggMWwAEvy9W.jpg:small
289 ms
CcXUyqhWEAAvqYT.jpg:small
302 ms
CcW_CS9XIAAjE4X.jpg:small
304 ms
CcW6CS4WEAAHULI.jpg:small
305 ms
pixel.js
46 ms
Pug
30 ms
Pug
106 ms
dpsync.html
97 ms
Pug
90 ms
req
76 ms
06282699185698565
304 ms
req
35 ms
blp.css
399 ms
gen.js
663 ms
fb.js
803 ms
jot.html
2 ms
uolsigainit.min.js
725 ms
uolsigaretarget.min.js
727 ms
complexogeek.com 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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
complexogeek.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
complexogeek.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Complexogeek.com 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 Complexogeek.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.
complexogeek.com
Open Graph data is detected on the main page of Complexo Geek. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: