Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

rdcrss.org

American Red Cross | Help Those Affected by Disasters

Page Load Speed

2.5 sec in total

First Response

19 ms

Resources Loaded

1 sec

Page Rendered

1.5 sec

rdcrss.org screenshot

About Website

Welcome to rdcrss.org homepage info - get ready to check Rdcrss best content right away, or after learning these important things about rdcrss.org

Every 8 minutes the American Red Cross responds to an emergency. Support the Red Cross. Join us today by making a donation.

Visit rdcrss.org

Key Findings

We analyzed Rdcrss.org page load time and found that the first response time was 19 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

rdcrss.org performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value1,690 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

rdcrss.org

19 ms

rdcrss.org

273 ms

www.redcross.org

82 ms

css

73 ms

base.min.38c753fae68ea793cf4581c563241e7d.css

22 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Rdcrss.org, 81% (60 requests) were made to Redcross.org and 9% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (344 ms) relates to the external source Redcross.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 458.9 kB (13%)

Content Size

3.4 MB

After Optimization

3.0 MB

In fact, the total size of Rdcrss.org main page is 3.4 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. 80% 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.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 109.7 kB

  • Original 125.3 kB
  • After minification 104.0 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 21.3 kB, which is 17% 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 109.7 kB or 88% of the original size.

Image Optimization

-10%

Potential reduce by 308.5 kB

  • Original 3.0 MB
  • After minification 2.6 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. Rdcrss images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 40.7 kB

  • Original 353.6 kB
  • After minification 353.6 kB
  • After compression 312.9 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 40.7 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (23%)

Requests Now

56

After Optimization

43

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

Accessibility Review

rdcrss.org accessibility score

86

Accessibility Issues

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

High

ARIA input fields do not have accessible names

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

rdcrss.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

Missing source maps for large first-party JavaScript

SEO Factors

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

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 doesn't use 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 Rdcrss.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 Rdcrss.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 data is detected on the main page of Rdcrss. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: