11.1 sec in total
757 ms
10 sec
375 ms
Click here to check amazing Mtrk content for Uzbekistan. Otherwise, check out these important facts you probably never knew about mtrk.uz
O`zbekiston milliy teleradiokompaniyasi
Visit mtrk.uzWe analyzed Mtrk.uz page load time and found that the first response time was 757 ms and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
mtrk.uz performance score
name
value
score
weighting
Value11.1 s
0/100
10%
Value12.2 s
0/100
25%
Value18.0 s
0/100
10%
Value3,720 ms
1/100
30%
Value0.6
11/100
15%
Value17.7 s
4/100
10%
757 ms
568 ms
908 ms
551 ms
930 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 96% of them (150 requests) were addressed to the original Mtrk.uz, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Vk.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Mtrk.uz.
Page size can be reduced by 782.8 kB (22%)
3.6 MB
2.8 MB
In fact, the total size of Mtrk.uz main page is 3.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. 50% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 68.4 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 9.7 kB, which is 13% 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 68.4 kB or 88% of the original size.
Potential reduce by 238.9 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. Mtrk images are well optimized though.
Potential reduce by 333.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 333.2 kB or 67% of the original size.
Potential reduce by 142.3 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. Mtrk.uz needs all CSS files to be minified and compressed as it can save up to 142.3 kB or 86% of the original size.
Number of requests can be reduced by 35 (24%)
146
111
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mtrk. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
mtrk.uz
757 ms
568 ms
jquery.min.js
908 ms
bootstrap.min.js
551 ms
bootstrap.css
930 ms
font-awesome.css
557 ms
jquery.flexslider-min.js
567 ms
flexslider.css
553 ms
share.js
254 ms
odkl_share.css
192 ms
odkl_share.js
318 ms
flexy.css
739 ms
main.css
930 ms
dojo.xd.js
1317 ms
back.js
923 ms
tools.js
929 ms
menuTree.js
1082 ms
menuTree.css
1098 ms
jwplayer.js
1104 ms
odkl_share.css
921 ms
odkl_share.js
320 ms
parser.xd.js
199 ms
easing.xd.js
197 ms
fx.xd.js
195 ms
dijit.xd.js
383 ms
scroll.xd.js
184 ms
_base.xd.js
196 ms
ContentPane.xd.js
368 ms
star_1.png
202 ms
ornament.png
3840 ms
bg-lines.png
1662 ms
logotype.png
943 ms
buttons-top.png
371 ms
lang-split.png
542 ms
sticker.png
557 ms
playtv.png
561 ms
uzbekistan.png
1262 ms
bg-dots.png
746 ms
yoshlarr.png
1319 ms
sportt.png
930 ms
tashkentt.png
1117 ms
madaniyatt.png
1130 ms
dunyoo.png
1304 ms
bolajonn.png
1320 ms
navoo.png
1619 ms
diyor.png
1491 ms
oilaviy.png
1508 ms
kinoteatr.png
1510 ms
uzhdd.png
1678 ms
mahalla.png
1883 ms
uzbekistan.png
1700 ms
yoshlarr.png
1978 ms
tashkentt.png
1845 ms
mahalla.png
2047 ms
Andijon.png
1891 ms
Buxoro.png
2031 ms
Jizzax.png
2071 ms
up_arrow.png
368 ms
star_2.png
371 ms
star_3.png
381 ms
down_arrow.png
379 ms
star_4.png
381 ms
star_5.png
382 ms
Qoraqalpogiston.png
2062 ms
cnt.png
628 ms
analytics.js
22 ms
collect
14 ms
cuprum.woff
2341 ms
pfdintextpro-regular.woff
2039 ms
pfdintextpro-medium.woff
2061 ms
pfdintextpro-thin.woff
2112 ms
fontawesome-webfont.woff
2266 ms
star_1.png
2212 ms
up_arrow.png
2054 ms
star_2.png
2081 ms
down_arrow.png
2234 ms
star_3.png
2244 ms
star_4.png
2258 ms
star_5.png
2268 ms
_core.xd.js
1778 ms
_base.xd.js
1860 ms
stamp.xd.js
1694 ms
html.xd.js
1698 ms
_Widget.xd.js
1580 ms
_Contained.xd.js
1585 ms
_LayoutWidget.xd.js
1667 ms
string.xd.js
1677 ms
loading.xd.js
1526 ms
Qashqadaryo.png
1524 ms
Navoi.png
1559 ms
Namangan.png
1552 ms
Samarqand.png
1527 ms
Sirdaryo.png
1529 ms
Surxondaryo.png
1523 ms
Fargona.png
1404 ms
Xorazm.png
1475 ms
000000002584.jpg
2043 ms
000000002559.jpg
1790 ms
000000002541.jpg
1571 ms
000000002565.jpg
2459 ms
000000002561.jpg
1481 ms
000000002498.jpg
1661 ms
000000015296.jpg
1550 ms
000000015293.jpg
1637 ms
000000015295.jpg
1649 ms
000000015291.jpg
1574 ms
000000015290.jpg
1598 ms
000000015285.jpg
1664 ms
000000015284.jpg
1636 ms
000000015294.jpg
1597 ms
000000015283.jpg
1560 ms
000000015282.jpg
1580 ms
000000015288.jpg
1667 ms
000000015289.jpg
1660 ms
000000015281.jpg
1625 ms
fx.xd.js
1566 ms
000000015280.jpg
1580 ms
000000015277.jpg
1666 ms
000000015292.jpg
1658 ms
000000015286.jpg
1634 ms
000000015287.jpg
1569 ms
000000015279.jpg
1575 ms
000000015278.jpg
1665 ms
000000015276.jpg
1653 ms
000000015275.jpg
1619 ms
000000015274.jpg
1540 ms
000000015273.jpg
1560 ms
000000015272.jpg
1555 ms
000000015271.jpg
1650 ms
000000015269.jpg
1626 ms
000000015270.jpg
1510 ms
000000015268.jpg
1348 ms
000000015267.jpg
1333 ms
000000015266.jpg
1201 ms
000000015265.jpg
1282 ms
000000015263.jpg
1264 ms
000000015262.jpg
1225 ms
000000015261.jpg
1155 ms
000000015260.jpg
1193 ms
000000015259.jpg
1174 ms
000000015258.jpg
1244 ms
000000015257.jpg
1220 ms
000000015256.jpg
1128 ms
partner-malay.png
1158 ms
partner-uznet.png
1171 ms
uzinfocom1.png
1138 ms
partner-canon.png
1205 ms
partner-govuz3.png
1119 ms
bg_direction_nav.png
1119 ms
top5.png
1130 ms
Toggler.xd.js
1133 ms
bg.png
1301 ms
invate.png
1095 ms
bg-ornament.jpg
1684 ms
button-slider.png
1113 ms
blank.gif
190 ms
connect.js
632 ms
mtrk.uz accessibility score
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.
mtrk.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
mtrk.uz 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
UZ
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mtrk.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 Russian language. Our system also found out that Mtrk.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.
mtrk.uz
Open Graph description is not detected on the main page of Mtrk. 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: