44.3 sec in total
2.2 sec
41.7 sec
450 ms
Click here to check amazing Uzavtosanoat content for Uzbekistan. Otherwise, check out these important facts you probably never knew about uzavtosanoat.uz
UzAuto Sanoat
Visit uzavtosanoat.uzWe analyzed Uzavtosanoat.uz page load time and found that the first response time was 2.2 sec and then it took 42.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
uzavtosanoat.uz performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value25.6 s
0/100
25%
Value45.4 s
0/100
10%
Value570 ms
52/100
30%
Value0.199
62/100
15%
Value18.8 s
3/100
10%
2162 ms
102 ms
1293 ms
578 ms
1692 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 92% of them (113 requests) were addressed to the original Uzavtosanoat.uz, 2% (2 requests) were made to Bs.yandex.ru and 2% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Uzavtosanoat.uz.
Page size can be reduced by 984.5 kB (14%)
7.1 MB
6.1 MB
In fact, the total size of Uzavtosanoat.uz main page is 7.1 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. 40% of websites need less resources to load. Images take 6.1 MB which makes up the majority of the site volume.
Potential reduce by 42.5 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 42.5 kB or 77% of the original size.
Potential reduce by 142.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. Uzavtosanoat images are well optimized though.
Potential reduce by 533.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 533.7 kB or 81% of the original size.
Potential reduce by 265.5 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. Uzavtosanoat.uz needs all CSS files to be minified and compressed as it can save up to 265.5 kB or 88% of the original size.
Number of requests can be reduced by 42 (36%)
118
76
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uzavtosanoat. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
uzavtosanoat.uz
2162 ms
css
102 ms
bootstrap.min.css
1293 ms
bootstrap-yii.css
578 ms
style.css
1692 ms
jquery.selectBox.css
584 ms
jquery.rating.css
582 ms
speaker.css
693 ms
fonts.css
783 ms
jquery.js
5106 ms
bootstrap.js
3478 ms
embed.js
1546 ms
orphus.js
704 ms
jquery.carouFredSel-6.0.4-packed.js
1040 ms
placeholder.js
1071 ms
jquery.jcarousel.min.js
1283 ms
selectivizr.js
1312 ms
plugins.js
1340 ms
modernizr-2.5.3.min.js
1480 ms
jquery.selectBox.js
1722 ms
jquery_cookie.js
1540 ms
jquery.queryloader2.min.js
1559 ms
imgloader.js
1689 ms
print.js
1743 ms
scriptbreaker-multiple-accordion-1.js
1788 ms
jquery.rating-2.0.min.js
1947 ms
jquery.rating-2.0.js
2473 ms
ajax.js
1982 ms
mediaelement-and-player.js
3518 ms
jQueryRotate.js
2188 ms
speaker.js
2208 ms
bases.css
1229 ms
3_1_FFFFFFFF_EFEFEFFF_0_pageviews
282 ms
bg6.png
10893 ms
logo.png
240 ms
03%20%D0%9A%D0%90%D0%A2%D0%90%D0%9B%D0%9E%D0%93%20%D0%94%D0%96%D0%98%D0%97%D0%90%D0%9A%D0%A1%D0%9A%D0%98%D0%99%20%D0%90%D0%9A%D0%9A%D0%A3%D0%9C%D0%A3%D0%9B%D0%AF%D0%A2%D0%9E%D0%A0%D0%9D%D0%AB%D0%99%20%D0%97%D0%90%D0%92%D0%9E%D0%94%20%D0%BE%D1%82%2007%2009%202015_2.jpg
858 ms
banner3_1.png
4623 ms
banner4_1.png
18133 ms
banner2_1.png
16794 ms
5_1.png
14642 ms
banner1_1.png
7852 ms
banner6_1.png
11092 ms
ff_1.jpg
11220 ms
12_2.png
11187 ms
u9_1.png
11539 ms
13_5.png
11413 ms
u8.png
13245 ms
11_1.png
12125 ms
u7.png
12401 ms
orf.png
13007 ms
QqaAnClHwz
230 ms
t-bg.png
12589 ms
icon6.png
12807 ms
bg_8.png
13020 ms
icon2.png
13418 ms
lupa.png
13667 ms
rss1.png
14080 ms
printer.png
15214 ms
disketa.png
13904 ms
ser.png
14119 ms
header-bg.png
14292 ms
bor.png
14328 ms
ovoz1.png
14511 ms
bg_9_new.png
14542 ms
Photo-Video-Camera-icon.png
14727 ms
City-No-Camera-icon.png
14757 ms
nex.png
14829 ms
bg_l.png
14955 ms
kal1.png
14970 ms
bl-arrow.png
15054 ms
hit
305 ms
watch.js
1 ms
cnt.png
1646 ms
widget_ru_RU.js
233 ms
7131335.woff
15842 ms
hit
265 ms
3_1_FFFFFFFF_EFEFEFFF_0_pageviews
116 ms
cnt.png
1264 ms
bor4.png
14403 ms
h-bg.png
10725 ms
flag.png
10347 ms
bor5.png
5858 ms
icon4.png
4577 ms
speaker32.png
5412 ms
bg-li.png
5125 ms
scroll2.png
5134 ms
bg6.png
19799 ms
logo.png
4945 ms
t-bg.png
4570 ms
logo.png
4394 ms
icon6.png
5315 ms
bg_8.png
5023 ms
icon2.png
4976 ms
lupa.png
5001 ms
rss1.png
4793 ms
printer.png
4634 ms
disketa.png
4436 ms
ser.png
4298 ms
header-bg.png
4306 ms
bg-li.png
4142 ms
bor.png
4180 ms
ovoz1.png
4036 ms
bg_9_new.png
4044 ms
Photo-Video-Camera-icon.png
4044 ms
City-No-Camera-icon.png
3921 ms
03%20%D0%9A%D0%90%D0%A2%D0%90%D0%9B%D0%9E%D0%93%20%D0%94%D0%96%D0%98%D0%97%D0%90%D0%9A%D0%A1%D0%9A%D0%98%D0%99%20%D0%90%D0%9A%D0%9A%D0%A3%D0%9C%D0%A3%D0%9B%D0%AF%D0%A2%D0%9E%D0%A0%D0%9D%D0%AB%D0%99%20%D0%97%D0%90%D0%92%D0%9E%D0%94%20%D0%BE%D1%82%2007%2009%202015_2.jpg
4457 ms
banner3_1.png
16195 ms
banner4_1.png
19842 ms
banner2_1.png
12680 ms
5_1.png
19049 ms
banner1_1.png
7888 ms
banner6_1.png
12192 ms
ff_1.jpg
12580 ms
nex.png
12275 ms
bg_l.png
12042 ms
bor4.png
11848 ms
h-bg.png
11869 ms
orf.png
11838 ms
flag.png
14084 ms
bor5.png
11867 ms
icon4.png
12503 ms
scroll2.png
12676 ms
speaker32.png
12864 ms
uzavtosanoat.uz accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
uzavtosanoat.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
Displays images with incorrect aspect ratio
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
uzavtosanoat.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
UZ
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uzavtosanoat.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 Uzavtosanoat.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.
uzavtosanoat.uz
Open Graph description is not detected on the main page of Uzavtosanoat. 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: