Regnum.Ru - Info receives about 934,467 unique visitors and 1,345,633 (1.44 per visitor) page views per day which should earn about $3,487.88/day from advertising revenue. Estimated site value is $2,548,287.94. According to Alexa Traffic Rank is ranked number 4,232 in the world and 0.0206% of global Internet users visit it. Site is hosted in Moscow, 48, Russia and links to network IP address This server supports HTTPS and doesn't support HTTP/2.

About -

Информационное агентство. Лента новостей политики, экономики, культуры и происшествий.
Информационное агентство REGNUM — федеральное информационное агентство, распространяющее новости России и ближайшего зарубежья от собственных корреспондентов, дочерних агентств и партнеров. Сфера вещания ИА REGNUM сегодня охватывает все регионы России и сопредельные государства Европы, Средней Азии и Закавказья.
Edit Site Info

Technologies used on Website

Font Scripts
Font Awesome
Google Font API
Google Analytics
Programming Languages
Cache Tools
reCAPTCHA Profile

Title: Новости России, СНГ и мира - ИА REGNUM
Keywords: новости, события, мнения, аналитика, Россия, Европа, Азия, мир, информация
Last update was 19 days ago
This can take up to 60 seconds. Please wait...

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

How popular is

0.9M daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
4,232 visit alexa
Alexa Reach:
0.0206%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources


Visitors by country

Russian Federation 62.8%59.9%211
United States 5.0%4.9%15813
Germany 4.5%4.0%3963
Azerbaijan 4.3%5.5%705
Netherlands 3.3%2.8%1087
Canada 1.7%2.9%4397
Uzbekistan 1.6%2.3%314
Belarus 1.3%1.3%605
Poland 1.2%0.9%4747
Lithuania 1.1%0.9%606
Kazakhstan 1.1%1.0%1177
Ukraine 1.1%1.0%2182
Estonia 0.9%2.1%202
United Kingdom 0.8%0.7%11403

Where do visitors go on this site?


Competitive Data

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

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

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

Desktop summary

Root domain:
Last Change Time:
(The last time that the site changed status.)
2019-11-05 05:08:03
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)

Mobile summary

Last Change Time:
(The last time that the site changed status.)
2019-11-05 05:08:03
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)

+ Abusive Experience Report

Root domain:
Last Change Time:
(The last time that the site changed status.)
2019-11-05 05:08:03
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Russian Federation 806,034$1,636.25
United States 65,936$756.29
Canada 39,023$273.55
Germany 53,825$259.98
Netherlands 37,678$191.78
Azerbaijan 74,010$119.16
Estonia 28,258$59.06
United Kingdom 9,419$58.68
Uzbekistan 30,950$37.76
Belarus 17,493$23.79
Poland 12,111$21.92
Lithuania 12,111$21.68
Ukraine 13,456$18.44
Kazakhstan 13,456$9.55

How much money do lose due to Adblock?

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

Daily revenue loss by country

BlockedLost Money
United States 11,868$136.13
Russian Federation 48,362$98.17
Germany 15,609$75.39
Canada 9,756$68.39
Netherlands 6,405$32.60
Azerbaijan 11,842$19.06
Estonia 7,347$15.36
United Kingdom 1,507$9.39
Poland 3,997$7.23
Uzbekistan 4,952$6.04
Lithuania 2,543$4.55
Ukraine 1,749$2.40
Belarus 1,749$2.38
Kazakhstan 404$0.29

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Server Location:
Russia, RU

Other sites hosted on

There are no other sites hosted on this IP

+ How fast does load?

Average Load Time:
(1642 ms) 54 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

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)1.7s % of loads for this page have a fast (<1s) First Contentful Paint (FCP) 56% 33% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 33% 10% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 10%
First Input Delay (FID)372ms 4% of loads for this page have a fast (<100ms) First Input Delay (FID) 4% 82% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 82% 12% of loads for this page have a slow (>300ms) First Input Delay (FID) 12%

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)2.3s 21% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 21% 62% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 62% 15% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 15%
First Input Delay (FID)304ms % of loads for this page have a fast (<100ms) First Input Delay (FID) 73% 21% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 21% 5% of loads for this page have a slow (>300ms) First Input Delay (FID) 5%

Lab Data

Estimated Input Latency 30 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) 9825 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 280 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 5.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 7.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 4.8 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 4.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 260 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 7.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.

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

Start Time
End Time
582 ms
9 ms
1020 ms
18 ms
1209 ms
37 ms
1253 ms
7 ms
1260 ms
7 ms
1267 ms
51 ms
1318 ms
9 ms
1333 ms
30 ms
1367 ms
8 ms
1379 ms
18 ms
1397 ms
7 ms
1404 ms
12 ms
1422 ms
6 ms
1427 ms
37 ms
1465 ms
10 ms
1483 ms
6 ms
1490 ms
7 ms
1499 ms
6 ms
1587 ms
5 ms
1834 ms
128 ms
2113 ms
22 ms
2252 ms
7 ms
Reduce JavaScript execution time - 1.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
933 ms28 ms7 ms
538 ms502 ms33 ms
389 ms346 ms8 ms
256 ms235 ms17 ms
157 ms126 ms22 ms
145 ms117 ms10 ms
65 ms47 ms18 ms
62 ms46 ms16 ms
Remove unused CSS - Potential savings of 43 KB
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.

SizePotential Savings
@charset "UTF-8";@font-face{font-family:'EB Garamond'; ... } ...
43 KB43 KB
Avoids enormous network payloads - Total size was 1,125 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

306 KB
164 KB
112 KB
95 KB
92 KB
72 KB
56 KB
52 KB
51 KB
36 KB
Minimize main-thread work - 2.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
Script Evaluation
1488 ms
483 ms
Style & Layout
213 ms
207 ms
Script Parsing & Compilation
137 ms
Parse HTML & CSS
66 ms
Serve images in next-gen formats - Potential savings of 383 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.

SizePotential Savings
164 KB140 KB
112 KB99 KB
71 KB55 KB
56 KB48 KB
50 KB42 KB
Avoids an excessive DOM size - 718 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

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

Time Spent
Keep request counts low and transfer sizes small - 68 requests • 1,125 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
681125 KB
26623 KB
20464 KB
229 KB
178 KB
31 KB
00 KB
00 KB
43229 KB
Eliminate render-blocking resources - Potential savings of 2,240 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.

SizePotential Savings,700
1 KB780
95 KB2130
306 KB3330
Enable text compression - Potential savings of 279 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

SizePotential Savings
306 KB217 KB
95 KB62 KB
Efficiently encode images - Potential savings of 113 KB
Optimized images load faster and consume less cellular data. Learn more.

SizePotential Savings
71 KB42 KB
56 KB38 KB
50 KB33 KB
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms268 ms0 KB0 KB301text/html
269 ms555 ms29 KB125 KB200text/htmlDocument
569 ms577 ms0 KB0 KB-1Script,700
574 ms592 ms1 KB3 KB200text/cssStylesheet
574 ms580 ms0 KB0 KB-1Stylesheet
574 ms581 ms0 KB0 KB-1Stylesheet
574 ms581 ms0 KB0 KB-1Script
575 ms987 ms95 KB95 KB200application/javascriptScript
575 ms1172 ms306 KB306 KB200application/javascriptScript
575 ms581 ms0 KB0 KB-1Script
581 ms604 ms3 KB8 KB200application/javascriptScript
583 ms829 ms36 KB155 KB200text/javascriptScript
575 ms582 ms0 KB0 KB-1Script
606 ms907 ms35 KB151 KB200application/javascriptScript
576 ms581 ms0 KB0 KB-1Script
830 ms974 ms7 KB6 KB200image/svg+xmlImage
908 ms1047 ms2 KB1 KB200image/pngImage
580 ms583 ms0 KB0 KB-1Script
1210 ms1356 ms2 KB7 KB200text/htmlXHR
1217 ms1222 ms0 KB0 KB-1Script
1228 ms1262 ms52 KB212 KB200application/javascriptScript
1229 ms1793 ms92 KB357 KB200application/javascriptScript;s412*660*24;uhttps%3A//;h%u041D%u043E%u0432%u043E%u0441%u0442%u0438%20%u0420%u043E%u0441%u0441%u0438%u0438%2C%20%u0421%u041D%u0413%20%u0438%20%u043C%u0438%u0440%u0430%20-%20%u0418%u0410%20REGNUM;0.1826685545323159
1231 ms1303 ms0 KB0 KB-1Image
1232 ms1303 ms0 KB0 KB-1Script
1232 ms1304 ms0 KB0 KB-1Script
1233 ms1371 ms1 KB1 KB200application/javascriptScript
1234 ms1354 ms1 KB0 KB302
1285 ms1341 ms0 KB0 KB-1XHR
1287 ms1342 ms0 KB0 KB-1XHR
1289 ms1342 ms0 KB0 KB-1Script
1290 ms1342 ms0 KB0 KB-1XHR
1292 ms1351 ms0 KB0 KB-1XHR
1302 ms1352 ms0 KB0 KB-1Image
1312 ms1353 ms0 KB0 KB-1Image
1312 ms1825 ms112 KB112 KB200image/pngImage
1312 ms1353 ms0 KB0 KB-1Image
1313 ms1589 ms56 KB56 KB200image/jpegImage
1313 ms1353 ms0 KB0 KB-1Image
1313 ms1636 ms164 KB164 KB200image/pngImage
1314 ms1723 ms72 KB71 KB200image/jpegImage
1314 ms1353 ms0 KB0 KB-1Image
1314 ms1353 ms0 KB0 KB-1Image
1315 ms1724 ms51 KB50 KB200image/jpegImage
1346 ms1559 ms0 KB0 KB200application/jsonXHR
1354 ms1457 ms1 KB1 KB200text/javascriptScript
1378 ms1440 ms0 KB0 KB-1Script
1404 ms1451 ms0 KB0 KB-1Script
1407 ms1451 ms0 KB0 KB-1Script
1409 ms1452 ms0 KB0 KB-1Script
1421 ms1453 ms0 KB0 KB-1XHR
1423 ms1562 ms1 KB1 KB200text/htmlXHR
1433 ms1454 ms0 KB0 KB-1XHR***R%3E*regnum_ru/ru/UTF-8/tmsec=regnum_total/527971811
1456 ms1594 ms1 KB0 KB302image/gif
1467 ms1470 ms0 KB0 KB-1Document
1462 ms1481 ms0 KB0 KB302
1463 ms1474 ms0 KB0 KB-1Image
1464 ms1514 ms1 KB0 KB307
1464 ms1474 ms0 KB0 KB-1Image
1481 ms1484 ms0 KB0 KB-1Image
1514 ms1540 ms0 KB0 KB307
1540 ms1640 ms0 KB0 KB200image/pngImage
1580 ms1649 ms1 KB0 KB200text/javascriptScript
1580 ms1583 ms0 KB0 KB-1Script
1581 ms1720 ms2 KB0 KB200application/javascriptScript***R%3E*regnum_ru/ru/UTF-8/tmsec=regnum_total/527971811
1594 ms1732 ms0 KB0 KB200image/gifImage
1934 ms2077 ms1 KB0 KB302
1946 ms2087 ms0 KB0 KB200image/gifImage
2077 ms2227 ms1 KB0 KB200application/jsonXHR
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.

Cache TTLSize
0 ms306 KB
0 ms164 KB
0 ms112 KB
0 ms95 KB
0 ms72 KB
0 ms56 KB
0 ms51 KB
0 ms35 KB
0 ms7 KB
0 ms2 KB
0 ms2 KB
3600000 ms92 KB
3600000 ms36 KB
3600000 ms0 KB
43200000 ms3 KB
259200000 ms52 KB
Reduce the impact of third-party code - Third-party code blocked the main thread for 510 ms
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.

SizeMain-Thread Blocking Time
94 KB401 ms
36 KB112 ms
55 KB0 ms
1 KB0 ms
1 KB0 ms
1 KB0 ms
0 KB0 ms
0 KB0 ms
0 KB0 ms
0 KB0 ms
0 KB0 ms
0 KB0 ms
0 KB0 ms
0 KB0 ms
0 KB0 ms
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.

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.

Avoid chaining critical requests - 8 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 290 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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.
Optimize images
Your images are optimized. Learn more about optimizing images.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Enable compression
You have compression enabled. Learn more about enabling compression.
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.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 125.01 KB
Compressed size: 28.34 KB
File reduced by: 96.68 KB (77%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name: *
Issuer: AlphaSSL CA - SHA256 - G2
Valid from: Feb 6 02:25:39 2019 GMT
Valid until: Feb 9 19:38:07 2020 GMT
Authority: Is not a CA
Common Name: AlphaSSL CA - SHA256 - G2
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign Root CA
Valid from: Feb 20 10:00:00 2014 GMT
Valid until: Feb 20 10:00:00 2024 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Russian/Новости и СМИ
Россия/Новости и СМИ

+ Http Header

Server: QRATOR
Date: Tue, 19 Nov 2019 14:09:59 GMT
Content-Type: text/html
Content-Length: 178
Connection: keep-alive
Keep-Alive: timeout=15

HTTP/1.1 200 OK
Server: QRATOR
Date: Tue, 19 Nov 2019 14:10:00 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 29017
Connection: keep-alive
Keep-Alive: timeout=15
X-Powered-By: PHP/5.6.40-0+deb8u4
Content-Encoding: gzip
Vary: Accept-Encoding
expires: 60.000
X-Varnish: 883684411 884611177
Age: 40
Via: 1.1 varnish-v4
Accept-Ranges: bytes
X-APP: app2

+ DNS Lookup

Currently Not Available

+ Whois Lookup

Domain Created:
Domain Age:
17 years 8 months 19 days  

whois lookup at
% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% (in Russian)
% (in English).

domain: REGNUM.RU
org: OOO Regnum
registrar: RD-RU
created: 2002-02-28T21:00:00Z
paid-till: 2020-02-29T21:00:00Z
free-date: 2020-04-01
source: TCI

Last updated on 2019-11-19T14:06:34Z
Last update was 19 days ago
This can take up to 60 seconds. Please wait...

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

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) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget