2.7 sec in total
511 ms
2 sec
174 ms
Click here to check amazing I content for United States. Otherwise, check out these important facts you probably never knew about i.church
i.Church with Ron Carpenter is an online church available from anywhere. Join us for LIVE every Sunday at 9am, 10:30am, 12pm, and 2:15pm ET.
Visit i.churchWe analyzed I.church page load time and found that the first response time was 511 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
i.church performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value7.3 s
4/100
25%
Value6.1 s
45/100
10%
Value2,040 ms
7/100
30%
Value0.08
94/100
15%
Value11.9 s
16/100
10%
511 ms
9 ms
17 ms
19 ms
12 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 47% of them (51 requests) were addressed to the original I.church, 10% (11 requests) were made to Pdk.theplatform.com and 5% (5 requests) were made to Static.olark.com. The less responsive or slowest element that took the longest time to load (565 ms) relates to the external source Rwoc.wufoo.com.
Page size can be reduced by 3.0 MB (64%)
4.7 MB
1.7 MB
In fact, the total size of I.church main page is 4.7 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. 85% 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. Javascripts take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 73.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. 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 73.9 kB or 79% of the original size.
Potential reduce by 96.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. Obviously, I needs image optimization as it can save up to 96.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.2 MB
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 2.2 MB or 71% of the original size.
Potential reduce by 600.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. I.church needs all CSS files to be minified and compressed as it can save up to 600.7 kB or 84% of the original size.
Number of requests can be reduced by 62 (66%)
94
32
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
i.church
511 ms
webfont.js
9 ms
settings.css
17 ms
bootstrap.min.css
19 ms
ss-gizmo.css
12 ms
font-awesome.min.css
13 ms
style.css
10 ms
responsive.css
22 ms
jquery.js
23 ms
jquery-migrate.min.js
15 ms
jquery.themepunch.tools.min.js
23 ms
jquery.themepunch.revolution.min.js
29 ms
css
41 ms
style.css
23 ms
lqJL5PNPZv4U
190 ms
ichurch-chat
278 ms
analytics.js
34 ms
form.js
187 ms
loader0.js
94 ms
redemptionLogoWhite.svg
32 ms
popup-maker-site.min.css
31 ms
style.css
31 ms
bootstrap.min.js
37 ms
jquery-ui-1.10.2.custom.min.js
36 ms
jquery.flexslider-min.js
43 ms
jquery.easing.js
44 ms
jquery.carouFredSel.min.js
47 ms
theme-scripts.js
67 ms
view.min.js
45 ms
js
66 ms
jquery.isotope.min.js
49 ms
imagesloaded.js
45 ms
jquery.infinitescroll.min.js
44 ms
functions.js
64 ms
comment-reply.min.js
48 ms
core.min.js
48 ms
position.min.js
50 ms
TweenMax.min.js
63 ms
popup-maker-site.min.js
49 ms
jquery.lwtCountdown.js
49 ms
1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf
37 ms
sntaY1Q8xeij0j8FAJb2VnYhjbSpvc47ee6xR_80Hnw.ttf
42 ms
Novecentosanswide-DemiBold-webfont.woff
521 ms
Novecentosanswide-DemiBold-webfont.woff
57 ms
fontawesome-webfont.woff
108 ms
ss-gizmo.woff
108 ms
collect
92 ms
collect
124 ms
3965-690-10-3970.js
51 ms
tpPdk.js
100 ms
main.css
91 ms
iChurchLogo_401x96.png
25 ms
connect_480x271.jpg
26 ms
getinvolved_480x271.jpg
25 ms
membership_960x271.jpg
26 ms
commit_960x271.jpg
26 ms
od_v2_480x271.jpg
22 ms
embedKey=qra9vka1svpwnw757985&entsource=&referrer=&secure=false
360 ms
main.css
69 ms
init.js
71 ms
praise_480x271.jpg
66 ms
update.min.js
40 ms
od_v2_960x250_MOBILE.jpg
38 ms
commit_960x250_MOBILE.jpg
38 ms
getInvolved_960x250_MOBILE.jpg
39 ms
membership_960x250_MOBILE.jpg
38 ms
connect_960x250_MOBILE.jpg
38 ms
t.gif
55 ms
ga.js
30 ms
main.png
55 ms
default.css
40 ms
28CB4550B05D606CF26E6783B72FEFED.cache.js
59 ms
praise_960x250_MOBILE1.jpg
36 ms
c
255 ms
main.js
8 ms
engine.js;jsessionid=m6pz6kee2ch
229 ms
__utm.gif
158 ms
4.cache.js
78 ms
index.0266.css
288 ms
theme.css
284 ms
custom.css
27 ms
dynamic.0266.js
565 ms
streamsense_plugin_theplatform.js
19 ms
sdk.js
15 ms
ServiceInterface.connect.req
119 ms
1.cache.js
35 ms
Novecentosanswide-DemiBold-webfont.ttf
413 ms
akamaiHD.js
20 ms
95 ms
270 ms
css
17 ms
xd_arbiter.php
22 ms
xd_arbiter.php
43 ms
glass.json
22 ms
metaLayout_floatingControls.xml
13 ms
2.cache.js
20 ms
ServiceInterface.updateUserPreference.req
153 ms
DEFAULTUSER-resize_20x20.jpg
141 ms
stream.html
271 ms
DEFAULTUSER-resize_20x20.jpg
303 ms
3.cache.js
147 ms
0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf
70 ms
MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf
77 ms
Novecentosanswide-DemiBold-webfont.svg
305 ms
application2.js
109 ms
HKzkrc8jBGL4
87 ms
xd_arbiter.php
7 ms
storage.html
136 ms
storage.js
29 ms
i.church accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
i.church best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
i.church 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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I.church 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 I.church 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.
i.church
Open Graph data is detected on the main page of I. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: