1.4 sec in total
93 ms
1.1 sec
238 ms
Visit cancercare.org now to see the best up-to-date Cancer Care content for United States and also check out these interesting facts you probably never knew about cancercare.org
CancerCare provides telephone, online and face-to-face counseling, support groups, education, publications and financial and co-payment assistance.
Visit cancercare.orgWe analyzed Cancercare.org page load time and found that the first response time was 93 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
cancercare.org performance score
name
value
score
weighting
Value2.1 s
79/100
10%
Value9.9 s
0/100
25%
Value5.0 s
64/100
10%
Value1,650 ms
11/100
30%
Value0.014
100/100
15%
Value17.5 s
4/100
10%
93 ms
242 ms
135 ms
67 ms
89 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 52% of them (22 requests) were addressed to the original Cancercare.org, 26% (11 requests) were made to F1.na.readspeaker.com and 12% (5 requests) were made to Media.cancercare.org. The less responsive or slowest element that took the longest time to load (414 ms) belongs to the original domain Cancercare.org.
Page size can be reduced by 688.8 kB (44%)
1.6 MB
879.2 kB
In fact, the total size of Cancercare.org main page is 1.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. 30% of websites need less resources to load. Images take 907.0 kB which makes up the majority of the site volume.
Potential reduce by 25.2 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 5.1 kB, which is 15% 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 25.2 kB or 74% of the original size.
Potential reduce by 218.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. Obviously, Cancer Care needs image optimization as it can save up to 218.4 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 351.0 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 351.0 kB or 69% of the original size.
Potential reduce by 94.1 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. Cancercare.org needs all CSS files to be minified and compressed as it can save up to 94.1 kB or 82% of the original size.
Number of requests can be reduced by 16 (40%)
40
24
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cancer Care. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
cancercare.org
93 ms
www.cancercare.org
242 ms
application-77e2405c1b81e7f7389563d646d22079.css
135 ms
jquery.min.js
67 ms
modernizr-0bb6c237de6805583e8e6ee05eb1dc1e.js
89 ms
application-622e65b1e35113a18510061ec736c5c3.js
281 ms
ReadSpeaker.js
90 ms
Online_Support_Group_Slider.jpg
358 ms
CEW_Slider_Andrew.jpg
326 ms
Video_Slider_Kathy_updated.jpg
326 ms
Monthly_Giving_Slider624.jpg
371 ms
pillow-talk-web-ad.jpg
175 ms
cancercare_logo_180x92-8369eccf8d955a02143a7872050c80a0.gif
112 ms
bullet-aaee6edca65292c3ab1685935566baaa.png
110 ms
bg_support_pulldown-bfce232cf87bcbbcf41e50704250c7b5.jpg
161 ms
facebook_icon_2013-34c42c4edc846e973e0e2b237d645583.png
111 ms
twitter_icon_2013-7b5856f98652f4d45817160d4920ed50.jpg
135 ms
youtube_icon_2013-057e5399f97cb9db9918199e4edd00e3.png
202 ms
instagram_icon_2014-071d950446c5985497aaf2df3956aec2.jpg
175 ms
blog_icon_2013-adf70f841996f3fab96ba7a6fb5f7682.jpg
286 ms
bg_megafooter-f044166b1775ca5595bd1904d31c0441.png
178 ms
facebook-footer-1628fcbc3f0f8a84f6419b5956728367.png
339 ms
twitter-footer-2698f676937cec6e6012ef5e05243e22.png
370 ms
youtube-footer-15475012b4ac1812276f762806374bb6.png
414 ms
instagram-footer-35eed8f12ab6dd7530cf575155abfb3e.png
286 ms
copelink-footer-8b64749934e0184c7550ebb3092d47e5.png
410 ms
ReadSpeaker.Styles.css
107 ms
ReadSpeaker.Core.js
149 ms
ReadSpeaker.pub.Config.js
63 ms
ga.js
33 ms
caption_bg-f1a000ed5cddb547ea129975bfc61c74.png
94 ms
slidenav-9992016b2ad921b60b6ea1579bfeab51.png
98 ms
ReadSpeaker.lib.Facade.adapter.jquery.js
51 ms
__utm.gif
11 ms
ReadSpeaker.Common.Settings.js
42 ms
ReadSpeaker.PlayerAPI.js
47 ms
ReadSpeaker.HL.js
73 ms
ReadSpeaker.ui.js
100 ms
print-1698b26b80b2efb3a25504c26504080d.css
83 ms
ReadSpeaker.enlargeHL.js
38 ms
ReadSpeaker.enlargeHL.css
68 ms
nr-852.min.js
15 ms
cancercare.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
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
cancercare.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
Browser errors were logged to the console
Page has valid source maps
cancercare.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Cancercare.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 Cancercare.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.
cancercare.org
Open Graph data is detected on the main page of Cancer Care. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: