Tools & Wizards About Us
futurechurch.com screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

futurechurch.com

Future of the Church

Page Load Speed

2.1 sec in total

First Response

192 ms

Resources Loaded

1.6 sec

Page Rendered

308 ms

futurechurch.com screenshot

About Website

Visit futurechurch.com now to see the best up-to-date Future Church content and also check out these interesting facts you probably never knew about futurechurch.com

The award winning documentary that journeys to find an Answer for the Christian Church's challenges. Over 80 pastors and church leaders were interviewed from across America. This feature length d...

Visit futurechurch.com

Key Findings

We analyzed Futurechurch.com page load time and found that the first response time was 192 ms and then it took 1.9 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.

Performance Metrics

futurechurch.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.2 s

50/100

10%

Network Requests Diagram

futurechurch.com

192 ms

www.futurechurch.com

266 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

170 ms

css_aA8pdKhox0GUNjuBSZx9PaRRt9T_fOYrZtiGsWKJKtw.css

169 ms

css_BuaAq3e7D5ICli2MqZtRmQRPRQIY3vTrmy3t41frXnY.css

179 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 63% of them (37 requests) were addressed to the original Futurechurch.com, 12% (7 requests) were made to Ssl.google-analytics.com and 10% (6 requests) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (670 ms) belongs to the original domain Futurechurch.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 731.1 kB (46%)

Content Size

1.6 MB

After Optimization

865.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Futurechurch.com main page is 1.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. 55% of websites need less resources to load. Images take 646.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 45.8 kB

  • Original 54.3 kB
  • After minification 52.4 kB
  • After compression 8.5 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 45.8 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 16.7 kB

  • Original 646.4 kB
  • After minification 629.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. Future Church images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 405.0 kB

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

CSS Optimization

-88%

Potential reduce by 263.6 kB

  • Original 300.8 kB
  • After minification 293.6 kB
  • After compression 37.2 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. Futurechurch.com needs all CSS files to be minified and compressed as it can save up to 263.6 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (43%)

Requests Now

53

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Future Church. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

futurechurch.com

futurechurch.com

192 ms

www.futurechurch.com

www.futurechurch.com

266 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

170 ms

css_aA8pdKhox0GUNjuBSZx9PaRRt9T_fOYrZtiGsWKJKtw.css

css_aA8pdKhox0GUNjuBSZx9PaRRt9T_fOYrZtiGsWKJKtw.css

169 ms

css_BuaAq3e7D5ICli2MqZtRmQRPRQIY3vTrmy3t41frXnY.css

css_BuaAq3e7D5ICli2MqZtRmQRPRQIY3vTrmy3t41frXnY.css

179 ms

css_PufZvnJTOD1rWx2r_Mdw_2Vfgtr-sXKGZ5SU-Jx_yYk.css

css_PufZvnJTOD1rWx2r_Mdw_2Vfgtr-sXKGZ5SU-Jx_yYk.css

248 ms

js_JLxuxbhhrFRy-sBnijHkR0TGGHgiukMPv94zvDWgQ3g.js

js_JLxuxbhhrFRy-sBnijHkR0TGGHgiukMPv94zvDWgQ3g.js

268 ms

js_QF66VqWslTl4k6A4mkXluNAoWfdnEFkkXIAa9yRHhhc.js

js_QF66VqWslTl4k6A4mkXluNAoWfdnEFkkXIAa9yRHhhc.js

202 ms

js_NpX2cwCeepkWZZ194B6-ViyVBHleaYLOx5R9EWBOMRU.js

js_NpX2cwCeepkWZZ194B6-ViyVBHleaYLOx5R9EWBOMRU.js

240 ms

js_bDMkxjvAb1fGnG-bSjPDcazPdN8vXdD-Kx7sLPkfdPE.js

js_bDMkxjvAb1fGnG-bSjPDcazPdN8vXdD-Kx7sLPkfdPE.js

237 ms

js__rk65t6WbAJTasXb6oYaAMYaywFXk6suA9CZaCebgNU.js

js__rk65t6WbAJTasXb6oYaAMYaywFXk6suA9CZaCebgNU.js

262 ms

jquery-ui.js

jquery-ui.js

19 ms

jquery.fittext.js

jquery.fittext.js

366 ms

analytics.js

analytics.js

35 ms

collect

collect

4 ms

collect

collect

161 ms

fotc-logo-545.png

fotc-logo-545.png

154 ms

menu-x-icon.png

menu-x-icon.png

183 ms

video-gallery-thumb.jpg

video-gallery-thumb.jpg

265 ms

video-gallery-thumb-hover.jpg

video-gallery-thumb-hover.jpg

181 ms

Travis-Hearn-thumb.jpg

Travis-Hearn-thumb.jpg

172 ms

Travis-Hearn-headshot.png

Travis-Hearn-headshot.png

181 ms

Wendy-Perez-thumb.jpg

Wendy-Perez-thumb.jpg

266 ms

Wendy-Perez-headshot.png

Wendy-Perez-headshot.png

263 ms

Larry-Osbourne-thumb.jpg

Larry-Osbourne-thumb.jpg

408 ms

Larry-Osborne-headshot.png

Larry-Osborne-headshot.png

274 ms

lines.png

lines.png

408 ms

gray-overlay.png

gray-overlay.png

408 ms

intro-video-first-frame.jpg

intro-video-first-frame.jpg

460 ms

about-fotc-static_0.jpg

about-fotc-static_0.jpg

482 ms

about-fotc-hover.jpg

about-fotc-hover.jpg

487 ms

jack-debartolo-thumb.jpg

jack-debartolo-thumb.jpg

498 ms

jack-debartolo-headshot.jpg

jack-debartolo-headshot.jpg

461 ms

paperclip.png

paperclip.png

461 ms

tommy-barnett-video-thumb_0.jpg

tommy-barnett-video-thumb_0.jpg

601 ms

tommy-barnett-headshot.png

tommy-barnett-headshot.png

541 ms

bg_tab.png

bg_tab.png

575 ms

montserrat-regular-webfont.woff

montserrat-regular-webfont.woff

569 ms

montserrat-bold-webfont.woff

montserrat-bold-webfont.woff

582 ms

pt_serif-web-regular-webfont.woff

pt_serif-web-regular-webfont.woff

574 ms

pt_serif-web-bold-webfont.woff

pt_serif-web-bold-webfont.woff

670 ms

84982790

84982790

107 ms

84625985

84625985

123 ms

84620660

84620660

108 ms

132355839

132355839

130 ms

86123389

86123389

128 ms

84507194

84507194

132 ms

player.js

player.js

171 ms

player.css

player.css

151 ms

ga.js

ga.js

61 ms

vuid.min.js

vuid.min.js

142 ms

__utm.gif

__utm.gif

85 ms

__utm.gif

__utm.gif

13 ms

__utm.gif

__utm.gif

20 ms

__utm.gif

__utm.gif

36 ms

__utm.gif

__utm.gif

37 ms

__utm.gif

__utm.gif

36 ms

proxy.html

proxy.html

81 ms

7183650_60x60.jpg

7183650_60x60.jpg

120 ms

Accessibility Review

futurechurch.com accessibility score

75

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

futurechurch.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

futurechurch.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

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 Futurechurch.com 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 Futurechurch.com 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

futurechurch.com

Open Graph description is not detected on the main page of Future Church. 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: