Tools & Wizards About Us
igda.org screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

igda.org

IGDA – International Game Developers Association

Page Load Speed

2.6 sec in total

First Response

78 ms

Resources Loaded

2 sec

Page Rendered

460 ms

igda.org screenshot

About Website

Click here to check amazing IGDA content for United States. Otherwise, check out these important facts you probably never knew about igda.org

Visit igda.org

Key Findings

We analyzed Igda.org page load time and found that the first response time was 78 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

igda.org performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

igda.org

78 ms

www.igda.org

387 ms

combined.css

196 ms

container.css

18 ms

yahoo-dom-event.js

18 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 67% of them (40 requests) were addressed to the original Igda.org, 12% (7 requests) were made to Ajax.googleapis.com and 8% (5 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (753 ms) belongs to the original domain Igda.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 371.4 kB (14%)

Content Size

2.6 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Igda.org main page is 2.6 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. 55% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 34.9 kB

  • Original 43.6 kB
  • After minification 41.8 kB
  • After compression 8.7 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 34.9 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 219.2 kB

  • Original 2.2 MB
  • After minification 2.0 MB

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. IGDA images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 88.8 kB

  • Original 248.0 kB
  • After minification 240.4 kB
  • After compression 159.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 88.8 kB or 36% of the original size.

CSS Optimization

-77%

Potential reduce by 28.5 kB

  • Original 37.1 kB
  • After minification 29.3 kB
  • After compression 8.6 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. Igda.org needs all CSS files to be minified and compressed as it can save up to 28.5 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (48%)

Requests Now

54

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

igda.org

igda.org

78 ms

www.igda.org

www.igda.org

387 ms

combined.css

combined.css

196 ms

container.css

container.css

18 ms

yahoo-dom-event.js

yahoo-dom-event.js

18 ms

dragdrop-min.js

dragdrop-min.js

18 ms

container-min.js

container-min.js

24 ms

json-min.js

json-min.js

18 ms

jquery.min.js

jquery.min.js

26 ms

jquery-ui.min.js

jquery-ui.min.js

88 ms

combined.js

combined.js

454 ms

jquery.slicknav.min.js

jquery.slicknav.min.js

116 ms

element.js

element.js

67 ms

css

css

108 ms

RadMenu.js

RadMenu.js

435 ms

jquery.data.js

jquery.data.js

28 ms

jquery.watermark.min.js

jquery.watermark.min.js

74 ms

ga.js

ga.js

25 ms

bg.png

bg.png

191 ms

icon-search.png

icon-search.png

114 ms

logo.png

logo.png

122 ms

igda_boardelectionsbanner_votenow.jpg

igda_boardelectionsbanner_votenow.jpg

319 ms

DSS2015-summaryreport.jpg

DSS2015-summaryreport.jpg

394 ms

HUB_Insurance.jpg

HUB_Insurance.jpg

319 ms

IGDA_forums.jpg

IGDA_forums.jpg

141 ms

Getinvolved3.jpg

Getinvolved3.jpg

324 ms

Advocacy2.jpg

Advocacy2.jpg

319 ms

yellowbox2.png

yellowbox2.png

317 ms

securesubmit.png

securesubmit.png

318 ms

translateelement.css

translateelement.css

140 ms

main.js

main.js

137 ms

__utm.gif

__utm.gif

52 ms

__utm.gif

__utm.gif

46 ms

bg-map.png

bg-map.png

753 ms

bg-menu.png

bg-menu.png

224 ms

element_main.js

element_main.js

39 ms

menu.css

menu.css

127 ms

styles.css

styles.css

28 ms

icon-home.png

icon-home.png

69 ms

icon-about.png

icon-about.png

59 ms

icon-news.png

icon-news.png

58 ms

icon-calendar.png

icon-calendar.png

59 ms

icon-community.png

icon-community.png

58 ms

icon-advocacy.png

icon-advocacy.png

59 ms

icon-books.png

icon-books.png

103 ms

icon-involved.png

icon-involved.png

101 ms

museo700-regular.woff

museo700-regular.woff

102 ms

bg-login.png

bg-login.png

344 ms

bg-login-2.png

bg-login-2.png

354 ms

html;charset=utf-8,%3Chtml%3E%3Chead%3E%3Cscript%20type%3D%22text%2Fjavascript%22%3Ewindow.onresize%3Dfunction()%7Bwindow.parent.YAHOO.widget.Module.textResizeEvent.fire()%3B%7D%3B%3C%2Fscript%3E%3C%2Fhead%3E%3Cbody%3E%3C%2Fbody%3E%3C%2Fhtml%3E

html;charset=utf-8,%3Chtml%3E%3Chead%3E%3Cscript%20type%3D%22text%2Fjavascript%22%3Ewindow.onresize%3Dfunction()%7Bwindow.parent.YAHOO.widget.Module.textResizeEvent.fire()%3B%7D%3B%3C%2Fscript%3E%3C%2Fhead%3E%3Cbody%3E%3C%2Fbody%3E%3C%2Fhtml%3E

222 ms

museo500-regular.woff

museo500-regular.woff

213 ms

bg-footer.png

bg-footer.png

153 ms

icon-social.png

icon-social.png

234 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

313 ms

slideShowPrev.png

slideShowPrev.png

145 ms

slideShowNext.png

slideShowNext.png

144 ms

translate_24dp.png

translate_24dp.png

103 ms

l

l

83 ms

cleardot.gif

cleardot.gif

64 ms

te_ctrl3.gif

te_ctrl3.gif

30 ms

Accessibility Review

igda.org accessibility score

68

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

igda.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

igda.org SEO score

76

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Igda.org 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 Igda.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

igda.org

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