4.9 sec in total
102 ms
3.9 sec
867 ms
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.orgWe analyzed Stmarysphoenix.org page load time and found that the first response time was 102 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
stmarysphoenix.org performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value7.1 s
6/100
25%
Value4.4 s
74/100
10%
Value2,510 ms
4/100
30%
Value0.035
100/100
15%
Value12.4 s
14/100
10%
102 ms
69 ms
145 ms
71 ms
76 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Stmarysphoenix.org, 51% (36 requests) were made to Static.parastorage.com and 23% (16 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.3 MB (48%)
4.8 MB
2.5 MB
In fact, the total size of Stmarysphoenix.org main page is 4.8 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 109.5 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 109.5 kB or 86% of the original size.
Potential reduce by 51.0 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. St Mary S Phoenix images are well optimized though.
Potential reduce by 2.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 2.1 MB or 77% of the original size.
Potential reduce by 44.1 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. Stmarysphoenix.org needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.
Number of requests can be reduced by 39 (66%)
59
20
The browser has sent 59 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 29 to 1 for JavaScripts and as a result speed up the page load time.
stmarysphoenix.org
102 ms
www.stmarysphoenix.org
69 ms
bt
145 ms
require.min.js
71 ms
main-r.min.js
76 ms
viewer.css
74 ms
dynamicmodel
53 ms
b5a917_02f7e58acdf327e6161eb9615cf0121b_448.json.z
630 ms
b5a917_3c0acd0b4905153abed918a31e8ab23a_445.json.z
660 ms
ugc-viewer
164 ms
bt
167 ms
skins.min.js
159 ms
components.min.js
67 ms
utils.min.js
66 ms
core.min.js
156 ms
react-with-addons.min.js
154 ms
lodash.min.js
152 ms
TweenMax.min.js
364 ms
layout.min.js
365 ms
tpa.min.js
363 ms
fonts.min.js
409 ms
animations.min.js
410 ms
swfobject.min.js
409 ms
mousetrap.min.js
411 ms
tweenEngine.min.js
410 ms
DrawSVGPlugin.min.js
409 ms
react-dom.min.js
413 ms
ScrollToPlugin.min.js
410 ms
widgets.min.js
410 ms
experiment.js
411 ms
render.min.js
408 ms
wixappsCore.min.js
412 ms
wixappsClassics.min.js
412 ms
wixappsBuilder.min.js
407 ms
zepto.min.js
405 ms
color.min.js
405 ms
react-dom-server.min.js
273 ms
bt
171 ms
bt
349 ms
shdtop.png
160 ms
css
156 ms
latin.css
144 ms
e0678ef25486466ba65ef6ad47b559e1.png
80 ms
c4392d634a0148fda8b7b2b0ad98293b.png
79 ms
e9bb463a1bc4434c9d33b81b1fe937f5.png
81 ms
b5a917_6686101a1f28492e801839ab15d52273.png
427 ms
b5a917_01da521606274dbbbf19466f21bd5449.jpg
373 ms
b5a917_5f1e01c097fc4c6c860c05e3017ec26f.jpg
394 ms
b5a917_07fb93c935f74ce7a32c5a53c33e0bb9.jpg
453 ms
b5a917_738f1e604efd4f7aad4cb3737769b993.png
426 ms
b5a917_48379cf8067f4d0ab3e6868c4e8826a4.jpg
320 ms
b5a917_7996bf4f663046a58a1953bc25e78e61.gif
2532 ms
b5a917_6450891c162f486890e941d235b13cd5.png
581 ms
b5a917_969cda0b999a4518a16f54fa1081e5b5.png
642 ms
b5a917_7ee7a1b04cf84ee8bb21b6e44f669489.jpg
666 ms
bt
80 ms
bt
79 ms
bt
121 ms
shadow_photo.png
78 ms
shdbottom.png
94 ms
dc.js
119 ms
c5749443-93da-4592-b794-42f28d62ef72.woff
29 ms
mqIu6qQ6CSd95gSOU8x3P6CWcynf_cDxXwCLxiixG1c.ttf
29 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
50 ms
03805817-4611-4dbc-8c65-0f73031c3973.woff
27 ms
EUmoFDHkGlLv5gLaHQnBnqCWcynf_cDxXwCLxiixG1c.ttf
51 ms
x6RZE5IaGzhqlvflqX29zvesZW2xOQ-xsNqO47m55DA.ttf
52 ms
7Es8Lxoku-e5eOZWpxw18kDGxn_GiFe8rHkZWsKDQtz3rGVtsTkPsbDajuO5ueQw.ttf
53 ms
__utm.gif
161 ms
ugc-viewer
36 ms
b5a917_7ee7a1b04cf84ee8bb21b6e44f669489.jpg
346 ms
stmarysphoenix.org accessibility score
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
stmarysphoenix.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
stmarysphoenix.org SEO score
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
Document uses legible font sizes
EN
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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.
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: