Tools & Wizards About Us
evangel.church screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

evangel.church

Evangel Church | A Contemporary Church in Kansas City

Page Load Speed

886 ms in total

First Response

130 ms

Resources Loaded

689 ms

Page Rendered

67 ms

evangel.church screenshot

About Website

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

Evangel Church in Kansas City is a family-friendly, diverse, and relevant church. Services at Evangel Church are engaging, dynamic, and geared toward the entire family. You can expect a relevant, Bibl...

Visit evangel.church

Key Findings

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

Performance Metrics

evangel.church performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value4.8 s

68/100

10%

TBT (Total Blocking Time)

Value1,480 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

www.evangel.church

130 ms

minified.js

42 ms

focus-within-polyfill.js

41 ms

polyfill.min.js

32 ms

thunderbolt-commons.e7839053.bundle.min.js

110 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Evangel.church, 38% (12 requests) were made to Static.parastorage.com and 38% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (349 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 541.4 kB (55%)

Content Size

988.3 kB

After Optimization

446.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Evangel.church main page is 988.3 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. 40% of websites need less resources to load. HTML takes 615.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 485.7 kB

  • Original 615.2 kB
  • After minification 613.5 kB
  • After compression 129.6 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 485.7 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 1.3 kB

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

JavaScript Optimization

-18%

Potential reduce by 54.4 kB

  • Original 310.6 kB
  • After minification 310.5 kB
  • After compression 256.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 54.4 kB or 18% of the original size.

Requests Breakdown

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

Requests Now

19

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Evangel. 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.evangel.church

www.evangel.church

130 ms

minified.js

minified.js

42 ms

focus-within-polyfill.js

focus-within-polyfill.js

41 ms

polyfill.min.js

polyfill.min.js

32 ms

thunderbolt-commons.e7839053.bundle.min.js

thunderbolt-commons.e7839053.bundle.min.js

110 ms

main.760485a2.bundle.min.js

main.760485a2.bundle.min.js

127 ms

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

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

112 ms

lodash.min.js

lodash.min.js

126 ms

react.production.min.js

react.production.min.js

109 ms

react-dom.production.min.js

react-dom.production.min.js

113 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

125 ms

4fb520_06f30057bde445b1bb548bc4d4b5d068~mv2.png

4fb520_06f30057bde445b1bb548bc4d4b5d068~mv2.png

349 ms

bundle.min.js

bundle.min.js

63 ms

11062b_cb0c4d13153f4008920bb26beda8de0ff000.jpg

11062b_cb0c4d13153f4008920bb26beda8de0ff000.jpg

39 ms

Halloween%202024%20SLIDE.jpg

Halloween%202024%20SLIDE.jpg

224 ms

Evangel%20logo%20NO%20WHITE.png

Evangel%20logo%20NO%20WHITE.png

258 ms

130 ms

125 ms

112 ms

114 ms

116 ms

115 ms

151 ms

151 ms

153 ms

150 ms

147 ms

146 ms

deprecation-en.v5.html

deprecation-en.v5.html

7 ms

bolt-performance

bolt-performance

24 ms

deprecation-style.v5.css

deprecation-style.v5.css

6 ms

right-arrow.svg

right-arrow.svg

5 ms

Accessibility Review

evangel.church accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

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

evangel.church SEO score

98

Search Engine Optimization Advices

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

evangel.church

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