Tools & Wizards About Us
wchgrace.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

wchgrace.com

WCH Grace Methodist Church - Home

Page Load Speed

4 sec in total

First Response

171 ms

Resources Loaded

3 sec

Page Rendered

870 ms

wchgrace.com screenshot

About Website

Welcome to wchgrace.com homepage info - get ready to check WCH Grace best content right away, or after learning these important things about wchgrace.com

Visit wchgrace.com

Key Findings

We analyzed Wchgrace.com page load time and found that the first response time was 171 ms and then it took 3.9 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

wchgrace.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value20.6 s

0/100

10%

TBT (Total Blocking Time)

Value8,140 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.203

61/100

15%

TTI (Time to Interactive)

Value57.2 s

0/100

10%

Network Requests Diagram

wchgrace.com

171 ms

wchgrace.com

565 ms

jquery.min.js

107 ms

website.min.css

92 ms

website.min.js

109 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Wchgrace.com, 42% (32 requests) were made to Share.fluro.io and 13% (10 requests) were made to Storage2.snappages.site. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Share.fluro.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 925.2 kB (16%)

Content Size

5.9 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wchgrace.com main page is 5.9 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. Javascripts take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 25.2 kB

  • Original 34.5 kB
  • After minification 34.2 kB
  • After compression 9.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 25.2 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 22.3 kB

  • Original 1.8 MB
  • After minification 1.7 MB

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. WCH Grace images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 877.7 kB

  • Original 4.0 MB
  • After minification 4.0 MB
  • After compression 3.1 MB

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 877.7 kB or 22% of the original size.

CSS Optimization

-0%

Potential reduce by 24 B

  • Original 89.0 kB
  • After minification 89.0 kB
  • After compression 89.0 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. Wchgrace.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (70%)

Requests Now

61

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wchgrace.com

wchgrace.com

171 ms

wchgrace.com

wchgrace.com

565 ms

jquery.min.js

jquery.min.js

107 ms

website.min.css

website.min.css

92 ms

website.min.js

website.min.js

109 ms

style1698934677.css

style1698934677.css

91 ms

fa-brands-400.ttf

fa-brands-400.ttf

108 ms

fa-brands-400.woff2

fa-brands-400.woff2

106 ms

fa-regular-400.ttf

fa-regular-400.ttf

104 ms

fa-regular-400.woff2

fa-regular-400.woff2

83 ms

fa-solid-900.ttf

fa-solid-900.ttf

119 ms

fa-solid-900.woff2

fa-solid-900.woff2

121 ms

all.min.css

all.min.css

108 ms

12668201_1563x1563_500.png

12668201_1563x1563_500.png

385 ms

embed-1.1.0.js

embed-1.1.0.js

317 ms

*

*

287 ms

6539266064885900371e0873

6539266064885900371e0873

1300 ms

11603339_3024x4032_1000.jpg

11603339_3024x4032_1000.jpg

606 ms

13264060_3024x4032_1000.jpg

13264060_3024x4032_1000.jpg

645 ms

13264091_4032x3024_1000.jpg

13264091_4032x3024_1000.jpg

607 ms

13264096_3024x4032_1000.jpg

13264096_3024x4032_1000.jpg

607 ms

13714903_1500x1125_500.jpg

13714903_1500x1125_500.jpg

354 ms

11603339_3024x4032_500.jpg

11603339_3024x4032_500.jpg

719 ms

13255728_3024x4032_500.jpg

13255728_3024x4032_500.jpg

840 ms

11603468_3024x4032_500.jpg

11603468_3024x4032_500.jpg

1075 ms

web-client-3c753ce8161b90f93b54fcb966ceeec7.css

web-client-3c753ce8161b90f93b54fcb966ceeec7.css

286 ms

blur.jpg

blur.jpg

30 ms

image.jpg

image.jpg

38 ms

vendor-9d17d536fd7112143f70ea8fb39ab337.js

vendor-9d17d536fd7112143f70ea8fb39ab337.js

282 ms

chunk.695.07e104dbf78548f8c5b7.js

chunk.695.07e104dbf78548f8c5b7.js

594 ms

chunk.143.22e258310f6f8bfd2e84.js

chunk.143.22e258310f6f8bfd2e84.js

208 ms

web-client-4b2051734a27318fc5de3ae194c843d6.js

web-client-4b2051734a27318fc5de3ae194c843d6.js

81 ms

analytics.js

analytics.js

26 ms

60 ms

image.jpg

image.jpg

10 ms

+j7srzs7

+j7srzs7

405 ms

ProximaNova-Sbold-webfont-bba11955959ea56cb0c1ae3d3b9b9b2a.woff

ProximaNova-Sbold-webfont-bba11955959ea56cb0c1ae3d3b9b9b2a.woff

299 ms

ProximaNova-Bold-webfont-0988922e8ed380689ca54855833342c9.woff

ProximaNova-Bold-webfont-0988922e8ed380689ca54855833342c9.woff

298 ms

ProximaNova-ExtraBold-webfont-b5afb0b6e2896cbe7ba8b2658d44da58.woff

ProximaNova-ExtraBold-webfont-b5afb0b6e2896cbe7ba8b2658d44da58.woff

300 ms

ProximaNova-Reg-webfont-5d0e746af028be8766181f227b3e87d1.woff

ProximaNova-Reg-webfont-5d0e746af028be8766181f227b3e87d1.woff

298 ms

ProximaNova-Light-webfont-01593b54d9e1069e75813fbd5b81d2dd.woff

ProximaNova-Light-webfont-01593b54d9e1069e75813fbd5b81d2dd.woff

77 ms

proximanova-thin-webfont-91a681efaf81cd7941866a196ad9b2b9.woff

proximanova-thin-webfont-91a681efaf81cd7941866a196ad9b2b9.woff

298 ms

fit-white.png

fit-white.png

6 ms

image.jpg

image.jpg

7 ms

image.png

image.png

7 ms

style.css

style.css

560 ms

css

css

25 ms

3f5dd89.js

3f5dd89.js

106 ms

3d3ca27.js

3d3ca27.js

186 ms

f11eea0.js

f11eea0.js

326 ms

11021c8.js

11021c8.js

546 ms

37cabca.js

37cabca.js

708 ms

61ef54b.js

61ef54b.js

609 ms

c23cfb4.js

c23cfb4.js

273 ms

8e80726.js

8e80726.js

571 ms

2e2b444.js

2e2b444.js

429 ms

c65fbb4.js

c65fbb4.js

474 ms

d9da7c3.js

d9da7c3.js

479 ms

fe8e14f.js

fe8e14f.js

550 ms

754b6ce.js

754b6ce.js

561 ms

4b47d05.js

4b47d05.js

638 ms

2d7d4f6.js

2d7d4f6.js

628 ms

5ea16b1.js

5ea16b1.js

641 ms

a0f0802.js

a0f0802.js

649 ms

b0380bb.js

b0380bb.js

687 ms

1b68fc1.js

1b68fc1.js

765 ms

622ad9c.js

622ad9c.js

769 ms

e4711ac.js

e4711ac.js

770 ms

bdddbbf.js

bdddbbf.js

769 ms

650fe86.js

650fe86.js

780 ms

b1b608a.js

b1b608a.js

809 ms

651994e.js

651994e.js

798 ms

24e4dde.js

24e4dde.js

800 ms

ecc151c.js

ecc151c.js

825 ms

0a3ff1a.js

0a3ff1a.js

828 ms

8843536.js

8843536.js

875 ms

ce5d023.js

ce5d023.js

893 ms

Accessibility Review

wchgrace.com accessibility score

66

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

wchgrace.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

wchgrace.com SEO score

77

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wchgrace.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wchgrace.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

wchgrace.com

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