2.3 sec in total
51 ms
1.7 sec
535 ms
Click here to check amazing Reaf Sf content. Otherwise, check out these important facts you probably never knew about reaf-sf.org
The Richmond/Ermet Aid Foundation of San Francisco produces fundraising events for HIV/AIDS, hunger and youth services.
Visit reaf-sf.orgWe analyzed Reaf-sf.org page load time and found that the first response time was 51 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
reaf-sf.org performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value5.2 s
23/100
25%
Value2.4 s
98/100
10%
Value140 ms
95/100
30%
Value0.274
44/100
15%
Value3.8 s
89/100
10%
51 ms
42 ms
90 ms
11 ms
115 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Reaf-sf.org, 38% (14 requests) were made to Img1.wsimg.com and 16% (6 requests) were made to Nebula.wsimg.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Nebula.wsimg.com.
Page size can be reduced by 217.8 kB (19%)
1.1 MB
902.2 kB
In fact, the total size of Reaf-sf.org main page is 1.1 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. 65% of websites need less resources to load. Images take 747.5 kB which makes up the majority of the site volume.
Potential reduce by 110.9 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 110.9 kB or 78% of the original size.
Potential reduce by 1.0 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. Reaf Sf images are well optimized though.
Potential reduce by 67.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 67.4 kB or 37% of the original size.
Potential reduce by 38.4 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. Reaf-sf.org needs all CSS files to be minified and compressed as it can save up to 38.4 kB or 82% of the original size.
Number of requests can be reduced by 20 (59%)
34
14
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reaf Sf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
www.reaf-sf.org
51 ms
css
42 ms
css
90 ms
site.css
11 ms
duel.js
115 ms
addthis_widget.js
533 ms
jq.js
643 ms
analytics.js
1101 ms
f9df2093285a8d9a0da14860d81d576a
820 ms
subNavigation.js
758 ms
media.audioplayer.js
754 ms
8420398
1265 ms
cookiemanager.js
758 ms
iebackground.js
789 ms
d4a8134852b8b61700ea2aa17a198876
788 ms
2005377490caa8a3a70df1b98fbe7195
1045 ms
66edb4e9ffeb7dbd4f9c7bc82d1324d8
1277 ms
5722fbdd15a0ea326c42a2a3fd539a8d
1074 ms
4250eeffdc6dc512ae93c0f6ec61b87e
1070 ms
wsb-audioplayer-controls-64.png
789 ms
tccl.min.js
971 ms
_Xmr-H4zszafZw3A-KPSZut9wQiX.woff
959 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYw.woff
999 ms
moatframe.js
728 ms
layers.fa6cd1947ce26e890d3d.js
318 ms
_ate.track.config_resp
755 ms
300lo.json
848 ms
sh.f48a1a04fe8dbf021b4cda1d.html
649 ms
util.instances.js
340 ms
util.model.js
335 ms
documentHelper.js
340 ms
jquery.dotdotdot.js
323 ms
jquery.jplayer.js
321 ms
overlay.js
314 ms
util.window.js
491 ms
sf.core.pkg.js
230 ms
collect
117 ms
reaf-sf.org accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
reaf-sf.org 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
reaf-sf.org SEO score
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 uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reaf-sf.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 Reaf-sf.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.
reaf-sf.org
Open Graph data is detected on the main page of Reaf Sf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: