FOME.RU Fome.ru - развлекательно-информационный портал

fome.ru Website Information

Daily Unique Visits: 976

Daily Page Views: 1,952

Income Per Day: $6

Estimated Value: $1,440

This website is located in Netherlands and is using following IP address 85.17.4.198. See the complete list of popular websites hosted in Netherlands.

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

Website fome.ru is using the following name servers:

  • ns1.neolocation.com
  • ns3.neolocation.com
  • ns2.neolocation.com

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

The highest website fome.ru position in Alexa rank database was 671379 and the lowest rank position was 755182. Current position of fome.ru in Alexa rank database is 734473.

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

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

Mobile speed score of fome.ru (85/100) is better than the results of 90.58% of other sites and shows that the landing page performance on mobile devices is excellent.

Advertisement

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


fome.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: FOME.RU
nserver: ns1.hostfly.by.
nserver: ns2.hostfly.by.
state: REGISTERED, DELEGATED, UNVERIFIED
person: Private Person
registrar: REGTIME-RU
admin-contact: https://whois.webnames.ru
created: 2007-01-31T21:00:00Z
paid-till: 2025-01-31T21:00:00Z
free-date: 2025-03-04
source: TCI

Last updated on 2024-10-11T06:46:30Z

fome.ru server information

Servers Location

fome.ru desktop page speed rank

Last tested: 2017-05-22


Desktop Speed Good
90/100

fome.ru Desktop Speed Test Quick Summary


priority - 4Enable 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 42.6KiB (83% reduction).

Compressing http://fome.ru/ could save 39.4KiB (85% reduction).
Compressing http://fome.ru/main.css could save 3.2KiB (71% reduction).

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

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

Optimize CSS Delivery of the following:

http://fome.ru/main.css

priority - 2Minify 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 17.4KiB (38% reduction).

Minifying http://fome.ru/ could save 17.4KiB (38% reduction).

priority - 1Optimize images

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

Optimize the following images to reduce their size by 2.3KiB (33% reduction).

Compressing http://fome.ru/i/pic-index.jpg could save 1.7KiB (30% reduction).
Compressing http://www.all.by/pics/allcounter.gif could save 665B (50% reduction).

priority - 1Leverage 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://www.all.by/pics/allcounter.gif (expiration not specified)

fome.ru Desktop Resource Breakdown

Total Resources86
Number of Hosts4
Static Resources75
CSS Resources1

fome.ru mobile page speed rank

Last tested: 2017-05-22


Mobile Speed Good
85/100

fome.ru Mobile Speed Test Quick Summary


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

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

Optimize CSS Delivery of the following:

http://fome.ru/main.css

priority - 4Enable 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 42.6KiB (83% reduction).

Compressing http://fome.ru/ could save 39.4KiB (85% reduction).
Compressing http://fome.ru/main.css could save 3.2KiB (71% reduction).

priority - 2Minify 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 17.4KiB (38% reduction).

Minifying http://fome.ru/ could save 17.4KiB (38% reduction).

priority - 1Leverage 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://www.all.by/pics/allcounter.gif (expiration not specified)

priority - 1Optimize images

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

Optimize the following images to reduce their size by 2.3KiB (33% reduction).

Compressing http://fome.ru/i/pic-index.jpg could save 1.7KiB (30% reduction).
Compressing http://www.all.by/pics/allcounter.gif could save 665B (50% reduction).

fome.ru Mobile Resource Breakdown

Total Resources86
Number of Hosts4
Static Resources75
CSS Resources1

fome.ru mobile page usability

Last tested: 2017-05-22


Mobile Usability Bad
56/100

fome.ru Mobile Usability Test Quick Summary


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

Развлекательный портал renders only 7 pixels tall (17 CSS pixels).

ВХОД НА САЙТ and 2 others render only 7 pixels tall (17 CSS pixels).

29.10.2010 and 1 others render only 4 pixels tall (10 CSS pixels).

Открылся новый раздел " and 3 others render only 4 pixels tall (10 CSS pixels).

Осмотрена гинекологом... and 152 others render only 4 pixels tall (10 CSS pixels).

Контакты and 1 others render only 5 pixels tall (12 CSS pixels).

ИГРЫ ДЛЯ ВЗРОСЛЫХ and 9 others render only 5 pixels tall (12 CSS pixels).

Наш сайт позна…нтересовавшие. and 1 others render only 4 pixels tall (11 CSS pixels).

Игры для взрослых and 9 others render only 6 pixels tall (16 CSS pixels).

ОБСУЖДЕНИЕ and 29 others render only 6 pixels tall (16 CSS pixels).

1. and 149 others render only 4 pixels tall (10 CSS pixels).

Приветствуем, and 3 others render only 4 pixels tall (11 CSS pixels).

Выход and 1 others render only 4 pixels tall (11 CSS pixels).

Притчи или фил…фские рассказы and 1 others render only 4 pixels tall (10 CSS pixels).

- большая коллекция renders only 4 pixels tall (10 CSS pixels).

Как стать другом? renders only 4 pixels tall (10 CSS pixels).

Контакты and 2 others render only 4 pixels tall (10 CSS pixels).
Развлекательный портал renders only 4 pixels tall (10 CSS pixels).
, все права защищены! and 2 others render only 4 pixels tall (10 CSS pixels).
fome.ru renders only 4 pixels tall (10 CSS pixels).

priority - 27Size 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="http://www.fome.ru"></a> and 1 others are close to other tap targets.

The tap target <input type="text" name="fsearch"> is close to 1 other tap targets.

The tap target <input type="button" name="bsearch"> is close to 3 other tap targets.

The tap target <a href="/">Главная</a> and 1 others are close to other tap targets.

The tap target <a href="/">Главная</a> and 1 others are close to other tap targets.

The tap target <a href="/party/" class="now">Игры для взрослых</a> and 9 others are close to other tap targets.

The tap target <a href="/party/" class="now">Игры для взрослых</a> and 11 others are close to other tap targets.

The tap target <a href="http://joke.fo…as-19-144.html">Вскрытие покажет!</a> and 151 others are close to other tap targets.

The tap target <a href="//privat/">0</a> and 1 others are close to other tap targets.

The tap target <a href="http://pritchi.castle.by/">Притчи или фил…фские рассказы</a> and 1 others are close to other tap targets.

The tap target <a href="http://www.fom…u/reclame.html">Как стать другом?</a> is close to 1 other tap targets.

The tap target <a href="http://www.fome.ru/">fome.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.

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

The element <img src="/i/pic-index.jpg"> falls outside the viewport.
The element <img src="/i/rc-01.gif"> falls outside the viewport.
The element <div class="header">ВХОД НА САЙТ</div> falls outside the viewport.
The element <div>Приветствуем,…сообщенийВыход</div> falls outside the viewport.
The element <img src="/i/rc-r1.gif"> falls outside the viewport.
The element <div class="header">ДРУЗЬЯ</div> falls outside the viewport.
The element <b>Притчи или фил…фские рассказы</b> falls outside the viewport.
The element <a href="http://www.fortima.by/">Создание сайта…зайн - Fortima</a> falls outside the viewport.
The element <a href="http://www.fom…u/reclame.html">Как стать другом?</a> falls outside the viewport.
The element <img src="/i/rc-r2zero.gif"> falls outside the viewport.
The element <td class="counter"></td> falls outside the viewport.

fome.ru HTML validation

fome.ru similar domains

Similar domains:
www.fome.com
www.fome.net
www.fome.org
www.fome.info
www.fome.biz
www.fome.us
www.fome.mobi
www.ome.ru
www.fome.ru
www.come.ru
www.fcome.ru
www.cfome.ru
www.dome.ru
www.fdome.ru
www.dfome.ru
www.rome.ru
www.frome.ru
www.rfome.ru
www.tome.ru
www.ftome.ru
www.tfome.ru
www.gome.ru
www.fgome.ru
www.gfome.ru
www.vome.ru
www.fvome.ru
www.vfome.ru
www.fme.ru
www.fime.ru
www.foime.ru
www.fiome.ru
www.fkme.ru
www.fokme.ru
www.fkome.ru
www.flme.ru
www.folme.ru
www.flome.ru
www.fpme.ru
www.fopme.ru
www.fpome.ru
www.foe.ru
www.fone.ru
www.fomne.ru
www.fonme.ru
www.foje.ru
www.fomje.ru
www.fojme.ru
www.foke.ru
www.fomke.ru
www.fom.ru
www.fomw.ru
www.fomew.ru
www.fomwe.ru
www.foms.ru
www.fomes.ru
www.fomse.ru
www.fomd.ru
www.fomed.ru
www.fomde.ru
www.fomr.ru
www.fomer.ru
www.fomre.ru

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


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