Tools & Wizards About Us
geekdo.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

geekdo.com

BoardGameGeek | Gaming Unplugged Since 2000

Page Load Speed

12.2 sec in total

First Response

321 ms

Resources Loaded

8.7 sec

Page Rendered

3.1 sec

geekdo.com screenshot

About Website

Welcome to geekdo.com homepage info - get ready to check Geek Do best content for United States right away, or after learning these important things about geekdo.com

Visit geekdo.com

Key Findings

We analyzed Geekdo.com page load time and found that the first response time was 321 ms and then it took 11.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

geekdo.com performance score

0

Network Requests Diagram

geekdo.com

321 ms

css_master2_569f6192c29eb.css

36 ms

js_master2_569f61767aaab.js

108 ms

onejs

98 ms

gpt.js

1022 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 28% of them (20 requests) were addressed to the original Geekdo.com, 15% (11 requests) were made to Cf.geekdo-static.com and 13% (9 requests) were made to Cf.geekdo-images.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Geekdo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 642.5 kB (51%)

Content Size

1.3 MB

After Optimization

611.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Geekdo.com main page is 1.3 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 490.7 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 405.2 kB

  • Original 455.1 kB
  • After minification 366.1 kB
  • After compression 49.9 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. This page needs HTML code to be minified as it can gain 89.1 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 405.2 kB or 89% of the original size.

Image Optimization

-7%

Potential reduce by 32.2 kB

  • Original 490.7 kB
  • After minification 458.5 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. Geek Do images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 141.2 kB

  • Original 228.4 kB
  • After minification 228.4 kB
  • After compression 87.2 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 141.2 kB or 62% of the original size.

CSS Optimization

-80%

Potential reduce by 63.9 kB

  • Original 80.1 kB
  • After minification 79.5 kB
  • After compression 16.2 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. Geekdo.com needs all CSS files to be minified and compressed as it can save up to 63.9 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (33%)

Requests Now

70

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geek Do. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

geekdo.com

geekdo.com

321 ms

css_master2_569f6192c29eb.css

css_master2_569f6192c29eb.css

36 ms

js_master2_569f61767aaab.js

js_master2_569f61767aaab.js

108 ms

onejs

onejs

98 ms

gpt.js

gpt.js

1022 ms

bgg_cornerlogo.png

bgg_cornerlogo.png

1000 ms

bggstorewidgettitle.png

bggstorewidgettitle.png

994 ms

ebaylogo.gif

ebaylogo.gif

993 ms

toyfair2016.png

toyfair2016.png

992 ms

gradients_2.png

gradients_2.png

244 ms

pubads_impl_79.js

pubads_impl_79.js

384 ms

tileicon_0_25.png

tileicon_0_25.png

383 ms

ads

ads

76 ms

container.html

container.html

46 ms

7442017716031410807

7442017716031410807

235 ms

ads

ads

90 ms

3402574043271249153

3402574043271249153

94 ms

osd.js

osd.js

170 ms

ads

ads

59 ms

getad

getad

151 ms

json

json

88 ms

5346597050655339869

5346597050655339869

62 ms

minus2.gif

minus2.gif

187 ms

module

module

103 ms

module

module

366 ms

module

module

378 ms

frontpagemodule

frontpagemodule

397 ms

module

module

385 ms

module

module

476 ms

module

module

408 ms

module

module

677 ms

module

module

719 ms

module

module

835 ms

module

module

514 ms

module

module

590 ms

module

module

629 ms

module

module

880 ms

module

module

978 ms

module

module

1347 ms

module

module

927 ms

module

module

1194 ms

module

module

1118 ms

amzn-widgets-sprite-2x.png

amzn-widgets-sprite-2x.png

470 ms

resolve

resolve

482 ms

amznassocview.js

amznassocview.js

482 ms

flag_usa.png

flag_usa.png

901 ms

pic2883116_mt.jpg

pic2883116_mt.jpg

805 ms

flag_great_britain.png

flag_great_britain.png

714 ms

pic2883374_mt.jpg

pic2883374_mt.jpg

706 ms

pic2883118_mt.jpg

pic2883118_mt.jpg

706 ms

pic2883117_mt.jpg

pic2883117_mt.jpg

705 ms

pic2883168_mt.jpg

pic2883168_mt.jpg

706 ms

pic2885949_mt.png

pic2885949_mt.png

705 ms

pic2884749_mt.jpg

pic2884749_mt.jpg

705 ms

pic2881815_mt.jpg

pic2881815_mt.jpg

705 ms

pic2885822_mt.jpg

pic2885822_mt.jpg

699 ms

analytics.js

analytics.js

165 ms

%7B%22adViewability%22:%5B%7B%22above_the_fold%22:%20false,%20%22topPos%22:%200.0019047619047619048,%20%22leftPos%22:%200.0011904761904761906%7D%5D%7D&cb=1374974

%7B%22adViewability%22:%5B%7B%22above_the_fold%22:%20false,%20%22topPos%22:%200.0019047619047619048,%20%22leftPos%22:%200.0011904761904761906%7D%5D%7D&cb=1374974

163 ms

61BnRT60n%2BL._AC_SL115_.jpg

61BnRT60n%2BL._AC_SL115_.jpg

123 ms

json

json

18 ms

ir

ir

187 ms

41tUnu%2BkhKL._AC_SL115_.jpg

41tUnu%2BkhKL._AC_SL115_.jpg

7 ms

61FRjAjJwuL._AC_SL115_.jpg

61FRjAjJwuL._AC_SL115_.jpg

62 ms

61MA6nDfNrL._AC_SL115_.jpg

61MA6nDfNrL._AC_SL115_.jpg

61 ms

61 ms

collect

collect

26 ms

collect

collect

849 ms

61BnRT60n%2BL._AC_SL148_.jpg

61BnRT60n%2BL._AC_SL148_.jpg

804 ms

quant.js

quant.js

830 ms

61FRjAjJwuL._AC_SL148_.jpg

61FRjAjJwuL._AC_SL148_.jpg

27 ms

61MA6nDfNrL._AC_SY115_.jpg

61MA6nDfNrL._AC_SY115_.jpg

70 ms

SEO Factors

geekdo.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geekdo.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Geekdo.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.

Social Sharing Optimization

geekdo.com

Open Graph description is not detected on the main page of Geek Do. 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: