Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

episcopalimpact.org

Episcopal Impact Fund | Bay Area Community and Congretional Grants

Page Load Speed

1.1 sec in total

First Response

62 ms

Resources Loaded

957 ms

Page Rendered

73 ms

episcopalimpact.org screenshot

About Website

Welcome to episcopalimpact.org homepage info - get ready to check Episcopal Impact best content right away, or after learning these important things about episcopalimpact.org

Episcopal Impact Fund promotes innovative, long-term solutions through Community and Congregational Grants to address the root causes of poverty in the Bay Area.

Visit episcopalimpact.org

Key Findings

We analyzed Episcopalimpact.org page load time and found that the first response time was 62 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

episcopalimpact.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,940 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

www.episcopalimpact.org

62 ms

minified.js

37 ms

focus-within-polyfill.js

76 ms

polyfill.min.js

144 ms

thunderbolt-commons.ec68bee9.bundle.min.js

60 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 841.0 kB (60%)

Content Size

1.4 MB

After Optimization

568.1 kB

In fact, the total size of Episcopalimpact.org 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. 40% of websites need less resources to load. HTML takes 923.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 745.3 kB

  • Original 923.9 kB
  • After minification 922.2 kB
  • After compression 178.6 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 745.3 kB or 81% of the original size.

Image Optimization

-36%

Potential reduce by 92.9 kB

  • Original 256.8 kB
  • After minification 163.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. Obviously, Episcopal Impact needs image optimization as it can save up to 92.9 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 2.7 kB

  • Original 228.3 kB
  • After minification 228.3 kB
  • After compression 225.6 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.

Requests Breakdown

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

Requests Now

28

After Optimization

16

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

Accessibility Review

episcopalimpact.org accessibility score

91

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

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

episcopalimpact.org 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

episcopalimpact.org SEO score

86

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

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

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