Tools & Wizards About Us
ekerk.org screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ekerk.org

Wat is ekerk | South Africa | Ekerk

Page Load Speed

2.9 sec in total

First Response

170 ms

Resources Loaded

2.7 sec

Page Rendered

57 ms

ekerk.org screenshot

About Website

Welcome to ekerk.org homepage info - get ready to check Ekerk best content for South Africa right away, or after learning these important things about ekerk.org

Ekerk maak Jesus sigbaar, voelbaar en verstaanbaar. Ekerk is nie 'n eie kerk nie. Ekerk vervang ook nie jou plaaslike gemeente nie. Ekerk is bloot net nog 'n manier om kerk te wees in die wêreld.

Visit ekerk.org

Key Findings

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

Performance Metrics

ekerk.org performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value1,960 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

www.ekerk.org

170 ms

minified.js

66 ms

focus-within-polyfill.js

66 ms

polyfill.min.js

1409 ms

optimize.js

131 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Ekerk.org, 31% (18 requests) were made to Static.parastorage.com and 29% (17 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (51%)

Content Size

2.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ekerk.org main page is 2.1 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. 60% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 889.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 202.8 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 889.9 kB or 81% of the original size.

Image Optimization

-18%

Potential reduce by 134.6 kB

  • Original 728.0 kB
  • After minification 593.4 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, Ekerk needs image optimization as it can save up to 134.6 kB or 18% 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 294.7 kB
  • After minification 294.7 kB
  • After compression 246.5 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 15 (38%)

Requests Now

39

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ekerk.org

www.ekerk.org

170 ms

minified.js

minified.js

66 ms

focus-within-polyfill.js

focus-within-polyfill.js

66 ms

polyfill.min.js

polyfill.min.js

1409 ms

optimize.js

optimize.js

131 ms

smart-app-banner.css

smart-app-banner.css

1131 ms

smart-app-banner.js

smart-app-banner.js

1066 ms

thunderbolt-commons.35876736.bundle.min.js

thunderbolt-commons.35876736.bundle.min.js

100 ms

main.cd290f82.bundle.min.js

main.cd290f82.bundle.min.js

99 ms

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

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

101 ms

lodash.min.js

lodash.min.js

106 ms

react.production.min.js

react.production.min.js

106 ms

react-dom.production.min.js

react-dom.production.min.js

106 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

105 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

103 ms

uwt.js

uwt.js

111 ms

gtm.js

gtm.js

171 ms

d6fab7_b88ee06e15754564b91cd8c039dc9fa4.png

d6fab7_b88ee06e15754564b91cd8c039dc9fa4.png

158 ms

d6fab7_2a3e6af09c9b4e609aaa5070b789250d~mv2.jpg

d6fab7_2a3e6af09c9b4e609aaa5070b789250d~mv2.jpg

490 ms

d6fab7_36642640f7a84629ae202be6cf86fd25~mv2.png

d6fab7_36642640f7a84629ae202be6cf86fd25~mv2.png

493 ms

d6fab7_fd938d00b09d483ca22fb99c7f88eda6~mv2.png

d6fab7_fd938d00b09d483ca22fb99c7f88eda6~mv2.png

304 ms

d6fab7_cfc5dbf53f6d47ad9844f294bd4250c1~mv2.png

d6fab7_cfc5dbf53f6d47ad9844f294bd4250c1~mv2.png

493 ms

d6fab7_48eeb4687d2a414a9340cf2bc66d3d63~mv2.png

d6fab7_48eeb4687d2a414a9340cf2bc66d3d63~mv2.png

223 ms

d6fab7_75b12b2ea2134e148a4e2b9cfea95d13~mv2.png

d6fab7_75b12b2ea2134e148a4e2b9cfea95d13~mv2.png

503 ms

d6fab7_23a5bfc51931441b95bd549c437b33b2~mv2.png

d6fab7_23a5bfc51931441b95bd549c437b33b2~mv2.png

492 ms

d6fab7_26bcb3c8882645439304d0a0fd6a3fd6~mv2.png

d6fab7_26bcb3c8882645439304d0a0fd6a3fd6~mv2.png

503 ms

d6fab7_d8dc49d471274d4792c9fec65d7cd97a~mv2.png

d6fab7_d8dc49d471274d4792c9fec65d7cd97a~mv2.png

692 ms

Payfast_white.png

Payfast_white.png

658 ms

snapscan%20grys_edited_edited.png

snapscan%20grys_edited_edited.png

665 ms

Zapper%20logo%20wit.png

Zapper%20logo%20wit.png

758 ms

d6fab7_2e7c9df3a05248f49578e4539e761ec8~mv2.png

d6fab7_2e7c9df3a05248f49578e4539e761ec8~mv2.png

786 ms

d6fab7_d3e52ecf405f4ac0ad6a2a081211946d~mv2.png

d6fab7_d3e52ecf405f4ac0ad6a2a081211946d~mv2.png

755 ms

Apple%20store%20wit.png

Apple%20store%20wit.png

904 ms

d6fab7_9d3972f12aee4d378cc937827a524643~mv2.png

d6fab7_9d3972f12aee4d378cc937827a524643~mv2.png

879 ms

bundle.min.js

bundle.min.js

143 ms

adsct

adsct

178 ms

adsct

adsct

346 ms

c5749443-93da-4592-b794-42f28d62ef72.woff

c5749443-93da-4592-b794-42f28d62ef72.woff

65 ms

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

65 ms

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

65 ms

03805817-4611-4dbc-8c65-0f73031c3973.woff

03805817-4611-4dbc-8c65-0f73031c3973.woff

64 ms

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

65 ms

js

js

95 ms

267 ms

265 ms

280 ms

275 ms

278 ms

270 ms

298 ms

295 ms

314 ms

311 ms

313 ms

308 ms

deprecation-en.v5.html

deprecation-en.v5.html

20 ms

bolt-performance

bolt-performance

17 ms

deprecation-style.v5.css

deprecation-style.v5.css

7 ms

right-arrow.svg

right-arrow.svg

3 ms

Accessibility Review

ekerk.org accessibility score

77

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

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

High

Page has valid source maps

SEO Factors

ekerk.org SEO score

83

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    AF

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ekerk.org can be misinterpreted by Google and other search engines. Our service has detected that Afrikaans is used on the page, and it does not match the claimed English language. Our system also found out that Ekerk.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

ekerk.org

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