Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

runtofightcancer.com

Run to Fight Children's Cancer | Children's Cancer Network

Page Load Speed

9.1 sec in total

First Response

1.7 sec

Resources Loaded

6.9 sec

Page Rendered

564 ms

runtofightcancer.com screenshot

About Website

Welcome to runtofightcancer.com homepage info - get ready to check Run To Fight Cancer best content right away, or after learning these important things about runtofightcancer.com

Run to Fight Children's Cancer 2023 Click Here to Register today! On your mark. Get set. GO! Days Hours Mins Race Starter 2023 >> Meet Elilai! Elilai is 9 years…

Visit runtofightcancer.com

Key Findings

We analyzed Runtofightcancer.com page load time and found that the first response time was 1.7 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

runtofightcancer.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value18.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.321

36/100

15%

TTI (Time to Interactive)

Value34.9 s

0/100

10%

Network Requests Diagram

www.runtofightcancer.com

1689 ms

wp-emoji-release.min.js

82 ms

style.min.css

309 ms

all.min.css

304 ms

simple-line-icons.min.css

160 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 97% of them (107 requests) were addressed to the original Runtofightcancer.com, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Runtofightcancer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 290.2 kB (6%)

Content Size

4.5 MB

After Optimization

4.2 MB

In fact, the total size of Runtofightcancer.com main page is 4.5 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. 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 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 176.6 kB

  • Original 212.2 kB
  • After minification 207.8 kB
  • After compression 35.6 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 176.6 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 112.5 kB

  • Original 3.8 MB
  • After minification 3.7 MB

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. Run To Fight Cancer images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 400 B

  • Original 295.8 kB
  • After minification 295.8 kB
  • After compression 295.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 695 B

  • Original 166.8 kB
  • After minification 166.8 kB
  • After compression 166.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. Runtofightcancer.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 57 (68%)

Requests Now

84

After Optimization

27

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

Accessibility Review

runtofightcancer.com accessibility score

93

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

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

Links do not have a discernible name

Best Practices

runtofightcancer.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

runtofightcancer.com SEO score

90

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

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

Social Sharing Optimization

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