Tools & Wizards About Us
thechapelchurch.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

thechapelchurch.com

Church in Chapel Hill, North Carolina - The Chapel of Chapel Hill

Page Load Speed

1.1 sec in total

First Response

89 ms

Resources Loaded

991 ms

Page Rendered

54 ms

thechapelchurch.com screenshot

About Website

Welcome to thechapelchurch.com homepage info - get ready to check The Chapel Church best content right away, or after learning these important things about thechapelchurch.com

The Chapel is a vibrant and welcoming church in Chapel Hill, North Carolina. We offer many ministries for children and adults. Come join us!

Visit thechapelchurch.com

Key Findings

We analyzed Thechapelchurch.com page load time and found that the first response time was 89 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

thechapelchurch.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

55/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

www.thechapelchurch.com

89 ms

minified.js

32 ms

focus-within-polyfill.js

31 ms

polyfill.min.js

31 ms

thunderbolt-commons.761c7707.bundle.min.js

96 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 734.4 kB (63%)

Content Size

1.2 MB

After Optimization

438.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Thechapelchurch.com main page is 1.2 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. 20% of websites need less resources to load. HTML takes 842.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 681.8 kB

  • Original 842.6 kB
  • After minification 840.9 kB
  • After compression 160.7 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 681.8 kB or 81% of the original size.

Image Optimization

-19%

Potential reduce by 4.4 kB

  • Original 23.6 kB
  • After minification 19.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. Obviously, The Chapel Church needs image optimization as it can save up to 4.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 48.1 kB

  • Original 306.8 kB
  • After minification 306.8 kB
  • After compression 258.7 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 11 (46%)

Requests Now

24

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.thechapelchurch.com

www.thechapelchurch.com

89 ms

minified.js

minified.js

32 ms

focus-within-polyfill.js

focus-within-polyfill.js

31 ms

polyfill.min.js

polyfill.min.js

31 ms

thunderbolt-commons.761c7707.bundle.min.js

thunderbolt-commons.761c7707.bundle.min.js

96 ms

main.aaff206b.bundle.min.js

main.aaff206b.bundle.min.js

107 ms

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

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

96 ms

lodash.min.js

lodash.min.js

95 ms

react.production.min.js

react.production.min.js

93 ms

react-dom.production.min.js

react-dom.production.min.js

107 ms

browser-deprecation.bundle.es5.js

browser-deprecation.bundle.es5.js

107 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

117 ms

Untitled%20design%203_47_34%20PM.png

Untitled%20design%203_47_34%20PM.png

275 ms

bundle.min.js

bundle.min.js

58 ms

21b246_c7423a75a9564673a1fe1f5ed01d77abf000.jpg

21b246_c7423a75a9564673a1fe1f5ed01d77abf000.jpg

414 ms

Coffee.png

Coffee.png

423 ms

worship.png

worship.png

390 ms

21b246_c0b91e5718ee4f3093cf7992f627235ff000.jpg

21b246_c0b91e5718ee4f3093cf7992f627235ff000.jpg

409 ms

21b246_a051e98c22374e0a8d039c93bcbf0046~mv2.png

21b246_a051e98c22374e0a8d039c93bcbf0046~mv2.png

462 ms

20b7c2_6cfed92345e44fabaf3bd48389505c56~mv2.png

20b7c2_6cfed92345e44fabaf3bd48389505c56~mv2.png

517 ms

20b7c2_03c40fef5c644708849c742824a484c0~mv2.png

20b7c2_03c40fef5c644708849c742824a484c0~mv2.png

656 ms

104 ms

103 ms

103 ms

102 ms

100 ms

101 ms

130 ms

130 ms

126 ms

126 ms

125 ms

125 ms

165 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

17 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

5 ms

Accessibility Review

thechapelchurch.com accessibility score

88

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

Best Practices

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

thechapelchurch.com SEO score

84

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

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

thechapelchurch.com

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