Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

rbf.org

Rockefeller Brothers Fund – Home | Rockefeller Brothers Fund

Page Load Speed

1.5 sec in total

First Response

51 ms

Resources Loaded

737 ms

Page Rendered

728 ms

About Website

Welcome to rbf.org homepage info - get ready to check Rbf best content for United States right away, or after learning these important things about rbf.org

The Rockefeller Brothers Fund advances social change that contributes to a more just, sustainable, and peaceful world.

Visit rbf.org

Key Findings

We analyzed Rbf.org page load time and found that the first response time was 51 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

rbf.org performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

8/100

25%

SI (Speed Index)

Value2.7 s

97/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.087

93/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

rbf.org

51 ms

rbf.org

95 ms

www.rbf.org

190 ms

js

52 ms

hotjar.script.js

23 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 80% of them (39 requests) were addressed to the original Rbf.org, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (336 ms) belongs to the original domain Rbf.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 116.9 kB (10%)

Content Size

1.2 MB

After Optimization

1.0 MB

In fact, the total size of Rbf.org main page is 1.2 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 43.2 kB

  • Original 52.1 kB
  • After minification 43.2 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 9.0 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 43.2 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 73.3 kB

  • Original 1.0 MB
  • After minification 947.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. Rbf images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 227 B

  • Original 65.5 kB
  • After minification 65.5 kB
  • After compression 65.3 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

-1%

Potential reduce by 176 B

  • Original 24.0 kB
  • After minification 24.0 kB
  • After compression 23.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. Rbf.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (20%)

Requests Now

45

After Optimization

36

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

Accessibility Review

rbf.org accessibility score

89

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.

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 IDs are not unique

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

rbf.org 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

rbf.org SEO score

93

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

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 Rbf.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 Rbf.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 description is not detected on the main page of Rbf. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: