Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

pilgrimplace.org

Senior Community in Southern California | Pilgrim Place

Page Load Speed

3.5 sec in total

First Response

1.1 sec

Resources Loaded

2.3 sec

Page Rendered

73 ms

pilgrimplace.org screenshot

About Website

Visit pilgrimplace.org now to see the best up-to-date Pilgrim Place content and also check out these interesting facts you probably never knew about pilgrimplace.org

Senior Community in Southern California - Pilgrim Place is an active and inclusive senior community of persons dedicated to peace, social justice and sustainability.

Visit pilgrimplace.org

Key Findings

We analyzed Pilgrimplace.org page load time and found that the first response time was 1.1 sec and then it took 2.4 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

pilgrimplace.org performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,970 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

www.pilgrimplace.org

1147 ms

minified.js

43 ms

focus-within-polyfill.js

40 ms

polyfill.min.js

35 ms

thunderbolt-commons.09398ec1.bundle.min.js

163 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pilgrimplace.org, 37% (15 requests) were made to Static.parastorage.com and 32% (13 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Pilgrimplace.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 900.8 kB (67%)

Content Size

1.4 MB

After Optimization

452.7 kB

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

HTML Optimization

-80%

Potential reduce by 673.5 kB

  • Original 840.9 kB
  • After minification 839.3 kB
  • After compression 167.4 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 673.5 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 441 B

  • Original 26.7 kB
  • After minification 26.3 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. Pilgrim Place images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 226.8 kB

  • Original 485.8 kB
  • After minification 485.8 kB
  • After compression 259.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 226.8 kB or 47% of the original size.

Requests Breakdown

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

Requests Now

24

After Optimization

13

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

pilgrimplace.org accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

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

Best Practices

pilgrimplace.org best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pilgrimplace.org SEO score

98

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 Pilgrimplace.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 Pilgrimplace.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 Pilgrim Place. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: