27.4 sec in total
1 sec
25.4 sec
909 ms
Welcome to customs.uz homepage info - get ready to check Customs best content for Uzbekistan right away, or after learning these important things about customs.uz
Visit customs.uzWe analyzed Customs.uz page load time and found that the first response time was 1 sec and then it took 26.3 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.
customs.uz performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value12.5 s
0/100
25%
Value14.8 s
1/100
10%
Value790 ms
37/100
30%
Value0.269
45/100
15%
Value19.9 s
2/100
10%
1027 ms
513 ms
516 ms
517 ms
1880 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 93% of them (62 requests) were addressed to the original Customs.uz, 1% (1 request) were made to Files.gov.uz and 1% (1 request) were made to Cert.uz. The less responsive or slowest element that took the longest time to load (18.7 sec) relates to the external source Meteo.uz.
Page size can be reduced by 1.2 MB (17%)
7.3 MB
6.1 MB
In fact, the total size of Customs.uz main page is 7.3 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 6.1 MB which makes up the majority of the site volume.
Potential reduce by 113.2 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 113.2 kB or 77% of the original size.
Potential reduce by 257.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. Customs images are well optimized though.
Potential reduce by 679.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 679.2 kB or 81% of the original size.
Potential reduce by 158.0 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. Customs.uz needs all CSS files to be minified and compressed as it can save up to 158.0 kB or 82% of the original size.
Number of requests can be reduced by 16 (24%)
66
50
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Customs. 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 from 9 to 1 for CSS and as a result speed up the page load time.
1027 ms
page_576f44b87633ab9ad07da4c30d96040a_dd01834bb5b315bec96dc4aef84e68f00.css
513 ms
kernel_main0.css
516 ms
template_f8de495aade05423e21758b6297760aa_f0f0a4e80b42e54088ee6aa51617459b0.css
517 ms
kernel_main.js
1880 ms
bootstrap.min.css
1360 ms
main.css
640 ms
specialView.css
710 ms
jquery-ui.css
929 ms
uSpeech.css
1330 ms
jquery.min.js
1476 ms
jquery-ui.js
2931 ms
bootstrap.min.js
1357 ms
default.js
1530 ms
specialView.js
1560 ms
jquery.cookie.js
1559 ms
map.js
1674 ms
uSpeech.js
1738 ms
jqvmap.css
2027 ms
916 ms
uzinfocomDarkMini.png
808 ms
bigLogo.png
2936 ms
header.jpg
689 ms
gerb.png
433 ms
logo.png
418 ms
menuArea.png
1271 ms
67130283f3a43b6050698de4523666c1.png
1032 ms
3be7f8524cfcae0e0d2ba75e8abcdfcb.png
1048 ms
b92220b250a65bfd9b5f62f0261a1039.png
1307 ms
icons.jpg
1707 ms
9b55a1f3f71c6027306264582bd5d7fd.JPG
1853 ms
9044208f8eb7a7562e0162a0fcf175c5.JPG
4360 ms
62948488581d44628fe87ed76aa441d0.jpg
1477 ms
abc55c18d0291c05fe33528b7c26e1bb.png
3582 ms
c1cfeafc41f125643855b805b0784b96.png
3368 ms
06fe912490f519ebab8b64855f67a7ac.JPG
3577 ms
8595d641f318f8527aa799aacdd444fc.JPG
4979 ms
a1a9fae482316177e8881a024c0d445e.jpg
3148 ms
tmp3.jpg
3365 ms
rsst.png
3564 ms
2483726ace8c47a6f2008d7e9ef1f109.JPG
5264 ms
1107f75b71a8c864387aff05a447c06a.png
4649 ms
714e00f6bab9b9589bf364bb15b3fc5a.jpg
5882 ms
1957860d0d51e994bac1cc2d97bfbfcc.jpg
6296 ms
tabBg.jpg
4555 ms
946a8813d1bd5616f2e6c736df66f47a.jpg
4758 ms
29b191bf5e97982f635f8f40a3110284.jpg
5917 ms
2202c90b62c96f24a1b407d0b0775b83.jpg
4960 ms
817674e0cd8b89ff82ec2e7adbc806d8.jpg
6246 ms
phone.png
5814 ms
map.png
6230 ms
video.png
6382 ms
customs.jpg
6026 ms
sares.jpg
6049 ms
kinologiy.jpg
6229 ms
yearname_uz.jpg
6264 ms
uz-certified.gif
941 ms
informer.php
18689 ms
informercb
4368 ms
collect
909 ms
SEGOEUISL.woff
6257 ms
glyphicons-halflings-regular.woff
6292 ms
mygov.jpg
6038 ms
dataGovUz.jpg
5851 ms
dc.png
5522 ms
gis.png
5622 ms
footerLogo.png
5494 ms
customs.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-*] attributes do not match their roles
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.
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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
customs.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
Issues were logged in the Issues panel in Chrome Devtools
customs.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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Customs.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Customs.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.
customs.uz
Open Graph description is not detected on the main page of Customs. 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: