ricom.ru Website Information

Daily Unique Visits: 907

Daily Page Views: 1,814

Income Per Day: $6

Estimated Value: $1,440

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

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

Website ricom.ru is using the following name servers:

ns.rts.ru
ns2.rts.ru

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

The highest website ricom.ru position in Alexa rank database was 99151 and the lowest rank position was 999782. Current position of ricom.ru in Alexa rank database is 790739.

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

Mobile usability score of ricom.ru (61/100) is better than the results of 5.47% of other sites and means that the page is not mobile-friendly.

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

ricom.ru Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

ricom.ru whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

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

domain: RICOM.RU
nserver: ns3-l2.nic.ru.
nserver: ns4-cloud.nic.ru.
nserver: ns4-l2.nic.ru.
nserver: ns8-cloud.nic.ru.
nserver: ns8-l2.nic.ru.
state: REGISTERED, DELEGATED, VERIFIED
org: CJSC Investment Company RICOM-TRUST
taxpayer-id: 7701033078
registrar: RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created: 1998-03-24T15:39:20Z
paid-till: 2025-03-31T21:00:00Z
free-date: 2025-05-02
source: TCI

Last updated on 2024-10-22T14:06:30Z

ricom.ru server information

Servers Location

ricom.ru desktop page speed rank

Last tested: 2019-06-17

Desktop Speed Medium

81/100

ricom.ru Desktop Speed Test Quick Summary

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

Your page has 1 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://www.ricom.ru/static/CACHE/js/d390edbc5495.js

Optimize CSS Delivery of the following:

https://www.ricom.ru/static/CACHE/css/6885c8f3b5b5.css
https://www.ricom.ru/static/CACHE/css/bc2ba4a82caf.css
https://www.ricom.ru/static/CACHE/css/25af4b299cae.css
https://www.ricom.ru/static/CACHE/css/12a9f3c91680.css

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

https://app.comagic.ru/static/cs.min.js (expiration not specified)
https://discovery.livetex.ru/event-service-app.widgets-thrift-http (expiration not specified)
https://widgets.livetex.ru/css/widgets/13152.css (5 minutes)
https://widgets.livetex.ru/js/settings/v3/13152.js (5 minutes)
https://static-lead-hub-client-ltx226.livetex.ru/client.js (30 minutes)
https://cs15.livetex.ru/js/client.js (60 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)
https://widgets.livetex.ru/js/app3.js (60 minutes)
https://widgets.livetex.ru/widget-ui-3.js (60 minutes)
https://www.googleadservices.com/pagead/conversion.js (60 minutes)
https://site.yandex.net/v2.0/js/all.js (6 hours)
https://site.yandex.net/v2.0/js/opensearch.js (6 hours)
https://site.yandex.net/v2.0/js/suggest.js (6 hours)

priority - 5Optimize images

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

Optimize the following images to reduce their size by 44.7KiB (32% reduction).

Compressing https://www.ricom.ru/static/images/slider/rttrader.jpg could save 38.3KiB (31% reduction).
Compressing https://www.ricom.ru/static/images/bx_controls.png?a7fbfce78e88 could save 1.4KiB (50% reduction).
Compressing https://www.ricom.ru/static/img/logo.png could save 1.2KiB (29% reduction).
Compressing https://www.ricom.ru/static/img/bottomLogo.png could save 1.1KiB (34% reduction).
Compressing https://www.ricom.ru/static/img/office.png could save 973B (50% reduction).
Compressing https://www.ricom.ru/static/img/look.png?a92027a3be54 could save 904B (81% reduction).
Compressing https://www.ricom.ru/static/img/home.png could save 899B (57% reduction).

priority - 1Reduce server response time

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

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

Minifying https://www.ricom.ru/ could save 1KiB (14% reduction) after compression.

ricom.ru Desktop Resource Breakdown

Total Resources	70
Number of Hosts	17
Static Resources	45
JavaScript Resources	19
CSS Resources	6

ricom.ru mobile page speed rank

Last tested: 2017-12-01

Mobile Speed Medium

65/100

ricom.ru Mobile Speed Test Quick Summary

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

Your page has 1 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://www.ricom.ru/static/CACHE/js/d390edbc5495.js

Optimize CSS Delivery of the following:

priority - 9Leverage 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:

https://app.comagic.ru/static/cs.min.js (expiration not specified)
https://discovery.livetex.ru/event-service-app.widgets-thrift-http (expiration not specified)
https://site.yandex.net/v2.0/js/opensearch.js (expiration not specified)
https://site.yandex.net/v2.0/js/suggest.js (expiration not specified)
https://widgets.livetex.ru/css/mobileWidgets/13152.css (5 minutes)
https://widgets.livetex.ru/js/settings/v3/13152.js (5 minutes)
https://static-lead-hub-client-ltx226.livetex.ru/client.js (30 minutes)
https://cs15.livetex.ru/js/client.js (60 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)
https://widgets.livetex.ru/js/app3.js (60 minutes)
https://widgets.livetex.ru/widget-ui-3.js (60 minutes)
https://www.googleadservices.com/pagead/conversion.js (60 minutes)
https://site.yandex.net/v2.0/js/all.js (6 hours)

priority - 5Optimize images

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

Optimize the following images to reduce their size by 44.7KiB (32% reduction).

priority - 1Reduce server response time

priority - 0Enable 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 738B (69% reduction).

Compressing https://discovery.livetex.ru/leadhub-id-service-ap…ase&0.3860347573645413 could save 738B (69% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

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

Minifying https://www.ricom.ru/ could save 1KiB (14% reduction) after compression.

ricom.ru Mobile Resource Breakdown

Total Resources	65
Number of Hosts	17
Static Resources	41
JavaScript Resources	19
CSS Resources	6

ricom.ru mobile page usability

Last tested: 2017-12-01

Mobile Usability Bad

61/100

ricom.ru Mobile Usability Test Quick Summary

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

+7 (495) 921-15-55 renders only 7 pixels tall (18 CSS pixels).

пн-пт: с 9:00 до 19:30 and 1 others render only 5 pixels tall (12 CSS pixels).

client@ricom.ru renders only 5 pixels tall (14 CSS pixels).

ОТКРЫТЬ СЧЕТ renders only 6 pixels tall (16 CSS pixels).

ЧАСТНЫЕ ИНВЕСТОРЫ and 3 others render only 4 pixels tall (11 CSS pixels).

АНАЛИТИКА renders only 4 pixels tall (11 CSS pixels).

1 день 1 идея renders only 5 pixels tall (14 CSS pixels).

Автоследование and 6 others render only 5 pixels tall (14 CSS pixels).

Раскрытие инфо…2.2015 №3921-У and 5 others render only 5 pixels tall (14 CSS pixels).

Приходите. Инв…Зарабатывайте! and 1 others render only 7 pixels tall (18 CSS pixels).

Жизнь меняется…ую - на бирже. renders only 5 pixels tall (14 CSS pixels).

Ценные бумаги,…сти буквально. and 2 others render only 5 pixels tall (14 CSS pixels).

сотрудники, ум…ансовом рынке; and 3 others render only 5 pixels tall (14 CSS pixels).

+7 (499) 241 06 08 renders only 8 pixels tall (20 CSS pixels).

Техническая по…овым операциям and 2 others render only 6 pixels tall (15 CSS pixels).

E-mail: renders only 5 pixels tall (13 CSS pixels).

support@ricom.ru renders only 5 pixels tall (13 CSS pixels).

Адрес: and 2 others render only 5 pixels tall (14 CSS pixels).

Проточный пер. д. 6. and 2 others render only 5 pixels tall (14 CSS pixels).

+7 (929) 682 83 85 renders only 8 pixels tall (20 CSS pixels).

Обратная связь renders only 8 pixels tall (20 CSS pixels).

Вы можете напи…о и мы ответим and 1 others render only 5 pixels tall (13 CSS pixels).

Напишите нам renders only 4 pixels tall (11 CSS pixels).

Демо-счет renders only 5 pixels tall (14 CSS pixels).

2007-2016 "РИКОМ ТРАСТ" and 1 others render only 4 pixels tall (10 CSS pixels).

webmaster@ricom.ru renders only 4 pixels tall (10 CSS pixels).

priority - 14Size 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 type="button" class="ya-site-form__…mit_type_image"> is close to 3 other tap targets.

The tap target <img id="login" src="/static/img/login.png"> is close to 1 other tap targets.

The tap target <a href="mailto:client@ricom.ru">client@ricom.ru</a> is close to 1 other tap targets.

The tap target <a href="/regions/"></a> is close to 1 other tap targets.

The tap target <a href="/"></a> is close to 2 other tap targets.

The tap target <a href="http://analytic.ricom.ru/">Аналитика</a> is close to 3 other tap targets.

The tap target <div class="bx-controls-auto">Stop</div> is close to 2 other tap targets.

The tap target <a href="" class="bx-stop">Stop</a> is close to 2 other tap targets.

The tap target <div class="bx-pager bx-custom-pager">1 день 1 идеяr…Автоследование</div> is close to 2 other tap targets.

The tap target <div class="bx-pager bx-custom-pager">1 день 1 идеяr…Автоследование</div> and 1 others are close to other tap targets.

The tap target <div class="bx-pager bx-custom-pager">1 день 1 идеяr…Автоследование</div> and 13 others are close to other tap targets.

The tap target <a href="/software/">Программы для трейдинга</a> and 3 others are close to other tap targets.

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

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

The element <ul class="nav nav-pills">Раскрытие инфо…2.2015 №3921-У</ul> falls outside the viewport.
The element <div class="lt-label-inner"> falls outside the viewport.
The element <li class="lt-label-chat-event">1</li> falls outside the viewport.
The element <span class="lt-label-state…lt-icon-callto"> falls outside the viewport.
The element <span class="lt-label-notify"> falls outside the viewport.
The element <div class="lt-label-touch"> falls outside the viewport.

ricom.ru HTML validation

Errors

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Line: 13 Column: 5 - 56
"...A" /> <meta http-equiv="X-UA-Compatible" content="IE=9" /> <..."

Bad start tag in “div” in “head”.

Line: 50 Column: 11 - 15
"...<noscript><div><img s..."

Element “head” is missing a required instance of child element “title”.

Line: 50 Column: 11 - 15
"...<noscript><div><img s..."

Stray end tag “noscript”.

Line: 50 Column: 119 - 129
"..." /></div></noscript> <!-- ..."

Bad value “https://www.facebook.com/tr?id=1114645878677903&ev=PageView &noscript=1” for attribute “src” on element “img”: Tab, new line or carriage return found.

Line: 69 Column: 3 - 30
"...script> <img height="1" width="1" src="https://www.facebook.com/tr?id=1114645878677903&ev=PageView &noscript=1"/> </nosc..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 69 Column: 3 - 30
"...script> <img height="1" width="1" src="https://www.facebook.com/tr?id=1114645878677903&ev=PageView &noscript=1"/> </nosc..." Line: 149 Column: 25 - 90
"... href="/"><img src="/static/img/logo.png" width="80" height="73" id="logo"/></a> ..." Line: 152 Column: 72 - 154
"...="_blank"><img src="//www.ricom.ru/media/r/up/premarket_ca881ba4.gif" class="top" id="rupb"/></a> ..." Line: 159 Column: 33 - 103
"...regions/"><img src="/static/img/office.png" width="186" height="14" id="office"/></a> ..." Line: 174 Column: 25 - 90
"... href="/"><img src="/static/img/home.png" width="48" height="48" id="home"/></a> ..." Line: 860 Column: 13 - 90
"... <img src="/static/img/bottomLogo.png" width="81" height="76" id="bottomLogo"/> ..."

Element “title” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)

Line: 92 Column: 5 - 11
"... <title>Риком-..."

Stray end tag “head”.

Line: 94 Column: 3 - 9
"...e> </head> <b..."

Start tag “body” seen but an element of the same type was already open.

Line: 96 Column: 3 - 8
".../head> <body> ..."

Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)

Line: 120 Column: 853 - 875
"...orm></div><style type="text/css">.ya-pa..."

Attribute “rel” not allowed on element “div” at this point.

Line: 703 Column: 3 - 47
"...er"> <div class="slide_item" data-slide-name="1 день 1 идея" rel="0"> ..." Line: 713 Column: 3 - 46
"...div> <div class="slide_item" data-slide-name="Криптовалюта" rel="1"> ..." Line: 723 Column: 3 - 43
"...div> <div class="slide_item" data-slide-name="Теханализ" rel="2"> ..." Line: 733 Column: 3 - 52
"...div> <div class="slide_item" data-slide-name=""Рантье"" rel="3"> ..." Line: 743 Column: 3 - 37
"...div> <div class="slide_item" data-slide-name="ИИС" rel="4"> ..." Line: 753 Column: 3 - 48
"...div> <div class="slide_item" data-slide-name="Автоследование" rel="5"> ..." Line: 763 Column: 3 - 49
"...div> <div class="slide_item" data-slide-name="Утренние обзоры" rel="6"> ..."

No “p” element in scope but a “p” end tag seen.

Line: 870 Column: 106 - 109
"...</address></p> ..."

Duplicate ID “bottom-button”.

Line: 914 Column: 11 - 75
"... <button class="btn btn-primary" type="button" id="bottom-button">Напиши..."

Duplicate ID “foot-text1”.

Line: 921 Column: 9 - 29
"...> <div id="foot-text1">E-mail..."

Duplicate ID “foot-text2”.

Line: 922 Column: 9 - 29
"...> <div id="foot-text2">2007-2..."

Warnings

The first occurrence of ID “bottom-button” was here.

Line: 883 Column: 11 - 75
"... <button class="btn btn-primary" type="button" id="bottom-button">Напиши..."

The first occurrence of ID “foot-text1” was here.

Line: 895 Column: 9 - 29
"...> <div id="foot-text1">E-mail..."

The first occurrence of ID “foot-text2” was here.

Line: 896 Column: 9 - 29
"...> <div id="foot-text2">2007-2..."

ricom.ru similar domains

Similar domains:

www.ricom.com
www.ricom.net
www.ricom.org
www.ricom.info
www.ricom.biz
www.ricom.us
www.ricom.mobi
www.icom.ru
www.ricom.ru
www.eicom.ru
www.reicom.ru
www.ericom.ru
www.dicom.ru
www.rdicom.ru
www.dricom.ru
www.ficom.ru
www.rficom.ru
www.fricom.ru
www.ticom.ru
www.rticom.ru
www.tricom.ru
www.rcom.ru
www.rucom.ru
www.riucom.ru
www.ruicom.ru
www.rjcom.ru
www.rijcom.ru
www.rjicom.ru
www.rkcom.ru
www.rikcom.ru
www.rkicom.ru
www.rocom.ru
www.riocom.ru
www.roicom.ru
www.riom.ru
www.rixom.ru
www.ricxom.ru
www.rixcom.ru
www.ridom.ru
www.ricdom.ru
www.ridcom.ru
www.rifom.ru
www.ricfom.ru
www.rifcom.ru
www.rivom.ru
www.ricvom.ru
www.rivcom.ru
www.ricm.ru
www.ricim.ru
www.ricoim.ru
www.riciom.ru
www.rickm.ru
www.ricokm.ru
www.rickom.ru
www.riclm.ru
www.ricolm.ru
www.riclom.ru
www.ricpm.ru
www.ricopm.ru
www.ricpom.ru
www.rico.ru
www.ricon.ru
www.ricomn.ru
www.riconm.ru
www.ricoj.ru
www.ricomj.ru
www.ricojm.ru
www.ricok.ru
www.ricomk.ru

ricom.ru Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.

ricom.ru TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.

RICOM.RU Website Information

ricom.ru Website Information

Advertisement

ricom.ru Alexa Rank

ricom.ru whois

ricom.ru server information

Servers Location

ricom.ru desktop page speed rank

ricom.ru Desktop Speed Test Quick Summary

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

Your page has 1 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

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

priority - 5Optimize images

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

Optimize the following images to reduce their size by 44.7KiB (32% reduction).

priority - 1Reduce server response time

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

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

ricom.ru Desktop Resource Breakdown

ricom.ru mobile page speed rank

ricom.ru Mobile Speed Test Quick Summary

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

Your page has 1 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 9Leverage 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:

priority - 5Optimize images

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

Optimize the following images to reduce their size by 44.7KiB (32% reduction).

priority - 1Reduce server response time

priority - 0Enable 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 738B (69% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

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

ricom.ru Mobile Resource Breakdown

ricom.ru mobile page usability

ricom.ru Mobile Usability Test Quick Summary

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

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

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

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

ricom.ru HTML validation

Errors

A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.

Bad start tag in “div” in “head”.

Element “head” is missing a required instance of child element “title”.

Stray end tag “noscript”.

Bad value “https://www.facebook.com/tr?id=1114645878677903&ev=PageView &noscript=1” for attribute “src” on element “img”: Tab, new line or carriage return found.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Element “title” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)

Stray end tag “head”.

Start tag “body” seen but an element of the same type was already open.

Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)

Attribute “rel” not allowed on element “div” at this point.

No “p” element in scope but a “p” end tag seen.

Duplicate ID “bottom-button”.

Duplicate ID “foot-text1”.

Duplicate ID “foot-text2”.

Warnings

The first occurrence of ID “bottom-button” was here.

The first occurrence of ID “foot-text1” was here.

The first occurrence of ID “foot-text2” was here.

ricom.ru similar domains

ricom.ru Ping