15.7 sec in total
2.6 sec
12.8 sec
208 ms
Click here to check amazing Central Bank Go content for Kenya. Otherwise, check out these important facts you probably never knew about centralbank.go.ke
Visit centralbank.go.keWe analyzed Centralbank.go.ke page load time and found that the first response time was 2.6 sec and then it took 13.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
centralbank.go.ke performance score
name
value
score
weighting
Value8.8 s
0/100
10%
Value10.6 s
0/100
25%
Value21.3 s
0/100
10%
Value2,220 ms
6/100
30%
Value0.07
96/100
15%
Value25.7 s
0/100
10%
2617 ms
59 ms
745 ms
762 ms
817 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 93% of them (63 requests) were addressed to the original Centralbank.go.ke, 3% (2 requests) were made to Ssl.google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Centralbank.go.ke.
Page size can be reduced by 856.8 kB (72%)
1.2 MB
333.4 kB
In fact, the total size of Centralbank.go.ke 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. 40% of websites need less resources to load. Images take 563.6 kB which makes up the majority of the site volume.
Potential reduce by 49.4 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.3 kB, which is 16% 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 49.4 kB or 84% of the original size.
Potential reduce by 410.6 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. Obviously, Central Bank Go needs image optimization as it can save up to 410.6 kB or 73% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 324.1 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 324.1 kB or 67% of the original size.
Potential reduce by 72.7 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. Centralbank.go.ke needs all CSS files to be minified and compressed as it can save up to 72.7 kB or 85% of the original size.
Number of requests can be reduced by 20 (32%)
62
42
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Central Bank Go. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
centralbank.go.ke
2617 ms
ga.js
59 ms
menu.min.css
745 ms
menu.fix.css
762 ms
style.css.php
817 ms
mootools-core.js
1837 ms
core.js
802 ms
caption.js
1480 ms
mootools-more.js
2959 ms
md_stylechanger.js
1510 ms
ext-core.js
2294 ms
menu.min.js
1585 ms
swfobject.js
2263 ms
system.css
2310 ms
position.css
2424 ms
layout.css
2828 ms
general.css
3046 ms
personal.css
3388 ms
__utm.gif
13 ms
collect
55 ms
ga-audiences
35 ms
hide.js
2903 ms
personal.css
2963 ms
layout.css
3430 ms
crawler.js
3244 ms
getseal
83 ms
system.css
781 ms
bg.jpg
366 ms
blue1.jpg
467 ms
blue2.jpg
787 ms
search.jpg
775 ms
cbk-logo.jpg
1049 ms
corner1.jpg
788 ms
corner2.jpg
1171 ms
menu-arrow-down.png
1235 ms
corner3.jpg
1516 ms
rates.jpg
1535 ms
rates1.jpg
1559 ms
downarrow.jpg
1849 ms
uparrow.jpg
1915 ms
didyouknow.jpg
2296 ms
facebook.jpg
2258 ms
twitter.jpg
2275 ms
securitys.jpg
2581 ms
Ibservices.jpg
2619 ms
bservices.jpg
2695 ms
depositeprot.jpg
3040 ms
advert.jpg
3058 ms
pay.jpg
3102 ms
faqs.jpg
3335 ms
coin.jpg
3360 ms
rss_fullposts.gif
3446 ms
rates2.jpg
3799 ms
banner.jpg
4290 ms
tabs.jpg
4067 ms
list1.jpg
4090 ms
bot_keydol.jpg
4381 ms
bot_keyrates.jpg
4226 ms
tender.jpg
4843 ms
top1.jpg
5057 ms
top2.jpg
4860 ms
top3.jpg
4969 ms
topi1.jpg
5263 ms
topi2.jpg
4794 ms
topi3.jpg
5168 ms
grey.jpg
4899 ms
fot.jpg
5013 ms
print.css
385 ms
centralbank.go.ke accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
centralbank.go.ke 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
Browser errors were logged to the console
centralbank.go.ke SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Centralbank.go.ke 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 Centralbank.go.ke 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.
centralbank.go.ke
Open Graph description is not detected on the main page of Central Bank Go. 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: