Tools & Wizards About Us
standrewsamarillo.org screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

standrewsamarillo.org

St Andrews | St. Andrew's Episcopal Church | Amarillo

Page Load Speed

950 ms in total

First Response

54 ms

Resources Loaded

835 ms

Page Rendered

61 ms

standrewsamarillo.org screenshot

About Website

Visit standrewsamarillo.org now to see the best up-to-date St Andrews Amarillo content and also check out these interesting facts you probably never knew about standrewsamarillo.org

St. Andrew's Episcopal Church in Amarillo, TX is a place to worship, connect, serve, and pray in an atmosphere steeped with love, beauty, hospitality, and inclusivity. A member of the Open and Affirmi...

Visit standrewsamarillo.org

Key Findings

We analyzed Standrewsamarillo.org page load time and found that the first response time was 54 ms and then it took 896 ms 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

standrewsamarillo.org performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

3/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value220 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.043

99/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

www.standrewsamarillo.org

54 ms

minified.js

36 ms

focus-within-polyfill.js

32 ms

polyfill.min.js

30 ms

thunderbolt-commons.c1d8ed1c.bundle.min.js

18 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Standrewsamarillo.org, 30% (16 requests) were made to Static.parastorage.com and 28% (15 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (396 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (50%)

Content Size

2.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Standrewsamarillo.org main page is 2.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. 50% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 872.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 221.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 872.4 kB or 80% of the original size.

Image Optimization

-26%

Potential reduce by 227.8 kB

  • Original 876.8 kB
  • After minification 649.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. Obviously, St Andrews Amarillo needs image optimization as it can save up to 227.8 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 4.2 kB

  • Original 260.3 kB
  • After minification 260.2 kB
  • After compression 256.0 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 10 (30%)

Requests Now

33

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.standrewsamarillo.org

www.standrewsamarillo.org

54 ms

minified.js

minified.js

36 ms

focus-within-polyfill.js

focus-within-polyfill.js

32 ms

polyfill.min.js

polyfill.min.js

30 ms

thunderbolt-commons.c1d8ed1c.bundle.min.js

thunderbolt-commons.c1d8ed1c.bundle.min.js

18 ms

main.1adb5ce4.bundle.min.js

main.1adb5ce4.bundle.min.js

144 ms

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

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

17 ms

lodash.min.js

lodash.min.js

142 ms

react.production.min.js

react.production.min.js

142 ms

react-dom.production.min.js

react-dom.production.min.js

145 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

144 ms

Rectangle%203.png

Rectangle%203.png

191 ms

mqdefault.jpg

mqdefault.jpg

135 ms

bundle.min.js

bundle.min.js

82 ms

sddefault.jpg%203x

sddefault.jpg%203x

51 ms

mqdefault.jpg

mqdefault.jpg

87 ms

sddefault.jpg%203x

sddefault.jpg%203x

50 ms

mqdefault.jpg

mqdefault.jpg

87 ms

sddefault.jpg%203x

sddefault.jpg%203x

52 ms

sddefault.jpg%202x

sddefault.jpg%202x

85 ms

eebc85_a86a87e20d5c40b79eeec53272475f54~mv2.jpg

eebc85_a86a87e20d5c40b79eeec53272475f54~mv2.jpg

137 ms

eebc85_17f4103ef549439796ac19dee42c2300~mv2.png

eebc85_17f4103ef549439796ac19dee42c2300~mv2.png

241 ms

eebc85_ba921962a0aa463a8b0731b33c3804d0~mv2.png

eebc85_ba921962a0aa463a8b0731b33c3804d0~mv2.png

166 ms

eebc85_13f43b84aa6e473bb27f262d0633a1c5~mv2.png

eebc85_13f43b84aa6e473bb27f262d0633a1c5~mv2.png

136 ms

eebc85_519ad0ef549347b7819185d49e0de0c2~mv2.png

eebc85_519ad0ef549347b7819185d49e0de0c2~mv2.png

166 ms

cd4140_7dc52b195d014558b0b7c41206134548~mv2.webp

cd4140_7dc52b195d014558b0b7c41206134548~mv2.webp

301 ms

cd4140_78fc33acf7a247eb9bc8b7768f5ad479~mv2.webp

cd4140_78fc33acf7a247eb9bc8b7768f5ad479~mv2.webp

230 ms

cd4140_097629b44850446e8c7238803ab04d9d~mv2.webp

cd4140_097629b44850446e8c7238803ab04d9d~mv2.webp

244 ms

eebc85_8cbee85f2469490188ebcbdce882d4d2~mv2.png

eebc85_8cbee85f2469490188ebcbdce882d4d2~mv2.png

264 ms

9f568c_b82f34fb0bee4a99bd56005c8624abdb~mv2.jpeg

9f568c_b82f34fb0bee4a99bd56005c8624abdb~mv2.jpeg

232 ms

eebc85_9bbe60bc28924f948a0928aa655e0416~mv2.jpg

eebc85_9bbe60bc28924f948a0928aa655e0416~mv2.jpg

328 ms

eebc85_53369f25e6ac4048b44325bbdabfe3f3~mv2.png

eebc85_53369f25e6ac4048b44325bbdabfe3f3~mv2.png

390 ms

eebc85_24db0de3a8f84595b1c993e11b3567b4~mv2.png

eebc85_24db0de3a8f84595b1c993e11b3567b4~mv2.png

396 ms

SAEC%20website%20(3).png

SAEC%20website%20(3).png

395 ms

119 ms

117 ms

111 ms

113 ms

107 ms

108 ms

148 ms

147 ms

146 ms

144 ms

146 ms

144 ms

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

6 ms

LuloCleanW05-OneBold.woff

LuloCleanW05-OneBold.woff

14 ms

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff

13 ms

deprecation-en.v5.html

deprecation-en.v5.html

9 ms

bolt-performance

bolt-performance

24 ms

deprecation-style.v5.css

deprecation-style.v5.css

8 ms

right-arrow.svg

right-arrow.svg

7 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

5 ms

Accessibility Review

standrewsamarillo.org accessibility score

87

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Standrewsamarillo.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 Standrewsamarillo.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

standrewsamarillo.org

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