8.2 sec in total
662 ms
7.2 sec
296 ms
Welcome to cdb.kz homepage info - get ready to check Cdb best content for Kazakhstan right away, or after learning these important things about cdb.kz
Центральный дом бухгалтера в Казахстане. Перейти на официальный сайт ЦДБ в Нур-Султане Алматы Астане и других городах РК.
Visit cdb.kzWe analyzed Cdb.kz page load time and found that the first response time was 662 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
cdb.kz performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value11.2 s
0/100
25%
Value12.3 s
3/100
10%
Value1,030 ms
26/100
30%
Value0.003
100/100
15%
Value26.8 s
0/100
10%
662 ms
1346 ms
523 ms
550 ms
540 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 68% of them (80 requests) were addressed to the original Cdb.kz, 4% (5 requests) were made to Cdn-ru.bitrix24.kz and 4% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Cdb.kz.
Page size can be reduced by 1.5 MB (61%)
2.5 MB
970.0 kB
In fact, the total size of Cdb.kz main page is 2.5 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 328.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. 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 328.9 kB or 77% of the original size.
Potential reduce by 1.1 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. Obviously, Cdb needs image optimization as it can save up to 1.1 MB or 74% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 22.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 68.2 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. Cdb.kz needs all CSS files to be minified and compressed as it can save up to 68.2 kB or 22% of the original size.
Number of requests can be reduced by 47 (49%)
95
48
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cdb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
cdb.kz
662 ms
cdb.kz
1346 ms
core.css
523 ms
styles.css
550 ms
style.css
540 ms
style.css
565 ms
style.css
565 ms
sprite.css
566 ms
modal-css.css
692 ms
style.css
712 ms
style.css
719 ms
style.css
725 ms
styles.css
729 ms
template_styles.css
730 ms
animate.min.css
862 ms
magnific-popup.min.css
884 ms
home.css
902 ms
core.js
1614 ms
core_fx.js
925 ms
jquery.min.js
1096 ms
foundation.min.js
1376 ms
slick.min.js
1059 ms
call.min.js
1077 ms
script.js
1087 ms
script.js
1232 ms
script.js
1254 ms
all.css
216 ms
slick.min.css
49 ms
slick-theme.min.css
59 ms
imask.es.min.js
1444 ms
what-input.js
930 ms
wow.min.js
1059 ms
jquery.magnific-popup.min.js
1086 ms
app.min.js
1111 ms
index.min.js
1198 ms
loader_3_hp1hts.js
1355 ms
loader_7_0jhs4y.js
1476 ms
ba.js
416 ms
gtm.js
210 ms
embed
261 ms
embed
264 ms
logo-white2.png
207 ms
sprite.png
447 ms
diler-map_.png
208 ms
12.png
206 ms
index-j.png
942 ms
informatsionnye-sistemy-i-protsessy-1024x768.jpg
399 ms
adult-learning3-small.jpg
357 ms
kons-ur.jpg
358 ms
1450404743_magazine-806073_1280.jpg
399 ms
b8a4a0085a1c63493d727f453fcaa9dd.png
943 ms
9e0181c86b068583d20b792b3c72a48b.png
716 ms
35eb59d9c975c00b2a22178ddccd8013.png
944 ms
107384c1de135764187bcb24cd62bdf9.png
1082 ms
c60fcc1b77edaeb86c2dbe111624ca27.png
738 ms
50c1d05993599b25a891be4134d1a011.png
942 ms
05d25a61cb94c5a54c9ef4c9f8c26c75.png
1382 ms
7a7359e660557158022938ece59581d0.png
1222 ms
694f874919acf8a6e3190890fa99e293.png
1054 ms
ef2a6d90710e1cc93d5fbf95e932853f.png
1074 ms
5895739d01bf83d5a99f661e7e2560d6.jpg
1092 ms
98ca06b7a85a6fc0fbc6bebe931ac7e6.png
1225 ms
f86a4d67e959c71f501dadd275007bf2.gif
1251 ms
24ff418f08c1c847fb8519744d0fc1dd.jpg
1379 ms
fe3f9ed9bd42af77bffdfc9af753e15e.jpg
1380 ms
b54dec3706c12ab2d1419bb8d70ef7b3.jpg
1432 ms
8c5e928162a615fbfbe59b77cadce16a.jpg
1433 ms
7cbeec279ab3e465a748c5792a4221a6.png
1579 ms
35d57845dcec5d437ae2760e01439f1b.jpg
1581 ms
fcc28043e68f98e61e054ac18ebaea1e.jpg
1581 ms
c971d2de7b90214522de308e43496d14.png
1581 ms
bcfe41beddf36ca1a03a61444fefd207.png
1581 ms
dc753c805115ce7cc56affce65776d2e.jpg
1580 ms
9c8ef509c6e48866c6759cfb205bbb7c.jpg
1716 ms
7a851b2ae3010420d53c641d7fdbcdb6.jpg
1718 ms
logo-white.png
1717 ms
Roboto-Bold.ttf
1911 ms
fa-solid-900.woff
152 ms
fa-regular-400.woff
213 ms
tag.js
796 ms
fa-brands-400.woff
288 ms
ajax-loader.gif
68 ms
Roboto-Bold.ttf
1582 ms
Roboto-Medium.ttf
1963 ms
Roboto-Medium.ttf
1687 ms
embed
268 ms
embed
305 ms
slick.woff
114 ms
analytics.js
74 ms
ajax_counter.php
1802 ms
bx_stat
201 ms
SF-Pro-Display-Bold.otf
2591 ms
SF-Pro-Display-Bold.otf
1519 ms
SF-Pro-Display-Medium.otf
1882 ms
SF-Pro-Display-Medium.otf
1688 ms
collect
8 ms
collect
36 ms
js
48 ms
ga-audiences
22 ms
gen_204
19 ms
init_embed.js
25 ms
Roboto-Regular.ttf
1543 ms
Roboto-Regular.ttf
1541 ms
SF-Pro-Display-Light.otf
1539 ms
SF-Pro-Display-Light.otf
1397 ms
advert.gif
840 ms
call.tracker.js
320 ms
styles.min.css
1830 ms
script.min.js
2240 ms
polyfill.js
287 ms
sync_cookie_image_decide
133 ms
app.js
320 ms
sync_cookie_image_decide
131 ms
app.bundle.min.css
544 ms
app.bundle.min.js
1072 ms
1
129 ms
upload-girl-mini-1.png
229 ms
cdb.kz accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
cdb.kz 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
Page has valid source maps
cdb.kz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cdb.kz can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Cdb.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.
cdb.kz
Open Graph description is not detected on the main page of Cdb. 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: