3.6 sec in total
633 ms
1.5 sec
1.5 sec
Click here to check amazing Red Cross content. Otherwise, check out these important facts you probably never knew about redcross.com
Every 8 minutes the American Red Cross responds to an emergency. Support the Red Cross. Join us today by making a donation.
Visit redcross.comWe analyzed Redcross.com page load time and found that the first response time was 633 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
redcross.com performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value10.6 s
0/100
25%
Value6.8 s
34/100
10%
Value1,020 ms
26/100
30%
Value0
100/100
15%
Value19.4 s
2/100
10%
633 ms
29 ms
105 ms
39 ms
31 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Redcross.com, 3% (2 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (633 ms) relates to the external source Redcross.org.
Page size can be reduced by 931.4 kB (24%)
3.9 MB
3.0 MB
In fact, the total size of Redcross.com main page is 3.9 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.0 MB which makes up the majority of the site volume.
Potential reduce by 112.3 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 112.3 kB or 88% of the original size.
Potential reduce by 308.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. Red Cross images are well optimized though.
Potential reduce by 510.6 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 510.6 kB or 62% of the original size.
Number of requests can be reduced by 13 (22%)
58
45
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Red Cross. 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.
www.redcross.org
633 ms
css
29 ms
base.min.38c753fae68ea793cf4581c563241e7d.css
105 ms
components.min.a5a85e73bbb5b25b40c4e90ded0cfbef.css
39 ms
dependencies.min.js
31 ms
new-relic-content-prod.js
54 ms
launch-b67461f3859d.min.js
63 ms
slick.min.60b63101d7aa0457930f2272e5a9e9b5.css
53 ms
slick.min.4afaabaef6ed241e1280cf45a2dfa7d1.js
84 ms
polyfills.min.js
78 ms
base.min.js
65 ms
components.min.js
86 ms
locationdetection.min.js
64 ms
token.json
267 ms
G5EYL-3FTNM-K2QN3-FX5YQ-53AZH
321 ms
locdet.min.js
81 ms
redcross-logo.png.img.png
65 ms
Donate-Promo-Jul24-255x217.jpg.img.jpeg
66 ms
Emergency-Need-Donate-Nav.jpg.img.jpeg
122 ms
TS-Lifeguarding-promo-box.jpg.img.jpeg
67 ms
Vol-Disaster-Spec-255x217.jpg.img.jpeg
159 ms
wildfire-255x217.jpg.img.jpeg
66 ms
413701-49_Appeal_HeroGraphicRed_1348x505-AR.jpg
84 ms
image.jpeg
353 ms
image.jpeg
84 ms
image.png
83 ms
image.png
88 ms
image.png
102 ms
image.png
101 ms
image.png
110 ms
image.png
153 ms
image.png
143 ms
image.png
129 ms
image.png
251 ms
image.jpeg
152 ms
image.png
164 ms
image.jpeg
170 ms
image.jpeg
169 ms
image.png
241 ms
image.png
184 ms
image.png
187 ms
image.png
186 ms
image.jpeg
205 ms
image.jpeg
204 ms
image.jpeg
204 ms
image.jpeg
223 ms
image.jpeg
263 ms
image.jpeg
224 ms
image.png
250 ms
font
18 ms
font
29 ms
rco-icon.ttf
238 ms
glyphicons-halflings-regular.woff
304 ms
fa-solid-900.ttf
201 ms
fa-solid-900.woff
231 ms
fa-regular-400.ttf
229 ms
fa-regular-400.woff
229 ms
js
55 ms
fa-brands-400.ttf
250 ms
fa-brands-400.woff
250 ms
image.png
227 ms
image.jpeg
268 ms
MAWM-desktop.jpg
265 ms
config.json
73 ms
image.png
230 ms
image.png
259 ms
image.png
242 ms
redcross.com 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 input fields do not have accessible names
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
Image elements do not have [alt] attributes
Links do not have a discernible name
redcross.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
redcross.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 doesn't use 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 Redcross.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 Redcross.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.
redcross.com
Open Graph data is detected on the main page of Red Cross. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: