3 sec in total
211 ms
2.1 sec
615 ms
Welcome to thetree.church homepage info - get ready to check The Tree best content right away, or after learning these important things about thetree.church
Discover the life-changing presence of God at The Tree Church in Lancaster Ohio. Join us in person or on YouTube. Empowering the next generation. Welcome home
Visit thetree.churchWe analyzed Thetree.church page load time and found that the first response time was 211 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
thetree.church performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value10.3 s
0/100
25%
Value12.7 s
3/100
10%
Value5,120 ms
0/100
30%
Value0.386
27/100
15%
Value49.6 s
0/100
10%
211 ms
433 ms
102 ms
89 ms
103 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Thetree.church, 21% (9 requests) were made to Assets2.snappages.site and 21% (9 requests) were made to Dashboard.static.subsplash.com. The less responsive or slowest element that took the longest time to load (588 ms) relates to the external source Subsplash.com.
Page size can be reduced by 47.1 kB (2%)
2.6 MB
2.5 MB
In fact, the total size of Thetree.church main page is 2.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 25.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 25.0 kB or 70% of the original size.
Potential reduce by 21.8 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. The Tree images are well optimized though.
Potential reduce by 124 B
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.
Potential reduce by 126 B
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Thetree.church has all CSS files already compressed.
Number of requests can be reduced by 14 (52%)
27
13
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of The Tree. 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 from 4 to 1 for CSS and as a result speed up the page load time.
thetree.church
211 ms
thetree.church
433 ms
jquery.min.js
102 ms
website.min.css
89 ms
website.min.js
103 ms
style1707137404.css
100 ms
fa-brands-400.ttf
106 ms
fa-brands-400.woff2
103 ms
fa-regular-400.ttf
103 ms
fa-regular-400.woff2
101 ms
fa-solid-900.ttf
112 ms
fa-solid-900.woff2
114 ms
all.min.css
106 ms
js
173 ms
js
383 ms
gtm.js
248 ms
10366694_3300x1500_500.png
52 ms
*
588 ms
screenshot.jpg
361 ms
14196209_1366x319_500.png
207 ms
10415233_1000x1000_500.png
276 ms
14197647_9504x6336_500.jpeg
224 ms
14197209_2048x1152_500.jpg
225 ms
10366281_2785x488_500.png
224 ms
screenshot.jpeg
328 ms
js
153 ms
web-client-b0eeeca725bb105049affa9ccb48d6b5.css
332 ms
blur.jpg
61 ms
image.jpg
68 ms
vendor-4394e8c34fc856e2fb031809f1152cb1.js
163 ms
chunk.695.5935b011001beb44e467.js
218 ms
chunk.143.c15dc7fe1e45d90aa07d.js
217 ms
web-client-ecc9097d08783902109d9f17964480c2.js
394 ms
analytics.js
28 ms
67 ms
image.jpg
25 ms
ProximaNova-Sbold-webfont-bba11955959ea56cb0c1ae3d3b9b9b2a.woff
260 ms
ProximaNova-Bold-webfont-0988922e8ed380689ca54855833342c9.woff
280 ms
ProximaNova-ExtraBold-webfont-b5afb0b6e2896cbe7ba8b2658d44da58.woff
272 ms
ProximaNova-Reg-webfont-5d0e746af028be8766181f227b3e87d1.woff
284 ms
ProximaNova-Light-webfont-01593b54d9e1069e75813fbd5b81d2dd.woff
299 ms
proximanova-thin-webfont-91a681efaf81cd7941866a196ad9b2b9.woff
372 ms
thetree.church accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
thetree.church best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
thetree.church 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thetree.church can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Thetree.church 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.
thetree.church
Open Graph description is not detected on the main page of The Tree. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: