2.3 sec in total
49 ms
2.1 sec
89 ms
Visit igg.me now to see the best up-to-date Igg content for United States and also check out these interesting facts you probably never knew about igg.me
Crowdfund innovations in tech and design before they go mainstream and support entrepreneurs that are working to bring their dreams to life.
Visit igg.meWe analyzed Igg.me page load time and found that the first response time was 49 ms and then it took 2.2 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.
igg.me performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value15.1 s
0/100
25%
Value16.2 s
0/100
10%
Value2,540 ms
4/100
30%
Value0
100/100
15%
Value25.5 s
0/100
10%
49 ms
171 ms
111 ms
54 ms
73 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Igg.me, 14% (8 requests) were made to Tags.tiqcdn.com and 9% (5 requests) were made to G2.iggcdn.com. The less responsive or slowest element that took the longest time to load (852 ms) relates to the external source Cookie.fuel451.com.
Page size can be reduced by 407.1 kB (56%)
728.0 kB
320.9 kB
In fact, the total size of Igg.me main page is 728.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 383.2 kB which makes up the majority of the site volume.
Potential reduce by 22.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 22.5 kB or 66% of the original size.
Potential reduce by 132 B
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. Igg images are well optimized though.
Potential reduce by 203.5 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 203.5 kB or 53% of the original size.
Potential reduce by 181.0 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. Igg.me needs all CSS files to be minified and compressed as it can save up to 181.0 kB or 82% of the original size.
Number of requests can be reduced by 29 (64%)
45
16
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Igg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
igg.me
49 ms
www.indiegogo.com
171 ms
dc.js
111 ms
analytics.js
54 ms
fbevents.js
73 ms
select2-38780fb5cf970ef197cc992d8f4052cc9607066a4390c6356a49f85c0c4407dd.css
105 ms
select-97a659f5cd2c0fb81677a4d20c93f9d44869ef071dc4a1a4bcef6beb3ec66022.css
116 ms
angular-motion-73d2902ef528dee5155e9ca9496bfca0718b4462ff4890b142129741e5914a5a.css
121 ms
fonts-44eefa59b6acbe4a65b15725d4942b02b01e7a306c472a1770837c6928f608b7.css
117 ms
common-44519aeaa45f12ecbcbf2166f6d6e13587adfa1233fbccfa6008f6fcca4a730a.css
131 ms
font-awesome.min-bc643228a7bd19950c6c4de35b778d602a7d3fb0781b959e07998fcb5ba0819f.css
117 ms
error-959cb384b04361d62abce3eb6d0a71394708d321931c3c3c504ec6d4c9f3750f.css
114 ms
gogodstlxzsxbqvueyqv.js
81 ms
api.js
83 ms
ec.js
29 ms
collect
22 ms
collect
12 ms
ga-audiences
57 ms
utag.js
51 ms
IGG_browserError_asset_ie-9ec8685fcb6eb0ad23227279c20fb413369861715dfe5159cb45e728b1a730bd.png
34 ms
IGG_browserError_asset_safari-95d177efbbf0045f0198df348eeb0aeac809d5923cb60b2d375265fea2992bf5.png
33 ms
174 ms
IGG_browserError_asset_moz-51ac0571a5f4c3077a0bf1f3086277d5b2c784559517719c86796325553c361c.png
44 ms
IGG_browserError_asset_chrome-9baba2b4c406d538ee7c97b6d9fc56ed0df8441ae16122d4df9e9e63347635e3.png
79 ms
recaptcha__en.js
120 ms
b364f043-858e-432f-be7c-55108d86186a-3-3c30f75486cc44810aeecf935490e1a8d79af7da532a7605d388d812e795f4df.woff
89 ms
b2b61d4f-e0f1-4776-8cb9-beb0c25d2d57-3-cba7690bbc90041ced9875a9477802d76a4b8f5ecab434756e389a495bc78185.woff
77 ms
66594866-86f8-4855-b363-3fb1fe03fed3-3-53323cca53bea01b6896d5064840570d4eec7477d42aac72e9a72055552665e7.woff
54 ms
ec76296f-53e8-42b9-81c7-00fcfc0663d9-3-33f5450a246d405e2929b1607cce78ccbc2be4b5698a94572ec9cb34eb76d33c.woff
56 ms
utag.22.js
22 ms
utag.25.js
42 ms
utag.167.js
65 ms
utag.203.js
64 ms
utag.204.js
64 ms
utag.209.js
62 ms
utag.230.js
62 ms
conversion_async.js
102 ms
quant.js
101 ms
bat.js
147 ms
2059373.js
57 ms
tracksa.min.js
360 ms
1002.js
77 ms
2860.js
241 ms
42 ms
pixel;r=1944960925;a=p-eSNAb5mDpCB7d;fpan=1;fpa=P0-1711438728-1458494329602;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458494329601;tzo=-180;ref=;url=https%3A%2F%2Fwww.indiegogo.com%2F;ogl=
37 ms
31 ms
appcues.css
23 ms
md5-userid:d7dcae4cf61bc0c2c5191714d7dfbde7.json
155 ms
flows.json
172 ms
hotspot-groups.json
177 ms
coachmark-groups.json
176 ms
trackCode
195 ms
nr-885.min.js
64 ms
sa
852 ms
52ee8e3327
112 ms
pixel
36 ms
cookiematch
354 ms
igg.me accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
igg.me best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
igg.me SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Igg.me 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 Igg.me 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.
igg.me
Open Graph description is not detected on the main page of Igg. 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: