LEX.UZ LEX.UZ - Ўзбекистон қонунчилиги


lex.uz website information.

lex.uz domain name is registered by .UZ top-level domain registry. See the other sites registred in .UZ domain zone.

Following name servers are specified for lex.uz domain:

  • no

and probably website lex.uz is hosted by iomart Cloud Services Limited. web hosting company. Check the complete list of other most popular websites hosted by iomart Cloud Services Limited. hosting company.

According to Alexa traffic rank the highest website lex.uz position was 56893 (in the world). The lowest Alexa rank position was 134968. Now website lex.uz ranked in Alexa database as number 57252 (in the world).

Website lex.uz Desktop speed measurement score (60/100) is better than the results of 35.69% of other sites shows that the page desktop performance can be improved.

lex.uz Mobile usability score (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of lex.uz (82/100) is better than the results of 89.15% of other sites and shows that the landing page performance on mobile devices is excellent.

Weekly Rank Report

DateRankChange
Sep-18-2024 57,252749
Sep-17-2024 58,001-1,108
Sep-16-2024 56,8931,407
Sep-15-2024 58,300-889
Sep-14-2024 57,411194
Sep-13-2024 57,605-60
Sep-12-2024 57,5451,669

Advertisement

lex.uz Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



lex.uz whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


% Uzbekistan Whois Server Version 1.0

% Domain names in the .uz domain can now be registered
% with many different competing registrars. Go to http://www.cctld.uz/
% for detailed information.

Domain Name: LEX.UZ
Registrar: SARKOR TELECOM
Whois Server: www.whois.uz
Referral URL: http://www.cctld.uz/
Name Server: ns1.lex.uz. 213.230.64.46
Name Server: ns.lex.uz. 195.158.31.202
Name Server: not.defined. not.defined.
Name Server: not.defined. not.defined.
Status: ACTIVE
Updated Date: 24-may-2019
Creation Date: 04-May-2007
Expiration Date: 25-may-2022

% >>> Last update of whois database: Wed, 12 May 2021 16:34:58 +0500

lex.uz server information

Servers Location

IP Address
no
Country
Region
City

lex.uz desktop page speed rank

Last tested: 2016-12-09


Desktop Speed Bad
60/100

lex.uz Desktop Speed Test Quick Summary


priority - 32 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 309.8KiB (78% reduction).

Compressing http://lex.uz/ could save 176.2KiB (87% reduction).
Compressing http://lex.uz/JavaScript/jquery.js could save 59.7KiB (64% reduction).
Compressing http://lex.uz/JavaScript/jquery.easytabs.js could save 23.1KiB (77% reduction).
Compressing http://lex.uz/JavaScript/jquery.fancybox-1.3.4.js could save 21.4KiB (74% reduction).
Compressing http://lex.uz/JavaScript/scripts_uz.js could save 6.4KiB (77% reduction).
Compressing http://lex.uz/JavaScript/custom_el.js could save 5.9KiB (76% reduction).
Compressing http://lex.uz/javascript/jquery.maskedinput-1.3.js could save 4.5KiB (67% reduction).
Compressing http://lex.uz/javascript/hoverIntent.js?_=1481294567613 could save 3.2KiB (67% reduction).
Compressing http://lex.uz/Pages/ajax_methods.aspx?action=getOr…rgan_1&_=1481294567635 could save 3.2KiB (82% reduction).
Compressing http://lex.uz/Pages/ajax_methods.aspx?action=getOr…=&idd=&_=1481294567634 could save 2.7KiB (80% reduction).
Compressing http://lex.uz/javascript/superfish.js?_=1481294567612 could save 2.3KiB (60% reduction).
Compressing http://lex.uz/javascript/jquery.cookie.js?_=1481294567611 could save 1.2KiB (55% reduction).

priority - 11 Reduce server response time

In our test, your server responded in 1.3 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 8 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 81.6KiB (41% reduction).

Minifying http://lex.uz/ could save 81.6KiB (41% reduction).

priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 6 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://lex.uz/JavaScript/jquery.js
http://lex.uz/JavaScript/custom_el.js
http://lex.uz/JavaScript/jquery.fancybox-1.3.4.js
http://lex.uz/JavaScript/jquery.easytabs.js
http://lex.uz/JavaScript/scripts_uz.js
http://lex.uz/javascript/jquery.maskedinput-1.3.js

Optimize CSS Delivery of the following:

http://lex.uz/css/style.css
http://lex.uz/css/selecter.css
http://lex.uz/css/jquery.fancybox-1.3.4.css
http://lex.uz/css/reset.css

priority - 4 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

202.8KiB of the HTML response was required to render the above-the-fold content. This requires 4 network round-trips. However, if the HTML response were compressed, then the HTML required to render the above-the-fold content could be delivered in just 2 network round-trips. Enable compression for the HTML response in order to prioritize the visible content for this page.

Only about 32% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.

priority - 4 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 36.8KiB (40% reduction).

Minifying http://lex.uz/JavaScript/jquery.easytabs.js could save 16.9KiB (56% reduction).
Minifying http://lex.uz/JavaScript/jquery.fancybox-1.3.4.js could save 7.9KiB (28% reduction).
Minifying http://lex.uz/javascript/hoverIntent.js?_=1481294567613 could save 3.4KiB (70% reduction).
Minifying http://lex.uz/JavaScript/scripts_uz.js could save 2.6KiB (32% reduction).
Minifying http://lex.uz/javascript/jquery.maskedinput-1.3.js could save 2.2KiB (34% reduction).
Minifying http://lex.uz/JavaScript/custom_el.js could save 2KiB (27% reduction).
Minifying http://lex.uz/javascript/superfish.js?_=1481294567612 could save 1.1KiB (28% reduction).
Minifying http://lex.uz/javascript/jquery.cookie.js?_=1481294567611 could save 677B (32% reduction).

priority - 3 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 21.8KiB (39% reduction).

Compressing http://lex.uz/images/bg/logo.png could save 6.1KiB (59% reduction).
Compressing and resizing http://lex.uz/image/android2.png could save 4.3KiB (90% reduction).
Compressing http://lex.uz/banners/ona-bola-uz.gif could save 2.2KiB (14% reduction).
Compressing http://lex.uz/images/bg/ad_uzor_bot.png could save 2.2KiB (41% reduction).
Compressing http://lex.uz/images/bg/ad_uzor_top.png could save 2.1KiB (23% reduction).
Compressing http://lex.uz/images/icons/rss.jpg could save 909B (59% reduction).
Compressing http://lex.uz/images/bg/nav_top_bg.jpg could save 908B (69% reduction).
Compressing http://lex.uz/images/icons/l_icon6.jpg could save 830B (53% reduction).
Compressing http://lex.uz/images/arrow/main_nav_uzor_right.png could save 705B (41% reduction).
Compressing http://lex.uz/images/arrow/main_nav_uzor_left.png could save 644B (39% reduction).
Compressing http://lex.uz/images/bg/uzor_sprite2.png could save 584B (22% reduction).
Compressing http://lex.uz/images/bg/checkbox.png could save 513B (57% reduction).

priority - 0 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://www.google-analytics.com/ga.js (2 hours)

lex.uz Desktop Resources

Total Resources79
Number of Hosts4
Static Resources62
JavaScript Resources10
CSS Resources4

lex.uz Desktop Resource Breakdown

lex.uz mobile page speed rank

Last tested: 2016-12-09


Mobile Speed Medium
82/100

lex.uz Mobile Speed Test Quick Summary


priority - 11 Reduce server response time

In our test, your server responded in 0.95 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Optimize CSS Delivery of the following:

http://lex.uz/css/iphone.css

priority - 1 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://www.google-analytics.com/ga.js (2 hours)

lex.uz Mobile Resources

Total Resources9
Number of Hosts4
Static Resources4
JavaScript Resources1
CSS Resources1

lex.uz Mobile Resource Breakdown

lex.uz mobile page usability

Last tested: 2016-12-09


Mobile Usability Good
100/100

lex.uz similar domains

Similar domains:
www.lex.com
www.lex.net
www.lex.org
www.lex.info
www.lex.biz
www.lex.us
www.lex.mobi
www.ex.uz
www.lex.uz
www.pex.uz
www.lpex.uz
www.plex.uz
www.oex.uz
www.loex.uz
www.olex.uz
www.kex.uz
www.lkex.uz
www.klex.uz
www.lx.uz
www.lwx.uz
www.lewx.uz
www.lwex.uz
www.lsx.uz
www.lesx.uz
www.ldx.uz
www.ledx.uz
www.ldex.uz
www.lrx.uz
www.lerx.uz
www.lrex.uz
www.le.uz
www.lez.uz
www.lexz.uz
www.lezx.uz
www.les.uz
www.lexs.uz
www.led.uz
www.lexd.uz
www.lec.uz
www.lexc.uz
www.lecx.uz

lex.uz Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


lex.uz TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.