1.5 sec in total
120 ms
1.3 sec
70 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 120 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
trinity-episcopal.org performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value7.5 s
4/100
25%
Value6.1 s
44/100
10%
Value3,050 ms
2/100
30%
Value0.063
97/100
15%
Value19.8 s
2/100
10%
120 ms
59 ms
56 ms
58 ms
53 ms
Our browser made a total of 64 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, 41% (26 requests) were made to Static.parastorage.com and 34% (22 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (824 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 849.0 kB (61%)
1.4 MB
546.0 kB
In fact, the total size of Trinity-episcopal.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. 55% of websites need less resources to load. HTML takes 1.0 MB which makes up the majority of the site volume.
Potential reduce by 843.1 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 843.1 kB or 80% of the original size.
Potential reduce by 2.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. Trinity Episcopal images are well optimized though.
Potential reduce by 3.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.
Number of requests can be reduced by 14 (26%)
53
39
The browser has sent 53 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 15 to 1 for JavaScripts and as a result speed up the page load time.
www.trinity-episcopal.org
120 ms
minified.js
59 ms
focus-within-polyfill.js
56 ms
polyfill.min.js
58 ms
7444.chunk.min.js
53 ms
4261.chunk.min.js
54 ms
576.chunk.min.js
54 ms
Cards.chunk.min.js
229 ms
thunderbolt-commons.7700cd07.bundle.min.js
197 ms
main.16c08821.bundle.min.js
198 ms
main.renderer.1d21f023.bundle.min.js
193 ms
lodash.min.js
196 ms
react.production.min.js
194 ms
react-dom.production.min.js
199 ms
siteTags.bundle.min.js
198 ms
logo-trinity.png
316 ms
bundle.min.js
269 ms
logo-trinity%202.png
328 ms
819beb_12a3f0217f6746d98d393dd58e2f6652f000.jpg
315 ms
25961d_eb8c8c7091cd478aae9491077f9cc5b9~mv2.jpg
383 ms
688919_a25e47f7534d4a3aabee369c9b7ce75b~mv2.jpg
327 ms
688919_7df67f3ef2ad4c7dab79b7e0983f4643~mv2.png
395 ms
688919_76af5051b4c947cda24d6932ac221e96~mv2.jpg
344 ms
688919_640fb778f35447ea824479bca2babdee~mv2.jpg
548 ms
688919_52a71b98e9ec4d8dbafa45169a214152~mv2.jpg
468 ms
688919_5c6d11b8fee441af9d4cfa6e685344fc~mv2.jpg
466 ms
688919_b333b539428840d5a13afecf1aabe586~mv2.jpg
481 ms
688919_2e389e78e9264796bf4675ee2556aa6c~mv2.jpg
514 ms
819beb_e1b826452a554016bcc139b4c849eec4~mv2.jpg
553 ms
819beb_aa413f9002704886bc0c652b336ade44~mv2.jpg
630 ms
688919_03450631a82c4c0682d7c9988ba729b8~mv2.jpeg
680 ms
688919_3ef814e456c34d51b0b3c20d88a2fc37~mv2.jpeg
621 ms
688919_b9f015cb48ce4489b90e795bfc5be40e~mv2.jpg
669 ms
688919_c48bc54b2acf4cb69d1e054a0244277f~mv2.jpg
713 ms
688919_c0fad52e040643af96287dde4cd1326e~mv2.jpg
705 ms
688919_d0a48993209b4ed789e16ef2964ef5e1~mv2.jpg
796 ms
688919_cf4ddb2b09664125b4e1a215a76aecc0~mv2.jpeg
745 ms
688919_fdcdb91cde1443dfa0b5048e498d3e2e~mv2.jpg
824 ms
03805817-4611-4dbc-8c65-0f73031c3973.woff
18 ms
80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff
38 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
38 ms
b56b944e-bbe0-4450-a241-de2125d3e682.woff
71 ms
6f8d1983-4d34-4fa4-9110-988f6c495757.woff
18 ms
dI-qzxlKVQA6TUC5RKSb3z8E0i7KZn-EPnyo3HZu7kw.woff
17 ms
cgaIrkaP9Empe8_PwXbajD8E0i7KZn-EPnyo3HZu7kw.woff
71 ms
115 ms
119 ms
114 ms
111 ms
112 ms
110 ms
148 ms
150 ms
144 ms
147 ms
146 ms
145 ms
deprecation-en.v5.html
8 ms
bolt-performance
39 ms
deprecation-style.v5.css
10 ms
right-arrow.svg
33 ms
WixMadeforDisplay_W_Bd.woff
4 ms
WixMadeforText_W_Bd.woff
6 ms
WixMadeforText_W_Rg.woff
5 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
Page has valid source maps
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: