9.9 sec in total
610 ms
8.4 sec
873 ms
Visit kun.uz now to see the best up-to-date Kun content for Uzbekistan and also check out these interesting facts you probably never knew about kun.uz
O‘zbekistonda va dunyoda ro‘y berayotgan eng so‘nggi yangiliklar va xabarlar, jamiyat, iqtisodiyot, madaniyat, sport, tenologiyalarga oid qiziqarli maqolalar. Mashhurlar bilan intervyular, barchasi KU...
Visit kun.uzWe analyzed Kun.uz page load time and found that the first response time was 610 ms and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
kun.uz performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value18.1 s
0/100
25%
Value14.6 s
1/100
10%
Value490 ms
59/100
30%
Value0.131
81/100
15%
Value15.6 s
6/100
10%
610 ms
964 ms
543 ms
2539 ms
550 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 49% of them (43 requests) were addressed to the original Kun.uz, 45% (39 requests) were made to Storage.kun.uz and 2% (2 requests) were made to Yandex.ru. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Storage.kun.uz.
Page size can be reduced by 840.8 kB (17%)
4.9 MB
4.1 MB
In fact, the total size of Kun.uz main page is 4.9 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. 55% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.
Potential reduce by 36.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 36.6 kB or 76% of the original size.
Potential reduce by 154.0 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. Kun images are well optimized though.
Potential reduce by 0 B
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 650.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. Kun.uz needs all CSS files to be minified and compressed as it can save up to 650.2 kB or 96% of the original size.
Number of requests can be reduced by 20 (27%)
74
54
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kun. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
kun.uz
610 ms
kun.uz
964 ms
vendor.css
543 ms
style.css
2539 ms
fonts.css
550 ms
js
59 ms
jquery.min.js
1104 ms
app.js
1843 ms
context.js
982 ms
context.js
927 ms
6mkkM3WVc6Dbm86BpVGZVdOVS7j2rimq_medium.jpg
2215 ms
VVwHv5hIqx3_z5lUW4o0g0WFGsv8GyPB_medium.jpg
1870 ms
Vo6d5shXFnIuNb1OUcCX6Ts9W8rv0F4g_medium.jpg
1742 ms
OtvrVzk6LE3r_wurWMNUtjh1f_HFbXOF_medium.jpg
1529 ms
okAsF--yqFzkUXSvhL36mEtvLd0lXt1n_medium.jpg
1714 ms
fNwd06Z9EPRB4b8g32JZFU8hWD834cUL_medium.jpg
1723 ms
ucxAfV5SJXGdlfdOOx7TS2TlEtNbBLSr_medium.jpg
2227 ms
fjM1g90eeNhsvMMctQrRNwgVFk_xhW1K_medium.jpg
2266 ms
kun-uz-logo.svg
183 ms
18plus-v2.svg
189 ms
social-youtube.svg
188 ms
social-telegram.svg
185 ms
social-facebook.svg
187 ms
social-twitter.svg
365 ms
social-instagram.svg
401 ms
social-rss.svg
403 ms
watch.js
0 ms
search-icon.svg
369 ms
toggle-circle-v2.svg
366 ms
new-search-icon.svg
511 ms
calendar.svg
566 ms
silver-arrow-right.svg
567 ms
Montserrat-Regular.woff
1430 ms
Montserrat-Light.woff
707 ms
Montserrat-Medium.woff
1270 ms
Montserrat-SemiBold.woff
1381 ms
Montserrat-Bold.woff
1318 ms
cd-top-arrow.svg
711 ms
list
847 ms
main
866 ms
list
1044 ms
list
1057 ms
list
1242 ms
list
1259 ms
list
1413 ms
ads.min.js
288 ms
h7vmz9AJPGgTlb_CSVCizNXXPQ3O8dRn_medium.jpg
1308 ms
MOEteWdFK71abaQatCai6WgQ7xu_fsL1_medium.jpg
1316 ms
TCMtpv-lYbHiuOc9y5Ufwm1XciSlHYzC_medium.jpg
1630 ms
9iLAdrnuKKtRW2gAk19MIY66zP4kw5Wa_medium.jpg
1788 ms
QpT1VTeT3Xc7B8XeSFFMfk_8QnjYlEbw_medium.jpg
1631 ms
f9qx0pZC14Mtn-DzgiRJzz3Eq9KowkF9_medium.jpg
1647 ms
d1WZhS2F2PaOunYjCXHU8xyJCc4Ae8Gt_medium.jpg
1846 ms
ZWA4b16peov4m6CRK9tzKRsBAELt3UMl_medium.jpg
1661 ms
_5D3NbxUQc-O665cOnw-HA3a9eclqkW6_medium.jpg
1968 ms
6nCmzvfmiMmmbO5K8au3AKrZLMcko2nI_medium.jpeg
1793 ms
5-HmjvXQ2U0rNSiPgpF9OjYBpf39oG6h_medium.jpg
1836 ms
h-FhlTACajE9M3UF4BkWxZ5i-V-htGtp_medium.jpg
1845 ms
blue-right-arrow.svg
372 ms
CiX5B8726Vn6FbgbpaLEu-zdDsqU1sSs_medium.jpg
1940 ms
eiOT1M4Nel4ZnknpO4AHg7HjYWUH2xG1_medium.jpg
1970 ms
njKHZ0T57lEXwBc37XBDgdJhISCTTdmz_medium.jpg
2024 ms
NP9RzCMukZyQAzdN9tCrS36munswB2-t_medium.jpg
2502 ms
okO6e3IUG_FmXbtzVdKSimFZZfYSwi7A_medium.jpg
2191 ms
KnUM1GKbXJKS-6-WrsrKNlVs_pE2rEJQ_medium.jpg
2376 ms
1Teh4T6uzenSUQETN-YctGj5CrKd7ziW_medium.jpg
1926 ms
nap2e2MD_zlD4V4S18M13YulOiNWpa16_medium.jpg
2141 ms
4F1-P5dKmnG3tigmwt59vu9qrv2I8H4i_medium.jpg
2197 ms
BzPn0DHhSBIemnbBT9Fm48br0-EgNUwV_medium.jpg
2287 ms
pEd8tc2EkkrEc9PNFObhHuNMfx8TxhWp_medium.jpg
2362 ms
JmIFr1ksVcubx_o0DkLn8CxeSyJRI34F_medium.jpg
2510 ms
O1yq1VD1RoAm2Je78MQCPs5Tar9QDDci_medium.jpg
2541 ms
9yI2IVB0Jtunc8ajMagJTnc6VIGx0gAY_medium.jpg
2568 ms
down-arrow.svg
186 ms
sijv2LOjVRuyi_LQw2oFBlKdoXrvpYLA_medium.jpg
2645 ms
4r45dNNnSZ_YmQ_hWBTJ5ywCfsK9fGo__medium.jpg
2844 ms
play-video-v3.svg
189 ms
play-video.svg
249 ms
DINPro-Bold.woff
1201 ms
DINPro-Black.woff
519 ms
DINPro-Medium.woff
1238 ms
DINPro.woff
728 ms
DINPro-Light.woff
1104 ms
AibjJ-F74ZVlikwjMieTf5kI7UTVjsdN_medium.jpg
2572 ms
play-image.svg
275 ms
5-PRMQjqdH803w621BBzaMNz6GRIy0m3_medium.jpg
2544 ms
MwVYmZLBbBQRluJYLWyjAYjHLqLr7bVN_medium.jpg
2380 ms
kun.uz 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
kun.uz 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
kun.uz SEO score
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
UZ
UZ
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kun.uz can be misinterpreted by Google and other search engines. Our service has detected that Uzbek is used on the page, and it matches the claimed language. Our system also found out that Kun.uz 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.
kun.uz
Open Graph data is detected on the main page of Kun. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: