Report Summary

  • 87

    Performance

    Renders faster than
    90% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

churchdb.org

ChurchInfo open source church database created with PHP & MySQL! - ChurchInfo open source church database created with PHP & MySQL!

Page Load Speed

1.7 sec in total

First Response

395 ms

Resources Loaded

786 ms

Page Rendered

551 ms

churchdb.org screenshot

About Website

Click here to check amazing Church Db content for Nigeria. Otherwise, check out these important facts you probably never knew about churchdb.org

ChurchInfo is a free church database program to help churches track members, families, groups, pledges and payments. Our feature set is comparable to expensive church management software packages. Our...

Visit churchdb.org

Key Findings

We analyzed Churchdb.org page load time and found that the first response time was 395 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

churchdb.org performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value3.1 s

92/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

churchdb.org

395 ms

cssloader.php

136 ms

newsletter.css

91 ms

modal.css

88 ms

jsloader.php

175 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that all of those requests were addressed to Churchdb.org and no external sources were called. The less responsive or slowest element that took the longest time to load (395 ms) belongs to the original domain Churchdb.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 240.2 kB (62%)

Content Size

384.6 kB

After Optimization

144.3 kB

In fact, the total size of Churchdb.org main page is 384.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 280.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 36.7 kB

  • Original 48.7 kB
  • After minification 46.8 kB
  • After compression 12.0 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 36.7 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 1.8 kB

  • Original 44.1 kB
  • After minification 42.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. Church Db images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 193.2 kB

  • Original 280.2 kB
  • After minification 269.4 kB
  • After compression 87.0 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 193.2 kB or 69% of the original size.

CSS Optimization

-74%

Potential reduce by 8.5 kB

  • Original 11.5 kB
  • After minification 10.3 kB
  • After compression 3.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. Churchdb.org needs all CSS files to be minified and compressed as it can save up to 8.5 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (50%)

Requests Now

18

After Optimization

9

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

Accessibility Review

churchdb.org accessibility score

65

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

churchdb.org 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

churchdb.org SEO score

62

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

High

Image elements do not have [alt] attributes

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

Social Sharing Optimization

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