Tools & Wizards About Us
thefattytalks.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

thefattytalks.com

10 Beautiful Jailbroken iPhone Theme Screenshots - Hack Required | The Fatty Talks by Adam Hirsch The Fatty Talks by Adam Hirsch

Page Load Speed

16.8 sec in total

First Response

5.5 sec

Resources Loaded

9.7 sec

Page Rendered

1.6 sec

thefattytalks.com screenshot

About Website

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

Giving dorky people like me something to read about

Visit thefattytalks.com

Key Findings

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

Performance Metrics

thefattytalks.com performance score

0

Network Requests Diagram

www.thefattytalks.com

5511 ms

style.css

109 ms

sample.css

144 ms

sociable.css

202 ms

jquery.js

281 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 20% of them (20 requests) were addressed to the original Thefattytalks.com, 9% (9 requests) were made to Ajax.googleapis.com and 9% (9 requests) were made to I.polldaddy.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Thefattytalks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.4 kB (28%)

Content Size

948.3 kB

After Optimization

683.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 48.4 kB

  • Original 62.4 kB
  • After minification 59.8 kB
  • After compression 14.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. 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 48.4 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 30.9 kB

  • Original 567.2 kB
  • After minification 536.3 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. The Fatty Talks images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 161.1 kB

  • Original 289.3 kB
  • After minification 288.4 kB
  • After compression 128.2 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 161.1 kB or 56% of the original size.

CSS Optimization

-82%

Potential reduce by 24.1 kB

  • Original 29.4 kB
  • After minification 20.6 kB
  • After compression 5.3 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. Thefattytalks.com needs all CSS files to be minified and compressed as it can save up to 24.1 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

87

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.thefattytalks.com

www.thefattytalks.com

5511 ms

style.css

style.css

109 ms

sample.css

sample.css

144 ms

sociable.css

sociable.css

202 ms

jquery.js

jquery.js

281 ms

jquery-migrate.min.js

jquery-migrate.min.js

206 ms

prototype.js

prototype.js

184 ms

sociable.js

sociable.js

197 ms

vuible.js

vuible.js

204 ms

addtofavorites.js

addtofavorites.js

211 ms

scriptaculous.js

scriptaculous.js

184 ms

effects.js

effects.js

190 ms

k2.functions.js.php

k2.functions.js.php

386 ms

external-tracking.min.js

external-tracking.min.js

327 ms

59 ms

plusone.js

plusone.js

109 ms

200368.js

200368.js

105 ms

199917.js

199917.js

99 ms

188 ms

show_ads.js

show_ads.js

54 ms

3.gif

3.gif

176 ms

bc_button.js.php

bc_button.js.php

166 ms

e-201611.js

e-201611.js

55 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

153 ms

bc_button.js.php

bc_button.js.php

347 ms

3.gif

3.gif

560 ms

plusone.js

plusone.js

197 ms

builder.js

builder.js

35 ms

effects.js

effects.js

35 ms

dragdrop.js

dragdrop.js

53 ms

controls.js

controls.js

58 ms

slider.js

slider.js

60 ms

sound.js

sound.js

63 ms

print.css

print.css

149 ms

sharethis.1ac33bc7d4476110a610f925104446ff.css

sharethis.1ac33bc7d4476110a610f925104446ff.css

8 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

111 ms

analytics.js

analytics.js

111 ms

iphone-blank.jpg

iphone-blank.jpg

246 ms

bitnami-open-source.jpg

bitnami-open-source.jpg

86 ms

AdamAHirschBlog

AdamAHirschBlog

218 ms

file_2276.png

file_2276.png

2353 ms

IAmMcLovin_Thumbnail.gif

IAmMcLovin_Thumbnail.gif

244 ms

160x600_videogame.jpg

160x600_videogame.jpg

83 ms

header-thefattytalks-adamhirsch.jpg

header-thefattytalks-adamhirsch.jpg

264 ms

time.png

time.png

216 ms

comment.png

comment.png

241 ms

quote.png

quote.png

217 ms

image.png

image.png

407 ms

wordpress4-thumb.png

wordpress4-thumb.png

263 ms

image42.png

image42.png

296 ms

160x600-8.jpg

160x600-8.jpg

79 ms

IHeartNY_160by600_9dd.jpg

IHeartNY_160by600_9dd.jpg

82 ms

100100banner.gif

100100banner.gif

76 ms

2374553183_8d400c7fcf.jpg

2374553183_8d400c7fcf.jpg

256 ms

spacer.gif

spacer.gif

184 ms

pdb01-bottom-left.gif

pdb01-bottom-left.gif

186 ms

pdb01-bottom-right.gif

pdb01-bottom-right.gif

190 ms

pdb01-top-left.gif

pdb01-top-left.gif

174 ms

pdb01-top-right.gif

pdb01-top-right.gif

185 ms

pdq01-bottom-left.gif

pdq01-bottom-left.gif

183 ms

pdq01-bottom-right.gif

pdq01-bottom-right.gif

188 ms

pdq01-top-left.gif

pdq01-top-left.gif

197 ms

pdq01-top-right.gif

pdq01-top-right.gif

195 ms

pd01-bargif.gif

pd01-bargif.gif

197 ms

bitnami-open-source.jpg

bitnami-open-source.jpg

144 ms

collect

collect

84 ms

bitnami-open-source.jpg

bitnami-open-source.jpg

72 ms

IAmMcLovin_Thumbnail.gif

IAmMcLovin_Thumbnail.gif

777 ms

zrt_lookup.html

zrt_lookup.html

306 ms

show_ads_impl.js

show_ads_impl.js

54 ms

ads

ads

532 ms

osd.js

osd.js

434 ms

3.gif

3.gif

475 ms

minibadge1.gif

minibadge1.gif

414 ms

count.js

count.js

450 ms

ga.js

ga.js

40 ms

__utm.gif

__utm.gif

310 ms

g.gif

g.gif

293 ms

getSegment.php

getSegment.php

188 ms

minibadge1.gif

minibadge1.gif

182 ms

3.gif

3.gif

640 ms

count-data.js

count-data.js

155 ms

3357293890858210684

3357293890858210684

156 ms

abg.js

abg.js

156 ms

m_js_controller.js

m_js_controller.js

182 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

341 ms

t.dhj

t.dhj

55 ms

t.dhj

t.dhj

194 ms

s

s

199 ms

x_button_blue2.png

x_button_blue2.png

194 ms

cm

cm

226 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

27 ms

s-3271.xgi

s-3271.xgi

28 ms

hbpix

hbpix

132 ms

30 ms

32 ms

pixel

pixel

33 ms

xrefid.xgi

xrefid.xgi

17 ms

2981

2981

49 ms

SEO Factors

thefattytalks.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 Thefattytalks.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 Thefattytalks.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

thefattytalks.com

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