9.9 sec in total
2.7 sec
6.5 sec
620 ms
Visit cancerchallenge.com now to see the best up-to-date Cancer Challenge content for United States and also check out these interesting facts you probably never knew about cancerchallenge.com
We are a non-profit local to Northwest Arkansas that raises money for cancer resources. Our organization is proud to be 100% local in our giving efforts.
Visit cancerchallenge.comWe analyzed Cancerchallenge.com page load time and found that the first response time was 2.7 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize Cancerchallenge.com rating and web reputation
cancerchallenge.com performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value17.3 s
0/100
25%
Value12.7 s
3/100
10%
Value70 ms
99/100
30%
Value0.654
8/100
15%
Value8.9 s
35/100
10%
2694 ms
445 ms
60 ms
1190 ms
1194 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 87% of them (39 requests) were addressed to the original Cancerchallenge.com, 7% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Cancerchallenge.com.
Page size can be reduced by 430.5 kB (19%)
2.2 MB
1.8 MB
In fact, the total size of Cancerchallenge.com main page is 2.2 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. 45% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 15.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 2.4 kB, which is 11% 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 15.8 kB or 76% of the original size.
Potential reduce by 166.5 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. Cancer Challenge images are well optimized though.
Potential reduce by 179.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 179.5 kB or 67% of the original size.
Potential reduce by 68.7 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. Cancerchallenge.com needs all CSS files to be minified and compressed as it can save up to 68.7 kB or 83% of the original size.
Number of requests can be reduced by 8 (21%)
39
31
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cancer Challenge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.cancerchallenge.com
2694 ms
ip-utilities.js
445 ms
css
60 ms
font-awesome.css
1190 ms
Pagetypes.css
1194 ms
Default-2016.css
1121 ms
modernizr.custom.js
1048 ms
jquery.carouFredSel-6.2.0-packed.js
1046 ms
scripts.js
975 ms
jquery.js
323 ms
analytics.js
15 ms
logo.png
144 ms
hero-bg.jpg
274 ms
hero01.jpg
563 ms
tennis+photoV2.jpg
460 ms
Gala+Photo+2.jpg
359 ms
Run+Start+Line+Photo.jpg
1275 ms
bg-dot.png
362 ms
image01.png
432 ms
image02.png
740 ms
logo01.jpg
791 ms
logo02.jpg
792 ms
logo03.jpg
790 ms
HOPE+LOGO+VERTICAL.jpg
1630 ms
CSH+LOGO.png
1021 ms
Mercy+Logo.jpg
1745 ms
cclinic+logo+v2.jpg
1018 ms
sponsors01.jpg
1019 ms
sponsors02.jpg
1292 ms
sponsors03.jpg
1677 ms
sponsors04.jpg
1290 ms
AMG+Logo.png
1596 ms
AHB+Logo.gif
1690 ms
footer-photo.jpg
1887 ms
footer-logo.png
1806 ms
footer-bg.png
1839 ms
Facebook+Logo.png
1913 ms
Twitter+Logo.png
1912 ms
PoweredbyACTIVE.png
1958 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
79 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
80 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
80 ms
fontawesome-webfont.woff
1913 ms
collect
13 ms
fontawesome-webfont.ttf
290 ms
cancerchallenge.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
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.
cancerchallenge.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
cancerchallenge.com SEO score
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 Cancerchallenge.com 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 Cancerchallenge.com 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.
cancerchallenge.com
Open Graph description is not detected on the main page of Cancer Challenge. 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: