1.4 sec in total
132 ms
1.2 sec
82 ms
Welcome to trinity-episcopal.org homepage info - get ready to check Trinity Episcopal best content right away, or after learning these important things about trinity-episcopal.org
We are a warm & welcoming Episcopal church in the heart of Portland. Whoever you are and whatever you believe, you are welcome here!
Visit trinity-episcopal.orgWe analyzed Trinity-episcopal.org page load time and found that the first response time was 132 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
trinity-episcopal.org performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value5.0 s
27/100
25%
Value9.2 s
13/100
10%
Value5,130 ms
0/100
30%
Value0.01
100/100
15%
Value20.4 s
2/100
10%
132 ms
76 ms
77 ms
74 ms
77 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Trinity-episcopal.org, 39% (24 requests) were made to Static.parastorage.com and 35% (22 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (774 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 720.5 kB (59%)
1.2 MB
490.7 kB
In fact, the total size of Trinity-episcopal.org main page is 1.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 896.1 kB which makes up the majority of the site volume.
Potential reduce by 714.0 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 714.0 kB or 80% of the original size.
Potential reduce by 3.7 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. Trinity Episcopal images are well optimized though.
Potential reduce by 2.8 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.
Number of requests can be reduced by 15 (36%)
42
27
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trinity Episcopal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
www.trinity-episcopal.org
132 ms
originTrials.41d7301a.bundle.min.js
76 ms
minified.js
77 ms
focus-within-polyfill.js
74 ms
polyfill.min.js
77 ms
5402.chunk.min.js
72 ms
2013.chunk.min.js
73 ms
5141.chunk.min.js
238 ms
Cards.chunk.min.js
254 ms
thunderbolt-commons.2113c4aa.bundle.min.js
210 ms
main.6c492079.bundle.min.js
210 ms
lodash.min.js
209 ms
react.production.min.js
205 ms
react-dom.production.min.js
210 ms
siteTags.bundle.min.js
209 ms
wix-perf-measure.umd.min.js
228 ms
logo-trinity.png
356 ms
bundle.min.js
253 ms
logo-trinity%202.png
309 ms
819beb_12a3f0217f6746d98d393dd58e2f6652f000.jpg
309 ms
25961d_eb8c8c7091cd478aae9491077f9cc5b9~mv2.jpg
309 ms
688919_f11cd416d2ef4e47af8212a1e1467d58~mv2.jpg
305 ms
688919_86e904bcb37c44ce9acb34fc14d842c0~mv2.jpeg
267 ms
688919_32e4b9c3a1264641a22d06b8a84c89e8~mv2.jpg
428 ms
688919_5976fbdc9f26475ba1c39bac03f62559~mv2.png
537 ms
688919_318e8da78ff44b6093c87e14b23c7d28~mv2.jpg
463 ms
688919_3d0445b0679a4d04bfd9a9357cf91827~mv2.webp
325 ms
688919_03450631a82c4c0682d7c9988ba729b8~mv2.jpeg
502 ms
688919_cf4ddb2b09664125b4e1a215a76aecc0~mv2.jpeg
440 ms
688919_2e389e78e9264796bf4675ee2556aa6c~mv2.jpg
471 ms
688919_df44ab35d9e648469b12626f9d10a31a~mv2.jpg
562 ms
688919_66fa040b318d4da896abf6e6e853a26d~mv2.png
526 ms
688919_869ad59d0b064e23914e0f9a1e6f1d70~mv2.jpg
582 ms
819beb_2e168ae84b91480189f1ff7b44d7b526~mv2.jpg
657 ms
688919_fdcdb91cde1443dfa0b5048e498d3e2e~mv2.jpg
670 ms
688919_074a74b259c74a71bfcecd2835e014aa~mv2.jpg
642 ms
688919_d0f3d2cdd3b842ec826854569b75a7b2~mv2.jpg
680 ms
688919_8344ab64a1b24f0fbdb7dbeb97afac19~mv2.jpg
774 ms
688919_69ead8dbbcec46f988261536ebaaee2d~mv2.png
741 ms
03805817-4611-4dbc-8c65-0f73031c3973.woff
37 ms
80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff
37 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
37 ms
b56b944e-bbe0-4450-a241-de2125d3e682.woff
38 ms
6f8d1983-4d34-4fa4-9110-988f6c495757.woff
36 ms
dI-qzxlKVQA6TUC5RKSb3z8E0i7KZn-EPnyo3HZu7kw.woff
13 ms
cgaIrkaP9Empe8_PwXbajD8E0i7KZn-EPnyo3HZu7kw.woff
38 ms
152 ms
150 ms
158 ms
145 ms
146 ms
154 ms
189 ms
190 ms
186 ms
179 ms
173 ms
173 ms
deprecation-en.v5.html
8 ms
bolt-performance
30 ms
deprecation-style.v5.css
10 ms
right-arrow.svg
10 ms
trinity-episcopal.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
trinity-episcopal.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
trinity-episcopal.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trinity-episcopal.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 Trinity-episcopal.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.
trinity-episcopal.org
Open Graph data is detected on the main page of Trinity Episcopal. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: