1.3 sec in total
67 ms
335 ms
936 ms
Click here to check amazing Igf content for United States. Otherwise, check out these important facts you probably never knew about igf.com
Annual event sponsored by UBM Tech to award excellence in independent video game development in several categories.
Visit igf.comWe analyzed Igf.com page load time and found that the first response time was 67 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
igf.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value6.8 s
7/100
25%
Value5.5 s
54/100
10%
Value780 ms
38/100
30%
Value0.177
68/100
15%
Value11.7 s
17/100
10%
67 ms
41 ms
15 ms
16 ms
123 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 48% of them (28 requests) were addressed to the original Igf.com, 28% (16 requests) were made to Gamasutra.com and 3% (2 requests) were made to Acme.medialiveinternational.com. The less responsive or slowest element that took the longest time to load (123 ms) relates to the external source I.cmpnet.com.
Page size can be reduced by 323.6 kB (27%)
1.2 MB
860.8 kB
In fact, the total size of Igf.com main page is 1.2 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. 35% of websites need less resources to load. Images take 848.2 kB which makes up the majority of the site volume.
Potential reduce by 108.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. This page needs HTML code to be minified as it can gain 38.3 kB, which is 30% 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 108.5 kB or 84% of the original size.
Potential reduce by 78.0 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. Igf images are well optimized though.
Potential reduce by 130.4 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 130.4 kB or 66% of the original size.
Potential reduce by 6.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. Igf.com needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 79% of the original size.
Number of requests can be reduced by 21 (38%)
55
34
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Igf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
igf.com
67 ms
igf.css
41 ms
tnow.css
15 ms
superfooter.css
16 ms
h_s_code_remote.js
123 ms
j.php
6 ms
gpt.js
8 ms
v.gif
6 ms
pubads_impl_81.js
11 ms
container.html
65 ms
sitetabs_bg.jpg
63 ms
header_01.gif
62 ms
header_02_IGF15.gif
61 ms
logo_ubm_white.png
61 ms
rssblue.gif
60 ms
gdca_igf.jpg
61 ms
igf-student.jpg
53 ms
ads
92 ms
gdc_china.jpg
22 ms
igf.jpg
49 ms
igf-image.jpg
52 ms
igf.jpg
49 ms
igf2015_announce2.jpg
51 ms
IGF%20awards.jpg
48 ms
IGF1.jpg
55 ms
igf-image.jpg
55 ms
gdc_china.jpg
54 ms
igfchinasubmissions.jpg
54 ms
indiegamesblog.jpg
20 ms
IGF14_510x188.jpg
62 ms
back_03.gif
36 ms
back_04.gif
35 ms
back_06.gif
34 ms
center_header_news.gif
38 ms
center_break.gif
46 ms
leftpanel_07.gif
47 ms
leftpanel_09.gif
47 ms
back_10.gif
45 ms
back_12.gif
47 ms
leftpanel_01.gif
34 ms
leftpanel_03.gif
32 ms
leftpanel_07.gif
45 ms
leftpanel_09.gif
45 ms
back_03.gif
44 ms
2010_cactusphilmatthew.jpg
46 ms
igf-student.jpg
44 ms
igf_nathan_2-thumb-200x133-19453.jpg
54 ms
itsmebrandon.jpg
47 ms
kwallick.jpg
59 ms
13280149844_24e5d76127_m.jpg
59 ms
chairman_2012s.jpg
70 ms
igf_2016.jpg
34 ms
igf_china.jpg
45 ms
gdc_china.jpg
42 ms
schafer_vella.jpg
58 ms
11789236812172205474
39 ms
osd.js
12 ms
s48579105245880
7 ms
igf.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
Image elements do not have [alt] attributes
Links do not have a discernible name
igf.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
igf.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Igf.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 Igf.com main page’s claimed encoding is . 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.
igf.com
Open Graph description is not detected on the main page of Igf. 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: