Tools & Wizards About Us
wpcfayetteville.org screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

wpcfayetteville.org

Westminster Presbyterian Church / Fayetteville

Page Load Speed

921 ms in total

First Response

130 ms

Resources Loaded

737 ms

Page Rendered

54 ms

wpcfayetteville.org screenshot

About Website

Visit wpcfayetteville.org now to see the best up-to-date Wpc Fayetteville content and also check out these interesting facts you probably never knew about wpcfayetteville.org

Westiminster Presbyterian Church in Fayetteville, NC is a place to grow in your faith with the love and support of a church family who wouldn't let you go through life alone.

Visit wpcfayetteville.org

Key Findings

We analyzed Wpcfayetteville.org page load time and found that the first response time was 130 ms and then it took 791 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

wpcfayetteville.org performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value2,900 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

www.wpcfayetteville.org

130 ms

minified.js

43 ms

focus-within-polyfill.js

39 ms

polyfill.min.js

37 ms

thunderbolt-commons.8db75bde.bundle.min.js

99 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 643.0 kB (56%)

Content Size

1.2 MB

After Optimization

507.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wpcfayetteville.org main page is 1.2 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. 30% of websites need less resources to load. HTML takes 732.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 591.2 kB

  • Original 732.4 kB
  • After minification 730.8 kB
  • After compression 141.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 591.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 107.3 kB
  • After minification 107.3 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. Wpc Fayetteville images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 51.8 kB

  • Original 310.4 kB
  • After minification 310.4 kB
  • After compression 258.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 51.8 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (61%)

Requests Now

18

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wpcfayetteville.org

www.wpcfayetteville.org

130 ms

minified.js

minified.js

43 ms

focus-within-polyfill.js

focus-within-polyfill.js

39 ms

polyfill.min.js

polyfill.min.js

37 ms

thunderbolt-commons.8db75bde.bundle.min.js

thunderbolt-commons.8db75bde.bundle.min.js

99 ms

main.aaff206b.bundle.min.js

main.aaff206b.bundle.min.js

102 ms

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

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

98 ms

lodash.min.js

lodash.min.js

101 ms

react.production.min.js

react.production.min.js

99 ms

react-dom.production.min.js

react-dom.production.min.js

102 ms

browser-deprecation.bundle.es5.js

browser-deprecation.bundle.es5.js

115 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

101 ms

93322e_907fe1bfb9224aa8963da17af6beae31~mv2.jpg

93322e_907fe1bfb9224aa8963da17af6beae31~mv2.jpg

283 ms

bundle.min.js

bundle.min.js

50 ms

5e23ae_364193eb4d6a45508ae4afd2b745744b~mv2.jpg

5e23ae_364193eb4d6a45508ae4afd2b745744b~mv2.jpg

342 ms

114 ms

112 ms

112 ms

107 ms

110 ms

101 ms

151 ms

149 ms

144 ms

150 ms

145 ms

146 ms

187 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 ms

bolt-performance

bolt-performance

20 ms

deprecation-style.v5.css

deprecation-style.v5.css

7 ms

right-arrow.svg

right-arrow.svg

6 ms

Accessibility Review

wpcfayetteville.org accessibility score

91

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

Buttons do not have an accessible name

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

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

Missing source maps for large first-party JavaScript

SEO Factors

wpcfayetteville.org SEO score

100

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

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

wpcfayetteville.org

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