Tools & Wizards About Us
idbz.co.zw screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    21% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

idbz.co.zw

Infrastructure Development Bank of Zimbabwe (IDBZ) |

Page Load Speed

16.2 sec in total

First Response

258 ms

Resources Loaded

15.6 sec

Page Rendered

327 ms

idbz.co.zw screenshot

About Website

Click here to check amazing IDBZ content for Zimbabwe. Otherwise, check out these important facts you probably never knew about idbz.co.zw

The IDBZ was formed on the 31st of August 2005, taking over the assets and liabilities of the former Zimbabwe Development Bank (“ZDB”). It was primarily set up as a vehicle for the promotion of econom...

Visit idbz.co.zw

Key Findings

We analyzed Idbz.co.zw page load time and found that the first response time was 258 ms and then it took 15.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.

Performance Metrics

idbz.co.zw performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value23.8 s

0/100

10%

TBT (Total Blocking Time)

Value23,460 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.292

41/100

15%

TTI (Time to Interactive)

Value36.2 s

0/100

10%

Network Requests Diagram

idbz.co.zw

258 ms

idbz.co.zw

95 ms

system.base.css

1146 ms

system.menus.css

1162 ms

system.messages.css

1160 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 89% of them (82 requests) were addressed to the original Idbz.co.zw, 5% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (7.4 sec) belongs to the original domain Idbz.co.zw.

Page Optimization Overview & Recommendations

Page size can be reduced by 422.1 kB (33%)

Content Size

1.3 MB

After Optimization

843.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Idbz.co.zw main page is 1.3 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. 35% of websites need less resources to load. Images take 760.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 66.2 kB

  • Original 80.3 kB
  • After minification 75.6 kB
  • After compression 14.1 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 66.2 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 42.0 kB

  • Original 760.7 kB
  • After minification 718.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. IDBZ images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 195.2 kB

  • Original 278.9 kB
  • After minification 222.0 kB
  • After compression 83.7 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 195.2 kB or 70% of the original size.

CSS Optimization

-81%

Potential reduce by 118.6 kB

  • Original 146.2 kB
  • After minification 108.1 kB
  • After compression 27.6 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. Idbz.co.zw needs all CSS files to be minified and compressed as it can save up to 118.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (63%)

Requests Now

84

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

idbz.co.zw

idbz.co.zw

258 ms

idbz.co.zw

idbz.co.zw

95 ms

system.base.css

system.base.css

1146 ms

system.menus.css

system.menus.css

1162 ms

system.messages.css

system.messages.css

1160 ms

system.theme.css

system.theme.css

1151 ms

jquery.ui.core.min.css

jquery.ui.core.min.css

1175 ms

jquery.ui.theme.min.css

jquery.ui.theme.min.css

1142 ms

jquery.ui.accordion.min.css

jquery.ui.accordion.min.css

1150 ms

aggregator.css

aggregator.css

2254 ms

comment.css

comment.css

2267 ms

date.css

date.css

2209 ms

datepicker.1.7.css

datepicker.1.7.css

2207 ms

date_repeat_field.css

date_repeat_field.css

1115 ms

field.css

field.css

2174 ms

node.css

node.css

1130 ms

search.css

search.css

2256 ms

user.css

user.css

3226 ms

views.css

views.css

3817 ms

ctools.css

ctools.css

3374 ms

lightbox.css

lightbox.css

3276 ms

flexslider_img.css

flexslider_img.css

3279 ms

flexslider.css

flexslider.css

3384 ms

nice_menus.css

nice_menus.css

4277 ms

nice_menus_default.css

nice_menus_default.css

4325 ms

mobile_navigation.css

mobile_navigation.css

4370 ms

responsive_menus_simple.css

responsive_menus_simple.css

4442 ms

addtoany.css

addtoany.css

4464 ms

alpha-reset.css

alpha-reset.css

3814 ms

alpha-mobile.css

alpha-mobile.css

4916 ms

alpha-alpha.css

alpha-alpha.css

5338 ms

formalize.css

formalize.css

5378 ms

omega-text.css

omega-text.css

5447 ms

omega-branding.css

omega-branding.css

5540 ms

omega-menu.css

omega-menu.css

5536 ms

omega-forms.css

omega-forms.css

4915 ms

omega-visuals.css

omega-visuals.css

6100 ms

widgets.js

widgets.js

132 ms

global.css

global.css

6657 ms

idbz-alpha-default.css

idbz-alpha-default.css

5354 ms

idbz-alpha-default-narrow.css

idbz-alpha-default-narrow.css

4356 ms

alpha-default-narrow-12.css

alpha-default-narrow-12.css

4351 ms

idbz-alpha-default-normal.css

idbz-alpha-default-normal.css

5408 ms

alpha-default-normal-12.css

alpha-default-normal-12.css

5509 ms

idbz-alpha-default-wide.css

idbz-alpha-default-wide.css

5488 ms

alpha-default-wide-12.css

alpha-default-wide-12.css

6116 ms

js_wKyFX46tVKJtPKN12qNjRfS4aubW4G2u7LK22vlDiKo.js

js_wKyFX46tVKJtPKN12qNjRfS4aubW4G2u7LK22vlDiKo.js

7438 ms

js_hS4dYTPGniGw07mAmET-ujCxLi1YH9Z-tB5BBR6t2g4.js

js_hS4dYTPGniGw07mAmET-ujCxLi1YH9Z-tB5BBR6t2g4.js

5390 ms

js_o0NmOA6FrOQamIKXP181IN2QejpF72PVBGsbUlh8LeY.js

js_o0NmOA6FrOQamIKXP181IN2QejpF72PVBGsbUlh8LeY.js

5430 ms

js_7GpLGoZEFnPsnKwbxxVkIAT3ZSSsLoljH71FePOyer0.js

js_7GpLGoZEFnPsnKwbxxVkIAT3ZSSsLoljH71FePOyer0.js

6030 ms

mobile_menu.js

mobile_menu.js

5766 ms

mobile_navigation.js

mobile_navigation.js

6180 ms

js_qtEap1FTgvPuDDwlSGKswqo6NixS1MB8El-HgNtWGXg.js

js_qtEap1FTgvPuDDwlSGKswqo6NixS1MB8El-HgNtWGXg.js

6375 ms

js_43n5FBy8pZxQHxPXkf-sQF7ZiacVZke14b0VlvSA554.js

js_43n5FBy8pZxQHxPXkf-sQF7ZiacVZke14b0VlvSA554.js

6402 ms

js_uTpGZRbRZm_lrt5640lI88hN-6jGIe3E3hxZcagIuss.js

js_uTpGZRbRZm_lrt5640lI88hN-6jGIe3E3hxZcagIuss.js

5991 ms

css

css

27 ms

analytics.js

analytics.js

15 ms

collect

collect

4 ms

collect

collect

24 ms

idbz-logo.png

idbz-logo.png

1067 ms

Index-2_10.png

Index-2_10.png

1068 ms

Index-2_08-12.png

Index-2_08-12.png

1071 ms

Index-2_12.png

Index-2_12.png

1075 ms

icon-lock.png

icon-lock.png

1064 ms

icon-search.png

icon-search.png

1804 ms

menu_arrow_down.png

menu_arrow_down.png

2714 ms

icon-menu.png

icon-menu.png

2140 ms

ndebele.jpg

ndebele.jpg

3171 ms

shona.jpg

shona.jpg

3160 ms

slider-idbz_0.jpg

slider-idbz_0.jpg

3284 ms

banner_0.jpg

banner_0.jpg

3636 ms

energy.png

energy.png

3191 ms

transport.png

transport.png

3768 ms

water.png

water.png

4270 ms

ict.png

ict.png

4228 ms

housing.png

housing.png

4284 ms

bullet.png

bullet.png

4366 ms

placeholder_0.png

placeholder_0.png

4689 ms

icon-plus.png

icon-plus.png

4820 ms

currencyconverter.png

currencyconverter.png

5283 ms

Papers.png

Papers.png

5596 ms

procurement.png

procurement.png

5339 ms

Financials.png

Financials.png

5751 ms

Bonds.png

Bonds.png

5761 ms

Publications.png

Publications.png

5887 ms

logo-footer.png

logo-footer.png

6547 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

13 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

46 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

47 ms

icon-caption-link.png

icon-caption-link.png

5814 ms

Accessibility Review

idbz.co.zw accessibility score

77

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

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

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

idbz.co.zw best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

idbz.co.zw SEO score

83

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

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

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 Idbz.co.zw 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 Idbz.co.zw 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

idbz.co.zw

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