Li.Ru - Info li.ru

li.ru receives about 14,083 unique visitors and 18,308 (1.30 per visitor) page views per day which should earn about $144.17/day from advertising revenue. Estimated site value is $107,575.03. According to Alexa Traffic Rank li.ru is ranked number 99,786 in the world and 0.00083% of global Internet users visit it. Site is hosted in Moscow, 48, Russia and links to network IP address 88.212.202.1. This server supports HTTPS and doesn't support HTTP/2.

About - li.ru

Мобильный LiveInternet
Edit Site Info

Technologies used on Website

Currently Not Available

li.ru Profile

Title: Мобильный LiveInternet
Keywords: ,liveinternet
Last update was 52 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with li.ru in any way. Only publicly available statistics data are displayed.

How popular is li.ru?

14.1K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
14,083
Monthly Unique Visitors:
337,992
Pages per Visit:
1.30
Daily Pageviews:
18,308
Alexa Rank:
99,786 visit alexa
Alexa Reach:
0.00083%   (of global internet users)
Avg. visit duration:
04:20
Bounce rate:
70.85%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
12.87%
Referral:
58.08%
Search:
26.31%
Social:
2.75%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
United States 59.1%63.2%32846
Russian Federation 9.1%7.6%33377
Canada 7.2%6.5%31949
Ukraine 1.0%0.8%40129
Kazakhstan 0.9%0.7%20923

Where do visitors go on this site?

Reach%Pageviews%PerUser
li.ru
98.64%98.93%1.2
OTHER
0%1.07%0

Competitive Data

SEMrush
Domain:
  li.ru
Rank:
(Rank based on keywords, cost and organic traffic)
  6,654,593
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  364
Organic Traffic:
(Number of visitors coming from top 20 search results)
  24
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $1.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is li.ru?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
li.ru
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
li.ru
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much li.ru can earn?

Daily Revenue:
$144.17
Monthly Revenue:
$4,325.10
Yearly Revenue:
$52,622.05
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 11,571$132.72
Canada 1,190$8.34
Russian Federation 1,391$2.82
Ukraine 146$0.20
Kazakhstan 128$0.09

How much money do li.ru lose due to Adblock?

Daily Revenue Loss:
$26.17
Monthly Revenue Loss:
$785.18
Yearly Revenue Loss:
$9,552.99
Daily Pageviews Blocked:
2,487
Monthly Pageviews Blocked:
74,598
Yearly Pageviews Blocked:
907,606
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 2,083$23.89
Canada 298$2.09
Russian Federation 83$0.17
Ukraine 19$0.03
Kazakhstan 4$0.00

How much is li.ru worth?

Website Value:
$107,575.03

+ Where is li.ru hosted?

Server IP:
88.212.202.1
ASN:
AS39134 
ISP:
United Network LLC 
Server Location:
Moscow
48
Russia, RU
 

Other sites hosted on 88.212.202.1

There are no other sites hosted on this IP

+ How fast does li.ru load?

Average Load Time:
(1507 ms) 60 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)4.1s 29% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 29% 44% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 44% 25% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 25%
First Input Delay (FID)20ms 97% of loads for this page have a fast (<50ms) First Input Delay (FID) 97% 1% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)4.1s 29% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 29% 44% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 44% 25% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 25%
First Input Delay (FID)20ms 97% of loads for this page have a fast (<50ms) First Input Delay (FID) 97% 1% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Lab Data

Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Eliminate render-blocking resources - Potential savings of 120 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://i.li.ru/ReActive/css/pda.css
3 KB190
Enable text compression - Potential savings of 1 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://www.li.ru/
3 KB1 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://li.ru/
0 ms360 ms0 KB0 KB301text/html
http://www.li.ru/
360 ms726 ms3 KB3 KB200text/htmlDocument
http://i.li.ru/ReActive/css/pda.css
738 ms944 ms3 KB8 KB200text/cssStylesheet
http://www.li.ru/adv/advtm.html?p=6&span-name=mobile_liru
742 ms949 ms1 KB0 KB200text/htmlDocument
http://counter.yadro.ru/hit?r;s800*600*24;uhttp%3A//www.li.ru/;0.8666554763350194
947 ms1306 ms0 KB0 KB302text/html
http://i.li.ru/ReActive/i/pda/ma-nav/bg.png
948 ms1127 ms1 KB1 KB200image/pngImage
http://i.li.ru/ReActive/i/pda/ma-nav/li-a.png
949 ms1143 ms1 KB1 KB200image/pngImage
http://www.liveinternet.ru/cgi-bin/adv.fcgi?qtype=parent,javascript&p=6&span-name=mobile_liru&ref=http%3A//www.li.ru/
970 ms1330 ms0 KB0 KB200text/htmlScript
http://counter.yadro.ru/hit?q;r;s800*600*24;uhttp%3A//www.li.ru/;0.8666554763350194
1306 ms1672 ms0 KB0 KB200image/gifImage
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
749 ms
8 ms
971 ms
10 ms
982 ms
6 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
54 ms4 ms2 ms
Avoids enormous network payloads - Total size was 10 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.li.ru/
3 KB
http://i.li.ru/ReActive/css/pda.css
3 KB
http://i.li.ru/ReActive/i/pda/ma-nav/bg.png
1 KB
http://i.li.ru/ReActive/i/pda/ma-nav/li-a.png
1 KB
http://www.li.ru/adv/advtm.html?p=6&span-name=mobile_liru
1 KB
http://counter.yadro.ru/hit?r;s800*600*24;uhttp%3A//www.li.ru/;0.8666554763350194
0 KB
http://counter.yadro.ru/hit?q;r;s800*600*24;uhttp%3A//www.li.ru/;0.8666554763350194
0 KB
http://www.liveinternet.ru/cgi-bin/adv.fcgi?qtype=parent,javascript&p=6&span-name=mobile_liru&ref=http%3A//www.li.ru/
0 KB
http://li.ru/
0 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
28 ms
Style & Layout
11 ms
Script Evaluation
5 ms
Parse HTML & CSS
5 ms
Rendering
5 ms
Script Parsing & Compilation
2 ms
Avoids an excessive DOM size - 32 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
32
Maximum DOM Depth
8
Maximum Child Elements
4
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://li.ru/)
0
http://www.li.ru/
190
Keep request counts low and transfer sizes small - 9 requests • 10 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
910 KB
Document
23 KB
Image
33 KB
Stylesheet
13 KB
Other
21 KB
Script
10 KB
Media
00 KB
Font
00 KB
Third-party
31 KB
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Minimize Critical Requests Depth - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 370 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

96
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)1.4s 29% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 82% 13% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 13% 4% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 4%
First Input Delay (FID)40ms 95% of loads for this page have a fast (<50ms) First Input Delay (FID) 95% 3% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 3% 1% of loads for this page have a slow (>250ms) First Input Delay (FID) 1%

Origin Data

All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)3.6s 23% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 23% 55% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 55% 20% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 20%
First Input Delay (FID)257ms 97% of loads for this page have a fast (<50ms) First Input Delay (FID) 85% 9% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 9% 5% of loads for this page have a slow (>250ms) First Input Delay (FID) 5%

Lab Data

Third-Party Usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
First Contentful Paint (3G) 3690 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 3.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1124 ms
39 ms
1164 ms
15 ms
1726 ms
22 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
438 ms14 ms9 ms
Avoids enormous network payloads - Total size was 10 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.li.ru/
3 KB
http://i.li.ru/ReActive/css/pda.css
3 KB
http://i.li.ru/ReActive/i/pda/ma-nav/bg.png
1 KB
http://i.li.ru/ReActive/i/pda/ma-nav/li-a.png
1 KB
http://www.li.ru/adv/advtm.html?p=6&span-name=mobile_liru
1 KB
http://counter.yadro.ru/hit?r;s412*660*24;uhttp%3A//www.li.ru/;0.1505255865836843
0 KB
http://counter.yadro.ru/hit?q;r;s412*660*24;uhttp%3A//www.li.ru/;0.1505255865836843
0 KB
http://www.liveinternet.ru/cgi-bin/adv.fcgi?qtype=parent,javascript&p=6&span-name=mobile_liru&ref=http%3A//www.li.ru/
0 KB
http://li.ru/
0 KB
Minimizes main-thread work - 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
236 ms
Style & Layout
92 ms
Parse HTML & CSS
69 ms
Rendering
21 ms
Script Evaluation
19 ms
Script Parsing & Compilation
11 ms
Avoids an excessive DOM size - 32 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
32
Maximum DOM Depth
8
Maximum Child Elements
4
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://li.ru/)
0
http://www.li.ru/
630
Keep request counts low and transfer sizes small - 9 requests • 10 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
910 KB
Document
23 KB
Image
33 KB
Stylesheet
13 KB
Other
21 KB
Script
10 KB
Media
00 KB
Font
00 KB
Third-party
31 KB
Eliminate render-blocking resources - Potential savings of 450 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://i.li.ru/ReActive/css/pda.css
3 KB630
Enable text compression - Potential savings of 1 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://www.li.ru/
3 KB1 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://li.ru/
0 ms547 ms0 KB0 KB301text/html
http://www.li.ru/
550 ms1085 ms3 KB3 KB200text/htmlDocument
http://i.li.ru/ReActive/css/pda.css
1133 ms1689 ms3 KB8 KB200text/cssStylesheet
http://www.li.ru/adv/advtm.html?p=6&span-name=mobile_liru
1153 ms1688 ms1 KB0 KB200text/htmlDocument
http://counter.yadro.ru/hit?r;s412*660*24;uhttp%3A//www.li.ru/;0.1505255865836843
1691 ms2236 ms0 KB0 KB302text/html
http://i.li.ru/ReActive/i/pda/ma-nav/bg.png
1692 ms2079 ms1 KB1 KB200image/pngImage
http://i.li.ru/ReActive/i/pda/ma-nav/li-a.png
1693 ms2057 ms1 KB1 KB200image/pngImage
http://www.liveinternet.ru/cgi-bin/adv.fcgi?qtype=parent,javascript&p=6&span-name=mobile_liru&ref=http%3A//www.li.ru/
1724 ms2272 ms0 KB0 KB200text/htmlScript
http://counter.yadro.ru/hit?q;r;s412*660*24;uhttp%3A//www.li.ru/;0.1505255865836843
2236 ms2629 ms0 KB0 KB200image/gifImage
Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Minimize Critical Requests Depth - 1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 540 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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://i.li.ru/ReActive/css/pda.css

