uzcard.uz Website Information
Daily Unique Visits: 0
Daily Page Views: 0
Income Per Day: $0
Estimated Value: $9
uzcard.uz is registered under .UZ top-level domain. Please check other sites in .UZ zone.
No name server records were found.
and is probably hosted by UZSCINET. See the full list of other websites hosted by UZSCINET.
The highest website uzcard.uz position in Alexa rank database was 38855 and the lowest rank position was 999492. Current position of uzcard.uz in Alexa rank database is below 1 million.
Desktop speed score of uzcard.uz (80/100) is better than the results of 69.89% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of uzcard.uz (62/100) is better than the results of 7.29% of other sites and means that the page is not mobile-friendly.
Mobile speed score of uzcard.uz (63/100) is better than the results of 61.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
uzcard.uz Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
uzcard.uz whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
% 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: UZCARD.UZ
Registrar: SUVAN NET
Whois Server: www.whois.uz
Referral URL: http://www.cctld.uz/
Name Server: ns1.ahost.uz. 83.69.139.168
Name Server: ns2.ahost.uz. 83.69.139.151
Name Server: not.defined.
Name Server: not.defined.
Status: ACTIVE
Updated Date: 17-Jan-2024
Creation Date: 23-Aug-2012
Expiration Date: 27-Jul-2033
% >>> Last update of whois database: Fri, 11 Oct 2024 12:26:50 +0500
uzcard.uz server information
Servers Location
uzcard.uz desktop page speed rank
Last tested: 2018-12-10
uzcard.uz Desktop Speed Test Quick Summary
priority - 18Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 180.5KiB (64% reduction).
Compressing http://uzcard.uz/templates/uzcard_ordinary/images/ico-sprite.png could save 2.8KiB (79% reduction).
Compressing http://uzcard.uz/templates/uzcard_ordinary/images/other-logo.png could save 1.4KiB (17% reduction).
Compressing http://uzcard.uz/templates/uzcard_ordinary/images/logo-f.png could save 881B (24% reduction).
Compressing https://informer.yandex.ru/informer/51238519/3_1_F…F_EFEFEFFF_0_pageviews could save 252B (19% reduction).
priority - 2Eliminate 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.
Optimize CSS Delivery of the following:
priority - 1Leverage 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:
https://mc.yandex.ru/metrika/tag.js (60 minutes)
http://code.jivosite.com/script/widget/pWN9HfTUS6 (2 hours)
priority - 1Reduce server response time
In our test, your server responded in 0.25 seconds.
priority - 0Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 2.9KiB (22% reduction).
Minifying http://uzcard.uz/templates/uzcard_ordinary/css/main.css could save 426B (12% reduction) after compression.
Minifying http://uzcard.uz/media/system/css/system.css could save 180B (33% reduction) after compression.
Minifying http://uzcard.uz/templates/system/css/system.css could save 159B (38% reduction) after compression.
Minifying http://uzcard.uz/templates/uzcard_ordinary/css/owl.carousel.css could save 113B (22% reduction) after compression.
priority - 0Minify 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 893B (29% reduction).
Minifying http://uzcard.uz/templates/uzcard_ordinary/js/script.js could save 362B (41% reduction) after compression.
priority - 0Minify 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 535B (13% reduction).
uzcard.uz Desktop Resource Breakdown
Total Resources | 39 |
Number of Hosts | 8 |
Static Resources | 28 |
JavaScript Resources | 13 |
CSS Resources | 9 |
uzcard.uz mobile page speed rank
Last tested: 2018-12-10
uzcard.uz Mobile Speed Test Quick Summary
priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 6 blocking script resources and 9 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
http://uzcard.uz/media/system/js/core.js
http://ajax.googleapis.com/ajax/libs/jquery/1.8/jquery.min.js
http://uzcard.uz/components/com_k2/js/k2.js?v2.6.9&sitepath=/
http://uzcard.uz/media/system/js/caption.js
http://uzcard.uz/media/system/js/mootools-more.js
Optimize CSS Delivery of the following:
http://uzcard.uz/media/mod_languages/css/template.css
http://fonts.googleapis.com/css?family=Open+Sans:4…&subset=latin,cyrillic
http://uzcard.uz/templates/system/css/system.css
http://uzcard.uz/media/system/css/system.css
http://uzcard.uz/templates/uzcard_ordinary/css/owl.carousel.css
http://uzcard.uz/templates/uzcard_ordinary/css/main.css
http://uzcard.uz/templates/uzcard_ordinary/css/font-awesome.min.css
http://uzcard.uz/templates/uzcard_ordinary/css/jquery.fancybox.min.css
priority - 18Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 180.5KiB (64% reduction).
Compressing http://uzcard.uz/templates/uzcard_ordinary/images/ico-sprite.png could save 2.8KiB (79% reduction).
Compressing http://uzcard.uz/templates/uzcard_ordinary/images/other-logo.png could save 1.4KiB (17% reduction).
Compressing http://uzcard.uz/templates/uzcard_ordinary/images/logo-f.png could save 881B (24% reduction).
Compressing https://informer.yandex.ru/informer/51238519/3_1_F…F_EFEFEFFF_0_pageviews could save 252B (19% reduction).
priority - 2Leverage 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:
https://mc.yandex.ru/metrika/tag.js (60 minutes)
http://code.jivosite.com/script/widget/pWN9HfTUS6 (2 hours)
priority - 1Reduce server response time
In our test, your server responded in 0.25 seconds.
priority - 0Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 2.9KiB (22% reduction).
Minifying http://uzcard.uz/templates/uzcard_ordinary/css/main.css could save 426B (12% reduction) after compression.
Minifying http://uzcard.uz/media/system/css/system.css could save 180B (33% reduction) after compression.
Minifying http://uzcard.uz/templates/system/css/system.css could save 159B (38% reduction) after compression.
Minifying http://uzcard.uz/templates/uzcard_ordinary/css/owl.carousel.css could save 113B (22% reduction) after compression.
priority - 0Minify 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 893B (29% reduction).
Minifying http://uzcard.uz/templates/uzcard_ordinary/js/script.js could save 362B (41% reduction) after compression.
priority - 0Minify 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 535B (13% reduction).
uzcard.uz Mobile Resource Breakdown
Total Resources | 39 |
Number of Hosts | 8 |
Static Resources | 28 |
JavaScript Resources | 13 |
CSS Resources | 9 |
uzcard.uz mobile page usability
Last tested: 2018-12-10
uzcard.uz Mobile Usability Test Quick Summary
priority - 40Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
For the Media
and 3 others render only 5 pixels tall (13 CSS pixels).RU
and 2 others render only 5 pixels tall (14 CSS pixels).PERSONAL CABINET
renders only 5 pixels tall (14 CSS pixels).Call centre +9…(71) 200-28-28
renders only 5 pixels tall (13 CSS pixels).NEWS
renders only 7 pixels tall (17 CSS pixels).Today, activel…– the portal…
and 11 others render only 5 pixels tall (14 CSS pixels).New suppliers…rtal «Woy-wo’»
and 5 others render only 5 pixels tall (14 CSS pixels).Uzcard news
and 5 others render only 5 pixels tall (14 CSS pixels).UzCard © 2016-…рава защищены.
renders only 5 pixels tall (14 CSS pixels).priority - 11Size content to viewport
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 1,050 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:
<a href="/index.php/en/">EN</a>
falls outside the viewport.The element
<img src="/media/k2/item…fee6e32_XL.jpg">
falls outside the viewport.The element
<a href="https://play.g….uzcard.uzcard" class="google-play">
falls outside the viewport.The element
<h3>News</h3>
falls outside the viewport.The element
<p class="date">Monday, 27 March 2017 11:30</p>
falls outside the viewport.The element
<a href="/index.php/en/…-portal-woy-wo" class="title">New suppliers…rtal «Woy-wo’»</a>
falls outside the viewport.The element
<p>Today, activel…– the portal…</p>
falls outside the viewport.The element
<p class="date">Monday, 20 February 2017 12:30</p>
falls outside the viewport.The element
<a href="/index.php/en/…-portal-woy-wo" class="title">New suppliers…rtal «Woy-wo’»</a>
falls outside the viewport.The element
<p>Today, activel…– the portal…</p>
falls outside the viewport.The element
<div class="row"></div>
falls outside the viewport.The element
<img src="http://www.uz/…fffff&p=4BC463">
falls outside the viewport.The element
<div class="copyright">UzCard © 2016-…рава защищены.</div>
falls outside the viewport.priority - 10Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
priority - 4Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<a href="/" class="logo"></a>
is close to 1 other tap targets.<a href="/index.php/en/about-uzcard">About Uzcard</a>
and 3 others are close to other tap targets.<a href="/index.php/ru/">RU</a>
and 2 others are close to other tap targets.<button type="submit">
is close to 2 other tap targets.<a href="https://my.uzcard.uz/">Personal cabinet</a>
is close to 1 other tap targets.<a href="http://woy-wo.uz" class="logoWoywo"></a>
is close to 1 other tap targets.<a href="https://itunes…l=ru&ls=1&mt=8" class="app-store">
is close to 1 other tap targets.<a href="https://play.g….uzcard.uzcard" class="google-play">
is close to 1 other tap targets.<a href="/index.php/en/…ns-and-answers" class="readmore">
is close to 1 other tap targets.<a href="https://ok.ru/…54555929739382"></a>
is close to 2 other tap targets.uzcard.uz HTML validation
Errors
A document must not include more than one “meta” element with a “http-equiv” attribute whose value is “content-type”.
"...uz/" /> <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <me..."
Element “title” not allowed as child of element “head” in this context. (Suppressing further errors from this subtree.)
"...x-icon"> <title>Uzcard..."
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
"...ss="logo"><img src="/templates/uzcard_ordinary/images/logo.png"></a> ..." Line: 109 Column: 2 - 76
"...item-1"> <img src="/media/k2/items/cache/e2bf3b11df0b872112757f1c2fee6e32_XL.jpg" /> <div..."
Attribute “target” not allowed on element “img” at this point.
"...uz"> <img src="/templates/uzcard_ordinary/images/logo-woywo.png" alt="" target="_blank" /> <..."
Bad value “_blank ” for attribute “target” on element “a”: Reserved keyword “blank ” used.
"... <li><a href="http://uzcard-service.uz" target="_blank " class="uzservice"></a></..."
The “language” attribute on the “script” element is obsolete. Use the “type” attribute instead.
"...SCRIPT> <SCRIPT language="javascript1.1" type="text/javascript"> <!-..." Line: 268 Column: 2 - 57
"...SCRIPT> <SCRIPT language="javascript1.2" type="text/javascript"> <!-..." Line: 274 Column: 2 - 57
"...SCRIPT> <SCRIPT language="javascript1.3" type="text/javascript"> <!-..."
Warnings
The “language” attribute on the “script” element is obsolete. You can safely omit it.
"...RATING --><SCRIPT language="javascript" type="text/javascript"> <!-..." Line: 279 Column: 2 - 54
"...SCRIPT> <SCRIPT language="JavaScript" type="text/javascript"> <!-..."
The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.
"...rget=_top><IMG height=31 src="http://www.uz/plugins/top_rating/count/nojs_cnt.png?id=32247&pg=http%3A//uzinfocom.uz&&col=342279&t=ffffff&p=4BC463" width=88 border=0 alt="Топ рейтинг www.uz"></A></NO..."
uzcard.uz similar domains
www.uzcard.net
www.uzcard.org
www.uzcard.info
www.uzcard.biz
www.uzcard.us
www.uzcard.mobi
www.zcard.uz
www.uzcard.uz
www.yzcard.uz
www.uyzcard.uz
www.yuzcard.uz
www.hzcard.uz
www.uhzcard.uz
www.huzcard.uz
www.jzcard.uz
www.ujzcard.uz
www.juzcard.uz
www.izcard.uz
www.uizcard.uz
www.iuzcard.uz
www.ucard.uz
www.uxcard.uz
www.uzxcard.uz
www.uxzcard.uz
www.uscard.uz
www.uzscard.uz
www.uszcard.uz
www.uacard.uz
www.uzacard.uz
www.uazcard.uz
www.uzard.uz
www.uzxard.uz
www.uzcxard.uz
www.uzdard.uz
www.uzcdard.uz
www.uzdcard.uz
www.uzfard.uz
www.uzcfard.uz
www.uzfcard.uz
www.uzvard.uz
www.uzcvard.uz
www.uzvcard.uz
www.uzcrd.uz
www.uzcqrd.uz
www.uzcaqrd.uz
www.uzcqard.uz
www.uzcwrd.uz
www.uzcawrd.uz
www.uzcward.uz
www.uzcsrd.uz
www.uzcasrd.uz
www.uzcsard.uz
www.uzczrd.uz
www.uzcazrd.uz
www.uzczard.uz
www.uzcad.uz
www.uzcaed.uz
www.uzcared.uz
www.uzcaerd.uz
www.uzcadd.uz
www.uzcardd.uz
www.uzcadrd.uz
www.uzcafd.uz
www.uzcarfd.uz
www.uzcafrd.uz
www.uzcatd.uz
www.uzcartd.uz
www.uzcatrd.uz
www.uzcar.uz
www.uzcarx.uz
www.uzcardx.uz
www.uzcarxd.uz
www.uzcars.uz
www.uzcards.uz
www.uzcarsd.uz
www.uzcare.uz
www.uzcarde.uz
www.uzcarr.uz
www.uzcardr.uz
www.uzcarrd.uz
www.uzcarf.uz
www.uzcardf.uz
www.uzcarc.uz
www.uzcardc.uz
www.uzcarcd.uz
uzcard.uz Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
uzcard.uz TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.