6.9 sec in total
557 ms
6 sec
318 ms
Visit kdds.ru now to see the best up-to-date Kdds content for Russia and also check out these interesting facts you probably never knew about kdds.ru
Оборудование для сетей связи от компании КДДС.
Visit kdds.ruWe analyzed Kdds.ru page load time and found that the first response time was 557 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
kdds.ru performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value8.4 s
2/100
25%
Value9.7 s
11/100
10%
Value90 ms
99/100
30%
Value0.004
100/100
15%
Value8.1 s
41/100
10%
557 ms
1362 ms
283 ms
36 ms
416 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 69% of them (74 requests) were addressed to the original Kdds.ru, 10% (11 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Kdds.ru.
Page size can be reduced by 751.8 kB (47%)
1.6 MB
847.1 kB
In fact, the total size of Kdds.ru 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. 70% of websites need less resources to load. Javascripts take 645.6 kB which makes up the majority of the site volume.
Potential reduce by 562.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. This page needs HTML code to be minified as it can gain 171.9 kB, which is 27% 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 562.1 kB or 88% of the original size.
Potential reduce by 1.8 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, Kdds needs image optimization as it can save up to 1.8 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 103.2 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 103.2 kB or 16% of the original size.
Potential reduce by 84.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. Kdds.ru needs all CSS files to be minified and compressed as it can save up to 84.7 kB or 28% of the original size.
Number of requests can be reduced by 73 (83%)
88
15
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kdds. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
kdds.ru
557 ms
kdds.ru
1362 ms
intranet-common.min.css
283 ms
css
36 ms
ui.design-tokens.min.css
416 ms
ui.font.opensans.min.css
417 ms
main.popup.bundle.min.css
423 ms
window.css
426 ms
bootstrap.min.css
567 ms
jquery.fancybox.min.css
425 ms
styles.css
691 ms
animation_ext.css
553 ms
footable.standalone.min.css
563 ms
blocks.min.css
565 ms
ajax.min.css
570 ms
new-detail.css
697 ms
slick.css
703 ms
slick-theme.css
705 ms
jquery.mCustomScrollbar.min.css
705 ms
style.min.css
707 ms
styles.min.css
826 ms
template_styles.css
1241 ms
media.min.css
845 ms
font-awesome.min.css
855 ms
print.min.css
856 ms
theme.css
857 ms
bgcolors.min.css
961 ms
width-3.min.css
985 ms
font-1.min.css
985 ms
custom.css
985 ms
core.min.js
1129 ms
kernel_main_v1.js
1237 ms
dexie3.bundle.min.js
1285 ms
core_ls.min.js
1128 ms
core_frame_cache.min.js
1128 ms
protobuf.min.js
1295 ms
model.min.js
1294 ms
rest.client.min.js
1293 ms
init.js
798 ms
pull.client.min.js
1242 ms
jquery-2.2.4.min.js
1104 ms
ajax.min.js
1003 ms
main.popup.bundle.min.js
1007 ms
cphttprequest.min.js
999 ms
currency-core.bundle.min.js
1001 ms
core_currency.min.js
1097 ms
error.js
971 ms
template_01d6d2d3016c0629e2ed248bcbef98c0_v1.js
1420 ms
default_cfe2cdb4dc2a63c43da6e9b091154c66_v1.js
1011 ms
setTheme.php
1047 ms
jquery.maskedinput-1.2.2.min.js
1004 ms
ba.js
521 ms
analytics.js
85 ms
gtm.js
297 ms
%D0%BB%D0%BE%D0%B3%D0%BE%20%D0%9A%D0%94%D0%94%D0%A1.svg
297 ms
init
1187 ms
script.js
845 ms
Marker.svg
281 ms
next.svg
282 ms
Phone_black.svg
281 ms
Search_gray_sm.svg
280 ms
burger_black.svg
251 ms
Search_black_sm.svg
404 ms
opensans-regular.woff
531 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4taVQ.woff
92 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4taVQ.woff
245 ms
opensans-light.woff
490 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4taVQ.woff
257 ms
opensans-semibold.woff
405 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4taVQ.woff
333 ms
opensans-bold.woff
601 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4taVQ.woff
333 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4taVQ.woff
333 ms
fontawesome-webfont.woff
697 ms
call.tracker.js
902 ms
mango.js
974 ms
ec.js
194 ms
pl3.gif
509 ms
sl-arrow-icon.png
509 ms
icons_wish.svg
553 ms
ai.svg
555 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV0exg.woff
220 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV0exg.woff
219 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV0exg.woff
287 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV0exg.woff
286 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV0exg.woff
286 ms
mail_xlg.png
681 ms
vk_icon.svg
680 ms
ytb_new_icon.svg
678 ms
ok.svg
679 ms
watch.js
7 ms
Close_mask.svg
595 ms
waiter.gif
670 ms
Basket_white.svg
732 ms
Wishlist_white.svg
729 ms
Comparison_white.svg
730 ms
code.js
840 ms
collect
111 ms
collect
176 ms
js
175 ms
bx_stat
220 ms
openapi.318ba3d5a50b8d6990cb0284cb0e0963.js
231 ms
ga-audiences
64 ms
rtrg
128 ms
sync-loader.js
763 ms
counter
128 ms
dyn-goal-config.js
220 ms
addVisit
850 ms
kdds.ru 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
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.
kdds.ru 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
kdds.ru SEO score
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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kdds.ru 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 Kdds.ru 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.
kdds.ru
Open Graph data is detected on the main page of Kdds. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: