Tools & Wizards About Us
vote.livestrong.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

vote.livestrong.org

LIVESTRONG voting

Page Load Speed

2.3 sec in total

First Response

56 ms

Resources Loaded

1.9 sec

Page Rendered

330 ms

vote.livestrong.org screenshot

About Website

Click here to check amazing Vote LIVESTRONG content for United States. Otherwise, check out these important facts you probably never knew about vote.livestrong.org

Your vote can have a lasting impact in the life of a cancer survivor. Vote in CIP today!

Visit vote.livestrong.org

Key Findings

We analyzed Vote.livestrong.org page load time and found that the first response time was 56 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

vote.livestrong.org performance score

0

Network Requests Diagram

vote.livestrong.org

56 ms

font-awesome.min.css

16 ms

fonts.css

844 ms

normalize.css

48 ms

foundation.min.css

33 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 37% of them (17 requests) were addressed to the original Vote.livestrong.org, 13% (6 requests) were made to Livestrong.org and 9% (4 requests) were made to Images.livestrong.org. The less responsive or slowest element that took the longest time to load (844 ms) relates to the external source Cloud.typography.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 326.2 kB (67%)

Content Size

487.0 kB

After Optimization

160.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vote.livestrong.org main page is 487.0 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. 50% of websites need less resources to load. Javascripts take 225.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 21.0 kB

  • Original 28.0 kB
  • After minification 23.7 kB
  • After compression 7.1 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 4.4 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 21.0 kB or 75% of the original size.

Image Optimization

-10%

Potential reduce by 6.0 kB

  • Original 59.0 kB
  • After minification 53.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. Vote LIVESTRONG images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 149.6 kB

  • Original 225.5 kB
  • After minification 193.7 kB
  • After compression 75.9 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 149.6 kB or 66% of the original size.

CSS Optimization

-86%

Potential reduce by 149.6 kB

  • Original 174.5 kB
  • After minification 163.1 kB
  • After compression 24.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. Vote.livestrong.org needs all CSS files to be minified and compressed as it can save up to 149.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (48%)

Requests Now

42

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vote 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 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vote.livestrong.org

vote.livestrong.org

56 ms

font-awesome.min.css

font-awesome.min.css

16 ms

fonts.css

fonts.css

844 ms

normalize.css

normalize.css

48 ms

foundation.min.css

foundation.min.css

33 ms

winners.css

winners.css

70 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

30 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

29 ms

jquery.cookie.js

jquery.cookie.js

43 ms

fastclick.js

fastclick.js

42 ms

foundation.js

foundation.js

99 ms

foundation.reveal.js

foundation.reveal.js

91 ms

jquery.tablesorter.min.js

jquery.tablesorter.min.js

59 ms

jquery.tablesorter.widgets.min.js

jquery.tablesorter.widgets.min.js

73 ms

jquery.imagemapster.min.js

jquery.imagemapster.min.js

77 ms

jquery.expander.min.js

jquery.expander.min.js

89 ms

jquery.validate.min.js

jquery.validate.min.js

88 ms

cip.js

cip.js

104 ms

13D19A210C662B2C9.css

13D19A210C662B2C9.css

77 ms

livestrong-logo.png

livestrong-logo.png

277 ms

cip-logo.png

cip-logo.png

123 ms

CIP-Overview-Video-Poster2.png

CIP-Overview-Video-Poster2.png

97 ms

region-map.svg

region-map.svg

98 ms

gtm.js

gtm.js

97 ms

all.js

all.js

95 ms

header-bg.jpg

header-bg.jpg

559 ms

tab-arrow-down.png

tab-arrow-down.png

457 ms

Video-Play-Blue2.svg

Video-Play-Blue2.svg

541 ms

analytics.js

analytics.js

28 ms

conversion_async.js

conversion_async.js

29 ms

163 ms

xd_arbiter.php

xd_arbiter.php

48 ms

xd_arbiter.php

xd_arbiter.php

64 ms

ec.js

ec.js

38 ms

74 ms

89 ms

collect

collect

10 ms

collect

collect

88 ms

121 ms

54 ms

ga-audiences

ga-audiences

17 ms

76 ms

160 ms

63 ms

66 ms

xd_arbiter.php

xd_arbiter.php

7 ms

SEO Factors

vote.livestrong.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 Vote.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 Vote.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

vote.livestrong.org

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