Rus.Ec rus.ec

Gen.Lib.Rus.Ec

gen.lib.rus.ec receives about 1,433,455 unique visitors and 10,449,884 (7.29 per visitor) page views per day which should earn about $32,502.90/day from advertising revenue. Estimated site value is $23,727,125.66. According to Alexa Traffic Rank gen.lib.rus.ec is ranked number 1,486 in the world and 0.0316% of global Internet users visit it. Site is hosted in Cotton Ground, Saint Thomas Lowland, 410001, St Kitts and Nevis and links to network IP address 198.167.223.167. This server doesn't support HTTPS and doesn't support HTTP/2.

About - gen.lib.rus.ec

Некоммерческая библиотека литературы на русском языке.
Library Genesis is a scientific community targeting collection of books on natural science disciplines and engineering.
Edit Site Info

Technologies used on Website

Web Servers
Nginx
Reverse proxies
Nginx

gen.lib.rus.ec Profile

Title: Library Genesis
Description: Некоммерческая библиотека литературы на русском языке.
Keywords: library genesis
Last update was 153 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is gen.lib.rus.ec?

1.4M daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
1,433,455
Monthly Unique Visitors:
34,402,920
Pages per Visit:
7.29
Daily Pageviews:
10,449,884
Alexa Rank:
1,486 visit alexa
Alexa Reach:
0.0316%   (of global internet users)
Avg. visit duration:
08:11
Bounce rate:
18.95%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
90.07%
Referral:
1.57%
Search:
3.36%
Social:
2.51%
Paid:
0.06%

Visitors by country

Users%Pageviews%Rank
United States 14.3%11.5%2155
India 11.9%12.6%1138
China 7.1%5.1%2122
Iran 5.6%5.9%988
France 3.0%3.5%1494
Canada 2.8%2.1%1311
Germany 2.6%2.1%2526
Ethiopia 2.4%2.6%74
Sudan 2.4%3.4%253
Romania 2.3%5.5%281
Spain 2.2%1.6%1557
Algeria 2.2%2.7%390
Brazil 2.0%3.5%3168
Indonesia 2.0%2.2%1186
Nigeria 1.8%1.4%836
Egypt 1.8%1.7%1122
Japan 1.6%1.8%8231
Morocco 1.6%1.6%410
Mexico 1.4%1.8%2203
Australia 1.4%1.3%1635
Turkey 1.3%1.2%2314
Korea, Republic of 1.2%1.3%3307
Netherlands 0.9%0.6%1815
Saudi Arabia 0.8%0.7%2093
Peru 0.8%3.4%676
Taiwan 0.8%0.6%3343
Pakistan 0.8%0.7%2477
Tanzania 0.7%0.4%290
Czech Republic 0.7%0.6%1038
Congo 0.7%1.2%64
South Africa 0.7%0.7%1885
Viet Nam 0.6%0.7%2234
Hong Kong 0.6%0.4%2126
Libya 0.6%0.9%506
Malaysia 0.6%0.6%1802
Yemen 0.5%0.6%414
Israel 0.5%0.4%1447
Estonia 0.5%0.5%181

Where do visitors go on this site?

Reach%Pageviews%PerUser
lib.rus.ec
96.37%99.29%7.39
rus.ec
3.54%0.69%1.4
OTHER
0%0.02%0

Competitive Data

SEMrush
Domain:
  gen.lib.rus.ec
Rank:
(Rank based on keywords, cost and organic traffic)
  322,807
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  514
Organic Traffic:
(Number of visitors coming from top 20 search results)
  3,608
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $70.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:
  68
Page Authority:
  61
MozRank:
  6

+ How socially engaged is gen.lib.rus.ec?

Facebook:
  3
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:
rus.ec
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:
rus.ec
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 gen.lib.rus.ec can earn?

Daily Revenue:
$32,502.90
Monthly Revenue:
$975,087.00
Yearly Revenue:
$11,863,558.50
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 1,201,737$13,783.92
Ethiopia 271,697$2,241.50
India 1,316,685$2,106.70
France 365,746$1,719.01
China 532,944$1,646.80
Canada 219,448$1,538.33
Germany 219,448$1,059.93
Australia 135,848$1,022.94
Iran 616,543$715.19
Romania 574,744$678.20
Brazil 365,746$647.37
Japan 188,098$601.91
Nigeria 146,298$383.30
Peru 355,296$380.17
South Africa 73,149$322.59
Netherlands 62,699$319.14
Korea, Republic of 135,848$315.17
Indonesia 229,897$282.77
Algeria 282,147$253.93
Israel 41,800$244.11
Malaysia 62,699$189.98
Spain 167,198$185.59
Mexico 188,098$182.45
Saudi Arabia 73,149$147.76
Sudan 355,296$145.67
Hong Kong 41,800$144.21
Egypt 177,648$143.89
Tanzania 41,800$142.54
Turkey 125,399$136.68
Czech Republic 62,699$136.06
Taiwan 62,699$119.13
Estonia 52,249$109.20
Morocco 167,198$96.97
Congo 125,399$89.03
Libya 94,049$82.76
Pakistan 73,149$77.54
Yemen 62,699$57.06
Viet Nam 73,149$53.40

How much money do gen.lib.rus.ec lose due to Adblock?

Daily Revenue Loss:
$5,308.74
Monthly Revenue Loss:
$159,262.13
Yearly Revenue Loss:
$1,937,689.20
Daily Pageviews Blocked:
1,476,778
Monthly Pageviews Blocked:
44,303,328
Yearly Pageviews Blocked:
539,023,827
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 216,313$2,481.11
India 368,672$589.88
Canada 54,862$384.58
Germany 63,640$307.38
China 69,283$214.08
Australia 27,170$204.59
France 40,232$189.09
Indonesia 133,341$164.01
Romania 120,696$142.42
Iran 98,647$114.43
Netherlands 10,659$54.25
Israel 7,942$46.38
Ethiopia 5,434$44.83
Brazil 21,945$38.84
Peru 35,530$38.02
Spain 31,768$35.26
Saudi Arabia 15,361$31.03
Estonia 13,585$28.39
Pakistan 23,408$24.81
Taiwan 10,032$19.06
Japan 5,643$18.06
Mexico 16,929$16.42
Malaysia 5,016$15.20
Hong Kong 4,180$14.42
Czech Republic 6,270$13.61
Algeria 14,107$12.70
Korea, Republic of 5,434$12.61
Turkey 8,778$9.57
Yemen 10,032$9.13
Nigeria 2,926$7.67
Egypt 8,882$7.19
South Africa 1,463$6.45
Sudan 7,106$2.91
Tanzania 836$2.85
Viet Nam 2,926$2.14
Morocco 3,344$1.94
Congo 2,508$1.78
Libya 1,881$1.66

How much is gen.lib.rus.ec worth?

Website Value:
$23,727,125.66

+ Where is gen.lib.rus.ec hosted?

Server IP:
198.167.223.167
ASN:
AS37560 
ISP:
CYBERDYNE 
Server Location:
Cotton Ground
Saint Thomas Lowland, 12
410001
St Kitts and Nevis, KN
 

Other sites hosted on 198.167.223.167

There are no other sites hosted on this IP

+ How fast does gen.lib.rus.ec load?

Average Load Time:
(3242 ms) 35 % 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 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

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.3 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.3 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.3 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 0.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize 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.

Screenshot Thumbnails

This is what the load of your site looked like.

Minify CSS - Potential savings of 2 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
http://gen.lib.rus.ec/menu.css
9 KB2 KB
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
53 ms2 ms1 ms
Avoids enormous network payloads - Total size was 32 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://gen.lib.rus.ec/paginator3000.js
12 KB
http://gen.lib.rus.ec/menu.css
9 KB
http://gen.lib.rus.ec/
7 KB
http://gen.lib.rus.ec/paginator3000.css
2 KB
http://gen.lib.rus.ec/img/drop.png
1 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. Learn more.