Size 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="//www.li.ru/index-statpda.html">Статистика сайтов</a> and 3 others are close to other tap targets .

Configure 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.

Configuring a viewport specifying width=device-width instead of width=320 will allow your page to adapt for devices of various widths. This may require additional work if the styling on your page relies on a fixed-width layout.

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://i.li.ru/ReActive/css/pda.css (73 minutes)

Optimize 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://i.li.ru/ReActive/i/pda/ma-nav/li-a.png could save 853B (92% reduction).
Compressing http://i.li.ru/ReActive/i/pda/ma-nav/bg.png could save 850B (78% reduction).

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

Compressing http://www.li.ru/ could save 1.4KiB (54% reduction).
Compressing http://www.li.ru/adv/advtm.html?p=6&span-name=mobile_liru could save 128B (31% reduction).

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 628B (28% reduction).

Minifying http://i.li.ru/ReActive/css/pda.css could save 628B (28% reduction) after compression.

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 p*** times.

Minify HTML for the following resources to reduce their size by 344B (14% reduction).

Minifying http://www.li.ru/ could save 344B (14% reduction).
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does li.ru use compression?

li.ru does not use compression.
Original size: 2.55 KB
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  83
Vendor reliability:
  83
Privacy:
  83
Child safety:
  74

+ SSL Checker - SSL Certificate Verify

li.ru supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: *.li.ru
Organization:
Location:
Issuer: COMODO RSA Domain Validation Secure Server CA
Valid from: Jan 7 00:00:00 2018 GMT
Valid until: Jan 6 23:59:59 2021 GMT
Authority: Is not a CA
Keysize: 2048 Bits
Common Name: COMODO RSA Domain Validation Secure Server CA
Organization: COMODO CA Limited
Location: Salford, Greater Manchester, GB
Issuer: COMODO RSA Certification Authority
Valid from: Feb 12 00:00:00 2014 GMT
Valid until: Feb 11 23:59:59 2029 GMT
Authority: Is a CA
Keysize: 2048 Bits
Common Name: COMODO RSA Certification Authority
Organization: COMODO CA Limited
Location: Salford, Greater Manchester, GB
Issuer: AddTrust External CA Root
Valid from: May 30 10:48:38 2000 GMT
Valid until: May 30 10:48:38 2020 GMT
Authority: Is a CA
Keysize: 4096 Bits

+ Verify HTTP/2 Support

li.ru does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx/1.10.2
Date: Tue, 01 Oct 2019 20:40:07 GMT
Content-Type: text/html; charset=windows-1251
Content-Length: 308
Connection: keep-alive
Location: http://www.li.ru/

HTTP/1.1 200 OK
Server: nginx/1.10.2
Date: Tue, 01 Oct 2019 20:40:07 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 2612
Connection: keep-alive
Accept-Ranges: bytes
Expires: Sun, 30 Sep 2018 21:00:00 GMT
pragma: no-cache
cache-control: no-cache

+ DNS Lookup

Type Ip Target TTL
A 88.212.202.1 900
MX emx.mail.ru 900
SOA 900
Mname ns.liveinternet.ru
Rname hostmaster.liveinternet.ru
Serial Number 2019062201
Refresh 10800
Retry 3600
Expire 604800
Minimum TTL 0
TXT 900
NS ns2.li.ru 900
NS ns.li.ru 900

+ Whois Lookup

Domain Created:
2000-03-16
Domain Age:
19 years 6 months 16 days  
WhoIs:
 

whois lookup at whois.tcinet.ru...
% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: LI.RU
nserver: ns2.li.ru. 88.212.202.37
nserver: ns.li.ru. 88.212.202.56
state: REGISTERED, DELEGATED, VERIFIED
org: Ventail Limited
registrar: RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created: 2000-03-16T14:51:12Z
paid-till: 2020-03-31T21:00:00Z
free-date: 2020-05-02
source: TCI

Last updated on 2019-10-01T20:36:30Z
Last update was 52 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with li.ru in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

magoanael.com.br
5 secs
cadsans.com
7 secs
niaozhan.org
7 secs
avcom.co.za
34 secs
tattooedmomphilly.com
1 min
successvalley.tech
1 min
avandermeulentransport.nl
1 min
kkiq.com
1 min
cardhouse.me
2 mins
ourmidland.com
2 mins

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
li.ru widget