3.8 sec in total
38 ms
3.1 sec
708 ms
Welcome to blog.cancersupportcommunity.org homepage info - get ready to check Blog Cancer Support Community best content for United States right away, or after learning these important things about blog.cancersupportcommunity.org
A cancer support and cancer experience blog with patient's cancer stories and insights about cancer
Visit blog.cancersupportcommunity.orgWe analyzed Blog.cancersupportcommunity.org page load time and found that the first response time was 38 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
blog.cancersupportcommunity.org performance score
38 ms
1903 ms
150 ms
8 ms
17 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Blog.cancersupportcommunity.org, 71% (40 requests) were made to Cancersupportcommunity.org and 9% (5 requests) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Cancersupportcommunity.org.
Page size can be reduced by 448.7 kB (41%)
1.1 MB
651.3 kB
In fact, the total size of Blog.cancersupportcommunity.org main page is 1.1 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. 55% of websites need less resources to load. Images take 550.4 kB which makes up the majority of the site volume.
Potential reduce by 129.4 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 129.4 kB or 84% of the original size.
Potential reduce by 23.9 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 Cancer Support Community images are well optimized though.
Potential reduce by 191.8 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 191.8 kB or 70% of the original size.
Potential reduce by 103.6 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.cancersupportcommunity.org needs all CSS files to be minified and compressed as it can save up to 103.6 kB or 87% of the original size.
Number of requests can be reduced by 13 (27%)
49
36
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Cancer Support Community. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
blog.cancersupportcommunity.org
38 ms
blog
1903 ms
06fbcc11-09ea-4d27-82c4-c18a90d31d6b.css
150 ms
css_FdwfnTd_1Qh41ujQssEMLwhK8vveu4cNKcdhGkc-eXE.css
8 ms
js_jwv0R2Wud9HOeAPCDeJvfiQ54llo0euJttPWPyfexNM.js
17 ms
js_H03IIe6ntDr1f47zj1SNRp6VojOnYcvEnuhgdRgIBFQ.js
16 ms
js_rkA59otYIcuyXIxgeBUPtq3M1X8HrBj5MKi_EEVuNJE.js
14 ms
gtm.js
337 ms
search.png
322 ms
logo.png
273 ms
banner-blog.jpg
274 ms
betsyclark2015headshot.jpg
275 ms
social-work-month-2016.png
274 ms
donna-kearney-22-webfinal2.png
273 ms
new-website-email-blast.jpg
275 ms
cer-stomach-cancer-web-image.jpg
275 ms
guitar_with_signatures_-_new.jpg
277 ms
distress_screening_cancer_survivorship_seminar_poster_rti.jpg
277 ms
blog_post_jan_6.jpg
275 ms
blog_post_dec_22.jpg
277 ms
blog_post_dec_11.jpg
278 ms
amgen.png
277 ms
astrazeneca.png
277 ms
avalere.png
279 ms
bayer.png
278 ms
bi-logo.png
279 ms
bristol-myers-squibb.png
277 ms
celgene.png
277 ms
eisai.png
279 ms
genentech-biooncology.png
279 ms
gsk.png
280 ms
helsinn-logo-webfinal.png
279 ms
incyte.png
280 ms
lilly-oncology.png
280 ms
merck.png
281 ms
novartis-oncology.png
281 ms
pfizer-oncology.png
281 ms
icon-call.png
281 ms
icon-chat.png
282 ms
guidestar.png
283 ms
charity-navigator.png
281 ms
philanthropedia.png
282 ms
bcf54343-d033-41ee-bbd7-2b77df3fe7ba.woff
274 ms
14ff6081-326d-4dae-b778-d7afa66166fc.woff
274 ms
analytics.js
232 ms
icomoon.woff
48 ms
2c056da8-4920-4e20-8c69-8a6b315458a9.woff
93 ms
628a0837-f9e0-4b32-83c4-d99689b9da93.woff
93 ms
4711.js
64 ms
linkid.js
9 ms
collect
63 ms
collect
69 ms
collect
20 ms
s
65 ms
u
79 ms
collect
34 ms
blog.cancersupportcommunity.org SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.cancersupportcommunity.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.cancersupportcommunity.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.
blog.cancersupportcommunity.org
Open Graph description is not detected on the main page of Blog Cancer Support Community. 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: