LOVE.RU Социальная сеть знакомств Love.Ru. Найди свою любовь в Москве, Санкт-Петербурге и других городах.


love.ru website information.

love.ru domain name is registered by .RU top-level domain registry. See the other sites registred in .RU domain zone.

No name server records were found.

and probably website love.ru is hosted by SERVERSTACK-ASN - ServerStack, Inc., US web hosting company. Check the complete list of other most popular websites hosted by SERVERSTACK-ASN - ServerStack, Inc., US hosting company.

According to Alexa traffic rank the highest website love.ru position was 85089 (in the world). The lowest Alexa rank position was 255793. Now website love.ru ranked in Alexa database as number 207131 (in the world).

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

love.ru Mobile usability score (92/100) is better than the results of 33.5% of other sites and means that the page is mobile-friendly.

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

Weekly Rank Report

DateRankChange
Sep-22-2024 207,131-2,214
Sep-21-2024 204,9172,606
Sep-20-2024 207,523-1,626
Sep-19-2024 205,897-285
Sep-18-2024 205,612-564
Sep-17-2024 205,0483,201
Sep-16-2024 208,2494,685

Advertisement

love.ru Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



love.ru whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


% 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: LOVE.RU
nserver: ns1.love.ru. 78.46.97.18, 2a01:4f8:120:8212::5
nserver: ns2.love.ru. 85.10.210.205, 2a01:4f8:222:8cd::5
state: REGISTERED, DELEGATED, VERIFIED
person: Private Person
registrar: RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created: 1999-03-01T10:04:31Z
paid-till: 2022-03-31T21:00:00Z
free-date: 2022-05-02
source: TCI

Last updated on 2021-05-22T00:51:30Z

love.ru server information

Servers Location

IP Address
Country
Region
City

love.ru desktop page speed rank

Last tested: 2017-06-01


Desktop Speed Medium
81/100

love.ru Desktop Speed Test Quick Summary


priority - 11 Optimize images

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

Optimize the following images to reduce their size by 104.2KiB (55% reduction).

Compressing and resizing http://f1.love.ru/c_Q0u_3NoaG_fxiS17xKw9eL41.jpg could save 17.7KiB (92% reduction).
Compressing and resizing http://f2.love.ru/4_IT4_42Gdg_TNCWOYOEoAQAeu.jpg could save 13.4KiB (92% reduction).
Compressing http://f3.love.ru/1_5Ca_1Ch3U_8OLIkhsEhbfLAf.jpg could save 13.2KiB (77% reduction).
Compressing http://f3.love.ru/g_Nhp2_2FWhx_KyrEcsxnU11RoK.jpg could save 7.6KiB (75% reduction).
Compressing http://f1.love.ru/4_AZ2_2PO6y_GmgaO1g1XyXdPu.jpg could save 6.9KiB (62% reduction).
Compressing http://f1.love.ru/l_A4Lg_yQTI_CaVwfWxPifiqhs.jpg could save 6.7KiB (66% reduction).
Compressing and resizing http://f2.love.ru/f_CaR6_1DX5c_Gmga1KvWUOOyor.jpg could save 3.6KiB (76% reduction).
Compressing and resizing http://f1.love.ru/T_4elE_S1wi_4CAecejTviDlpF.jpg could save 3.5KiB (78% reduction).
Compressing http://f1.love.ru/I_L7Y_4omDw_XZNAL2wGoMD0s7.jpg could save 3.2KiB (41% reduction).
Compressing http://f3.love.ru/O_7ns_1IRUT_CaVwOWNY5uz1TC.jpg could save 3KiB (50% reduction).
Compressing http://f3.love.ru/j_AYm_2PO6y_Gmga6TdvY1hQib.jpg could save 2.6KiB (45% reduction).
Compressing http://f3.love.ru/T_Id2u_1o7mq_GmgaR9VbplhFlR.jpg could save 2.5KiB (41% reduction).
Compressing http://f4.love.ru/a_KoK0_27GAa_XZNACgsSRkmlAc.jpg could save 2.4KiB (40% reduction).
Compressing and resizing http://f1.love.ru/m_QDA_31zgu_fxiSZVPEP5p1HT.jpg could save 2.4KiB (70% reduction).
Compressing http://f2.love.ru/5_Qg2_61THQ_fxiSI1zknMIeUx.jpg could save 2KiB (29% reduction).
Compressing http://f2.love.ru/x_Fbk_3c5AS_PB1s4mawFgr7XY.jpg could save 2KiB (35% reduction).
Compressing http://f4.love.ru/z_Q0u_1LvQu_fxiSG1nBxGzdgu.jpg could save 1.7KiB (31% reduction).
Compressing http://f3.love.ru/K_FqA_3c5AS_PB1s3CZKYfHZg1.jpg could save 1.7KiB (32% reduction).
Compressing http://f3.love.ru/8_7ns_PB1s_CaVwB0qouLnjdb.jpg could save 1.4KiB (31% reduction).
Compressing http://f4.love.ru/J_D0S_fxiS_KyrEq2ZBYK94Zu.jpg could save 1.3KiB (31% reduction).
Compressing http://love.ru/f/sprite.png could save 1.3KiB (24% reduction).
Compressing http://f3.love.ru/O_vGzI_2NADj_TNCWxOZF195krC.jpg could save 1.1KiB (20% reduction).
Compressing http://f2.love.ru/k_IPZ_3ADcy_TNCWSgMF79zuNA.jpg could save 1KiB (25% reduction).
Compressing http://love.ru/f/logo-1397048718.png could save 793B (27% reduction).
Compressing http://f1.love.ru/z_2eJ_DqZ8_4CAeu089wx1l2x.jpg could save 568B (14% reduction).
Compressing http://f4.love.ru/0_Qk4_61THQ_fxiSyTWFNE0JRU.jpg could save 541B (13% reduction).

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

Your page has 10 blocking script resources and 4 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://love.ru/s/js/gz/prototype.js?174019323
http://love.ru/s/js/gz/libs/history.js?174019322
http://love.ru/s/js/ru/js.js?176722949
http://love.ru/s/js/ru/pay.js?171108635
http://love.ru/s/js/ru/main.js?174117717
http://love.ru/s/js/ru/libs/bb.js?173598846
http://love.ru/s/js/gz/oauth.js?174019323
http://love.ru/s/js/ru/not-auth.js?167706601
http://love.ru/s/js/ru/comments.js?173703295
http://love.ru/s/js/gz/js_versions.js?177219865

Optimize CSS Delivery of the following:

http://love.ru/s/static/all-8f6b89f0ffc2af06f6909a39a4908cae.css?174869028
http://love.ru/s/static/screen-8f6b89f0ffc2af06f69…a4908cae.css?164090491
http://love.ru/s/static/wysiwyg-bb-8f6b89f0ffc2af0…a4908cae.css?171685220
http://love.ru/s/static/custom-7127-75a87875f9b702…7272f81.css?1478066562

priority - 2 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://love.ru/f/bgg.png (60 minutes)
http://love.ru/f/logo-1397048718.png (60 minutes)
http://love.ru/f/reg.png (60 minutes)
http://love.ru/f/sprite.png (60 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)

priority - 1 Minify JavaScript

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

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

Minifying http://love.ru/s/js/ru/js.js?176722949 could save 3.6KiB (17% reduction) after compression.
Minifying http://love.ru/s/js/ru/main.js?174117717 could save 2.6KiB (17% reduction) after compression.
Minifying http://love.ru/s/js/ru/pay.js?171108635 could save 750B (17% reduction) after compression.
Minifying http://love.ru/s/js/ru/not-auth.js?167706601 could save 668B (16% reduction) after compression.
Minifying http://love.ru/s/js/ru/comments.js?173703295 could save 660B (19% reduction) after compression.

love.ru Desktop Resources

Total Resources61
Number of Hosts8
Static Resources52
JavaScript Resources13
CSS Resources4

love.ru Desktop Resource Breakdown

love.ru mobile page speed rank

Last tested: 2017-06-01


Mobile Speed Medium
73/100

love.ru Mobile Speed Test Quick Summary


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

Your page has 3 blocking script resources and 5 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://m.love.ru/s/js/ru/mobile/mobile.js?176766787
http://m.love.ru/s/js/gz/mobile/left_menu.js?174019329
http://m.love.ru/s/js/ru/libs/bb.js?173598859

Optimize CSS Delivery of the following:

http://m.love.ru/s/static/m-ddb0eba8bcb00d4a957f2d547846a904.css?177219891
http://m.love.ru/s/static/m-screen-ddb0eba8bcb00d4…7846a904.css?173600767
http://m.love.ru/s/static/m-index-ddb0eba8bcb00d4a…7846a904.css?165027311
http://m.love.ru/s/static/smiles-png-emoji.css1166…1453e4a42ee13bc014.css
http://m.love.ru/s/static/smiles-png-stickers.cssb…4751faa8b5ad5cf4e8.css

priority - 8 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 68% of the final above-the-fold content could be rendered with the full HTML response.

priority - 3 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://an.yandex.ru/system/context.js (60 minutes)
http://m.love.ru/f/logo-1397048718.png (60 minutes)
http://m.love.ru/f/mlogo-1452685177.png (60 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)

priority - 0 Minify JavaScript

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

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

Minifying http://m.love.ru/s/js/ru/mobile/mobile.js?176766787 could save 2.5KiB (15% reduction) after compression.

priority - 0 Optimize images

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

Optimize the following images to reduce their size by 1.5KiB (27% reduction).

Compressing http://m.love.ru/f/logo-1397048718.png could save 793B (27% reduction).
Compressing http://m.love.ru/f/mlogo-1452685177.png could save 793B (27% reduction).

love.ru Mobile Resources

Total Resources37
Number of Hosts7
Static Resources29
JavaScript Resources7
CSS Resources5

love.ru Mobile Resource Breakdown

love.ru mobile page usability

Last tested: 2017-06-01


Mobile Usability Good
92/100

love.ru Mobile Usability Test Quick Summary


priority - 7 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="https://an.yan…9078117466113&amp;" class="yap-sitelinks_…-sitelink-text">Регистрация</a> and 4 others are close to other tap targets.
The tap target <a href="https://an.yan…9078117466113&amp;" class="yap-sitelinks_…-sitelink-text">Регистрация</a> and 6 others are close to other tap targets.
The tap target <a href="https://an.yan…9078117466113&amp;" class="yap-sitelinks_…-sitelink-text">Знакомство с мужчинами</a> and 1 others are close to other tap targets.
The tap target <yatag class="yap-adtune yap…ne_oldie_false">Скрыть объявление</yatag> and 1 others are close to other tap targets.

love.ru similar domains

Similar domains:
www.love.com
www.love.net
www.love.org
www.love.info
www.love.biz
www.love.us
www.love.mobi
www.ove.ru
www.love.ru
www.pove.ru
www.lpove.ru
www.plove.ru
www.oove.ru
www.loove.ru
www.olove.ru
www.kove.ru
www.lkove.ru
www.klove.ru
www.lve.ru
www.live.ru
www.loive.ru
www.liove.ru
www.lkve.ru
www.lokve.ru
www.llve.ru
www.lolve.ru
www.llove.ru
www.lpve.ru
www.lopve.ru
www.loe.ru
www.loce.ru
www.lovce.ru
www.locve.ru
www.lofe.ru
www.lovfe.ru
www.lofve.ru
www.loge.ru
www.lovge.ru
www.logve.ru
www.lobe.ru
www.lovbe.ru
www.lobve.ru
www.lov.ru
www.lovw.ru
www.lovew.ru
www.lovwe.ru
www.lovs.ru
www.loves.ru
www.lovse.ru
www.lovd.ru
www.loved.ru
www.lovde.ru
www.lovr.ru
www.lover.ru
www.lovre.ru

love.ru Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


love.ru TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.