13 sec in total
173 ms
11.2 sec
1.7 sec
Welcome to rapidcpr.com homepage info - get ready to check Rapidcpr best content for United States right away, or after learning these important things about rapidcpr.com
Join the fight against our nations No. 1 and No. 5 killers - heart disease and stroke - and find out how to give and donate to the American Heart Association.
Visit rapidcpr.comWe analyzed Rapidcpr.com page load time and found that the first response time was 173 ms and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rapidcpr.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value23.3 s
0/100
25%
Value18.0 s
0/100
10%
Value51,360 ms
0/100
30%
Value0.039
100/100
15%
Value63.4 s
0/100
10%
173 ms
1683 ms
319 ms
445 ms
406 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rapidcpr.com, 36% (40 requests) were made to Heart.org and 8% (9 requests) were made to Static.cloud.coveo.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Heart.org.
Page size can be reduced by 225.3 kB (30%)
751.3 kB
526.0 kB
In fact, the total size of Rapidcpr.com main page is 751.3 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. 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 259.2 kB which makes up the majority of the site volume.
Potential reduce by 124.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 124.0 kB or 78% of the original size.
Potential reduce by 1.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. Rapidcpr images are well optimized though.
Potential reduce by 96.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 96.0 kB or 55% of the original size.
Potential reduce by 3.8 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. Rapidcpr.com has all CSS files already compressed.
Number of requests can be reduced by 64 (62%)
103
39
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rapidcpr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
rapidcpr.com
173 ms
1683 ms
optimize.js
319 ms
aha-custom-gtm-recipes.js
445 ms
css2
406 ms
vendor.css
90 ms
app.css
280 ms
VisitorIdentification.js
234 ms
global.css
851 ms
vendor.bundle.js
309 ms
app.bundle.js
295 ms
CoveoFullSearch.css
396 ms
CoveoForSitecore.css
393 ms
CoveoJsSearch.Lazy.min.js
838 ms
CoveoForSitecore.Lazy.min.js
429 ms
en.js
429 ms
ARMPCVPV
1353 ms
gtm.js
5007 ms
AHA_icon.svg
874 ms
search.svg
876 ms
search.svg
882 ms
red-symptoms-icon.svg
859 ms
twitter-gray.svg
852 ms
facebook-gray.svg
900 ms
instagram-gray.svg
923 ms
youtube-gray.svg
897 ms
pinterest-gray.svg
927 ms
linkedin-gray.svg
910 ms
red-symptoms-icon.svg
907 ms
aha_heart.svg
937 ms
senior_couple_heart_hands.jpg
952 ms
hands_holding_candle.jpg
950 ms
family_close_up.jpg
949 ms
Finn.jpg
908 ms
Events_icon.jpg
949 ms
Volunteer_icon.jpg
951 ms
Fundraise_icon.jpg
947 ms
Give_Today_icon.jpg
4564 ms
Shop_to_Save_Lives_icon.jpg
4564 ms
Corporate_Giving_icon.jpg
4564 ms
Honor_Memorial_icon.jpg
4563 ms
Planned_giving_icon.jpg
4563 ms
AHA_Full.svg
4874 ms
Tiktok_grey.png
4893 ms
nhc_optimized.png
4892 ms
bbb_100px.png
4890 ms
Charity-Navigator.png
4890 ms
ComodoSSLSecureSeal.png
4878 ms
ahalogo.png
5218 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
3708 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
4036 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
4040 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
4041 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
4039 ms
aha-icon-font.ttf
4374 ms
css
204 ms
conversion_async.js
613 ms
hotjar-1023445.js
789 ms
gtm.js
601 ms
fbevents.js
782 ms
pixie.js
942 ms
js
774 ms
analytics.js
575 ms
Oct22_FY23_lightbox.jpg
265 ms
token
337 ms
484 ms
45269291.js
485 ms
core.js
594 ms
insight.min.js
613 ms
uwt.js
610 ms
up_loader.1.1.0.js
601 ms
js
256 ms
btp.js
1100 ms
ytc.js
591 ms
sv.js
590 ms
744 ms
modules.bcd9ade6b0bb9bdd0789.js
1054 ms
736154100088324
180 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
913 ms
pixie
906 ms
Searchbox.min__4da234f0fccb61abb03c.js
180 ms
CoveoForSitecoreConfigureSearchHub.min.js
176 ms
CoveoForSitecoreBindWithUserContext.min.js
176 ms
CoveoForSitecoreExpressions.min.js
176 ms
js
482 ms
js
295 ms
js
649 ms
collect
778 ms
1716007538720452
406 ms
collect
198 ms
1066 ms
main.3a217bc7.js
505 ms
adsct
1116 ms
adsct
1116 ms
10178052.json
459 ms
track.securedvisit.com
447 ms
track.securedvisit.com
637 ms
566975180179047
423 ms
720 ms
512 ms
ga-audiences
596 ms
880 ms
860 ms
827 ms
454054155084786
234 ms
visit-data
893 ms
96 ms
640841653478511
153 ms
716774359567706
218 ms
371 ms
20 ms
ct.html
63 ms
rapidcpr.com accessibility score
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.
rapidcpr.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
rapidcpr.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Rapidcpr.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 Rapidcpr.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.
rapidcpr.com
Open Graph data is detected on the main page of Rapidcpr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: