16.7 sec in total
114 ms
16.2 sec
319 ms
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.zwWe analyzed Idbz.co.zw page load time and found that the first response time was 114 ms and then it took 16.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
idbz.co.zw performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value7.4 s
4/100
25%
Value13.3 s
2/100
10%
Value1,050 ms
25/100
30%
Value0.396
26/100
15%
Value16.2 s
5/100
10%
114 ms
57 ms
1039 ms
1066 ms
1078 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 88% of them (81 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.5 sec) belongs to the original domain Idbz.co.zw.
Page size can be reduced by 442.2 kB (27%)
1.6 MB
1.2 MB
In fact, the total size of Idbz.co.zw main page is 1.6 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 67.6 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 67.6 kB or 82% of the original size.
Potential reduce by 62.9 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.
Potential reduce by 198.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 198.7 kB or 70% of the original size.
Potential reduce by 113.0 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 113.0 kB or 81% of the original size.
Number of requests can be reduced by 52 (62%)
84
32
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 12 to 1 for JavaScripts and from 42 to 1 for CSS and as a result speed up the page load time.
idbz.co.zw
114 ms
idbz.co.zw
57 ms
system.base.css
1039 ms
system.menus.css
1066 ms
system.messages.css
1078 ms
system.theme.css
1066 ms
jquery.ui.core.min.css
1122 ms
jquery.ui.theme.min.css
1069 ms
jquery.ui.accordion.min.css
2082 ms
aggregator.css
2092 ms
comment.css
2090 ms
date_repeat_field.css
2106 ms
field.css
2107 ms
node.css
2155 ms
search.css
3130 ms
user.css
3125 ms
views.css
3128 ms
ctools.css
3132 ms
lightbox.css
3151 ms
flexslider_img.css
3205 ms
flexslider.css
4234 ms
nice_menus.css
4172 ms
nice_menus_default.css
4162 ms
mobile_navigation.css
4171 ms
responsive_menus_simple.css
4182 ms
addtoany.css
4265 ms
alpha-reset.css
5201 ms
alpha-mobile.css
5202 ms
alpha-alpha.css
5222 ms
formalize.css
5213 ms
omega-text.css
5266 ms
omega-branding.css
5298 ms
omega-menu.css
6226 ms
omega-forms.css
6249 ms
omega-visuals.css
6242 ms
global.css
6561 ms
idbz-alpha-default.css
6297 ms
embed-lite.min.js
80 ms
idbz-alpha-default-narrow.css
6331 ms
alpha-default-narrow-12.css
6237 ms
idbz-alpha-default-normal.css
6240 ms
alpha-default-normal-12.css
6243 ms
idbz-alpha-default-wide.css
6268 ms
alpha-default-wide-12.css
6310 ms
js_Pt6OpwTd6jcHLRIjrE-eSPLWMxWDkcyYrPTIrXDSON0.js
7250 ms
js_hS4dYTPGniGw07mAmET-ujCxLi1YH9Z-tB5BBR6t2g4.js
6481 ms
js_o0NmOA6FrOQamIKXP181IN2QejpF72PVBGsbUlh8LeY.js
6260 ms
js_7GpLGoZEFnPsnKwbxxVkIAT3ZSSsLoljH71FePOyer0.js
6777 ms
mobile_menu.js
6523 ms
mobile_navigation.js
6331 ms
js_qtEap1FTgvPuDDwlSGKswqo6NixS1MB8El-HgNtWGXg.js
7506 ms
js_43n5FBy8pZxQHxPXkf-sQF7ZiacVZke14b0VlvSA554.js
6277 ms
js_uTpGZRbRZm_lrt5640lI88hN-6jGIe3E3hxZcagIuss.js
6362 ms
css
31 ms
analytics.js
142 ms
idbz-logo.png
1033 ms
Index-2_10.png
1090 ms
Index-2_08-12.png
1091 ms
Index-2_12.png
1036 ms
icon-lock.png
1048 ms
icon-search.png
1052 ms
menu_arrow_down.png
2317 ms
icon-menu.png
2073 ms
ussp.jpg
3402 ms
slider-image.jpg
3192 ms
slider-idbz_0.jpg
2931 ms
sustaining.jpg
2912 ms
energy.png
3177 ms
transport.png
3387 ms
water.png
3998 ms
housing.png
4001 ms
bullet.png
4205 ms
placeholder_0.png
4224 ms
icon-plus.png
4418 ms
housing_0.png
4475 ms
currencyconverter.png
5070 ms
Papers.png
5344 ms
gold-coins.png
5494 ms
procurement.png
5255 ms
Financials.png
5499 ms
Bonds.png
5575 ms
Publications.png
6142 ms
logo-footer.png
6307 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
95 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
122 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
146 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
147 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
147 ms
icon-caption-link.png
6264 ms
collect
56 ms
collect
82 ms
js
76 ms
idbz.co.zw accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
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.
idbz.co.zw 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
idbz.co.zw 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 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.
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: