Nepryakhin.Ru - Website Report

Nepryakhin.Ru

Traffic estimate for Nepryakhin.ru is about 56 unique visits and 89.6 page views per day. Each unique visitor makes about 1.6 page views on average. According to traffic estimate, Nepryakhin.ru should earn about $0.42 per day from the advertising revenue, which implies that this website is worth about $170.99. Alexa Traffic Rank estimates that it is ranked number 3,754,795 in the world and less then 0.0001% of global Internet users are visiting Nepryakhin.ru on a regular basis. Website hosting location for Nepryakhin.ru is: Moscow, MOW, Russia. Server IP address: 89.111.179.65


About - nepryakhin.ru

Edit WebSite Info

Earnings Report

Website Value: $170.99
Daily Revenue: $0.42
Monthly Revenue: $12.82
Yearly Revenue: $156.03

Traffic Report

Daily Unique Visitors: 56
Monthly Unique Visitors: 1,680
Daily Pageviews: 89.6 (1.6 per day)
Montly Pageviews: 2,688
Daily PageViews Per User: 1.6
Alexa Global Rank: 3,754,795
Alexa Reach: less then 0.0001% of global Internet users
Alexa Backlinks: 24
Average Page Load Time: 0

Country Report

Country Alexa Rank PageViews Visitors
Russia 400582 50.0% 56.5%
OTHER 47.7% 39.1%

Contributing Subdomains

Domain Reach PageViews Per User
nepryakhin.ru 100.00% 100.00% 2

Social Report


Hosting Info

nepryakhin.ru Server Location
Server IP: 89.111.179.65
ASN: AS41126
ISP: CJSC Registrar R01
Server Location: Moscow MOW Russia

Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Reputation / Confidence
Trustworthiness: N/A
Child safety: N/A
MyWOT Categories: N/A

Google PageSpeed Insights

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

Your page has 1 blocking script resources and 2 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://nepryakhin.ru/wp-includes/js/jquery/jquery.js?ver=1.12.4

Optimize CSS Delivery of the following:
http://nepryakhin.ru/wp-content/cache/autoptimize/css/autoptimize_790b9aa4be20d97eceb5483c1de18d23.css
http://fonts.googleapis.com/css?family=Noto+Sans%3A400%2C700%7CRaleway%3A400%2C700&ver=1.2.1

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:
https://www.google.com/recaptcha/api.js?onload=griwpcOnloadCallback&render=explicit&ver=4.7.8 (5 minutes)
http://connect.facebook.net/ru_RU/sdk.js (20 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

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 11.1KiB (15% reduction).
Minifying https://vk.com/js/al/lite.js?145463682 could save 7.2KiB (15% reduction) after compression.
Minifying http://vk.com/js/api/openapi.js?116 could save 3.5KiB (17% reduction) after compression.
Minifying https://vk.com/js/api/xdm.js?1449919642 could save 433B (17% reduction) after compression.

Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 9.3KiB (17% reduction).
Compressing http://nepryakhin.ru/wp-content/uploads/2015/12/msk-400x200.jpg could save 3.5KiB (14% reduction).
Compressing http://nepryakhin.ru/wp-content/uploads/2015/02/yourline-400x200.jpg could save 2.4KiB (13% reduction).
Compressing https://pp.userapi.com/c625523/v625523901/4f66a/cgCwMEJcM64.jpg could save 796B (30% reduction).
Compressing https://pp.userapi.com/c633219/v633219271/fb0f/yad91gahp3g.jpg could save 636B (31% reduction).
Compressing https://pp.userapi.com/c628228/v628228760/13f56/EQTlGF-Gfzg.jpg could save 630B (29% reduction).
Compressing https://pp.userapi.com/c624119/v624119194/12fa7/pfM8dieqjnE.jpg could save 593B (29% reduction).
Compressing https://pp.userapi.com/c836533/v836533615/71aaf/3Yr_ODW0l4s.jpg could save 500B (31% reduction).
Compressing https://pp.userapi.com/c606520/v606520942/150e/d_Ze5LiRUok.jpg could save 317B (26% 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 407B (50% reduction).
Compressing http://nepryakhin.ru/?wc-ajax=get_refreshed_fragments could save 407B (50% reduction).

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.

Prioritize visible content

You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.

Minify HTML

Your HTML is minified. Learn more about minifying HTML.

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

Your page has 1 blocking script resources and 2 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://nepryakhin.ru/wp-includes/js/jquery/jquery.js?ver=1.12.4

Optimize CSS Delivery of the following:
http://nepryakhin.ru/wp-content/cache/autoptimize/css/autoptimize_790b9aa4be20d97eceb5483c1de18d23.css
http://fonts.googleapis.com/css?family=Noto+Sans%3A400%2C700%7CRaleway%3A400%2C700&ver=1.2.1

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:
https://www.google.com/recaptcha/api.js?onload=griwpcOnloadCallback&render=explicit&ver=4.7.8 (5 minutes)
http://connect.facebook.net/ru_RU/sdk.js (20 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

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 11.1KiB (15% reduction).
Minifying https://vk.com/js/al/lite.js?145463682 could save 7.2KiB (15% reduction) after compression.
Minifying http://vk.com/js/api/openapi.js?116 could save 3.5KiB (17% reduction) after compression.
Minifying https://vk.com/js/api/xdm.js?1449919642 could save 433B (17% reduction) after compression.

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="javascript:void(0)" class="sb-toggle-left"></a> is close to 1 other tap targets final.
The tap target <a href="http://nepryak…rubrika/radio/">Радио</a> and 8 others are close to other tap targets.
The tap target <a href="http://nepryak…debat-klub-19/" class="url">«Дебат-клуб»</a> is close to 1 other tap targets.
The tap target <a href="http://nepryakhin.ru/treningi/">• Автор серии тренингов</a> and 3 others are close to 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 3.4KiB (29% reduction).
Compressing https://pp.userapi.com/c625523/v625523901/4f66a/cgCwMEJcM64.jpg could save 796B (30% reduction).
Compressing https://pp.userapi.com/c633219/v633219271/fb0f/yad91gahp3g.jpg could save 636B (31% reduction).
Compressing https://pp.userapi.com/c628228/v628228760/13f56/EQTlGF-Gfzg.jpg could save 630B (29% reduction).
Compressing https://pp.userapi.com/c624119/v624119194/12fa7/pfM8dieqjnE.jpg could save 593B (29% reduction).
Compressing https://pp.userapi.com/c836533/v836533615/71aaf/3Yr_ODW0l4s.jpg could save 500B (31% reduction).
Compressing https://pp.userapi.com/c606520/v606520942/150e/d_Ze5LiRUok.jpg could save 317B (26% 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 407B (50% reduction).
Compressing http://nepryakhin.ru/?wc-ajax=get_refreshed_fragments could save 407B (50% reduction).

Reduce server response time

Your server responded quickly. Learn more about server response time optimization.

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.

Configure the viewport

Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.

Minify HTML

Your HTML is minified. Learn more about minifying HTML.

Minify CSS

Your CSS is minified. Learn more about minifying CSS.

Use legible font sizes

The text on your page is legible. Learn more about using legible font sizes.

Size content to viewport

The contents of your page fit within the viewport. Learn more about sizing content to the viewport.

Prioritize visible content

You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.

Avoid landing page redirects

Your page has no redirects. Learn more about avoiding landing page redirects.

Http Header

Currently Not Available

DNS Lookup

Type Ip Target TTL
A 89.111.179.65 3599
NS ns1.hc.ru 3599
NS ns2.hc.ru 3599
SOA 3600
MX mx.mail.plesk.hosting.hc.ru 3600
TXT 3600
TXT 3600

WhoIs Lookup

Domain Created: 2007-04-16
Domain Age: 12 years
WhoIs:
WhoIs lookup results from whois.tcinet.ru server:

domain:        NEPRYAKHIN.RU
nserver:       ns1.hc.ru.
nserver:       ns2.hc.ru.
state:         REGISTERED, DELEGATED, VERIFIED
person:        Private Person
registrar:     R01-RU
admin-contact: https://partner.r01.ru/contact_admin.khtml
created:       2007-04-16T20:00:00Z
paid-till:     2018-04-16T21:00:00Z
free-date:     2018-05-18
source:        TCI
Last updated on 2018-01-13T23