Category
Time Spent
Other
20 ms
Style & Layout
18 ms
Rendering
6 ms
Parse HTML & CSS
5 ms
Script Evaluation
2 ms
Script Parsing & Compilation
2 ms
Avoid an excessive DOM size - 912 elements
A large DOM will 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
912
Maximum DOM Depth
12
Maximum Child Elements
42
Minify JavaScript - Potential savings of 3 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://gen.lib.rus.ec/paginator3000.js
12 KB3 KB
Keep request counts low and transfer sizes small - 5 requests • 32 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
532 KB
Script
112 KB
Stylesheet
211 KB
Document
17 KB
Image
11 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 90 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://gen.lib.rus.ec/menu.css
9 KB70
http://gen.lib.rus.ec/paginator3000.css
2 KB110
Enable text compression - Potential savings of 15 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://gen.lib.rus.ec/paginator3000.js
12 KB9 KB
http://gen.lib.rus.ec/menu.css
9 KB7 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://gen.lib.rus.ec/
0 ms372 ms7 KB45 KB200text/htmlDocument
http://gen.lib.rus.ec/menu.css
386 ms895 ms9 KB9 KB200text/cssStylesheet
http://gen.lib.rus.ec/paginator3000.css
386 ms722 ms2 KB2 KB200text/cssStylesheet
http://gen.lib.rus.ec/paginator3000.js
386 ms1559 ms12 KB12 KB200application/javascriptScript
http://gen.lib.rus.ec/img/drop.png
899 ms1247 ms1 KB1 KB200image/pngImage
Uses efficient cache policy on static assets - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://gen.lib.rus.ec/paginator3000.js
0 ms12 KB
http://gen.lib.rus.ec/menu.css
0 ms9 KB
http://gen.lib.rus.ec/paginator3000.css
0 ms2 KB
http://gen.lib.rus.ec/img/drop.png
0 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
392 ms
8 ms
915 ms
13 ms
1577 ms
6 ms
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. 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.

Avoid chaining critical requests - 3 chains 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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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.

Efficiently encode images
Optimized images load faster and consume less cellular data. 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.


Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

First Contentful Paint (3G) 2190 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.1 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.1 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.1 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.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize 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.

Screenshot Thumbnails

This is what the load of your site looked like.

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
190 ms8 ms3 ms
Minify CSS - Potential savings of 2 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
http://gen.lib.rus.ec/menu.css
9 KB2 KB
Avoids enormous network payloads - Total size was 32 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://gen.lib.rus.ec/paginator3000.js
12 KB
http://gen.lib.rus.ec/menu.css
9 KB
http://gen.lib.rus.ec/
7 KB
http://gen.lib.rus.ec/paginator3000.css
2 KB
http://gen.lib.rus.ec/img/drop.png
1 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Other
71 ms
Style & Layout
63 ms
Rendering
23 ms
Parse HTML & CSS
22 ms
Script Evaluation
9 ms
Script Parsing & Compilation
6 ms
Avoid an excessive DOM size - 912 elements
A large DOM will 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
912
Maximum DOM Depth
12
Maximum Child Elements
42
Minify JavaScript - Potential savings of 3 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://gen.lib.rus.ec/paginator3000.js
12 KB3 KB
Keep request counts low and transfer sizes small - 5 requests • 32 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
532 KB
Script
112 KB
Stylesheet
211 KB
Document
17 KB
Image
11 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 210 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://gen.lib.rus.ec/menu.css
9 KB180
http://gen.lib.rus.ec/paginator3000.css
2 KB330
Enable text compression - Potential savings of 15 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://gen.lib.rus.ec/paginator3000.js
12 KB9 KB
http://gen.lib.rus.ec/menu.css
9 KB7 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://gen.lib.rus.ec/
0 ms506 ms7 KB45 KB200text/htmlDocument
http://gen.lib.rus.ec/menu.css
518 ms891 ms9 KB9 KB200text/cssStylesheet
http://gen.lib.rus.ec/paginator3000.css
519 ms998 ms2 KB2 KB200text/cssStylesheet
http://gen.lib.rus.ec/paginator3000.js
519 ms1005 ms12 KB12 KB200application/javascriptScript
http://gen.lib.rus.ec/img/drop.png
1001 ms1350 ms1 KB1 KB200image/pngImage
Uses efficient cache policy on static assets - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://gen.lib.rus.ec/paginator3000.js
0 ms12 KB
http://gen.lib.rus.ec/menu.css
0 ms9 KB
http://gen.lib.rus.ec/paginator3000.css
0 ms2 KB
http://gen.lib.rus.ec/img/drop.png
0 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
531 ms
5 ms
1022 ms
9 ms
1031 ms
7 ms
1038 ms
6 ms
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.

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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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.

Avoid chaining critical requests - 3 chains 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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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 510 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.

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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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

RU renders only 5 pixels tall (14 CSS pixels) .
DOWNLOAD and 5 others render only 5 pixels tall (14 CSS pixels) .
2M renders only 7 pixels tall (18 CSS pixels) .
Introducing Li…p application! and 1 others render only 5 pixels tall (14 CSS pixels) .
Search with mask (word*): and 5 others render only 5 pixels tall (14 CSS pixels) .
Author(s) and 13 others render only 5 pixels tall (14 CSS pixels) .
The column set default and 6 others render only 5 pixels tall (14 CSS pixels) .
LibGen Search options: renders only 5 pixels tall (14 CSS pixels) .
Language renders only 5 pixels tall (14 CSS pixels) .

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

Your page has 1 blocking script resources and 2 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://gen.lib.rus.ec/paginator3000.js
Optimize CSS Delivery of the following:

http://gen.lib.rus.ec/menu.css
http://gen.lib.rus.ec/paginator3000.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="#" class="drop">OTHERS</a> is close to 1 other tap targets .
The tap target <a href="https://wiki.m…libgen_desktop">Introducing Li…p application!</a> and 1 others are close to other tap targets .
The tap target <input id="searchform" name="req"> is close to 2 other tap targets .
The tap target <input type="submit"> is close to 1 other tap targets .
The tap target <input type="radio" name="lg_topic"> and 17 others are close to other tap targets .
The tap target <a href="/">LibGen (Sci-Tech)</a> and 6 others are close to other tap targets .
The tap target <a href="">Language</a> is close to 2 other tap targets .

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

Configure a viewport for this page.

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://gen.lib.rus.ec/img/drop.png (expiration not specified)
http://gen.lib.rus.ec/menu.css (expiration not specified)
http://gen.lib.rus.ec/paginator3000.css (expiration not specified)
http://gen.lib.rus.ec/paginator3000.js (expiration not specified)

Size 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,030 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <ul id="menu">RU FO…ar: Journalism</ul> falls outside the viewport.

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

Compressing http://gen.lib.rus.ec/paginator3000.js could save 8.7KiB (73% reduction).
Compressing http://gen.lib.rus.ec/menu.css could save 6.6KiB (74% reduction).
Compressing http://gen.lib.rus.ec/paginator3000.css could save 1.1KiB (60% reduction).

Reduce server response time

In our test, your server responded in 0.25 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.

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

Minifying http://gen.lib.rus.ec/menu.css could save 2.7KiB (31% reduction).
Minifying http://gen.lib.rus.ec/paginator3000.css could save 684B (38% reduction).

Minify JavaScript

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

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

Minifying http://gen.lib.rus.ec/paginator3000.js could save 3.2KiB (28% reduction).

Optimize images

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

Optimize the following images to reduce their size by 906B (86% reduction).

Compressing http://gen.lib.rus.ec/img/drop.png could save 906B (86% 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.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does gen.lib.rus.ec use compression?

gen.lib.rus.ec use gzip compression.
Original size: 45.11 KB
Compressed size: 7.09 KB
File reduced by: 38.02 KB (84%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  93
Vendor reliability:
  93
Privacy:
  93
Child safety:
  92

+ SSL Checker - SSL Certificate Verify

gen.lib.rus.ec does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

gen.lib.rus.ec does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Библиотеки/Электронные

+ Http Header

Server: nginx
Date: Thu, 02 Jan 2020 15:43:11 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 7261
Connection: keep-alive
Set-Cookie: lg_topic=libgen; expires=Mon, 06-Jan-2020 19:43:11 GMT; Max-Age=360000
Vary: Accept-Encoding
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
HINFO 3600

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

Currently Not Available
Last update was 153 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

limomake.tumblr.com
40 secs
kivilinn.ope.ee
57 secs
kiss4d.com
1 min
techcluter.com
2 mins
lightingcoast.com
2 mins
kisreport.com
2 mins
libtechbwn.blogspot.com
3 mins
kirjad.edu.ee
3 mins
baidu.com
3 mins
esportbets.io
4 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

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!
gen.lib.rus.ec widget