Tools & Wizards About Us
bnr.rw screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

bnr.rw

BNR-National Bank of Rwanda: Home

Page Load Speed

7.4 sec in total

First Response

600 ms

Resources Loaded

6.6 sec

Page Rendered

224 ms

bnr.rw screenshot

About Website

Click here to check amazing BNR content for Rwanda. Otherwise, check out these important facts you probably never knew about bnr.rw

Visit bnr.rw

Key Findings

We analyzed Bnr.rw page load time and found that the first response time was 600 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

bnr.rw performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value25.3 s

0/100

25%

SI (Speed Index)

Value20.4 s

0/100

10%

TBT (Total Blocking Time)

Value2,270 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value36.0 s

0/100

10%

Network Requests Diagram

index.php

600 ms

stylesheet_c9ed22c3dc.css

278 ms

default.css

554 ms

javascript_ebd9c81938.js

553 ms

reset.css

558 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that all of those requests were addressed to Bnr.rw and no external sources were called. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Bnr.rw.

Page Optimization Overview & Recommendations

Page size can be reduced by 725.1 kB (41%)

Content Size

1.8 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bnr.rw main page is 1.8 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. 30% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 25.0 kB

  • Original 31.3 kB
  • After minification 29.2 kB
  • After compression 6.2 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 25.0 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 47.2 kB

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

JavaScript Optimization

-88%

Potential reduce by 616.4 kB

  • Original 702.7 kB
  • After minification 340.5 kB
  • After compression 86.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 616.4 kB or 88% of the original size.

CSS Optimization

-82%

Potential reduce by 36.5 kB

  • Original 44.4 kB
  • After minification 31.6 kB
  • After compression 7.9 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. Bnr.rw needs all CSS files to be minified and compressed as it can save up to 36.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (32%)

Requests Now

50

After Optimization

34

  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BNR. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

index.php

index.php

600 ms

stylesheet_c9ed22c3dc.css

stylesheet_c9ed22c3dc.css

278 ms

default.css

default.css

554 ms

javascript_ebd9c81938.js

javascript_ebd9c81938.js

553 ms

reset.css

reset.css

558 ms

index.css

index.css

562 ms

sidebar.css

sidebar.css

563 ms

jquery-1.4.min.js

jquery-1.4.min.js

855 ms

jquery.dropdownPlain.js

jquery.dropdownPlain.js

831 ms

jquery.jqplot.js

jquery.jqplot.js

1710 ms

jqplot.canvasTextRenderer.js

jqplot.canvasTextRenderer.js

840 ms

jqplot.categoryAxisRenderer.js

jqplot.categoryAxisRenderer.js

843 ms

jqplot.canvasAxisTickRenderer.js

jqplot.canvasAxisTickRenderer.js

841 ms

jqplot.highlighter.js

jqplot.highlighter.js

1106 ms

jqplot.cursor.js

jqplot.cursor.js

1120 ms

jqplot.dateAxisRenderer.js

jqplot.dateAxisRenderer.js

1122 ms

jquery.jqplot.css

jquery.jqplot.css

1120 ms

nivo-slider.css

nivo-slider.css

1135 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

1391 ms

background3.jpg

background3.jpg

276 ms

logo.jpg

logo.jpg

558 ms

Banknote1.jpg

Banknote1.jpg

555 ms

Banknote_3.jpg

Banknote_3.jpg

852 ms

mp1.jpg

mp1.jpg

841 ms

mp2.jpg

mp2.jpg

1111 ms

mp3.jpg

mp3.jpg

1102 ms

mp4.jpg

mp4.jpg

1104 ms

mp5.jpg

mp5.jpg

1390 ms

mp6.jpg

mp6.jpg

1396 ms

mp7.jpg

mp7.jpg

1417 ms

mp8.jpg

mp8.jpg

1654 ms

mp9.jpg

mp9.jpg

1655 ms

mp10.jpg

mp10.jpg

1662 ms

mp11.jpg

mp11.jpg

1943 ms

mp12.jpg

mp12.jpg

1950 ms

mp13.jpg

mp13.jpg

1980 ms

mp14.jpg

mp14.jpg

2204 ms

feedback.PNG

feedback.PNG

1932 ms

output_aOZ06i.gif

output_aOZ06i.gif

1938 ms

charter.PNG

charter.PNG

2208 ms

BERNARD.jpg

BERNARD.jpg

2214 ms

facebook.png

facebook.png

2218 ms

twitter.png

twitter.png

2226 ms

youtube.png

youtube.png

2261 ms

greyb.jpg

greyb.jpg

2423 ms

note.jpg

note.jpg

2430 ms

monetary2.jpg

monetary2.jpg

2436 ms

pay.jpg

pay.jpg

2442 ms

financial.jpg

financial.jpg

2447 ms

blue.jpg

blue.jpg

2488 ms

tdbk.gif

tdbk.gif

2696 ms

arrows.png

arrows.png

277 ms

Accessibility Review

bnr.rw accessibility score

64

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-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

bnr.rw best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

bnr.rw SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 uses 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 Bnr.rw 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 Bnr.rw 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

bnr.rw

Open Graph description is not detected on the main page of BNR. 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: