Tools & Wizards About Us
brazenchurch.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

brazenchurch.com

Brazen Church: A Community of Free-Thinking Christians

Page Load Speed

1.6 sec in total

First Response

468 ms

Resources Loaded

786 ms

Page Rendered

351 ms

brazenchurch.com screenshot

About Website

Click here to check amazing Brazen Church content for United States. Otherwise, check out these important facts you probably never knew about brazenchurch.com

“I came that they may have life, and have it abundantly.” Jesus came to bring GOOD NEWS, and somewhere behind the dogma, hypocrisy, and dysfunctional traditions of modern Christianity, there is Truth ...

Visit brazenchurch.com

Key Findings

We analyzed Brazenchurch.com page load time and found that the first response time was 468 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

brazenchurch.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value220 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

brazenchurch.com

468 ms

wp-emoji-release.min.js

23 ms

A.main.css,qver=2.4.4.pagespeed.cf.HGZjIDBG7C.css

62 ms

A.style.css,qver=2.4.4.pagespeed.cf.YNGMXbKAJI.css

44 ms

A.style.css,qver=1.0.2.pagespeed.cf.rSgt6vmphi.css

44 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 68% of them (15 requests) were addressed to the original Brazenchurch.com, 9% (2 requests) were made to Google-analytics.com and 9% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (468 ms) belongs to the original domain Brazenchurch.com.

Page Optimization Overview & Recommendations

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

Content Size

603.3 kB

After Optimization

328.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brazenchurch.com main page is 603.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 230.2 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 15.1 kB

  • Original 22.3 kB
  • After minification 22.1 kB
  • After compression 7.2 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 15.1 kB or 68% of the original size.

Image Optimization

-0%

Potential reduce by 1 B

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

JavaScript Optimization

-63%

Potential reduce by 144.8 kB

  • Original 230.2 kB
  • After minification 228.1 kB
  • After compression 85.4 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 144.8 kB or 63% of the original size.

CSS Optimization

-70%

Potential reduce by 115.4 kB

  • Original 164.3 kB
  • After minification 163.8 kB
  • After compression 48.9 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. Brazenchurch.com needs all CSS files to be minified and compressed as it can save up to 115.4 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (56%)

Requests Now

18

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brazen 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 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

brazenchurch.com

brazenchurch.com

468 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

23 ms

A.main.css,qver=2.4.4.pagespeed.cf.HGZjIDBG7C.css

A.main.css,qver=2.4.4.pagespeed.cf.HGZjIDBG7C.css

62 ms

A.style.css,qver=2.4.4.pagespeed.cf.YNGMXbKAJI.css

A.style.css,qver=2.4.4.pagespeed.cf.YNGMXbKAJI.css

44 ms

A.style.css,qver=1.0.2.pagespeed.cf.rSgt6vmphi.css

A.style.css,qver=1.0.2.pagespeed.cf.rSgt6vmphi.css

44 ms

dashicons.min.css,qver=4.4.2.pagespeed.ce.X2cvQ4DGDW.css

dashicons.min.css,qver=4.4.2.pagespeed.ce.X2cvQ4DGDW.css

73 ms

css

css

24 ms

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

76 ms

wp-includes,_js,_jquery,_jquery-migrate.min.js,qver==1.2.1+wp-content,_plugins,_contact-form-7,_includes,_js,_jquery.form.min.js,qver==3.51.0-2014.06.20+wp-content,_plugins,_anspress-question-answer,_assets,_min,_ap-functions.min.js,qver==4.4.2.pagespeed.jc.JLvmfMWQtw.js

wp-includes,_js,_jquery,_jquery-migrate.min.js,qver==1.2.1+wp-content,_plugins,_contact-form-7,_includes,_js,_jquery.form.min.js,qver==3.51.0-2014.06.20+wp-content,_plugins,_anspress-question-answer,_assets,_min,_ap-functions.min.js,qver==4.4.2.pagespeed.jc.JLvmfMWQtw.js

70 ms

plugins,_anspress-question-answer,_assets,_min,_anspress_site.min.js,qver==2.4.4+plugins,_anspress-question-answer,_theme,_default,_js,_jquery.peity.min.js,qver==2.4.4+plugins,_anspress-question-answer,_theme,_default,_js,_initial.min.js,qver==2.4.4+plugins,_anspress-question-answer,_theme,_default,_js,_jquery.scrollbar.min.js,qver==2.4.4+plugins,_anspress-question-answer,_theme,_default,_min,_ap.min.js,qver==2.4.4+themes,_altitude-pro,_js,_global.js,qver==1.0.0+themes,_altitude-pro,_js,_home.js,qver==1.0.0.pagespeed.jc.l4E9W_xHwE.js

plugins,_anspress-question-answer,_assets,_min,_anspress_site.min.js,qver==2.4.4+plugins,_anspress-question-answer,_theme,_default,_js,_jquery.peity.min.js,qver==2.4.4+plugins,_anspress-question-answer,_theme,_default,_js,_initial.min.js,qver==2.4.4+plugins,_anspress-question-answer,_theme,_default,_js,_jquery.scrollbar.min.js,qver==2.4.4+plugins,_anspress-question-answer,_theme,_default,_min,_ap.min.js,qver==2.4.4+themes,_altitude-pro,_js,_global.js,qver==1.0.0+themes,_altitude-pro,_js,_home.js,qver==1.0.0.pagespeed.jc.l4E9W_xHwE.js

75 ms

load.sumome.com

load.sumome.com

278 ms

wp-content,_plugins,_contact-form-7,_includes,_js,_scripts.js,qver==4.3.1+wp-content,_themes,_altitude-pro,_js,_jquery.scrollTo.min.js,qver==1.4.5-beta+wp-content,_themes,_altitude-pro,_js,_jquery.localScroll.min.js,qver==1.2.8b+wp-includes,_js,_wp-embed.min.js,qver==4.4.2.pagespeed.jc.kyLpL6ftSj.js

wp-content,_plugins,_contact-form-7,_includes,_js,_scripts.js,qver==4.3.1+wp-content,_themes,_altitude-pro,_js,_jquery.scrollTo.min.js,qver==1.4.5-beta+wp-content,_themes,_altitude-pro,_js,_jquery.localScroll.min.js,qver==1.2.8b+wp-includes,_js,_wp-embed.min.js,qver==4.4.2.pagespeed.jc.kyLpL6ftSj.js

74 ms

ga.js

ga.js

106 ms

xalt-logo.png.pagespeed.ic.bGHR4wkDCT.png

xalt-logo.png.pagespeed.ic.bGHR4wkDCT.png

39 ms

xaltitude-background.jpg.pagespeed.ic.t8MmeJ72cQ.jpg

xaltitude-background.jpg.pagespeed.ic.t8MmeJ72cQ.jpg

83 ms

xfree-thinkers-guide.jpg.pagespeed.ic.gpfULKlgLE.jpg

xfree-thinkers-guide.jpg.pagespeed.ic.gpfULKlgLE.jpg

57 ms

xask-questions-all-day.jpg.pagespeed.ic.O217NZcUdc.jpg

xask-questions-all-day.jpg.pagespeed.ic.O217NZcUdc.jpg

57 ms

xask-questions.jpg.pagespeed.ic.ZxYwJQCI5z.jpg

xask-questions.jpg.pagespeed.ic.ZxYwJQCI5z.jpg

40 ms

I9kEeiTYrUZc3iQHHEx8QobN6UDyHWBl620a-IRfuBk.woff

I9kEeiTYrUZc3iQHHEx8QobN6UDyHWBl620a-IRfuBk.woff

34 ms

2UQ4ICJih3YLJ7TCrdw9b4bN6UDyHWBl620a-IRfuBk.woff

2UQ4ICJih3YLJ7TCrdw9b4bN6UDyHWBl620a-IRfuBk.woff

35 ms

__utm.gif

__utm.gif

25 ms

collect

collect

59 ms

Accessibility Review

brazenchurch.com accessibility score

81

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

brazenchurch.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

brazenchurch.com SEO score

79

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 Brazenchurch.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 Brazenchurch.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

brazenchurch.com

Open Graph data is detected on the main page of Brazen Church. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: