Tools & Wizards About Us

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

i.church

i.Church with Ron Carpenter | LIVE Every Saturday at 9pm, Sunday at 9am, 10:30am, 12pm, and 2:15pm ET.

Page Load Speed

2.7 sec in total

First Response

309 ms

Resources Loaded

2.1 sec

Page Rendered

263 ms

About Website

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.church

Key Findings

We analyzed I.church page load time and found that the first response time was 309 ms and then it took 2.4 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

i.church performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value7,060 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

i.church

309 ms

i.church

183 ms

pe_styles.css

37 ms

style.min.css

42 ms

extendify-utilities.css

46 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 80% of them (86 requests) were addressed to the original I.church, 10% (11 requests) were made to Use.typekit.net and 5% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (714 ms) relates to the external source Ichurch.churchonline.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 166.1 kB (11%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I.church main page is 1.5 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. Only a small number of websites need less resources to load. Images take 580.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 123.6 kB

  • Original 148.9 kB
  • After minification 141.8 kB
  • After compression 25.3 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 123.6 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 580.3 kB
  • After minification 580.3 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 images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 27.4 kB

  • Original 496.5 kB
  • After minification 496.5 kB
  • After compression 469.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 15.1 kB

  • Original 275.3 kB
  • After minification 274.7 kB
  • After compression 260.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. I.church has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 83 (89%)

Requests Now

93

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 93 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 59 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

i.church accessibility score

76

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

i.church best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

i.church SEO score

81

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

    EN

  • Encoding

    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.

Social Sharing Optimization

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: