Tools & Wizards About Us
fameseattle.org screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

fameseattle.org

FAME Seattle | First African Methodist Episcopal Church-Seattle, WA

Page Load Speed

738 ms in total

First Response

68 ms

Resources Loaded

608 ms

Page Rendered

62 ms

fameseattle.org screenshot

About Website

Welcome to fameseattle.org homepage info - get ready to check FAME Seattle best content right away, or after learning these important things about fameseattle.org

FAME Seattle is a Christ-centered, welcoming community to our neighbors, here to build up the total person both spiritually and physically.

Visit fameseattle.org

Key Findings

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

Performance Metrics

fameseattle.org performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

www.fameseattle.org

68 ms

originTrials.41d7301a.bundle.min.js

47 ms

minified.js

50 ms

focus-within-polyfill.js

48 ms

polyfill.min.js

43 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 397.8 kB (45%)

Content Size

879.5 kB

After Optimization

481.7 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-76%

Potential reduce by 395.0 kB

  • Original 520.8 kB
  • After minification 519.4 kB
  • After compression 125.9 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 395.0 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 135.2 kB
  • After minification 135.2 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. FAME Seattle images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 223.4 kB
  • After minification 223.4 kB
  • After compression 220.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 11 (35%)

Requests Now

31

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FAME Seattle. 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.fameseattle.org

www.fameseattle.org

68 ms

originTrials.41d7301a.bundle.min.js

originTrials.41d7301a.bundle.min.js

47 ms

minified.js

minified.js

50 ms

focus-within-polyfill.js

focus-within-polyfill.js

48 ms

polyfill.min.js

polyfill.min.js

43 ms

thunderbolt-commons.24e46262.bundle.min.js

thunderbolt-commons.24e46262.bundle.min.js

44 ms

main.8752ee81.bundle.min.js

main.8752ee81.bundle.min.js

153 ms

lodash.min.js

lodash.min.js

132 ms

react.production.min.js

react.production.min.js

132 ms

react-dom.production.min.js

react-dom.production.min.js

136 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

135 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

136 ms

FAME%20Logo%20rev%201.jpg

FAME%20Logo%20rev%201.jpg

195 ms

bundle.min.js

bundle.min.js

60 ms

ec7d3b_447f262ff34145e4a6d30c3899d288db~mv2.jpg

ec7d3b_447f262ff34145e4a6d30c3899d288db~mv2.jpg

303 ms

ec7d3b_4b8b854338384a3a8bbac7d2c661c7c9~mv2.jpg

ec7d3b_4b8b854338384a3a8bbac7d2c661c7c9~mv2.jpg

247 ms

151 ms

155 ms

152 ms

152 ms

158 ms

151 ms

181 ms

191 ms

190 ms

187 ms

184 ms

194 ms

8fb1090e-b4d0-4685-ac8f-3d0c29d60130.woff

8fb1090e-b4d0-4685-ac8f-3d0c29d60130.woff

21 ms

c5749443-93da-4592-b794-42f28d62ef72.woff

c5749443-93da-4592-b794-42f28d62ef72.woff

19 ms

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

192dac76-a6d9-413d-bb74-22308f2e0cc5.woff

13 ms

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff

20 ms

deprecation-en.v5.html

deprecation-en.v5.html

12 ms

bolt-performance

bolt-performance

15 ms

deprecation-style.v5.css

deprecation-style.v5.css

6 ms

right-arrow.svg

right-arrow.svg

7 ms

Accessibility Review

fameseattle.org accessibility score

88

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

High

<frame> or <iframe> elements do not have a title

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.

Best Practices

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

fameseattle.org SEO score

99

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

High

Tap targets are not sized appropriately

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

fameseattle.org

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