Tools & Wizards About Us
churchtrac.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

churchtrac.com

ChurchTrac - Church Management Software for Small and Large Churches

Page Load Speed

1.5 sec in total

First Response

29 ms

Resources Loaded

736 ms

Page Rendered

768 ms

churchtrac.com screenshot

About Website

Click here to check amazing Church Trac content for United States. Otherwise, check out these important facts you probably never knew about churchtrac.com

The most user-friendly and affordable church software to track online giving, accounting, membership, child check-in, visitors, small groups, events, volunteers, attendance and more.

Visit churchtrac.com

Key Findings

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

Performance Metrics

churchtrac.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

churchtrac.com

29 ms

churchtrac.com

18 ms

www.churchtrac.com

69 ms

jquery-3.3.1.min.js

21 ms

bootstrap.min.css

33 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 77% of them (47 requests) were addressed to the original Churchtrac.com, 15% (9 requests) were made to Use.typekit.net and 3% (2 requests) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (284 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 990.5 kB (25%)

Content Size

4.0 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Churchtrac.com main page is 4.0 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. 70% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 33.3 kB

  • Original 41.8 kB
  • After minification 36.0 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 5.8 kB, which is 14% 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 33.3 kB or 80% of the original size.

Image Optimization

-25%

Potential reduce by 940.8 kB

  • Original 3.8 MB
  • After minification 2.8 MB

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, Church Trac needs image optimization as it can save up to 940.8 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 124 B

  • Original 63.7 kB
  • After minification 63.7 kB
  • After compression 63.6 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

-21%

Potential reduce by 16.3 kB

  • Original 79.3 kB
  • After minification 73.5 kB
  • After compression 63.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. Churchtrac.com needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (27%)

Requests Now

45

After Optimization

33

  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Church Trac. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

churchtrac.com

churchtrac.com

29 ms

churchtrac.com

churchtrac.com

18 ms

www.churchtrac.com

www.churchtrac.com

69 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

21 ms

bootstrap.min.css

bootstrap.min.css

33 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

14 ms

all.min.css

all.min.css

40 ms

typeit.js

typeit.js

12 ms

style.css

style.css

12 ms

bootbox.min.js

bootbox.min.js

19 ms

toastr.min.js

toastr.min.js

19 ms

toastr.min.css

toastr.min.css

47 ms

player.js

player.js

47 ms

js

js

122 ms

khp0vip.css

khp0vip.css

37 ms

p.css

p.css

24 ms

ct-logo-color-lower.png

ct-logo-color-lower.png

23 ms

547673797

547673797

274 ms

hex-blue.png

hex-blue.png

24 ms

hex-tangerine.png

hex-tangerine.png

27 ms

hero3.png

hero3.png

45 ms

people.png

people.png

63 ms

2-devices@2x.png

2-devices@2x.png

64 ms

support@2x.jpg

support@2x.jpg

43 ms

no_risk@2x.jpg

no_risk@2x.jpg

56 ms

capterra_badges.png

capterra_badges.png

41 ms

capterra.png

capterra.png

104 ms

3-bluebg-man@2x.png

3-bluebg-man@2x.png

91 ms

1.png

1.png

49 ms

2.png

2.png

54 ms

3.png

3.png

60 ms

4.png

4.png

60 ms

5.png

5.png

65 ms

6.png

6.png

65 ms

7.png

7.png

65 ms

8.png

8.png

66 ms

9.png

9.png

69 ms

10.png

10.png

70 ms

11.png

11.png

70 ms

12.png

12.png

70 ms

13.png

13.png

75 ms

14.png

14.png

76 ms

15.png

15.png

76 ms

16.png

16.png

74 ms

17.png

17.png

79 ms

18.png

18.png

79 ms

19.png

19.png

80 ms

ct_logo_text.png

ct_logo_text.png

84 ms

d

d

4 ms

d

d

12 ms

d

d

15 ms

d

d

284 ms

d

d

51 ms

d

d

50 ms

d

d

17 ms

d

d

50 ms

fa-light-300.woff

fa-light-300.woff

15 ms

fa-regular-400.woff

fa-regular-400.woff

15 ms

fa-solid-900.woff

fa-solid-900.woff

15 ms

fa-brands-400.woff

fa-brands-400.woff

15 ms

api.js

api.js

17 ms

Accessibility Review

churchtrac.com accessibility score

79

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

churchtrac.com SEO score

91

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

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 Churchtrac.com 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 Churchtrac.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

churchtrac.com

Open Graph description is not detected on the main page of Church Trac. 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: