Tools & Wizards About Us
ourgrace.church screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ourgrace.church

Independent Baptist Church | Grace Baptist Church Chattanooga | United States

Page Load Speed

1.9 sec in total

First Response

113 ms

Resources Loaded

1.4 sec

Page Rendered

297 ms

ourgrace.church screenshot

About Website

Visit ourgrace.church now to see the best up-to-date Our Grace content and also check out these interesting facts you probably never knew about ourgrace.church

Grace Baptist is an Independent Baptist Church in Chattanooga, Tenn. Our mission is to glorify God by delighting in and declaring the person and work of Jesus Christ. In short... Enjoy God. Tell Other...

Visit ourgrace.church

Key Findings

We analyzed Ourgrace.church page load time and found that the first response time was 113 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

ourgrace.church performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value1,960 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

www.ourgrace.church

113 ms

minified.js

34 ms

focus-within-polyfill.js

80 ms

polyfill.min.js

1059 ms

thunderbolt-commons.b70ee867.bundle.min.js

66 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Ourgrace.church, 53% (9 requests) were made to Static.parastorage.com and 29% (5 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 591.0 kB (59%)

Content Size

995.0 kB

After Optimization

404.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ourgrace.church main page is 995.0 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. HTML takes 675.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 542.9 kB

  • Original 675.2 kB
  • After minification 673.5 kB
  • After compression 132.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 542.9 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-16%

Potential reduce by 48.1 kB

  • Original 304.3 kB
  • After minification 304.3 kB
  • After compression 256.2 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 48.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (63%)

Requests Now

16

After Optimization

6

  • Images
  • JavaScript

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

Network Requests Diagram

www.ourgrace.church

www.ourgrace.church

113 ms

minified.js

minified.js

34 ms

focus-within-polyfill.js

focus-within-polyfill.js

80 ms

polyfill.min.js

polyfill.min.js

1059 ms

thunderbolt-commons.b70ee867.bundle.min.js

thunderbolt-commons.b70ee867.bundle.min.js

66 ms

main.317ed945.bundle.min.js

main.317ed945.bundle.min.js

66 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

62 ms

lodash.min.js

lodash.min.js

67 ms

react.production.min.js

react.production.min.js

64 ms

react-dom.production.min.js

react-dom.production.min.js

71 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

68 ms

Symbol%20cropped.png

Symbol%20cropped.png

82 ms

162a49_295d45b7ca294cbf92399e732aeb3ac5~mv2.jpg

162a49_295d45b7ca294cbf92399e732aeb3ac5~mv2.jpg

110 ms

162a49_d23c1283c7774b6e98e36752e54d92e8~mv2.jpg

162a49_d23c1283c7774b6e98e36752e54d92e8~mv2.jpg

115 ms

ebb8500360674f40bd4d9f8745f30f17.jpg

ebb8500360674f40bd4d9f8745f30f17.jpg

115 ms

1%20Grace%20Baptist%20Church%20rendering%20square_.jpg

1%20Grace%20Baptist%20Church%20rendering%20square_.jpg

116 ms

bundle.min.js

bundle.min.js

66 ms

Accessibility Review

ourgrace.church accessibility score

95

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

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

Best Practices

ourgrace.church best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ourgrace.church SEO score

86

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

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

ourgrace.church

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