Tools & Wizards About Us
ctdiocese.org.za screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ctdiocese.org.za

Anglican Diocese of Cape Town – | Anglican Church of Southern Africa

Page Load Speed

7.2 sec in total

First Response

668 ms

Resources Loaded

6.2 sec

Page Rendered

327 ms

ctdiocese.org.za screenshot

About Website

Visit ctdiocese.org.za now to see the best up-to-date Ct Diocese content for South Africa and also check out these interesting facts you probably never knew about ctdiocese.org.za

Visit ctdiocese.org.za

Key Findings

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

Performance Metrics

ctdiocese.org.za performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value460 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

ctdiocese.org.za

668 ms

ctdiocese.org.za

1486 ms

embed-pdf-viewer.css

18 ms

custom-frontend-lite.min.css

25 ms

post-205.css

34 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 88% of them (86 requests) were addressed to the original Ctdiocese.org.za, 10% (10 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Ctdiocese.org.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 206.7 kB (15%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ctdiocese.org.za main page is 1.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 628.9 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 203.2 kB

  • Original 235.3 kB
  • After minification 230.9 kB
  • After compression 32.2 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 203.2 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 628.9 kB
  • After minification 628.9 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. Ct Diocese images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 496 B

  • Original 272.3 kB
  • After minification 272.3 kB
  • After compression 271.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

-1%

Potential reduce by 3.1 kB

  • Original 246.5 kB
  • After minification 244.5 kB
  • After compression 243.4 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. Ctdiocese.org.za has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 73 (89%)

Requests Now

82

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ctdiocese.org.za

ctdiocese.org.za

668 ms

ctdiocese.org.za

ctdiocese.org.za

1486 ms

embed-pdf-viewer.css

embed-pdf-viewer.css

18 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

25 ms

post-205.css

post-205.css

34 ms

main.min.css

main.min.css

20 ms

css

css

37 ms

tribe-events-single-skeleton.min.css

tribe-events-single-skeleton.min.css

13 ms

tribe-events-single-full.min.css

tribe-events-single-full.min.css

17 ms

widget-base.min.css

widget-base.min.css

18 ms

eae.min.css

eae.min.css

1389 ms

peel.css

peel.css

1086 ms

v4-shims.min.css

v4-shims.min.css

26 ms

all.min.css

all.min.css

31 ms

vegas.min.css

vegas.min.css

30 ms

astra-addon-662f55423866a5-66453958.css

astra-addon-662f55423866a5-66453958.css

28 ms

elementor-icons.min.css

elementor-icons.min.css

37 ms

swiper.min.css

swiper.min.css

35 ms

post-7.css

post-7.css

33 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

35 ms

post-88.css

post-88.css

49 ms

post-1713.css

post-1713.css

1134 ms

ekiticons.css

ekiticons.css

42 ms

style.css

style.css

52 ms

widget-styles.css

widget-styles.css

69 ms

widget-styles-pro.css

widget-styles-pro.css

53 ms

responsive.css

responsive.css

84 ms

general.min.css

general.min.css

86 ms

css

css

36 ms

fontawesome.min.css

fontawesome.min.css

87 ms

solid.min.css

solid.min.css

1145 ms

brands.min.css

brands.min.css

91 ms

jquery.min.js

jquery.min.js

89 ms

jquery-migrate.min.js

jquery-migrate.min.js

90 ms

iconHelper.js

iconHelper.js

1162 ms

jarallax.js

jarallax.js

96 ms

email-decode.min.js

email-decode.min.js

100 ms

post-1522.css

post-1522.css

109 ms

post-1527.css

post-1527.css

118 ms

animations.min.css

animations.min.css

129 ms

elementskit-reset-button.css

elementskit-reset-button.css

142 ms

particles.css

particles.css

154 ms

moppm_elementor.min.js

moppm_elementor.min.js

162 ms

frontend.min.js

frontend.min.js

1249 ms

eae.min.js

eae.min.js

1082 ms

index.min.js

index.min.js

1089 ms

v4-shims.min.js

v4-shims.min.js

1099 ms

animated-main.min.js

animated-main.min.js

1098 ms

particles.min.js

particles.min.js

1106 ms

magnific.min.js

magnific.min.js

1113 ms

vegas.min.js

vegas.min.js

1114 ms

astra-addon-662f554239fd21-57220385.js

astra-addon-662f554239fd21-57220385.js

1120 ms

frontend-script.js

frontend-script.js

1118 ms

widget-scripts.js

widget-scripts.js

1126 ms

anime.js

anime.js

1127 ms

parallax-frontend-scripts.js

parallax-frontend-scripts.js

1112 ms

general.min.js

general.min.js

1120 ms

premium-wrapper-link.min.js

premium-wrapper-link.min.js

1120 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1107 ms

webpack.runtime.min.js

webpack.runtime.min.js

2185 ms

frontend-modules.min.js

frontend-modules.min.js

1096 ms

hooks.min.js

hooks.min.js

1091 ms

i18n.min.js

i18n.min.js

1095 ms

frontend.min.js

frontend.min.js

1097 ms

waypoints.min.js

waypoints.min.js

1100 ms

core.min.js

core.min.js

1103 ms

frontend.min.js

frontend.min.js

2197 ms

elements-handlers.min.js

elements-handlers.min.js

1120 ms

animate-circle.min.js

animate-circle.min.js

1090 ms

elementor.js

elementor.js

1092 ms

elementor.js

elementor.js

1091 ms

elementskit-sticky-content.js

elementskit-sticky-content.js

1089 ms

elementskit-reset-button.js

elementskit-reset-button.js

1076 ms

particles.min.js

particles.min.js

1076 ms

ekit-particles.js

ekit-particles.js

165 ms

parallax-admin-scripts.js

parallax-admin-scripts.js

163 ms

wrapper.js

wrapper.js

151 ms

Diocese-of-Cape-Town-Crest-1.png

Diocese-of-Cape-Town-Crest-1.png

137 ms

bram-house.png

bram-house.png

138 ms

diocesan-family-service-1.jpg

diocesan-family-service-1.jpg

2463 ms

Diocese-of-York-1.png

Diocese-of-York-1.png

139 ms

Diocese-of-False-Bay-1.png

Diocese-of-False-Bay-1.png

139 ms

Diocese-of-Saldanha-Bay-1.png

Diocese-of-Saldanha-Bay-1.png

139 ms

ACSA-Compass-Rose-300x300-1-1-1.png

ACSA-Compass-Rose-300x300-1-1-1.png

140 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fAZ9hjQ.ttf

66 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfAZ9hjQ.ttf

139 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfAZ9hjQ.ttf

175 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfAZ9hjQ.ttf

195 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeAZ9hjQ.ttf

195 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYAZ9hjQ.ttf

195 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYAZ9hjQ.ttf

195 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyYAZ9hjQ.ttf

193 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuBWYAZ9hjQ.ttf

194 ms

-nFnOHM81r4j6k0gjAW3mujVU2B2G_Bx1w.ttf

-nFnOHM81r4j6k0gjAW3mujVU2B2G_Bx1w.ttf

195 ms

elementskit.woff

elementskit.woff

2452 ms

fa-brands-400.woff

fa-brands-400.woff

63 ms

fa-solid-900.woff

fa-solid-900.woff

29 ms

fa-regular-400.woff

fa-regular-400.woff

1414 ms

Accessibility Review

ctdiocese.org.za accessibility score

96

Accessibility Issues

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

ctdiocese.org.za 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

ctdiocese.org.za SEO score

86

Search Engine Optimization Advices

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 Ctdiocese.org.za 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 Ctdiocese.org.za 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

ctdiocese.org.za

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