5.9 sec in total
919 ms
4.5 sec
479 ms
Visit uzreport.uz now to see the best up-to-date Uz Report content for Uzbekistan and also check out these interesting facts you probably never knew about uzreport.uz
Toshkent va O'zbekiston yangiliklari: bugungi yangiliklar, foto va video, eng muhim O'zbekiston yangiliklari UZREPORT TV va FUTBOL TV da.
Visit uzreport.uzWe analyzed Uzreport.uz page load time and found that the first response time was 919 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
uzreport.uz performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value16.8 s
0/100
25%
Value10.5 s
7/100
10%
Value1,550 ms
13/100
30%
Value0.445
21/100
15%
Value18.9 s
3/100
10%
919 ms
985 ms
907 ms
32 ms
826 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Uzreport.uz, 70% (49 requests) were made to Uzreport.news and 7% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Yandex.ru.
Page size can be reduced by 621.5 kB (32%)
1.9 MB
1.3 MB
In fact, the total size of Uzreport.uz main page is 1.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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 289.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 289.6 kB or 83% of the original size.
Potential reduce by 110.2 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. Uz Report images are well optimized though.
Potential reduce by 221.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 221.7 kB or 61% of the original size.
Number of requests can be reduced by 8 (13%)
61
53
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uz Report. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
uzreport.uz
919 ms
uzreport.uz
985 ms
uzreport.news
907 ms
css
32 ms
header-bidding.js
826 ms
uzreport.news.js
554 ms
context.js
1245 ms
adsbygoogle.js
389 ms
context.js
1186 ms
sidenav_ico_sprite.png
103 ms
id_uz.png
191 ms
uzr_agency_oz.png
364 ms
UzREROPT-tv.jpg
366 ms
xf.jpg
455 ms
b85c8062a9ec76dba70cda1c3aedc6dd.png
757 ms
3b0c1b22327b4916b94f90784a190b7f.jpeg
368 ms
fd99b013913cc895092eee9f21441a88.jpeg
278 ms
78705ffd19e0cc82f351ecb47cf160ea.jpeg
367 ms
a31a6e341b34de78a373e8499dcdf124.jpeg
451 ms
9ecaa1e91bd4bb021c75e7cb8331f595.jpeg
452 ms
b9fa922196594c7011e6b3a0152b8dfe.jpeg
454 ms
e2ec8be95453d2d3c9518607fa8b3516.jpeg
456 ms
5cddc0ffe4bbb8c7a9acaa48669cb9e1.jpeg
538 ms
fa39810b260301619b5f2547c94cad69.jpeg
540 ms
ececf8f7661a104b066e47ba9e666cba.jpeg
541 ms
f25c60ea19f3bfde821b329d5ec2e85f.jpeg
542 ms
ba6fe5dbcc9cbf849f0c5f58cae9de5b.jpeg
543 ms
e5390d85ee765b26539195cced470cc7.jpeg
626 ms
fa0d47b94363ad7037d16d21e0a9f4e6.jpeg
629 ms
0a19f2f2e96067c5b4d08109118c34b8.jpeg
627 ms
Reelvideo-94516%20(1).jpg
630 ms
%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202023-10-29%20%D0%B2%2015.45.35%20(1).png
631 ms
3a156fb722b5d44c9ce865cd0432086c.jpeg
803 ms
masico02.png
753 ms
KFOmCnqEu92Fr1Mu5mxP.ttf
26 ms
KFOlCnqEu92Fr1MmEU9fABc9.ttf
36 ms
KFOlCnqEu92Fr1MmSU5fABc9.ttf
46 ms
KFOlCnqEu92Fr1MmWUlfABc9.ttf
56 ms
KFOlCnqEu92Fr1MmYUtfABc9.ttf
57 ms
3_0_FFFFFFFF_EFEFEFFF_0_pageviews
567 ms
tag.js
820 ms
libs.min.js
983 ms
bee7ce79418f4dfe737210022ee4a325.jpeg
792 ms
cbb9cf69f7fce92d8f70eb4829f4c050.jpeg
792 ms
10358ebf4339c2fe1bf09e1890123af2.jpeg
901 ms
97d7bfbb6e993e03d38539484257381b.jpeg
796 ms
82916488d2bf9717277b2be0ce5fd378.jpeg
897 ms
13cd71861049e439171ea92f40334881.jpeg
898 ms
75596d27705bd135ea71c9f600d86792.jpeg
899 ms
69a4b1b9ab46db27103111123404608c.jpeg
902 ms
2411c638bc614e5653ea6ccfc3d10f04.jpeg
928 ms
899ad99eb4e50cd34e26b5bd40fd979d.jpeg
927 ms
f78505b1b0cc4e2471daedb7c77d95f1.jpeg
879 ms
fontawesome-webfont.woff
996 ms
ad0433f139dfc4a506096e47a5df0eb1.jpeg
707 ms
4f9f98c60445f5e89a09e76845fcf355.jpeg
822 ms
a1014658142d06bf3b6fbe3143f39f4b.jpeg
821 ms
ee10ebf662328d24604c356d47cab3c1.jpeg
820 ms
1f35bb0dcf269d4d71672c908a7aee8c.jpeg
820 ms
show_ads_impl.js
294 ms
b267f70a25121e2e5591e5127591e5f4.jpeg
737 ms
26fe297a56d4ab6b569929a26706b0a7.jpeg
738 ms
07c28584c8ca8b3be6de9f41089f073d.jpeg
736 ms
359188d9dc3baeead0932200e36bca65.jpeg
737 ms
footer-logo.png
735 ms
zrt_lookup.html
51 ms
ads
111 ms
ads.min.js
291 ms
advert.gif
343 ms
sync_cookie_image_decide
146 ms
uzreport.uz 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 IDs are not unique
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
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 valid value for its [lang] attribute.
uzreport.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
Missing source maps for large first-party JavaScript
uzreport.uz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
![]()
UZ
![]()
OZ
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uzreport.uz can be misinterpreted by Google and other search engines. Our service has detected that Uzbek is used on the page, and it does not match the claimed language. Our system also found out that Uzreport.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.
uzreport.uz
Open Graph data is detected on the main page of Uz Report. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: