4.2 sec in total
600 ms
2.7 sec
905 ms
Visit geekbr.com now to see the best up-to-date Geekbr content and also check out these interesting facts you probably never knew about geekbr.com
Visit geekbr.comWe analyzed Geekbr.com page load time and found that the first response time was 600 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. This domain responded with an error, which can significantly jeopardize Geekbr.com rating and web reputation
geekbr.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.1 s
46/100
25%
Value4.1 s
79/100
10%
Value750 ms
39/100
30%
Value0.081
94/100
15%
Value6.8 s
55/100
10%
600 ms
94 ms
142 ms
118 ms
26 ms
Our browser made a total of 197 requests to load all elements on the main page. We found that 23% of them (46 requests) were addressed to the original Geekbr.com, 11% (21 requests) were made to Apis.google.com and 7% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (863 ms) relates to the external source Cdvagabundo.com.br.
Page size can be reduced by 699.8 kB (34%)
2.0 MB
1.3 MB
In fact, the total size of Geekbr.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. 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 74.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 74.5 kB or 78% of the original size.
Potential reduce by 61.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. Geekbr images are well optimized though.
Potential reduce by 314.3 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 314.3 kB or 60% of the original size.
Potential reduce by 249.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. Geekbr.com needs all CSS files to be minified and compressed as it can save up to 249.7 kB or 84% of the original size.
Number of requests can be reduced by 84 (49%)
173
89
The browser has sent 173 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geekbr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
geekbr.com
600 ms
style.css
94 ms
font-awesome.min.css
142 ms
fontello.css
118 ms
css
26 ms
css
39 ms
css
49 ms
css
47 ms
css
49 ms
jetpack.css
171 ms
fbseo-style.css
165 ms
wpcomments.css
190 ms
thickbox.min.css
188 ms
jquery.js
283 ms
jquery-migrate.min.js
214 ms
q2w3-fixed-widget.min.js
215 ms
jquery.flexslider-min.js
255 ms
jquery.fitvids.js
226 ms
jquery.easing.1.3.js
238 ms
thickbox.min.js
260 ms
blue.css
263 ms
adsbygoogle.js
17 ms
spd_display
227 ms
ad.js
59 ms
counter.js
15 ms
lyte-min.js
204 ms
mediaelementplayer.min.css
285 ms
wp-mediaelement.css
286 ms
devicepx-jetpack.js
4 ms
modernizr.js
307 ms
jquery.prettyPhoto.js
306 ms
jquery.cycle.all.min.js
306 ms
custom.js
306 ms
jquery.hoverIntent.minified.js
306 ms
jquery.placeholder.js
304 ms
cherry-scripts.js
401 ms
counter.asp
6 ms
mediaelement-and-player.min.js
426 ms
wp-mediaelement.js
385 ms
e-201611.js
5 ms
banner-rnt_125x125.jpg
185 ms
magnatas_80x80px.jpg
185 ms
80X80-2.jpg
212 ms
80x80.png
554 ms
bannergamedev150.gif
581 ms
banner60x60.jpg
631 ms
parceria4.jpg
863 ms
YXrKaBV.png
144 ms
fq0e.jpg
618 ms
google-pr-9d95dAZ0-18-3.gif
77 ms
bg_1.jpg
209 ms
search-button.png
208 ms
logo_geekbr.png
292 ms
blue.png
246 ms
bg-2.png
292 ms
author_link.png
551 ms
post_date.png
555 ms
10506811_783471688369571_1417739590127268779_o.png
863 ms
1911245_780480815335325_226163069228132914_o.jpg
631 ms
pFWoZ4K.jpg
630 ms
100x100.png
765 ms
madjoystick.jpg
710 ms
Sem+T%C3%ADtulo-3.png
716 ms
geeks-of-war-80x80.png
548 ms
GeekWalks80x80.png
206 ms
banner80x80.jpg
207 ms
nerdsvszombies.jpg
178 ms
banner-tdb.png
547 ms
arenageek.jpg
627 ms
bloggamworld.jpg
629 ms
selo_geekit_100-100.jpg
625 ms
80x80LOGO.jpg
627 ms
logohvl.png
628 ms
1323.png
706 ms
back80x80.png
714 ms
plusone.js
268 ms
AWM5wXtMJeRP-AcRTgT4qQ.ttf
49 ms
l1cOQ90roY9yC7voEhngDKCWcynf_cDxXwCLxiixG1c.ttf
115 ms
dI-qzxlKVQA6TUC5RKSb36CWcynf_cDxXwCLxiixG1c.ttf
154 ms
IgZJs4-7SA1XX_edsoXWog.ttf
154 ms
DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf
265 ms
MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf
181 ms
k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf
180 ms
EInbV5DfGHOiMmvb1Xr-hi3USBnSvpkopQaUR-2r7iU.ttf
181 ms
pRpLdo0SawzO7MoBpvowsEu5jiO09VgwnaAULz5Gfhw.ttf
221 ms
kkvG0zg1nqKzOChG5DPiZfesZW2xOQ-xsNqO47m55DA.ttf
221 ms
widgets.js
179 ms
ca-pub-4613087833151401.js
516 ms
zrt_lookup.html
512 ms
show_ads_impl.js
247 ms
twitter.png
506 ms
rss.png
501 ms
googleplus.png
585 ms
facebook.png
587 ms
platform.js
429 ms
like.php
632 ms
logo_hotofertas.png
453 ms
56ec273be4b00c1dcc89b56f.jpg
603 ms
spider3.php
373 ms
beacon.js
438 ms
line.png
539 ms
bt_hotofertas.png
405 ms
ga.js
352 ms
js15_as.js
375 ms
meter.asp
325 ms
analytics.js
533 ms
mpp.vindicosuite.com
480 ms
arrow_totop.png
476 ms
like.php
595 ms
like.php
656 ms
like.php
617 ms
like.php
614 ms
like.php
647 ms
likebox.php
808 ms
ads
555 ms
cb=gapi.loaded_0
277 ms
cb=gapi.loaded_1
261 ms
fastbutton
361 ms
fastbutton
415 ms
fastbutton
414 ms
fastbutton
413 ms
fastbutton
412 ms
fastbutton
409 ms
page
499 ms
osd.js
253 ms
ads
508 ms
ads
415 ms
g.gif
214 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
367 ms
loadingAnimation.gif
231 ms
meter.asp
161 ms
__utm.gif
134 ms
0.php
130 ms
postmessageRelay
252 ms
0
264 ms
rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw
74 ms
qeKvIRsJabD.js
222 ms
LVx-xkvaJ0b.png
339 ms
206 ms
cb=gapi.loaded_0
92 ms
cb=gapi.loaded_1
92 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
202 ms
rs=AGLTcCNwBglnRFJRg0mRD_l9WzbpnP29GQ
53 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
92 ms
rs=AGLTcCNKsEtbbeYP1KQXZJw9Vmp_uEZhTQ
120 ms
m_js_controller.js
265 ms
abg.js
322 ms
googlelogo_color_112x36dp.png
276 ms
1218439399498707353
451 ms
3193398744-postmessagerelay.js
281 ms
rpc:shindig_random.js
191 ms
photo.jpg
181 ms
995665_544062538974631_304934883_n.jpg
178 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
169 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
180 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
180 ms
blank.gif
213 ms
rs=AGLTcCNKsEtbbeYP1KQXZJw9Vmp_uEZhTQ
84 ms
hDvwL1_H7g-.css
92 ms
56WNbrUYLbL.css
150 ms
q68gy-v_YMF.js
163 ms
FJmpeSpHpjS.js
192 ms
0wM5s1Khldu.js
200 ms
1bNoFZUdlYZ.js
192 ms
rs=AGLTcCNKsEtbbeYP1KQXZJw9Vmp_uEZhTQ
51 ms
favicon
199 ms
nessie_icon_tiamat_white.png
157 ms
imgad
159 ms
x_button_blue2.png
121 ms
cb=gapi.loaded_0
103 ms
s
112 ms
1653830_658046377576246_39376926_n.jpg
108 ms
184376_173594442688111_1588558_n.jpg
144 ms
12195797_954945794579287_3614701449950373074_n.jpg
147 ms
1935307_10201237302331809_2356771430152441330_n.jpg
146 ms
12799275_890727811044889_1240156946211325380_n.jpg
147 ms
480406_134410663361810_1203980719_n.jpg
164 ms
1014117_1008729585835343_1941734233514384832_n.jpg
148 ms
12472696_754452601351415_4586716677808595654_n.jpg
214 ms
12650814_799164683545873_590507353949195629_n.jpg
148 ms
wL6VQj7Ab77.png
61 ms
s7jcwEQH7Sx.png
67 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
10 ms
I6-MnjEovm5.js
35 ms
pQrUxxo5oQp.js
35 ms
bannergamedev150.gif
31 ms
banner60x60.jpg
371 ms
fq0e.jpg
377 ms
0.jpg
22 ms
play.png
323 ms
lytesprite.png
297 ms
0.jpg
20 ms
0.jpg
19 ms
0.jpg
19 ms
0.jpg
21 ms
jot.html
30 ms
ui
44 ms
geekbr.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
geekbr.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
geekbr.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geekbr.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 Portuguese language. Our system also found out that Geekbr.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.
geekbr.com
Open Graph description is not detected on the main page of Geekbr. 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: