7.6 sec in total
1.4 sec
5.9 sec
210 ms
Click here to check amazing Supcourt content for Uzbekistan. Otherwise, check out these important facts you probably never knew about supcourt.uz
Visit supcourt.uzWe analyzed Supcourt.uz page load time and found that the first response time was 1.4 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
supcourt.uz performance score
name
value
score
weighting
Value12.8 s
0/100
10%
Value37.7 s
0/100
25%
Value18.9 s
0/100
10%
Value810 ms
36/100
30%
Value0.034
100/100
15%
Value19.7 s
2/100
10%
1408 ms
208 ms
377 ms
387 ms
389 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 99% of them (77 requests) were addressed to the original Supcourt.uz, 1% (1 request) were made to Www.uz. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Supcourt.uz.
Page size can be reduced by 670.8 kB (55%)
1.2 MB
556.1 kB
In fact, the total size of Supcourt.uz main page is 1.2 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. 45% of websites need less resources to load. Images take 532.0 kB which makes up the majority of the site volume.
Potential reduce by 45.0 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 11.2 kB, which is 21% 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 45.0 kB or 83% of the original size.
Potential reduce by 98.4 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, Supcourt needs image optimization as it can save up to 98.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 388.3 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 388.3 kB or 82% of the original size.
Potential reduce by 139.1 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. Supcourt.uz needs all CSS files to be minified and compressed as it can save up to 139.1 kB or 83% of the original size.
Number of requests can be reduced by 22 (31%)
71
49
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Supcourt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
supcourt.uz
1408 ms
jquery.fancybox.css
208 ms
font-awesome.min.css
377 ms
jquery.formstyler.css
387 ms
jquery-ui.css
389 ms
fonts.css
391 ms
forms.css
403 ms
additional.css
406 ms
style.css
565 ms
jquery.js
1160 ms
jquery-ui.min.js
578 ms
jquery.cookie.js
604 ms
transform.js
608 ms
jquery.hoverIntent.js
609 ms
jquery.formstyler.min.js
753 ms
jquery.easytabs.js
771 ms
jcarousellite.js
799 ms
jquery.selection.js
807 ms
jquery.fancybox.js
809 ms
funcs.js
936 ms
textZoom.js
960 ms
aside.js
990 ms
scripts.js
1005 ms
narrator.js
1005 ms
datepicker.js
1118 ms
home.png
192 ms
fast-nav-hover.png
188 ms
site-map.png
181 ms
mail.png
190 ms
flag.png
194 ms
mobile.png
185 ms
version.png
365 ms
search.png
375 ms
banner-ru.jpg
764 ms
logo.png
579 ms
int-links-bg.png
387 ms
icon-2.png
392 ms
icon-3.png
554 ms
e-sud.jpg
567 ms
icon-5.png
586 ms
icon-6.png
592 ms
icon-7.png
738 ms
icon-8.png
756 ms
lexuz_banner-ru.jpg
771 ms
resized_6878007902493b9071fc8e0b459ee318_1.jpg
779 ms
resized_971c2752fb0cb1ce1c7906a73ea3fe58_22.jpg
981 ms
resized_2b2f42a677ea229faedd7a50b39a2778_resized_c25840e4943681f35756daa9c019b33b_%D0%B7%D0%B4%D0%B0%D0%BD%D0%B8%D0%B5%20%D0%B2%D0%B5%D1%80%D1%85%D0%BE%D0%B2%D0%BD%D0%BE%D0%B3%D0%BE%20%D1%81%D1%83%D0%B4%D0%B0%20%D0%A0%D0%A3%D0%B7.jpg
1101 ms
resized_e3c936f0a1c87d656a140cfd1ff0c276_senat-uzbekistan.jpg
1125 ms
resized_2ce1aa36e7035b95bd70aa7252dde9c7_resized_e8a3574940e2cc242e7d2707023a9914_%D0%92%D0%B5%D1%80%D1%85%D0%BE%D0%B2%D0%BD%D1%8B%D0%B9%20%D1%81%D1%83%D0%B4%20%D0%A0%D0%A3%D0%B7-%D0%B7%D0%B4%D0%B0%D0%BD%D0%B8%D0%B5.jpg
951 ms
map.png
961 ms
media-img-1.jpg
1163 ms
photogall-icon.png
1139 ms
media-img-2.jpg
1340 ms
videogall-icon.png
1177 ms
icon-9.png
1281 ms
icon-10.png
1308 ms
link-icon-1.png
1324 ms
link-icon-2.png
1353 ms
link-icon-3.png
1370 ms
link-icon-6.png
1463 ms
link-icon-4.png
1481 ms
cnt.png
1644 ms
opensans-regular.woff
1346 ms
opensans-semibold.woff
1551 ms
fontawesome-webfont.woff
1758 ms
opensans-light.woff
1778 ms
opensans-bold.woff
1828 ms
supcourt.uz
2974 ms
link-icon-5.png
1356 ms
5a875ca8f3bfd04cad8cb9f7eaa30c94.png
1533 ms
d0b4ab42b92701a8e58fcea6b3787c98.png
1538 ms
60c55e65d64227ac4c9e5ad5768151bf.png
1702 ms
580b1beb7b8f6a137178d9eea32605b5.png
1559 ms
created.png
1567 ms
shadow-top.png
1581 ms
shadow-bottom.png
1612 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
2765 ms
icons-s7815203d3b.png
1566 ms
supcourt.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
supcourt.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
supcourt.uz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Supcourt.uz can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Russian. Our system also found out that Supcourt.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.
supcourt.uz
Open Graph description is not detected on the main page of Supcourt. 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: