Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

kdb.kz

Официальный сайт АО «Банк Развития Казахстана» | АО «Банк Развития Казахстана»

Page Load Speed

11.8 sec in total

First Response

1 sec

Resources Loaded

10.6 sec

Page Rendered

233 ms

kdb.kz screenshot

About Website

Welcome to kdb.kz homepage info - get ready to check Kdb best content for Kazakhstan right away, or after learning these important things about kdb.kz

Банк развития Казахстана (БРК) - это государственный банк, осуществляющий средне- и долгосрочное финансирование проектов в сфере обрабатывающей промышленности. Банк содействует устойчивому развитию на...

Visit kdb.kz

Key Findings

We analyzed Kdb.kz page load time and found that the first response time was 1 sec and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster. This domain responded with an error, which can significantly jeopardize Kdb.kz rating and web reputation

Performance Metrics

kdb.kz performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

Network Requests Diagram

kdb.kz

1026 ms

2221 ms

style.css

446 ms

jquery.min.js

891 ms

modernizr-2.5.3.min.js

456 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 86% of them (114 requests) were addressed to the original Kdb.kz, 5% (6 requests) were made to Mc.yandex.ru and 5% (6 requests) were made to Static.cloudim.ru. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Kdb.kz.

Page Optimization Overview & Recommendations

Page size can be reduced by 673.5 kB (13%)

Content Size

5.3 MB

After Optimization

4.6 MB

In fact, the total size of Kdb.kz main page is 5.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. 65% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 67.0 kB

  • Original 79.0 kB
  • After minification 65.9 kB
  • After compression 11.9 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 13.1 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 67.0 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 87.6 kB

  • Original 4.5 MB
  • After minification 4.4 MB

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. Kdb images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 421.5 kB

  • Original 606.9 kB
  • After minification 590.0 kB
  • After compression 185.4 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 421.5 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 97.4 kB

  • Original 119.1 kB
  • After minification 108.6 kB
  • After compression 21.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. Kdb.kz needs all CSS files to be minified and compressed as it can save up to 97.4 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

124

After Optimization

71

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

Accessibility Review

kdb.kz accessibility score

67

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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.

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

kdb.kz best practices score

75

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

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

kdb.kz SEO score

89

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    KK

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kdb.kz can be misinterpreted by Google and other search engines. Our service has detected that Kazakh is used on the page, and it does not match the claimed Russian language. Our system also found out that Kdb.kz 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 Kdb. 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: