Tools & Wizards About Us
stmarysphoenix.org screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

stmarysphoenix.org

Welcome to St. Mary's Episcopal Church - Phoenix, AZ

Page Load Speed

2.4 sec in total

First Response

113 ms

Resources Loaded

2.2 sec

Page Rendered

61 ms

stmarysphoenix.org screenshot

About Website

Visit stmarysphoenix.org now to see the best up-to-date St Mary S Phoenix content and also check out these interesting facts you probably never knew about stmarysphoenix.org

St. Mary's Church, Phoenix, is a welcoming, diverse community in the Episcopal Diocese of Arizona. Traditional worship every Sunday at 10am. Welcome!

Visit stmarysphoenix.org

Key Findings

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

Performance Metrics

stmarysphoenix.org performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value420 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

www.stmarysphoenix.org

113 ms

minified.js

25 ms

focus-within-polyfill.js

68 ms

polyfill.min.js

1370 ms

thunderbolt-commons.e8d8c161.bundle.min.js

4 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Stmarysphoenix.org, 39% (17 requests) were made to Static.parastorage.com and 27% (12 requests) were made to Sentry-next.wixpress.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 540.5 kB (55%)

Content Size

982.2 kB

After Optimization

441.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Stmarysphoenix.org main page is 982.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. HTML takes 602.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 473.5 kB

  • Original 602.9 kB
  • After minification 601.2 kB
  • After compression 129.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 473.5 kB or 79% of the original size.

Image Optimization

-22%

Potential reduce by 18.9 kB

  • Original 84.5 kB
  • After minification 65.7 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, St Mary S Phoenix needs image optimization as it can save up to 18.9 kB or 22% 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.8 kB
  • After minification 294.8 kB
  • After compression 246.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 48.1 kB or 16% of the original size.

Requests Breakdown

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

Requests Now

27

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of St Mary S Phoenix. 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.stmarysphoenix.org

www.stmarysphoenix.org

113 ms

minified.js

minified.js

25 ms

focus-within-polyfill.js

focus-within-polyfill.js

68 ms

polyfill.min.js

polyfill.min.js

1370 ms

thunderbolt-commons.e8d8c161.bundle.min.js

thunderbolt-commons.e8d8c161.bundle.min.js

4 ms

main.cd290f82.bundle.min.js

main.cd290f82.bundle.min.js

7 ms

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

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

7 ms

lodash.min.js

lodash.min.js

9 ms

react.production.min.js

react.production.min.js

9 ms

react-dom.production.min.js

react-dom.production.min.js

12 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

10 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

10 ms

b5a917_dda4005b0553411b99f2df9a83bcec45~mv2.png

b5a917_dda4005b0553411b99f2df9a83bcec45~mv2.png

380 ms

b5a917_969cda0b999a4518a16f54fa1081e5b5.png

b5a917_969cda0b999a4518a16f54fa1081e5b5.png

430 ms

b5a917_daf1cb4a93ba4bc9a1cd39d2ae046c6d~mv2.jpg

b5a917_daf1cb4a93ba4bc9a1cd39d2ae046c6d~mv2.jpg

465 ms

episcopal-church-near-me_edited.jpg

episcopal-church-near-me_edited.jpg

322 ms

b5a917_7750a2513c824baf841b98f21b29764c~mv2.png

b5a917_7750a2513c824baf841b98f21b29764c~mv2.png

457 ms

b5a917_1bae2f7b1ed84f9f80e9c99eb3547670~mv2.png

b5a917_1bae2f7b1ed84f9f80e9c99eb3547670~mv2.png

418 ms

st-marys-phoenix-az.png

st-marys-phoenix-az.png

574 ms

st-marys-church-phoenix-arizona-episcopa.png

st-marys-church-phoenix-arizona-episcopa.png

581 ms

st-marys-phoenix-arizona-episcopal-churc.png

st-marys-phoenix-arizona-episcopal-churc.png

691 ms

st-marys-phoenix-arizona-episcopal-churc.png

st-marys-phoenix-arizona-episcopal-churc.png

673 ms

shdtop.42378c12.png

shdtop.42378c12.png

134 ms

bundle.min.js

bundle.min.js

85 ms

file.woff

file.woff

434 ms

118 ms

114 ms

105 ms

109 ms

108 ms

106 ms

118 ms

116 ms

113 ms

114 ms

112 ms

102 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

20 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

14 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

3 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

4 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

8 ms

Accessibility Review

stmarysphoenix.org accessibility score

95

Accessibility Issues

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.

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

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

stmarysphoenix.org SEO score

93

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

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

stmarysphoenix.org

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