5.6 sec in total
327 ms
5 sec
298 ms
Visit i2i.org now to see the best up-to-date I 2 content for United States and also check out these interesting facts you probably never knew about i2i.org
Think Freedom
Visit i2i.orgWe analyzed I2i.org page load time and found that the first response time was 327 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
i2i.org performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value6.2 s
11/100
25%
Value14.2 s
1/100
10%
Value3,460 ms
2/100
30%
Value0.247
50/100
15%
Value28.4 s
0/100
10%
327 ms
1563 ms
287 ms
73 ms
87 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 52% of them (51 requests) were addressed to the original I2i.org, 11% (11 requests) were made to Causes.anedot.com and 8% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain I2i.org.
Page size can be reduced by 1.6 MB (63%)
2.6 MB
964.6 kB
In fact, the total size of I2i.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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 64.6 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 64.6 kB or 84% of the original size.
Potential reduce by 20.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. I 2 images are well optimized though.
Potential reduce by 695.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 695.2 kB or 56% of the original size.
Potential reduce by 857.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. I2i.org needs all CSS files to be minified and compressed as it can save up to 857.2 kB or 90% of the original size.
Number of requests can be reduced by 63 (72%)
87
24
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
i2i.org
327 ms
www.i2i.org
1563 ms
wp-emoji-release.min.js
287 ms
css
73 ms
css
87 ms
css
100 ms
reset.css
220 ms
superfish.css
221 ms
prettyPhoto.css
317 ms
jquery.qtip.css
238 ms
odometer-theme-default.css
286 ms
animations.css
279 ms
style.css
306 ms
responsive.css
405 ms
custom.css
348 ms
js_composer.min.css
918 ms
jquery.js
537 ms
jquery-migrate.min.js
381 ms
img-mouseover.js
418 ms
js
56 ms
style.css
310 ms
jquery.min.js
29 ms
scripts.js
252 ms
jquery.browser.min.js
255 ms
core.min.js
252 ms
widget.min.js
254 ms
accordion.min.js
252 ms
tabs.min.js
254 ms
jquery.ba-bbq.min.js
255 ms
jquery.history.js
281 ms
jquery.easing.1.3.js
255 ms
jquery.carouFredSel-6.2.1-packed.js
256 ms
jquery.touchSwipe.min.js
255 ms
jquery.transit.min.js
256 ms
jquery.sliderControl.js
280 ms
jquery.timeago.js
255 ms
jquery.hint.js
274 ms
jquery.qtip.min.js
278 ms
jquery.blockUI.js
369 ms
jquery.prettyPhoto.js
383 ms
odometer.min.js
374 ms
main.js
439 ms
js_composer_front.min.js
372 ms
ga.js
112 ms
quant.js
173 ms
header_search.png
183 ms
facebook.png
240 ms
twitter.png
416 ms
youtube.png
416 ms
i2i-logo-3-copy.png
416 ms
menu_arrow.png
414 ms
wind_turbine_01-524x261.jpg
416 ms
HealthCare_senior_patient-524x261.jpg
416 ms
shutterstock_273092756-524x261.jpg
483 ms
Prop_104-524x524.jpg
680 ms
Krause_Freedom_Minute-524x524.jpg
496 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
146 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
162 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
313 ms
embed.js
341 ms
embed.js
335 ms
overlay.png
424 ms
analytics.js
333 ms
__utm.gif
64 ms
pixel;r=659471295;a=p-2dCDSKRxSZ0ag;fpan=1;fpa=P0-1521431668-1458289721291;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458289721278;tzo=-180;ref=;url=https%3A%2F%2Fwww.i2i.org%2F;ogl=
249 ms
preloader.gif
129 ms
independence-institute
880 ms
skout.js
219 ms
iframe_api
123 ms
E-v1.js
237 ms
50d3daca-2550-4a90-a53b-9d99dd2eb392
37 ms
6bb62151-34e8-4a1d-a13c-f3d1d874b4e1
59 ms
www-widgetapi.js
94 ms
iframe_shim
50 ms
page-view
113 ms
modernizr-e096006d8cd668cafe3c7c2d6fa152e43fee7bf2e107b772db1b3ed8801da164.js
26 ms
donations-eb97873f49d5ad8d93d235e485f354106c88ad6cd30c012c31219e67f520a394.css
455 ms
jquery-f4879eb8690155de2bdcafd0967e4171fd96bdfcea8d747a3d1f771479f5689f.js
609 ms
2705790559.js
76 ms
donations-6154c56f4f8c9c37593e6dd24f064c0c94a64e25d9c7d12d4bd9a054fda6db04.js
457 ms
css
21 ms
logo-white-ef551dc2b53d67a03acc01593b0c1b6f9857bad2d34b4d629e625dfa2536fd22.svg
55 ms
donation-form-input-sprite-1e5b7d45986771913da074d86956390b52dacaa825458fc45ae43e1b8845a9a7.svg
49 ms
dropdown-0bbb2934591546b787a8bb0ba8030a6a17a649c91bf46b5b2b249ce957c96838.svg
51 ms
bg-card-brands-d2cd587c3c2419d9e59b02f6f583ad8add77edc225be30581ff871f439644540.svg
51 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
6 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
6 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
16 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
15 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
14 ms
anedot-icons-04d13a85f362b2cd22f96b7ff0b8ed7dcd9d093942af75a698e48a9c6c3d1bae.ttf
29 ms
analytics.js
58 ms
fbevents.js
112 ms
donations-printable-38c8be7b4e0128aa0ba718bccdea6c97af88ef0a85b2bb216947077dad500c9d.css
48 ms
collect
15 ms
collect
53 ms
155 ms
nr-885.min.js
44 ms
i2i.org 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.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
i2i.org 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
i2i.org 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I2i.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that I2i.org 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.
i2i.org
Open Graph description is not detected on the main page of I 2. 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: