Report Summary

  • 56

    Performance

    Renders faster than
    74% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

findcancerhelp.org

Find Cancer Help: Resources, Support & Stories of Hope

Page Load Speed

3.3 sec in total

First Response

626 ms

Resources Loaded

2.2 sec

Page Rendered

476 ms

findcancerhelp.org screenshot

About Website

Welcome to findcancerhelp.org homepage info - get ready to check Find Cancer Help best content right away, or after learning these important things about findcancerhelp.org

Find the resources, support, and inspiration your journey deserves from the people who have walked it themselves.

Visit findcancerhelp.org

Key Findings

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

Performance Metrics

findcancerhelp.org performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

Network Requests Diagram

findcancerhelp.com

626 ms

wp-emoji-release.min.js

265 ms

widget.css

222 ms

style.min.css

217 ms

style-legacy.css

219 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Findcancerhelp.org, 6% (3 requests) were made to Cdnjs.cloudflare.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (636 ms) relates to the external source Cdnjs.cloudflare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 120.2 kB (14%)

Content Size

861.6 kB

After Optimization

741.4 kB

In fact, the total size of Findcancerhelp.org main page is 861.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 734.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 91.0 kB

  • Original 113.9 kB
  • After minification 107.9 kB
  • After compression 23.0 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 91.0 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 21.1 kB

  • Original 734.5 kB
  • After minification 713.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. Find Cancer Help images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 8.2 kB

  • Original 13.2 kB
  • After minification 12.7 kB
  • After compression 5.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 8.2 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (82%)

Requests Now

44

After Optimization

8

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Find Cancer Help. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

findcancerhelp.org accessibility score

62

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

findcancerhelp.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

findcancerhelp.org SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Findcancerhelp.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 Findcancerhelp.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

Open Graph description is not detected on the main page of Find Cancer Help. 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: