Tools & Wizards About Us
blog.livestrong.org screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

blog.livestrong.org

Livestrong Voices

Page Load Speed

3.1 sec in total

First Response

80 ms

Resources Loaded

2.8 sec

Page Rendered

198 ms

blog.livestrong.org screenshot

About Website

Click here to check amazing Blog Livestrong content for United States. Otherwise, check out these important facts you probably never knew about blog.livestrong.org

Gain strength and get inspired by the voices of survivors as they share their cancer stories.

Visit blog.livestrong.org

Key Findings

We analyzed Blog.livestrong.org page load time and found that the first response time was 80 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

blog.livestrong.org performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value380 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

blog.livestrong.org

80 ms

font-awesome.min.css

38 ms

bootstrap.min.css

43 ms

grid.css

33 ms

base.css

80 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 17% of them (19 requests) were addressed to the original Blog.livestrong.org, 23% (26 requests) were made to Static.xx.fbcdn.net and 11% (12 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (921 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

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

Content Size

915.8 kB

After Optimization

496.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.livestrong.org main page is 915.8 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. 65% of websites need less resources to load. Images take 336.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 44.0 kB

  • Original 58.8 kB
  • After minification 51.3 kB
  • After compression 14.8 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 7.5 kB, which is 13% 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 44.0 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 10.3 kB

  • Original 336.7 kB
  • After minification 326.4 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. Blog Livestrong images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 159.6 kB

  • Original 276.7 kB
  • After minification 257.2 kB
  • After compression 117.1 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 159.6 kB or 58% of the original size.

CSS Optimization

-85%

Potential reduce by 205.8 kB

  • Original 243.6 kB
  • After minification 222.4 kB
  • After compression 37.8 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. Blog.livestrong.org needs all CSS files to be minified and compressed as it can save up to 205.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (58%)

Requests Now

108

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.livestrong.org

blog.livestrong.org

80 ms

font-awesome.min.css

font-awesome.min.css

38 ms

bootstrap.min.css

bootstrap.min.css

43 ms

grid.css

grid.css

33 ms

base.css

base.css

80 ms

style.css

style.css

87 ms

modernizr-1.7.min.js

modernizr-1.7.min.js

78 ms

jquery-1.5.1.min.js

jquery-1.5.1.min.js

102 ms

jquery-ui.min.js

jquery-ui.min.js

75 ms

videotracking.js

videotracking.js

470 ms

player_api

player_api

73 ms

sidebar-slideshow.css

sidebar-slideshow.css

98 ms

jquery.cycle.all.js

jquery.cycle.all.js

98 ms

widgets.js

widgets.js

113 ms

all.js

all.js

439 ms

plugins.js

plugins.js

113 ms

script.js

script.js

114 ms

iframe_api

iframe_api

37 ms

www-widgetapi.js

www-widgetapi.js

35 ms

b63723789d955d0a9af85866f43cc288.png

b63723789d955d0a9af85866f43cc288.png

40 ms

author_icon.gif

author_icon.gif

31 ms

gtm.js

gtm.js

38 ms

author_icon.gif

author_icon.gif

35 ms

recent_posts_drop_down_arrow.gif

recent_posts_drop_down_arrow.gif

46 ms

sidebar_left_arrow.gif

sidebar_left_arrow.gif

44 ms

dfbec84d3b668b5b0d0bf20ccece66f0.png

dfbec84d3b668b5b0d0bf20ccece66f0.png

53 ms

36f3dd9ea240dddf0af3fce64de64e6e.png

36f3dd9ea240dddf0af3fce64de64e6e.png

54 ms

20e237eb79bbb41e9678ce4d1fbc9feb.png

20e237eb79bbb41e9678ce4d1fbc9feb.png

54 ms

2491cc33fab900b15c177bded64c8816.png

2491cc33fab900b15c177bded64c8816.png

53 ms

b80b95ae502d684bd4c258f997b2287f.png

b80b95ae502d684bd4c258f997b2287f.png

52 ms

analytics.js

analytics.js

50 ms

conversion_async.js

conversion_async.js

49 ms

plusone.js

plusone.js

138 ms

ga.js

ga.js

31 ms

85 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

180 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

227 ms

190 ms

like.php

like.php

309 ms

xd_arbiter.php

xd_arbiter.php

231 ms

xd_arbiter.php

xd_arbiter.php

439 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

31 ms

105 ms

ec.js

ec.js

81 ms

__utm.gif

__utm.gif

59 ms

legal-208x145.jpg

legal-208x145.jpg

49 ms

Jerry-and-Amy-Pic-e1456411274844-208x145.jpg

Jerry-and-Amy-Pic-e1456411274844-208x145.jpg

67 ms

FullSizeRender29-208x145.jpg

FullSizeRender29-208x145.jpg

72 ms

gabe-208x145.png

gabe-208x145.png

91 ms

collect

collect

13 ms

collect

collect

78 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

30 ms

71 ms

like_box.php

like_box.php

259 ms

syndication

syndication

112 ms

348225171615793153

348225171615793153

193 ms

ga-audiences

ga-audiences

33 ms

tweet_button.6a78875565a912489e9aef879c881358.en.html

tweet_button.6a78875565a912489e9aef879c881358.en.html

46 ms

rU2ubZ6l1Q5.js

rU2ubZ6l1Q5.js

488 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

554 ms

FbUd6dZS1Af.css

FbUd6dZS1Af.css

586 ms

dGJLq38YL-C.css

dGJLq38YL-C.css

651 ms

Msuaq9yC6iC.css

Msuaq9yC6iC.css

720 ms

jsSBgYmM8Bv.css

jsSBgYmM8Bv.css

664 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

784 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

799 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

661 ms

TTCre3391I0.js

TTCre3391I0.js

715 ms

C-h3nYPqETO.js

C-h3nYPqETO.js

732 ms

rFmE1g6Dkoz.js

rFmE1g6Dkoz.js

921 ms

7cm7D75Y0Sf.js

7cm7D75Y0Sf.js

847 ms

oRoBXlHCpEy.js

oRoBXlHCpEy.js

814 ms

336JejShbZp.js

336JejShbZp.js

814 ms

sj-JwAJi4AH.js

sj-JwAJi4AH.js

849 ms

DKRU1bYTkTw.js

DKRU1bYTkTw.js

849 ms

ZNPAadQNc33.js

ZNPAadQNc33.js

851 ms

W0OV23mIOyO.js

W0OV23mIOyO.js

853 ms

36TdwhIHusi.js

36TdwhIHusi.js

915 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

28 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

74 ms

MjRINlxF_normal.jpeg

MjRINlxF_normal.jpeg

122 ms

cDJFk8qJ_normal.jpg

cDJFk8qJ_normal.jpg

185 ms

p6PL2KFg_normal.jpg

p6PL2KFg_normal.jpg

211 ms

jrFwnfv9_normal.jpeg

jrFwnfv9_normal.jpeg

223 ms

dnywUI04_normal.png

dnywUI04_normal.png

235 ms

7830ca91dc1c7e34a27100568e628a93_normal.png

7830ca91dc1c7e34a27100568e628a93_normal.png

239 ms

7_ySVxG4_normal.png

7_ySVxG4_normal.png

241 ms

CcZpKtBW0AAeTeu.jpg:small

CcZpKtBW0AAeTeu.jpg:small

243 ms

CcKgjvIW8AEYoia.jpg:small

CcKgjvIW8AEYoia.jpg:small

243 ms

CcLbIfJWAAA76CM.jpg:small

CcLbIfJWAAA76CM.jpg:small

249 ms

CcKbTFiUMAAZuYV.jpg:small

CcKbTFiUMAAZuYV.jpg:small

287 ms

CcENuWRXIAEinNG.jpg:small

CcENuWRXIAEinNG.jpg:small

292 ms

jot.html

jot.html

29 ms

10376997_10152524969009916_6062832165761986268_n.jpg

10376997_10152524969009916_6062832165761986268_n.jpg

361 ms

31447_10151515220339916_1922110153_n.jpg

31447_10151515220339916_1922110153_n.jpg

419 ms

11988621_997110910351537_3932787136469381969_n.jpg

11988621_997110910351537_3932787136469381969_n.jpg

488 ms

11817256_872888359464451_1511300504755480856_n.jpg

11817256_872888359464451_1511300504755480856_n.jpg

553 ms

12311250_451024145083072_7511874144321005016_n.jpg

12311250_451024145083072_7511874144321005016_n.jpg

557 ms

12643000_1288184727864299_2006386001249557168_n.jpg

12643000_1288184727864299_2006386001249557168_n.jpg

585 ms

1936619_10208044629939091_128058360460136188_n.jpg

1936619_10208044629939091_128058360460136188_n.jpg

555 ms

12189152_10153692613554717_7570209433697806267_n.jpg

12189152_10153692613554717_7570209433697806267_n.jpg

595 ms

12246609_10208478732510261_8306339133476501768_n.jpg

12246609_10208478732510261_8306339133476501768_n.jpg

628 ms

HEyyDkPknAC.png

HEyyDkPknAC.png

87 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

87 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

85 ms

pUFVdPjIRct.png

pUFVdPjIRct.png

69 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

69 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

135 ms

nr-885.min.js

nr-885.min.js

29 ms

chartbeat.js

chartbeat.js

6 ms

ping

ping

8 ms

e3921fef6d

e3921fef6d

50 ms

Accessibility Review

blog.livestrong.org accessibility score

97

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

blog.livestrong.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

blog.livestrong.org SEO score

100

Search Engine Optimization Advices

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 Blog.livestrong.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 Blog.livestrong.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

blog.livestrong.org

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