1.9 sec in total
111 ms
1.6 sec
172 ms
Visit torch.church now to see the best up-to-date Torch content for United States and also check out these interesting facts you probably never knew about torch.church
Simply different
Visit torch.churchWe analyzed Torch.church page load time and found that the first response time was 111 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
torch.church performance score
name
value
score
weighting
Value12.8 s
0/100
10%
Value32.6 s
0/100
25%
Value29.8 s
0/100
10%
Value510 ms
57/100
30%
Value0.05
99/100
15%
Value25.3 s
0/100
10%
111 ms
927 ms
17 ms
19 ms
13 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Torch.church, 83% (55 requests) were made to 3snl5824rlo8gha9v1u5pjpx.wpengine.netdna-cdn.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (927 ms) relates to the external source Fierce.church.
Page size can be reduced by 732.5 kB (25%)
3.0 MB
2.2 MB
In fact, the total size of Torch.church main page is 3.0 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. 60% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 44.6 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 44.6 kB or 79% of the original size.
Potential reduce by 87.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. Torch images are well optimized though.
Potential reduce by 386.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 386.0 kB or 69% of the original size.
Potential reduce by 214.8 kB
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. Torch.church needs all CSS files to be minified and compressed as it can save up to 214.8 kB or 84% of the original size.
Number of requests can be reduced by 47 (80%)
59
12
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Torch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
torch.church
111 ms
www.fierce.church
927 ms
style.css
17 ms
jquery.countdown.css
19 ms
events_manager.css
13 ms
juiz_last_tweet.css
14 ms
mappress.css
18 ms
page-list.css
13 ms
flexslider.css
18 ms
style.css
20 ms
podpress.css
18 ms
1pixelout_audio-player.js
104 ms
jquery.js
17 ms
jquery-migrate.min.js
19 ms
jquery.countdown.min.js
129 ms
supersubs.js
18 ms
jquery.bgiframe.min.js
19 ms
superfish.js
20 ms
screen.js
23 ms
core.min.js
20 ms
widget.min.js
20 ms
position.min.js
21 ms
mouse.min.js
23 ms
sortable.min.js
23 ms
datepicker.min.js
23 ms
menu.min.js
24 ms
autocomplete.min.js
24 ms
resizable.min.js
24 ms
draggable.min.js
24 ms
button.min.js
25 ms
dialog.min.js
25 ms
events-manager.js
25 ms
events-manager-pro.js
25 ms
common.js
27 ms
jquery.flexslider-min.js
27 ms
podpress.js
28 ms
slider.js
145 ms
formreset.min.css
24 ms
formsmain.min.css
25 ms
font-awesome.min.css
12 ms
css
28 ms
readyclass.min.css
23 ms
browsers.min.css
23 ms
soliloquy.css
155 ms
hoverIntent.min.js
51 ms
wp-embed.min.js
50 ms
jquery.json.js
50 ms
gravityforms.min.js
49 ms
soliloquy-min.js
158 ms
wp-emoji-release.min.js
70 ms
ga.js
5 ms
__utm.gif
91 ms
logo.png
11 ms
Website-Slider-worship.jpg
269 ms
holder.gif
12 ms
gk5FxslNkTTHtojXrkp-xF1YPouZEKgzpqZW9wN-3Ek.woff
132 ms
gk5FxslNkTTHtojXrkp-xONSK5BxN3NFS4EJkViHIqo.woff
137 ms
preloader.gif
130 ms
Acceptance-2.jpg
230 ms
Fun-2.jpg
9 ms
Kids-2.jpg
260 ms
Friends-Slider.jpg
228 ms
music-2.jpg
234 ms
fontawesome-webfont.woff
7 ms
jIXlqT1WKafUSwj6s9AzV6XnXbwdDC8wAz6IIzmCDUP3rGVtsTkPsbDajuO5ueQw.woff
8 ms
trench300nv-webfont.woff
126 ms
torch.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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
torch.church 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
torch.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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Torch.church 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 Torch.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.
torch.church
Open Graph data is detected on the main page of Torch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: