Tools & Wizards About Us
fail-blog.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fail-blog.org

FAIL Blog - Funny FAIL Pictures and Videos - epic fail photos - Cheezburger

Page Load Speed

3.7 sec in total

First Response

168 ms

Resources Loaded

2.6 sec

Page Rendered

1 sec

fail-blog.org screenshot

About Website

Click here to check amazing FAIL Blog content. Otherwise, check out these important facts you probably never knew about fail-blog.org

Funny FAIL Pictures and Videos

Visit fail-blog.org

Key Findings

We analyzed Fail-blog.org page load time and found that the first response time was 168 ms and then it took 3.6 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

fail-blog.org performance score

0

Network Requests Diagram

fail-blog.org

168 ms

failblog.org

10 ms

failblog.cheezburger.com

23 ms

jstag

26 ms

load.js

71 ms

Our browser made a total of 149 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fail-blog.org, 25% (37 requests) were made to S.chzbgr.com and 13% (20 requests) were made to I.chzbgr.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source S.chzbgr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.2 MB (53%)

Content Size

6.0 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fail-blog.org main page is 6.0 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 302.5 kB

  • Original 356.6 kB
  • After minification 312.2 kB
  • After compression 54.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 44.3 kB, which is 12% 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 302.5 kB or 85% of the original size.

Image Optimization

-10%

Potential reduce by 189.2 kB

  • Original 1.9 MB
  • After minification 1.7 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. FAIL Blog images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 2.4 MB

  • Original 3.4 MB
  • After minification 3.4 MB
  • After compression 993.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 2.4 MB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 305.4 kB

  • Original 367.8 kB
  • After minification 366.5 kB
  • After compression 62.4 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. Fail-blog.org needs all CSS files to be minified and compressed as it can save up to 305.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (46%)

Requests Now

128

After Optimization

69

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fail-blog.org

fail-blog.org

168 ms

failblog.org

failblog.org

10 ms

failblog.cheezburger.com

failblog.cheezburger.com

23 ms

jstag

jstag

26 ms

load.js

load.js

71 ms

bootstrap-3.3.4.min.css

bootstrap-3.3.4.min.css

91 ms

nw_chzboot.less

nw_chzboot.less

51 ms

modernizr.min.js

modernizr.min.js

51 ms

main-moist.js

main-moist.js

61 ms

loader.js

loader.js

55 ms

t

t

336 ms

impl.200-RELEASE.js

impl.200-RELEASE.js

459 ms

beacon.js

beacon.js

209 ms

425 ms

cheezburger.png

cheezburger.png

353 ms

twitter-header-white.png

twitter-header-white.png

352 ms

fb-header-white.png

fb-header-white.png

351 ms

mobile-header-white.png

mobile-header-white.png

352 ms

social-icons.png

social-icons.png

417 ms

FailBlog.png

FailBlog.png

225 ms

FailBlog.png

FailBlog.png

225 ms

Win.png

Win.png

225 ms

TheDailyWhat.png

TheDailyWhat.png

225 ms

ArtOfTrolling.png

ArtOfTrolling.png

416 ms

cb-favorite.png

cb-favorite.png

417 ms

repost-nw.png

repost-nw.png

424 ms

cb-vote-up.png

cb-vote-up.png

425 ms

cb-vote-down.png

cb-vote-down.png

426 ms

remix.png

remix.png

426 ms

cb-comments.png

cb-comments.png

1273 ms

cb-tags.png

cb-tags.png

746 ms

squarelogo_failnation.png

squarelogo_failnation.png

349 ms

nw-social-black.png

nw-social-black.png

889 ms

nw-footer-social.png

nw-footer-social.png

889 ms

nw_appstore.png

nw_appstore.png

887 ms

nw_googlestore.png

nw_googlestore.png

887 ms

428 ms

0

0

425 ms

0

0

423 ms

415 ms

423 ms

424 ms

887 ms

886 ms

887 ms

886 ms

885 ms

931 ms

1012 ms

Memebase.png

Memebase.png

345 ms

1011 ms

948 ms

948 ms

932 ms

1010 ms

robotocondensed-bold.ttf

robotocondensed-bold.ttf

1011 ms

roboto-bold.ttf

roboto-bold.ttf

1010 ms

roboto-black.ttf

roboto-black.ttf

947 ms

roboto-medium.ttf

roboto-medium.ttf

946 ms

robotocondensed-regular.ttf

robotocondensed-regular.ttf

1009 ms

roboto-regular.ttf

roboto-regular.ttf

1266 ms

gpt.js

gpt.js

244 ms

analytics.js

analytics.js

233 ms

quant.js

quant.js

248 ms

p.js

p.js

247 ms

visitor

visitor

222 ms

widgets.js

widgets.js

1082 ms

platform.js

platform.js

830 ms

bundle.js

bundle.js

553 ms

sdk.js

sdk.js

230 ms

addthis_widget.js

addthis_widget.js

228 ms

fql

fql

540 ms

Scores

Scores

687 ms

805 ms

2XLPmY89cGM

2XLPmY89cGM

675 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

797 ms

IcoMoon.woff

IcoMoon.woff

1048 ms

icomoon_new.woff

icomoon_new.woff

1048 ms

IcoMoon-Essential.ttf

IcoMoon-Essential.ttf

1066 ms

trk.gif

trk.gif

186 ms

68701A37019A4AAE829B18CF67015687.png

68701A37019A4AAE829B18CF67015687.png

195 ms

VideoPlayIcon.svg

VideoPlayIcon.svg

199 ms

moatad.js

moatad.js

148 ms

moatvideo.js

moatvideo.js

458 ms

1C75D86FE67540149A916F6A2EBF3D5D.png

1C75D86FE67540149A916F6A2EBF3D5D.png

135 ms

trk.gif

trk.gif

135 ms

VIfe6sh4fzo

VIfe6sh4fzo

672 ms

json

json

610 ms

da2070b5fc9354997cf429124f504bdc24e1da1aa0a3fd984095a20ec74b185e.png

da2070b5fc9354997cf429124f504bdc24e1da1aa0a3fd984095a20ec74b185e.png

853 ms

7c5955621ed7fefd1f50edfff37b4fc389795123d6dfa826825bd7d453afd461.png

7c5955621ed7fefd1f50edfff37b4fc389795123d6dfa826825bd7d453afd461.png

515 ms

pubads_impl_82.js

pubads_impl_82.js

547 ms

boost

boost

376 ms

300lo.json

300lo.json

406 ms

pixel;r=1657794846;a.1=p-75z9nhQwNH4Ek;fpan=1;fpa=P0-1309599487-1458212179864;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458212179864;tzo=-180;ref=;url=http%3A%2F%2Ffailblog.cheezburger.com%2F;ogl=site_name.FAIL%20Blog%2Curl.http%3A%2F%2Ffailblog%252Echeezburger%252Ecom%2Ctitle.FAIL%20Blog%2Cdescription.Funny%20FAIL%20Pictures%20and%20Videos%20%2Ctype.profile%2Cimage.https%3A%2F%2Fi%252Echzbgr%252Ecom%2Ffull%2F78831617%2Fh7A568220%2F1

pixel;r=1657794846;a.1=p-75z9nhQwNH4Ek;fpan=1;fpa=P0-1309599487-1458212179864;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458212179864;tzo=-180;ref=;url=http%3A%2F%2Ffailblog.cheezburger.com%2F;ogl=site_name.FAIL%20Blog%2Curl.http%3A%2F%2Ffailblog%252Echeezburger%252Ecom%2Ctitle.FAIL%20Blog%2Cdescription.Funny%20FAIL%20Pictures%20and%20Videos%20%2Ctype.profile%2Cimage.https%3A%2F%2Fi%252Echzbgr%252Ecom%2Ffull%2F78831617%2Fh7A568220%2F1

207 ms

701 ms

sh.07f0d9bf220d07a763adad1e.html

sh.07f0d9bf220d07a763adad1e.html

160 ms

cheezburger.com

cheezburger.com

190 ms

pixel.gif

pixel.gif

107 ms

bundle.js

bundle.js

791 ms

xd_arbiter.php

xd_arbiter.php

67 ms

xd_arbiter.php

xd_arbiter.php

407 ms

www-embed-player-vfl8xM8me.css

www-embed-player-vfl8xM8me.css

380 ms

www-embed-player.js

www-embed-player.js

399 ms

pixel.gif

pixel.gif

69 ms

collect

collect

509 ms

container.html

container.html

347 ms

3aadbb71016ecd7a194bbe2791777e9a.png

3aadbb71016ecd7a194bbe2791777e9a.png

308 ms

failblog-main-v3.css

failblog-main-v3.css

230 ms

jquery.min.js

jquery.min.js

193 ms

acj

acj

601 ms

trk.gif

trk.gif

96 ms

6f385aa4073e7414dbfad3d84e21d88ffe6b2074.jpg

6f385aa4073e7414dbfad3d84e21d88ffe6b2074.jpg

112 ms

48e549d41ec9dacbccb0bafb191d4b6b.jpg

48e549d41ec9dacbccb0bafb191d4b6b.jpg

111 ms

0daa36e23add248d35c52af7df859711c7fe9566.jpeg

0daa36e23add248d35c52af7df859711c7fe9566.jpeg

117 ms

desktop-1446672431.jpg

desktop-1446672431.jpg

111 ms

ptrack-v0.4.10.js

ptrack-v0.4.10.js

61 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

121 ms

ad_status.js

ad_status.js

126 ms

joe-nicolas-cage-1200x630-c.jpg

joe-nicolas-cage-1200x630-c.jpg

46 ms

abf8bcbd3fd63bf9e28c51a5a7b26a1c.jpg

abf8bcbd3fd63bf9e28c51a5a7b26a1c.jpg

108 ms

dff22586-d4d6-4d09-8593-579dfbcc5259.jpg

dff22586-d4d6-4d09-8593-579dfbcc5259.jpg

107 ms

199519e8b44117b71efbd259d71c2af7.jpg

199519e8b44117b71efbd259d71c2af7.jpg

50 ms

acj

acj

477 ms

acj

acj

273 ms

acj

acj

344 ms

acj

acj

452 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

100 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

103 ms

71 ms

pd

pd

144 ms

bo

bo

5 ms

bo

bo

5 ms

openx

openx

5 ms

pixel

pixel

20 ms

openx

openx

4 ms

sd

sd

85 ms

pd

pd

142 ms

bo

bo

8 ms

pixel

pixel

17 ms

bo

bo

8 ms

sd

sd

119 ms

sd

sd

139 ms

bo

bo

45 ms

sd

sd

72 ms

sd

sd

104 ms

664513af-99ce-ab48-f631-f572af288b7b

664513af-99ce-ab48-f631-f572af288b7b

34 ms

sd

sd

72 ms

sd

sd

86 ms

sd

sd

72 ms

SEO Factors

fail-blog.org 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 Fail-blog.org 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 Fail-blog.org 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

fail-blog.org

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