Tools & Wizards About Us
church111.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

church111.com

CMS Church websites: Custom design or templates: Church111

Page Load Speed

1.2 sec in total

First Response

133 ms

Resources Loaded

945 ms

Page Rendered

86 ms

church111.com screenshot

About Website

Welcome to church111.com homepage info - get ready to check Church111 best content right away, or after learning these important things about church111.com

CMS Church websites with custom design or template options that are affordable, easy-to-edit, easy-to-use, eature-rich, SEO strong and customizable. Rely on Church111 for your church website.

Visit church111.com

Key Findings

We analyzed Church111.com page load time and found that the first response time was 133 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

church111.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.261

47/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

church111.com

133 ms

jquery-ui.css

15 ms

font-awesome.min.css

28 ms

default.cfm

34 ms

tcal.css

25 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 76% of them (19 requests) were addressed to the original Church111.com, 16% (4 requests) were made to Fonts.googleapis.com and 8% (2 requests) were made to Secure.build111.com. The less responsive or slowest element that took the longest time to load (649 ms) belongs to the original domain Church111.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.1 kB (5%)

Content Size

1.1 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Church111.com main page is 1.1 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. 30% of websites need less resources to load. Images take 940.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 12.5 kB

  • Original 15.8 kB
  • After minification 11.5 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 4.3 kB, which is 27% 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 12.5 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 169 B

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

JavaScript Optimization

-27%

Potential reduce by 46.1 kB

  • Original 171.3 kB
  • After minification 171.3 kB
  • After compression 125.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 46.1 kB or 27% of the original size.

CSS Optimization

-2%

Potential reduce by 291 B

  • Original 15.1 kB
  • After minification 15.1 kB
  • After compression 14.9 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. Church111.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (68%)

Requests Now

22

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Church111. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

church111.com

church111.com

133 ms

jquery-ui.css

jquery-ui.css

15 ms

font-awesome.min.css

font-awesome.min.css

28 ms

default.cfm

default.cfm

34 ms

tcal.css

tcal.css

25 ms

flashobject.js

flashobject.js

32 ms

tcal.js

tcal.js

27 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

649 ms

jquery-ui.js

jquery-ui.js

97 ms

common_js.cfm

common_js.cfm

43 ms

css

css

21 ms

css

css

40 ms

css

css

39 ms

css

css

40 ms

111Styles.css

111Styles.css

619 ms

main.js

main.js

618 ms

camera_jquery1.9_.min.js

camera_jquery1.9_.min.js

40 ms

camera.css

camera.css

42 ms

footer_js.cfm

footer_js.cfm

46 ms

imagecaptions.js

imagecaptions.js

50 ms

church111-logo.png

church111-logo.png

17 ms

white70.png

white70.png

26 ms

camera-loader.gif

camera-loader.gif

14 ms

church111Home.jpg

church111Home.jpg

85 ms

church111Home.jpg

church111Home.jpg

71 ms

Accessibility Review

church111.com accessibility score

54

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

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

church111.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

church111.com SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Church111.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 Church111.com 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

church111.com

Open Graph data is detected on the main page of Church111. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: