Tools & Wizards About Us
brotherpreacher.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

brotherpreacher.com

Page Load Speed

2.1 sec in total

First Response

529 ms

Resources Loaded

1.3 sec

Page Rendered

265 ms

brotherpreacher.com screenshot

About Website

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

Visit brotherpreacher.com

Key Findings

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

Performance Metrics

brotherpreacher.com performance score

0

Network Requests Diagram

johnrichardsjr.com

529 ms

webfont.js

67 ms

inline-tweet-sharer.css

78 ms

mediaelementplayer.min.css

102 ms

wp-mediaelement.css

79 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Brotherpreacher.com, 6% (3 requests) were made to S.gravatar.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (529 ms) relates to the external source Johnrichardsjr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 832.8 kB (23%)

Content Size

3.6 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brotherpreacher.com main page is 3.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. 45% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 55.1 kB

  • Original 64.0 kB
  • After minification 52.0 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 12.0 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 55.1 kB or 86% of the original size.

Image Optimization

-8%

Potential reduce by 220.0 kB

  • Original 2.8 MB
  • After minification 2.6 MB

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. Brotherpreacher images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 309.2 kB

  • Original 439.7 kB
  • After minification 401.5 kB
  • After compression 130.5 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 309.2 kB or 70% of the original size.

CSS Optimization

-81%

Potential reduce by 248.6 kB

  • Original 308.1 kB
  • After minification 257.3 kB
  • After compression 59.6 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. Brotherpreacher.com needs all CSS files to be minified and compressed as it can save up to 248.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (72%)

Requests Now

47

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

johnrichardsjr.com

johnrichardsjr.com

529 ms

webfont.js

webfont.js

67 ms

inline-tweet-sharer.css

inline-tweet-sharer.css

78 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

102 ms

wp-mediaelement.css

wp-mediaelement.css

79 ms

flick.css

flick.css

103 ms

johnrichardsjr.com

johnrichardsjr.com

294 ms

styles.css

styles.css

105 ms

frontend-style.css

frontend-style.css

106 ms

frontend-style.css

frontend-style.css

112 ms

style.css

style.css

128 ms

style.css

style.css

185 ms

genericons.css

genericons.css

160 ms

jetpack.css

jetpack.css

162 ms

inline-tweet-sharer.js

inline-tweet-sharer.js

140 ms

player.min.js

player.min.js

155 ms

jquery.js

jquery.js

195 ms

jquery-migrate.min.js

jquery-migrate.min.js

182 ms

powerpress-mejs.js

powerpress-mejs.js

190 ms

scrollTo.js

scrollTo.js

188 ms

jquery.form.min.js

jquery.form.min.js

210 ms

mailchimp.js

mailchimp.js

207 ms

core.min.js

core.min.js

211 ms

datepicker.js

datepicker.js

262 ms

frontend.js

frontend.js

216 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

189 ms

scripts.js

scripts.js

187 ms

devicepx-jetpack.js

devicepx-jetpack.js

5 ms

gprofiles.js

gprofiles.js

56 ms

wpgroho.js

wpgroho.js

184 ms

comment-reply.min.js

comment-reply.min.js

187 ms

jquery.assets.js

jquery.assets.js

344 ms

jquery.custom.js

jquery.custom.js

213 ms

jquery.async.js

jquery.async.js

215 ms

e-201611.js

e-201611.js

4 ms

John-Richards-Jr.-web-header1.png

John-Richards-Jr.-web-header1.png

130 ms

march-madness-370x247.png

march-madness-370x247.png

130 ms

studying-scripture-370x247.jpg

studying-scripture-370x247.jpg

66 ms

black-lives-370x247.jpg

black-lives-370x247.jpg

65 ms

Scripture.jpg

Scripture.jpg

386 ms

season-preview-370x247.jpg

season-preview-370x247.jpg

64 ms

twisted-gun-370x247.jpg

twisted-gun-370x247.jpg

130 ms

goals-370x247.jpg

goals-370x247.jpg

129 ms

JEt-370x247.jpg

JEt-370x247.jpg

131 ms

Brunswick.jpg

Brunswick.jpg

132 ms

icomoon.ttf

icomoon.ttf

68 ms

g.gif

g.gif

53 ms

hovercard.css

hovercard.css

37 ms

services.css

services.css

62 ms

SEO Factors

brotherpreacher.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brotherpreacher.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Brotherpreacher.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

brotherpreacher.com

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