LI.RU Мобильный LiveInternet

li.ru Website Information

Daily Unique Visits: 24,174

Daily Page Views: 145,044

Income Per Day: $290

Estimated Value: $208,800

This website is located in Russian Federation and is using following IP address 88.212.202.1. See the complete list of popular websites hosted in Russian Federation.

li.ru is registered under .RU top-level domain. Please check other sites in .RU zone.

Website li.ru is using the following name servers:

  • ns2.li.ru
  • ns.li.ru

and is probably hosted by United Network LLC. See the full list of other websites hosted by United Network LLC.

The highest website li.ru position in Alexa rank database was 51605 and the lowest rank position was 126237. Current position of li.ru in Alexa rank database is 59330.

Desktop speed score of li.ru (91/100) is better than the results of 90.07% of other sites and shows that the page is performing great on desktop computers.

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

Mobile speed score of li.ru (78/100) is better than the results of 86.92% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

li.ru 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.


li.ru 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.


% TCI Whois Service. Terms of use:
% https://tcinet.ru/documents/whois_ru_rf.pdf (in Russian)
% https://tcinet.ru/documents/whois_su.pdf (in Russian)

domain: LI.RU
nserver: ns2.li.ru. 88.212.202.37
nserver: ns.li.ru. 88.212.202.56
state: REGISTERED, DELEGATED, VERIFIED
org: OOO Laboratoriya poiskovyh i statisticheskih resheniy
taxpayer-id: 7730551564
registrar: RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created: 2000-03-16T14:51:12Z
paid-till: 2025-03-31T21:00:00Z
free-date: 2025-05-02
source: TCI

Last updated on 2024-09-22T00:56:30Z

li.ru server information

Servers Location

li.ru desktop page speed rank

Last tested: 2017-05-23


Desktop Speed Good
91/100

li.ru Desktop Speed Test Quick Summary


priority - 6Eliminate 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:

http://www.liveinternet.ru/ReActive/css/pda.css

priority - 1Enable 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 7.3KiB (67% reduction).

Compressing http://www.liveinternet.ru/ReActive/css/pda.css could save 5.8KiB (72% reduction).
Compressing http://www.li.ru/ could save 1.4KiB (54% reduction).

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:

http://www.liveinternet.ru/ReActive/css/pda.css (expiration not specified)

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.7KiB (34% reduction).

Minifying http://www.liveinternet.ru/ReActive/css/pda.css could save 2.7KiB (34% reduction).

priority - 0Optimize images

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

Optimize the following images to reduce their size by 1.7KiB (84% reduction).

Compressing http://www.liveinternet.ru/ReActive/i/pda/ma-nav/li-a.png could save 853B (92% reduction).
Compressing http://www.liveinternet.ru/ReActive/i/pda/ma-nav/bg.png could save 850B (78% reduction).

li.ru Desktop Resource Breakdown

Total Resources9
Number of Hosts4
Static Resources3
JavaScript Resources1
CSS Resources1

li.ru mobile page speed rank

Last tested: 2017-05-23


Mobile Speed Medium
78/100

li.ru Mobile Speed Test Quick Summary


priority - 24Eliminate 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:

http://www.liveinternet.ru/ReActive/css/pda.css

priority - 1Enable 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 7.3KiB (67% reduction).

Compressing http://www.liveinternet.ru/ReActive/css/pda.css could save 5.8KiB (72% reduction).
Compressing http://www.li.ru/ could save 1.4KiB (54% reduction).

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:

http://www.liveinternet.ru/ReActive/css/pda.css (expiration not specified)

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.7KiB (34% reduction).

Minifying http://www.liveinternet.ru/ReActive/css/pda.css could save 2.7KiB (34% reduction).

priority - 0Optimize images

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

Optimize the following images to reduce their size by 1.7KiB (84% reduction).

Compressing http://www.liveinternet.ru/ReActive/i/pda/ma-nav/li-a.png could save 853B (92% reduction).
Compressing http://www.liveinternet.ru/ReActive/i/pda/ma-nav/bg.png could save 850B (78% reduction).

li.ru Mobile Resource Breakdown

Total Resources9
Number of Hosts4
Static Resources3
JavaScript Resources1
CSS Resources1

li.ru mobile page usability

Last tested: 2017-05-23


Mobile Usability Good
93/100

li.ru Mobile Usability Test Quick Summary


priority - 3Size 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.

The tap target <a href="http://www.li.…x-statpda.html">Статистика сайтов</a> and 3 others are close to other tap targets.

priority - 3Configure the viewport

Your page specifies a fixed-width mobile viewport. Consider using a responsive viewport to allow your page to render properly on all devices.

li.ru HTML validation

Errors

Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 6
"...<html> <h..."

Internal encoding declaration “windows-1251” disagrees with the actual encoding of the document (“utf-8”).

Line: 6 Column: 3 - 78
"...tle> <meta http-equiv="Content-Type" content="text/html; charset=windows-1251" /> <m..."

Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.

Line: 7 Column: 3 - 53
"...51" /> <meta http-equiv="Content-Language" content="ru" /> <m..."

Bad value “Pragma” for attribute “http-equiv” on element “meta”.

Line: 8 Column: 3 - 49
"...ru" /> <meta http-equiv="Pragma" content="no-cache" /> <m..."

Bad value “Expires” for attribute “http-equiv” on element “meta”.

Line: 9 Column: 3 - 44
"...he" /> <meta http-equiv="Expires" content="-1" /> <m..."

Bad value “Cache-Control” for attribute “http-equiv” on element “meta”.

Line: 10 Column: 3 - 56
"...-1" /> <meta http-equiv="Cache-Control" content="no-cache" /> <m..."

The “scrolling” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 60 Column: 1 - 179
"...u></span> <iframe src="/adv/advtm.html?p=6&span-name=mobile_liru" style="position:absolute;top:0;left:0;width:1;height:1;visibility:hidden; border:0px outset;" scrolling=no frameborder=no></ifram..."

The “frameborder” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 60 Column: 1 - 179
"...u></span> <iframe src="/adv/advtm.html?p=6&span-name=mobile_liru" style="position:absolute;top:0;left:0;width:1;height:1;visibility:hidden; border:0px outset;" scrolling=no frameborder=no></ifram..."

End tag for “body” seen, but there were unclosed elements.

Line: 70 Column: 2 - 8
"...pt> </body> </htm..."

Unclosed element “div”.

Line: 23 Column: 3 - 23
"...dy> <div class="ma_wrap"> ..."

Warnings

Consider avoiding viewport values that prevent users from resizing documents.

Line: 16 Column: 3 - 116
"..." /> <meta id="viewport" name="viewport" content="width=320; initial-scale=1.0; maximum-scale=1.0; user-scalable=0;" /> ..."

li.ru similar domains

Similar domains:
www.li.com
www.li.net
www.li.org
www.li.info
www.li.biz
www.li.us
www.li.mobi
www.i.ru
www.li.ru
www.pi.ru
www.lpi.ru
www.pli.ru
www.oi.ru
www.loi.ru
www.oli.ru
www.ki.ru
www.lki.ru
www.kli.ru
www.l.ru
www.lu.ru
www.liu.ru
www.lui.ru
www.lj.ru
www.lij.ru
www.lji.ru
www.lk.ru
www.lik.ru
www.lo.ru
www.lio.ru

li.ru 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.


li.ru 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.