Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

wildwoodgathering.org

WildWood Gathering | Olympia, Wa | Progressive Church

Page Load Speed

3.8 sec in total

First Response

1.8 sec

Resources Loaded

1.9 sec

Page Rendered

69 ms

About Website

Welcome to wildwoodgathering.org homepage info - get ready to check Wild Wood Gathering best content right away, or after learning these important things about wildwoodgathering.org

A new kind of church in Olympia, Washington. WildWood Gathering is an open & affirming community of faith.

Visit wildwoodgathering.org

Key Findings

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

Performance Metrics

wildwoodgathering.org performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value2,070 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

www.wildwoodgathering.org

1790 ms

originTrials.41d7301a.bundle.min.js

32 ms

minified.js

36 ms

focus-within-polyfill.js

36 ms

polyfill.min.js

116 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Wildwoodgathering.org, 50% (10 requests) were made to Static.parastorage.com and 25% (5 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Wildwoodgathering.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 310.2 kB (46%)

Content Size

680.8 kB

After Optimization

370.6 kB

In fact, the total size of Wildwoodgathering.org main page is 680.8 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 410.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 307.1 kB

  • Original 410.6 kB
  • After minification 408.9 kB
  • After compression 103.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 307.1 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 311 B

  • Original 41.4 kB
  • After minification 41.1 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. Wild Wood Gathering images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 228.8 kB
  • After minification 228.8 kB
  • After compression 226.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 11 (65%)

Requests Now

17

After Optimization

6

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wild Wood Gathering. 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.

Accessibility Review

wildwoodgathering.org accessibility score

89

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

Links do not have a discernible name

Best Practices

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

wildwoodgathering.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 Wildwoodgathering.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 Wildwoodgathering.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

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