1under.Ru - Info 1under.ru

1under.ru receives about 423,061 unique visitors and 1,269,183 (3.00 per visitor) page views per day which should earn about $5,698.63/day from advertising revenue. Estimated site value is $3,435,629.74. According to Alexa Traffic Rank 1under.ru is ranked number 1,141 in the world and 0% of global Internet users visit it. Site is hosted in Moscow, 48, Russia and links to network IP address 89.208.145.156. This server doesn't support HTTPS and doesn't support HTTP/2.

About - 1under.ru

1under.ru - /
Edit Site Info

Technologies used on Website

Currently Not Available

1under.ru Profile

Title: 2under.ru - надежная партнерская программа вебмастеру / описание
Keywords: 1under.ru,-,,,,,/,
Last update was 245 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is 1under.ru?

423.1K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
423,061
Monthly Unique Visitors:
10,153,464
Pages per Visit:
3.00
Daily Pageviews:
1,269,183
Alexa Rank:
1,141 visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
0%
Referral:
0%
Search:
0%
Social:
0%
Paid:
0%

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  1under.ru
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.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 1under.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:
1under.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:
1under.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 1under.ru can earn?

Daily Revenue:
$5,698.63
Monthly Revenue:
$170,958.90
Yearly Revenue:
$2,079,999.95
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do 1under.ru lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is 1under.ru worth?

Website Value:
$3,435,629.74

+ Where is 1under.ru hosted?

Server IP:
89.208.145.156
ASN:
AS12695 
ISP:
JSC Digital Network 
Server Location:
Moscow
48
Russia, RU
 

Other sites hosted on 89.208.145.156

+ How fast does 1under.ru load?

Average Load Time:
n/a ms n/a % 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 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)2.0s 73% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 73% 19% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 19% 6% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 6%
First Input Delay (FID)24ms 96% of loads for this page have a fast (<50ms) First Input Delay (FID) 96% 1% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 1% 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 AVERAGE 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)2.0s 73% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 73% 19% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 19% 6% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 6%
First Input Delay (FID)24ms 96% of loads for this page have a fast (<50ms) First Input Delay (FID) 96% 1% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 1% 1% of loads for this page have a slow (>250ms) First Input Delay (FID) 1%

Lab Data

Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.5 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.5 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.5 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.5 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.
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.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 88 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://2under.ru/images/img_02.jpg
20 KB
http://2under.ru/
18 KB
http://2under.ru/images/img_01.jpg
13 KB
http://2under.ru/images/img_04.jpg
10 KB
http://2under.ru/images/img_03.jpg
4 KB
http://2under.ru/images/img_08.jpg
3 KB
https://megastock.ru/Doc/88x31_accept/blue_rus.gif
3 KB
http://2under.ru/images/img_05.jpg
3 KB
http://2under.ru/images/table.css
3 KB
http://2under.ru/images/img_06.jpg
3 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
Style & Layout
47 ms
Other
40 ms
Rendering
36 ms
Parse HTML & CSS
7 ms
Script Evaluation
5 ms
Garbage Collection
1 ms
Script Parsing & Compilation
1 ms
Serve images in next-gen formats - Potential savings of 26 KB
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.

URL
SizePotential Savings
http://2under.ru/images/img_02.jpg
20 KB16 KB
http://2under.ru/images/img_01.jpg
13 KB10 KB
Avoids an excessive DOM size - 286 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
286
Maximum DOM Depth
32
Maximum Child Elements
19
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://1under.ru/)
0
http://2under.ru/
190
Keep request counts low and transfer sizes small - 21 requests • 88 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
2188 KB
Image
1567 KB
Document
118 KB
Stylesheet
13 KB
Other
31 KB
Script
10 KB
Media
00 KB
Font
00 KB
Third-party
55 KB
Eliminate render-blocking resources - Potential savings of 70 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://2under.ru/skriptik.js
0 KB110
Enable text compression - Potential savings of 11 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://2under.ru/
17 KB10 KB
http://2under.ru/images/table.css
2 KB2 KB
Efficiently encode images - Potential savings of 24 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://2under.ru/images/img_02.jpg
20 KB12 KB
http://2under.ru/images/img_01.jpg
13 KB7 KB
http://2under.ru/images/img_04.jpg
10 KB5 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://1under.ru/
0 ms568 ms0 KB0 KB301text/html
http://2under.ru/
569 ms853 ms18 KB17 KB200text/htmlDocument
http://2under.ru/images/table.css
871 ms1017 ms3 KB2 KB200text/cssStylesheet
http://2under.ru/skriptik.js
871 ms1012 ms0 KB0 KB200application/javascriptScript
http://2under.ru/images/img_01.jpg
871 ms1152 ms13 KB13 KB200image/jpegImage
http://2under.ru/images/img_02.jpg
872 ms1281 ms20 KB20 KB200image/jpegImage
http://2under.ru/images/img_04.jpg
1019 ms1425 ms10 KB10 KB200image/jpegImage
http://2under.ru/images/4.gif
1019 ms1159 ms2 KB1 KB200image/gifImage
http://www.megastock.ru/Doc/88x31_accept/blue_rus.gif
1019 ms1157 ms0 KB0 KB301text/html
http://2under.ru/images/batt.jpg
1020 ms1160 ms1 KB1 KB200image/jpegImage
http://2under.ru/images/img_03.jpg
1025 ms1437 ms4 KB3 KB200image/jpegImage
http://2under.ru/images/img_05.jpg
1028 ms1290 ms3 KB2 KB200image/jpegImage
http://2under.ru/images/img_06.jpg
1029 ms1304 ms3 KB2 KB200image/jpegImage
http://2under.ru/images/img_07.jpg
1029 ms1304 ms2 KB2 KB200image/jpegImage
http://2under.ru/images/img_08.jpg
1029 ms1480 ms3 KB3 KB200image/jpegImage
http://2under.ru/images/border-left.jpg
1030 ms1429 ms1 KB1 KB200image/jpegImage
http://2under.ru/images/border-right.jpg
1031 ms1444 ms1 KB1 KB200image/jpegImage
http://counter.yadro.ru/hit?t44.10;r;s800*600*24;uhttp%3A//2under.ru/;0.6589417974842848
1074 ms1216 ms0 KB0 KB302text/html
http://2under.ru/images/bottom.jpg
1075 ms1486 ms2 KB2 KB200image/jpegImage
https://megastock.ru/Doc/88x31_accept/blue_rus.gif
1157 ms1433 ms3 KB3 KB200image/gifImage
http://counter.yadro.ru/hit?q;t44.10;r;s800*600*24;uhttp%3A//2under.ru/;0.6589417974842848
1216 ms1492 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 16 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://2under.ru/images/img_02.jpg
0 ms20 KB
http://2under.ru/images/img_01.jpg
0 ms13 KB
http://2under.ru/images/img_04.jpg
0 ms10 KB
http://2under.ru/images/img_03.jpg
0 ms4 KB
http://2under.ru/images/img_08.jpg
0 ms3 KB
https://megastock.ru/Doc/88x31_accept/blue_rus.gif
0 ms3 KB
http://2under.ru/images/img_05.jpg
0 ms3 KB
http://2under.ru/images/table.css
0 ms3 KB
http://2under.ru/images/img_06.jpg
0 ms3 KB
http://2under.ru/images/img_07.jpg
0 ms2 KB
http://2under.ru/images/bottom.jpg
0 ms2 KB
http://2under.ru/images/4.gif
0 ms2 KB
http://2under.ru/images/batt.jpg
0 ms1 KB
http://2under.ru/images/border-left.jpg
0 ms1 KB
http://2under.ru/images/border-right.jpg
0 ms1 KB
http://2under.ru/skriptik.js
0 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
879 ms
12 ms
1047 ms
48 ms
1100 ms
21 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
135 ms3 ms1 ms
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.

Minimize Critical Requests Depth - 2 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.

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 280 ms
Time To First Byte identifies the time at which your server sends a response. 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.


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

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.8 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.8 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.
First Contentful Paint (3G) 3405 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 3.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.8 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.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 286 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
286
Maximum DOM Depth
32
Maximum Child Elements
19
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://1under.ru/)
0
http://2under.ru/
630
Keep request counts low and transfer sizes small - 21 requests • 88 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
2188 KB
Image
1567 KB
Document
118 KB
Stylesheet
13 KB
Other
31 KB
Script
10 KB
Media
00 KB
Font
00 KB
Third-party
55 KB
Eliminate render-blocking resources - Potential savings of 180 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://2under.ru/skriptik.js
0 KB330
Efficiently encode images - Potential savings of 24 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://2under.ru/images/img_02.jpg
20 KB12 KB
http://2under.ru/images/img_01.jpg
13 KB7 KB
http://2under.ru/images/img_04.jpg
10 KB5 KB
Enable text compression - Potential savings of 11 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://2under.ru/
17 KB10 KB
http://2under.ru/images/table.css
2 KB2 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://1under.ru/
0 ms713 ms0 KB0 KB301text/html
http://2under.ru/
714 ms1284 ms18 KB17 KB200text/htmlDocument
http://2under.ru/images/table.css
1303 ms1443 ms3 KB2 KB200text/cssStylesheet
http://2under.ru/skriptik.js
1304 ms1756 ms0 KB0 KB200application/javascriptScript
http://2under.ru/images/img_01.jpg
1304 ms1679 ms13 KB13 KB200image/jpegImage
http://2under.ru/images/img_02.jpg
1305 ms1718 ms20 KB20 KB200image/jpegImage
http://2under.ru/images/img_04.jpg
1681 ms1961 ms10 KB10 KB200image/jpegImage
http://2under.ru/images/4.gif
1719 ms1865 ms2 KB1 KB200image/gifImage
http://www.megastock.ru/Doc/88x31_accept/blue_rus.gif
1758 ms2174 ms0 KB0 KB301text/html
http://2under.ru/images/batt.jpg
1758 ms1900 ms1 KB1 KB200image/jpegImage
http://2under.ru/images/img_03.jpg
1762 ms2175 ms4 KB3 KB200image/jpegImage
http://2under.ru/images/img_05.jpg
1766 ms1907 ms3 KB2 KB200image/jpegImage
http://2under.ru/images/img_06.jpg
1767 ms2041 ms3 KB2 KB200image/jpegImage
http://2under.ru/images/img_07.jpg
1767 ms1999 ms2 KB2 KB200image/jpegImage
http://2under.ru/images/img_08.jpg
1767 ms2040 ms3 KB3 KB200image/jpegImage
http://2under.ru/images/border-left.jpg
1768 ms2047 ms1 KB1 KB200image/jpegImage
http://2under.ru/images/border-right.jpg
1769 ms2119 ms1 KB1 KB200image/jpegImage
http://counter.yadro.ru/hit?t44.10;r;s412*660*24;uhttp%3A//2under.ru/;0.4053061417562338
1817 ms2097 ms0 KB0 KB302text/html
http://2under.ru/images/bottom.jpg
1819 ms2166 ms2 KB2 KB200image/jpegImage
http://counter.yadro.ru/hit?q;t44.10;r;s412*660*24;uhttp%3A//2under.ru/;0.4053061417562338
2097 ms2405 ms0 KB0 KB200image/gifImage
https://megastock.ru/Doc/88x31_accept/blue_rus.gif
2174 ms2870 ms3 KB3 KB200image/gifImage
Serve static assets with an efficient cache policy - 16 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://2under.ru/images/img_02.jpg
0 ms20 KB
http://2under.ru/images/img_01.jpg
0 ms13 KB
http://2under.ru/images/img_04.jpg
0 ms10 KB
http://2under.ru/images/img_03.jpg
0 ms4 KB
http://2under.ru/images/img_08.jpg
0 ms3 KB
https://megastock.ru/Doc/88x31_accept/blue_rus.gif
0 ms3 KB
http://2under.ru/images/img_05.jpg
0 ms3 KB
http://2under.ru/images/table.css
0 ms3 KB
http://2under.ru/images/img_06.jpg
0 ms3 KB
http://2under.ru/images/img_07.jpg
0 ms2 KB
http://2under.ru/images/bottom.jpg
0 ms2 KB
http://2under.ru/images/4.gif
0 ms2 KB
http://2under.ru/images/batt.jpg
0 ms1 KB
http://2under.ru/images/border-left.jpg
0 ms1 KB
http://2under.ru/images/border-right.jpg
0 ms1 KB
http://2under.ru/skriptik.js
0 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1322 ms
12 ms
1796 ms
54 ms
1855 ms
30 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
624 ms13 ms4 ms
Avoids enormous network payloads - Total size was 88 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://2under.ru/images/img_02.jpg
20 KB
http://2under.ru/
18 KB
http://2under.ru/images/img_01.jpg
13 KB
http://2under.ru/images/img_04.jpg
10 KB
http://2under.ru/images/img_03.jpg
4 KB
http://2under.ru/images/img_08.jpg
3 KB
https://megastock.ru/Doc/88x31_accept/blue_rus.gif
3 KB
http://2under.ru/images/img_05.jpg
3 KB
http://2under.ru/images/table.css
3 KB
http://2under.ru/images/img_06.jpg
3 KB
Minimizes main-thread work - 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Rendering
206 ms
Style & Layout
199 ms
Other
176 ms
Parse HTML & CSS
26 ms
Script Evaluation
19 ms
Script Parsing & Compilation
6 ms
Serve images in next-gen formats - Potential savings of 26 KB
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.

URL
SizePotential Savings
http://2under.ru/images/img_02.jpg
20 KB16 KB
http://2under.ru/images/img_01.jpg
13 KB10 KB
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 570 ms
Time To First Byte identifies the time at which your server sends a response. 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.

Minimize Critical Requests Depth - 2 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.

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.

Пароль: and 1 others render only 4 pixels tall (11 CSS pixels) .
Введи число &quot;одиHадцаTь&quot;: renders only 4 pixels tall (10 CSS pixels) .
Описание renders only 4 pixels tall (11 CSS pixels) .
Регистрация and 2 others render only 4 pixels tall (11 CSS pixels) .
Описание renders only 4 pixels tall (11 CSS pixels) .
Стоимость 1000…от 1 до 25 wmz and 8 others render only 4 pixels tall (11 CSS pixels) .
31.05.2019 and 14 others render only 4 pixels tall (11 CSS pixels) .
Ставка выкупа…курсу доллара and 14 others render only 4 pixels tall (11 CSS pixels) .
В связи с нест…этой странице. and 17 others render only 4 pixels tall (11 CSS pixels) .
полном объеме and 1 others render only 4 pixels tall (11 CSS pixels) .
- По контекстн…блокируется). and 36 others render only 4 pixels tall (11 CSS pixels) .
Выплаты осущес…й в аккаунте). and 4 others render only 4 pixels tall (11 CSS pixels) .
Плавающий поп-…баннер 468х60 and 6 others render only 4 pixels tall (11 CSS pixels) .
Регистрация and 3 others render only 4 pixels tall (11 CSS pixels).
© 2under.ru. and 3 others render only 4 pixels tall (10 CSS pixels).

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

Your page has 1 blocking script resources and 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.Remove render-blocking JavaScript:

http://2under.ru/skriptik.js
Optimize CSS Delivery of the following:

http://2under.ru/images/table.css

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://2under.ru/images/4.gif (expiration not specified)
http://2under.ru/images/batt.jpg (expiration not specified)
http://2under.ru/images/border-left.jpg (expiration not specified)
http://2under.ru/images/border-right.jpg (expiration not specified)
http://2under.ru/images/bottom.jpg (expiration not specified)
http://2under.ru/images/img_01.jpg (expiration not specified)
http://2under.ru/images/img_02.jpg (expiration not specified)
http://2under.ru/images/img_03.jpg (expiration not specified)
http://2under.ru/images/img_04.jpg (expiration not specified)
http://2under.ru/images/img_05.jpg (expiration not specified)
http://2under.ru/images/img_06.jpg (expiration not specified)
http://2under.ru/images/img_07.jpg (expiration not specified)
http://2under.ru/images/img_08.jpg (expiration not specified)
http://2under.ru/images/table.css (expiration not specified)
http://2under.ru/skriptik.js (expiration not specified)
https://megastock.ru/Doc/88x31_accept/blue_rus.gif (expiration not specified)

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.

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 <input name="login" class="in"> and 2 others are close to other tap targets .
The tap target <input type="submit" name="go" class="in2"> is close to 3 other tap targets .
The tap target <a href="http://www.webmoney.ru/"></a> is close to 1 other tap targets.
The tap target <a href="http://www.liv…ernet.ru/click"></a> is close to 1 other tap targets.
The tap target <a href="faq.php">FAQ</a> is close to 2 other tap targets.

Optimize images

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

Optimize the following images to reduce their size by 38.7KiB (64% reduction).

Compressing http://2under.ru/images/img_02.jpg could save 14.1KiB (***% reduction).
Compressing http://2under.ru/images/img_01.jpg could save 8.4KiB (66% reduction).
Compressing http://2under.ru/images/img_04.jpg could save 6.5KiB (64% reduction).
Compressing http://2under.ru/images/img_03.jpg could save 2.7KiB (79% reduction).
Compressing http://2under.ru/images/img_08.jpg could save 1.6KiB (54% reduction).
Compressing http://2under.ru/images/img_05.jpg could save 1.3KiB (55% reduction).
Compressing http://2under.ru/images/img_06.jpg could save 1.2KiB (54% reduction).
Compressing http://2under.ru/images/img_07.jpg could save 863B (53% reduction).
Compressing http://2under.ru/images/4.gif could save 802B (57% reduction).
Compressing http://2under.ru/images/bottom.jpg could save 436B (28% reduction).
Compressing http://2under.ru/images/batt.jpg could save 3***B (47% reduction).
Compressing http://2under.ru/images/border-left.jpg could save 235B (45% reduction).
Compressing http://2under.ru/images/border-right.jpg could save 235B (45% 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 12.3KiB (63% reduction).

Compressing http://2under.ru/ could save 10.6KiB (61% reduction).
Compressing http://2under.ru/images/table.css could save 1.7KiB (72% 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 302B (13% reduction).

Minifying http://2under.ru/images/table.css could save 302B (13% 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 HTML
Your HTML is minified. Learn more about minifying HTML.
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.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does 1under.ru use compression?

1under.ru does not use compression.
Original size: 17.16 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:
  12
Vendor reliability:
  12
Privacy:
  12
Child safety:
  7

+ SSL Checker - SSL Certificate Verify

1under.ru does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

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

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Wed, 02 Oct 2019 02:02:37 GMT
Content-Type: text/html; charset=windows-1251
Transfer-Encoding: chunked
Connection: keep-alive
Server: Apache
Location: http://2under.ru/
Set-Cookie: PHPSESSID=3b32543bb7a35392f17e8492ae176589; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Transfer-Encoding: chunked

HTTP/1.1 200 OK
Date: Wed, 02 Oct 2019 02:02:38 GMT
Content-Type: text/html; charset=windows-1251
Transfer-Encoding: chunked
Connection: keep-alive
Server: Apache
Set-Cookie: PHPSESSID=a9ba808c42399af2f8403487e0bef1cc; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache

+ DNS Lookup

Type Ip Target TTL
A 89.208.145.156 3600
SOA 3600
Mname ns1.reg.ru
Rname hostmaster.ns1.reg.ru
Serial Number 1565689208
Refresh 14400
Retry 3600
Expire 604800
Minimum TTL 0
NS ns1.reg.ru 3574
NS ns2.reg.ru 3574

+ Whois Lookup

Domain Created:
2011-08-12
Domain Age:
8 years 1 months 20 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: 1UNDER.RU
nserver: ns1.reg.ru.
nserver: ns2.reg.ru.
state: REGISTERED, DELEGATED, UNVERIFIED
person: Private Person
registrar: REGRU-RU
admin-contact: http://www.reg.ru/whois/admin_contact
created: 2011-08-12T13:17:03Z
paid-till: 2020-08-12T14:17:03Z
free-date: 2020-09-12
source: TCI

Last updated on 2019-10-02T02:46:32Z
Last update was 245 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with 1under.ru in any way. Only publicly available statistics data are displayed.
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!
1under.ru widget