Tools & Wizards About Us
holycomm.org screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

holycomm.org

The Church of the Holy Communion • Episcopal Church in Charleston SC

Page Load Speed

3.9 sec in total

First Response

123 ms

Resources Loaded

3.5 sec

Page Rendered

272 ms

holycomm.org screenshot

About Website

Welcome to holycomm.org homepage info - get ready to check Holy Comm best content right away, or after learning these important things about holycomm.org

All are welcome at the Church of the Holy Communion, to spend some quiet time alone with your prayers in this historic building, or discover the transcendent glory of a solemn high mass, or to enjoy t...

Visit holycomm.org

Key Findings

We analyzed Holycomm.org page load time and found that the first response time was 123 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

holycomm.org performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

holycomm.org

123 ms

holycomm.org

78 ms

bb-plugin.min.css

18 ms

style.min.css

37 ms

astra-local-fonts.css

33 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 92% of them (55 requests) were addressed to the original Holycomm.org, 7% (4 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Holycomm.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 156.0 kB (31%)

Content Size

508.0 kB

After Optimization

352.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Holycomm.org main page is 508.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. 55% of websites need less resources to load. Javascripts take 179.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 122.2 kB

  • Original 150.5 kB
  • After minification 150.3 kB
  • After compression 28.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 122.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 40 B

  • Original 84.6 kB
  • After minification 84.5 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. Holy Comm images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 15.9 kB

  • Original 179.7 kB
  • After minification 179.2 kB
  • After compression 163.8 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

-19%

Potential reduce by 17.8 kB

  • Original 93.1 kB
  • After minification 90.4 kB
  • After compression 75.3 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. Holycomm.org needs all CSS files to be minified and compressed as it can save up to 17.8 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (92%)

Requests Now

52

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

holycomm.org

holycomm.org

123 ms

holycomm.org

holycomm.org

78 ms

bb-plugin.min.css

bb-plugin.min.css

18 ms

style.min.css

style.min.css

37 ms

astra-local-fonts.css

astra-local-fonts.css

33 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

38 ms

style.min.css

style.min.css

38 ms

9-layout.css

9-layout.css

41 ms

style.css

style.css

27 ms

3012f69f31eba10a407d6fb948b48cfb-layout-bundle.css

3012f69f31eba10a407d6fb948b48cfb-layout-bundle.css

44 ms

astra-addon-66c77ad83117d1-77509459.css

astra-addon-66c77ad83117d1-77509459.css

47 ms

style.css

style.css

51 ms

animate.min.css

animate.min.css

49 ms

css

css

44 ms

jquery.min.js

jquery.min.js

56 ms

holycomm.org

holycomm.org

53 ms

variables-skeleton.min.css

variables-skeleton.min.css

53 ms

common-skeleton.min.css

common-skeleton.min.css

53 ms

widget-events-list-skeleton.min.css

widget-events-list-skeleton.min.css

130 ms

variables-full.min.css

variables-full.min.css

126 ms

common-full.min.css

common-full.min.css

127 ms

widget-events-list-full.min.css

widget-events-list-full.min.css

128 ms

widgets-events-common-skeleton.min.css

widgets-events-common-skeleton.min.css

131 ms

widgets-events-common-full.min.css

widgets-events-common-full.min.css

130 ms

archives.min.css

archives.min.css

136 ms

basic.min.css

basic.min.css

131 ms

theme-ie11.min.css

theme-ie11.min.css

136 ms

theme.min.css

theme.min.css

137 ms

gravity-forms.min.css

gravity-forms.min.css

141 ms

widget-events-list-skeleton.min.css

widget-events-list-skeleton.min.css

139 ms

widget-events-list-full.min.css

widget-events-list-full.min.css

140 ms

style.min.js

style.min.js

140 ms

9-layout.js

9-layout.js

153 ms

lazysizes.min.js

lazysizes.min.js

154 ms

jquery.imagesloaded.min.js

jquery.imagesloaded.min.js

153 ms

jquery.ba-throttle-debounce.min.js

jquery.ba-throttle-debounce.min.js

153 ms

ffd07de60e55c570983ea8ef72f08cec-layout-bundle.js

ffd07de60e55c570983ea8ef72f08cec-layout-bundle.js

152 ms

astra-addon-66c77ad8358610-16960613.js

astra-addon-66c77ad8358610-16960613.js

153 ms

tribe-common.min.js

tribe-common.min.js

146 ms

query-string.min.js

query-string.min.js

137 ms

underscore-before.js

underscore-before.js

131 ms

underscore-after.js

underscore-after.js

126 ms

manager.min.js

manager.min.js

126 ms

breakpoints.min.js

breakpoints.min.js

128 ms

hooks.min.js

hooks.min.js

130 ms

i18n.min.js

i18n.min.js

124 ms

jquery.json.min.js

jquery.json.min.js

123 ms

gravityforms.min.js

gravityforms.min.js

227 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

118 ms

utils.min.js

utils.min.js

227 ms

vendor-theme.min.js

vendor-theme.min.js

234 ms

scripts-theme.min.js

scripts-theme.min.js

235 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

170 ms

siteground-optimizer-combined-js-9bee6529deaf72a8dbff340804d84fad.js

siteground-optimizer-combined-js-9bee6529deaf72a8dbff340804d84fad.js

3107 ms

CHC-Homepage.jpg

CHC-Homepage.jpg

166 ms

logo-the-diocese-of-sc-10-2019-1.png

logo-the-diocese-of-sc-10-2019-1.png

158 ms

icomoon.ttf

icomoon.ttf

32 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

32 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

45 ms

zrf-0GXbz-H3Wb4XBsGrTgq2PVmdmATiog.ttf

zrf-0GXbz-H3Wb4XBsGrTgq2PVmdmATiog.ttf

46 ms

Accessibility Review

holycomm.org accessibility score

96

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

Some elements have a [tabindex] value greater than 0

Best Practices

holycomm.org best practices score

83

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

Browser errors were logged to the console

SEO Factors

holycomm.org SEO score

99

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

holycomm.org

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