Tools & Wizards About Us
brianjoecurry.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

brianjoecurry.com

BrianJoeCurry.com

Page Load Speed

3.4 sec in total

First Response

205 ms

Resources Loaded

2.7 sec

Page Rendered

562 ms

brianjoecurry.com screenshot

About Website

Click here to check amazing Brian Joe Curry content. Otherwise, check out these important facts you probably never knew about brianjoecurry.com

Nutrition and Agility

Visit brianjoecurry.com

Key Findings

We analyzed Brianjoecurry.com page load time and found that the first response time was 205 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

brianjoecurry.com performance score

0

Network Requests Diagram

brianjoecurry.com

205 ms

webfont.js

60 ms

wp-emoji-release.min.js

115 ms

jquery-ui.css

47 ms

nivo-slider.css

127 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 53% of them (40 requests) were addressed to the original Brianjoecurry.com, 13% (10 requests) were made to Static.xx.fbcdn.net and 8% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Brianjoecurry.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 416.0 kB (54%)

Content Size

772.2 kB

After Optimization

356.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brianjoecurry.com main page is 772.2 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. 60% of websites need less resources to load. Javascripts take 264.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 35.0 kB

  • Original 45.2 kB
  • After minification 42.9 kB
  • After compression 10.3 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 35.0 kB or 77% of the original size.

Image Optimization

-10%

Potential reduce by 26.7 kB

  • Original 258.3 kB
  • After minification 231.6 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. Brian Joe Curry images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 178.9 kB

  • Original 264.3 kB
  • After minification 247.4 kB
  • After compression 85.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 178.9 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 175.4 kB

  • Original 204.4 kB
  • After minification 153.2 kB
  • After compression 28.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. Brianjoecurry.com needs all CSS files to be minified and compressed as it can save up to 175.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (74%)

Requests Now

68

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brianjoecurry.com

brianjoecurry.com

205 ms

webfont.js

webfont.js

60 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

115 ms

jquery-ui.css

jquery-ui.css

47 ms

nivo-slider.css

nivo-slider.css

127 ms

custom-nivo-slider.css

custom-nivo-slider.css

125 ms

shortcodes.css

shortcodes.css

146 ms

layouts.css

layouts.css

135 ms

style.css

style.css

121 ms

jquery-ui.min.js

jquery-ui.min.js

51 ms

jquery.js

jquery.js

205 ms

jquery-migrate.min.js

jquery-migrate.min.js

172 ms

swfobject.js

swfobject.js

178 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

177 ms

gprofiles.js

gprofiles.js

110 ms

widget.min.js

widget.min.js

171 ms

core.min.js

core.min.js

186 ms

accordion.min.js

accordion.min.js

211 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

221 ms

jquery.colorbox.min.js

jquery.colorbox.min.js

221 ms

jquery.md5.js

jquery.md5.js

218 ms

jquery.smooth-scroll.min.js

jquery.smooth-scroll.min.js

236 ms

affilo.js

affilo.js

237 ms

globalStyles.css

globalStyles.css

259 ms

colorbox.css

colorbox.css

275 ms

style3.css

style3.css

56 ms

loveclaw.js

loveclaw.js

53 ms

awt_analytics.js

awt_analytics.js

82 ms

position.min.js

position.min.js

258 ms

swfobject.js

swfobject.js

265 ms

css

css

58 ms

glide.css

glide.css

191 ms

style.css

style.css

180 ms

styles.php

styles.php

1140 ms

style.css

style.css

47 ms

TC_CoachBanner_160x600_02.gif

TC_CoachBanner_160x600_02.gif

344 ms

163 ms

CE_728x90.gif

CE_728x90.gif

342 ms

p90x_DVDs728x90.gif

p90x_DVDs728x90.gif

278 ms

TMT_728x90.gif

TMT_728x90.gif

332 ms

noise1.png

noise1.png

103 ms

glow1.png

glow1.png

102 ms

header1.png

header1.png

276 ms

nav-transparent1.png

nav-transparent1.png

100 ms

menu-arrow.png

menu-arrow.png

103 ms

head-grad.png

head-grad.png

100 ms

tab-gradient.png

tab-gradient.png

138 ms

categories-meta.png

categories-meta.png

138 ms

timthumb.php

timthumb.php

333 ms

timthumb.php

timthumb.php

394 ms

timthumb.php

timthumb.php

379 ms

footer-copy.png

footer-copy.png

179 ms

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf

68 ms

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

69 ms

FUDHvzEKSJww3kCxuiAo2A.ttf

FUDHvzEKSJww3kCxuiAo2A.ttf

70 ms

0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf

0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf

69 ms

PIPMHY90P7jtyjpXuZ2cLKCWcynf_cDxXwCLxiixG1c.ttf

PIPMHY90P7jtyjpXuZ2cLKCWcynf_cDxXwCLxiixG1c.ttf

67 ms

lILlYDvubYemzYzN7GbLkInF5uFdDttMLvmWuJdhhgs.ttf

lILlYDvubYemzYzN7GbLkInF5uFdDttMLvmWuJdhhgs.ttf

70 ms

widgets.js

widgets.js

133 ms

overlay.png

overlay.png

108 ms

like.php

like.php

181 ms

likebox.php

likebox.php

165 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

37 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

79 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

296 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

335 ms

410ucuAGgaJ.css

410ucuAGgaJ.css

359 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

472 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

497 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

397 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

398 ms

jot

jot

105 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

240 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

90 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

89 ms

SEO Factors

brianjoecurry.com SEO score

0

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

brianjoecurry.com

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