3.2 sec in total
225 ms
2.4 sec
531 ms
Click here to check amazing Livestrong content for United States. Otherwise, check out these important facts you probably never knew about livestrong.org
Livestrong unites, inspires and empowers people affected by cancer. We provide free cancer support services to anyone fighting cancer today.
Visit livestrong.orgWe analyzed Livestrong.org page load time and found that the first response time was 225 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
livestrong.org performance score
name
value
score
weighting
Value12.5 s
0/100
10%
Value29.1 s
0/100
25%
Value19.2 s
0/100
10%
Value14,500 ms
0/100
30%
Value0
100/100
15%
Value33.7 s
0/100
10%
225 ms
8 ms
311 ms
10 ms
150 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 27% of them (23 requests) were addressed to the original Livestrong.org, 24% (20 requests) were made to and 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (658 ms) relates to the external source Blog.livestrong.org.
Page size can be reduced by 834.3 kB (32%)
2.6 MB
1.7 MB
In fact, the total size of Livestrong.org main page is 2.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. 65% of websites need less resources to load. CSS take 983.9 kB which makes up the majority of the site volume.
Potential reduce by 89.9 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 18.0 kB, which is 16% 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 89.9 kB or 80% of the original size.
Potential reduce by 64.0 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. Livestrong images are well optimized though.
Potential reduce by 397.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 397.5 kB or 74% of the original size.
Potential reduce by 282.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. Livestrong.org needs all CSS files to be minified and compressed as it can save up to 282.9 kB or 29% of the original size.
Number of requests can be reduced by 27 (47%)
57
30
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 19 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.livestrong.org
225 ms
font-awesome.min.css
8 ms
fonts.css
311 ms
modernizr-2.6.2.min.js
10 ms
197921816.js
150 ms
jquery.min.js
97 ms
shared.css
9 ms
home.css
103 ms
spcjs.php
78 ms
vendor.js
98 ms
shared.bundle.js
36 ms
home.bundle.js
94 ms
bootstrap.min.js
55 ms
59C989969A82F64B9.css
203 ms
event
88 ms
spc.php
143 ms
fl.js
62 ms
nav-feature-wecanhelp.png
32 ms
kbefyltme5iyp9w2o70f.jpg
271 ms
NCDs_in_SDGs_forWeb_Page_1-300x212.jpg
124 ms
Amanda-1024x768.jpg
580 ms
MAT4696-841x1024.jpg
658 ms
nav-feature-takeaction.png
29 ms
nav-feature-whatwedo.png
29 ms
nav-feature-whoweare.jpg
28 ms
new_play_button.png
28 ms
gtm.js
122 ms
atrk.js
65 ms
all.js
478 ms
widgets.js
482 ms
b63723789d955d0a9af85866f43cc288.png
39 ms
iuirvejtdnan9ilp2wle.jpg
413 ms
vvq2vlwngjlbjq2ezzb1.jpg
418 ms
16681e0b74dfc5df53142b2e40e08ebb.jpg
59 ms
cbc2cc29e3e1bf50884a3a9a6963ee6f.png
56 ms
75663ca52a942c54c47ae0cd4ee5cd49.jpg
56 ms
fontawesome-webfont.woff
50 ms
dfbec84d3b668b5b0d0bf20ccece66f0.png
360 ms
36f3dd9ea240dddf0af3fce64de64e6e.png
361 ms
20e237eb79bbb41e9678ce4d1fbc9feb.png
360 ms
2491cc33fab900b15c177bded64c8816.png
360 ms
b80b95ae502d684bd4c258f997b2287f.png
360 ms
ALX1PnQ=
147 ms
2i0qcQd9IHsXY9B2CxT0Pghcy73YNJQtY8HnbWekqWY4cXJTHj6mO2xifX+28uuPjD6X4DeaaPoA=
146 ms
pVAkD3iFt6JGJeyP8oY7KjV20xQF3NsvKjGEoZU8iqnpOwSLex4EL2Te7RoqFrDg87a30tWymji4uEgeUh23MT692nl1J8cfSvkLdUk+ZA==
146 ms
2nl1J8cfSvEbhXg+aA==
145 ms
tZJYbQN5JHMTZ9i0C440HwQubdrqFkAQs+bzuSrpLlyMHFefKY6rCN8fnVzqs7OfxQit+lyj5w
145 ms
QewtokLNNxrhAe+4cAc79D2ihoEJCl1doP6lZtaMXjYnEL+jwyns2JfzqmomNfIwnTXkMIYNGxSN9Wr2qYlcCKZFwbEH6Zj88wc59axki2DW53Uzx3MQeEpOefJHfEVeoSutNGONL5J5kcwjkjlVSj7Oemp7sT6+wZv1W5il6TzkZ5ZeyPxfCnnygJd7KypUwv4obrijUmM7TlHAvf2iEkPoG8mjGJu+Q7C450HwQubdrqFkAQs+bzsrXSXLkYOL8+Qh1XEb49OrnVd3cvyhFL8AtfU+dA==
145 ms
aLSpxB30gexdj0HYLFPQ+CFzLvdg0lC1jwedtZ6SpZjhxclMePqY7bGJ9f7by64+MPpfgN5po+gA==
145 ms
KGOyo1dtMUBdzbLyoxhKGVPIqp6TsEi3seBC9k3u0aKhaw4PO2t9LVspo4uLhIHlIdtzE+vdp5dSfHH0r5C3VJPmQ=
145 ms
2nl1J8cfSvEbhXg+aA==
144 ms
1LIk0e83JOoUAn6WdxwR6XGdpyigAf7WSWG0DeSRzE2fYtAuONB8ELm3a6hZAELPm87kq6S5cjBxXnymOqwjfH51c6rOzn8UIrfpco+cA==
145 ms
UijSB7wikJCoBf0ob7ijymA7TlHAvf2sEmfQN4pHMTZ9i0C440HwQubdbqBiAQs+bztSXqpq5OCTIn1IddjG+PRq59WdHn4o5S9lDj5g
144 ms
Lj8g
143 ms
lDKX2UiPmA=
144 ms
UijSB7wikJCoBf0ob7ijymA7TlHAvf2sEmfQN4pHMTZ9i0C440HwQubdbqBiAQs+bztSXqpq5OCTIn1IddjG+PRq59WdHn4o5S80iT5U
143 ms
FDKX1TjPlw=
142 ms
UijSB7wikJCoBf0ob7ijymA7TlHAvf2sEmfQN4pHMTZ9i0C440HwQubdbqBiAQs+bztSXqpq5OCTIn1IddjG+PRq59WdHn4o5S9lDj5g
143 ms
Lj8g
142 ms
1Iokge8wpOoUQn6Ud5wR6XGbpqigHv7RSWGMLSSRzE1fYdAuOdB8ELm3a6hYgELPm97kq6W1cTBxUXykOq4jfHp1c6rOzn+UMpfZSI+YA==
142 ms
UijSB7wikJCoBf0ob7ijymA7TlHAvf2sEmfQN4pHMTZ9i0C440HwQubdbqBiAQs+bztSXqpq5OCTIn1IddjG+PRq59WdHn4o5S80iT5U
143 ms
FDKX1TjPlw=
142 ms
ff762b3831af39d5c79dbc5370b93ff4.woff
347 ms
iframe_api
417 ms
lvnmnoxq3bc9s0l2zxum.jpg
309 ms
atrk.gif
316 ms
analytics.js
296 ms
conversion_async.js
272 ms
loyce-pace-survey-drop.jpg
400 ms
test.png
455 ms
163 ms
xd_arbiter.php
131 ms
xd_arbiter.php
272 ms
www-widgetapi.js
91 ms
66 ms
ec.js
32 ms
37 ms
collect
16 ms
collect
66 ms
collect
20 ms
collect
31 ms
collect
51 ms
ga-audiences
15 ms
ga-audiences
18 ms
xd_arbiter.php
77 ms
livestrong.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
livestrong.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
livestrong.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.
livestrong.org
Open Graph data is detected on the main page of Livestrong. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: