Matkan.Ru - Info matkan.ru

matkan.ru receives about 2,586 unique visitors and 6,464 (2.50 per visitor) page views per day which should earn about $4.59/day from advertising revenue. Estimated site value is $3,350.37. According to Alexa Traffic Rank matkan.ru is ranked number 719,235 in the world and 5.7E-5% of global Internet users visit it. Site is hosted in Moscow, Moscow, 129128, Russia and links to network IP address 91.236.136.43. This server doesn't support HTTPS and doesn't support HTTP/2.

About - matkan.ru


Technologies used on Website

Miscellaneous
Gravatar
Analytics
Liveinternet
Web Servers
Nginx
Reverse proxies
Nginx
CMS
WordPress
Blogs
WordPress
Programming Languages
PHP
Databases
MySQL

matkan.ru Profile

Title: Блог Курочка А.Н.
Last update was 115 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is matkan.ru?

2.6K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
2,586
Monthly Unique Visitors:
62,064
Pages per Visit:
2.50
Daily Pageviews:
6,464
Alexa Rank:
719,235 visit alexa
Alexa Reach:
5.7E-5%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Users%Pageviews%Rank
Kazakhstan 100.0%100.0%3415

Where do visitors go on this site?

Reach%Pageviews%PerUser
matkan.ru
100.00%100.00%2.2

Competitive Data

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

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is matkan.ru?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

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

Desktop summary

Root domain:
matkan.ru
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
matkan.ru
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much matkan.ru can earn?

Daily Revenue:
$4.59
Monthly Revenue:
$137.70
Yearly Revenue:
$1,675.35
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Kazakhstan 6,464$4.59

How much money do matkan.ru lose due to Adblock?

Daily Revenue Loss:
$0.14
Monthly Revenue Loss:
$4.13
Yearly Revenue Loss:
$50.25
Daily Pageviews Blocked:
194
Monthly Pageviews Blocked:
5,818
Yearly Pageviews Blocked:
70,781
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Kazakhstan 194$0.14

How much is matkan.ru worth?

Website Value:
$3,350.37

+ Where is matkan.ru hosted?

Server IP:
91.236.136.43
ASN:
AS44094 
ISP:
Webhost LLC 
Server Location:
Moscow
Moscow, MOW
129128
Russia, RU
 

Other sites hosted on 91.236.136.43

+ How fast does matkan.ru load?

Average Load Time:
(1598 ms) 59 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.4 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 0.4 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 0.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 30 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 0.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
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.
Estimated Input Latency 10 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.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 68 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://matkan.ru/wp-includes/css/dist/block-library/style.min.css?ver=5.3.2
8 KB
http://matkan.ru/
7 KB
http://matkan.ru/wp-content/themes/voidy/img/rss.png
7 KB
http://matkan.ru/wp-content/themes/voidy/img/twitter.png
7 KB
http://matkan.ru/wp-includes/js/wp-emoji-release.min.js?ver=5.3.2
5 KB
http://matkan.ru/wp-content/themes/voidy/style.css
5 KB
http://matkan.ru/wp-content/uploads/2014/11/%D0%AF.jpg
5 KB
http://matkan.ru/wp-content/themes/voidy/img/bg_header.png
3 KB
http://matkan.ru/wp-content/themes/voidy/img/bg_footer.png
2 KB
http://2.gravatar.com/avatar/81632dd73ad927d02bf28c3c4f95cb38?s=28&d=wavatar&r=g
2 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
65 ms
Script Evaluation
61 ms
Other
44 ms
Rendering
19 ms
Parse HTML & CSS
14 ms
Script Parsing & Compilation
4 ms
Avoids an excessive DOM size - 195 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
195
Maximum DOM Depth
11
Maximum Child Elements
13
Keep request counts low and transfer sizes small - 26 requests • 68 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
2668 KB
Image
1738 KB
Stylesheet
415 KB
Script
38 KB
Document
17 KB
Other
10 KB
Media
00 KB
Font
00 KB
Third-party
68 KB
Eliminate render-blocking resources - Potential savings of 270 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.

URL
SizePotential Savings
http://matkan.ru/wp-content/themes/voidy/style.css
5 KB70
http://matkan.ru/wp-includes/css/dist/block-library/style.min.css?ver=5.3.2
8 KB110
http://matkan.ru/wp-content/plugins/contact-form-plugin/css/form_style.css?ver=4.1.8
1 KB110
http://matkan.ru/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
1 KB110
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://matkan.ru/
0 ms467 ms7 KB19 KB200text/htmlDocument
http://matkan.ru/wp-content/themes/voidy/style.css
486 ms629 ms5 KB14 KB200text/cssStylesheet
http://matkan.ru/wp-includes/css/dist/block-library/style.min.css?ver=5.3.2
487 ms629 ms8 KB40 KB200text/cssStylesheet
http://matkan.ru/wp-content/plugins/contact-form-plugin/css/form_style.css?ver=4.1.8
487 ms628 ms1 KB5 KB200text/cssStylesheet
http://matkan.ru/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
487 ms627 ms1 KB0 KB200text/cssStylesheet
http://matkan.ru/wp-content/uploads/2014/11/%D0%AF.jpg
488 ms630 ms5 KB5 KB200image/jpegImage
http://2.gravatar.com/avatar/81632dd73ad927d02bf28c3c4f95cb38?s=28&d=wavatar&r=g
488 ms505 ms2 KB2 KB200image/pngImage
http://0.gravatar.com/avatar/39642b2f1ea2f36fba9898a3eac8aec8?s=28&d=wavatar&r=g
681 ms709 ms2 KB2 KB200image/pngImage
http://0.gravatar.com/avatar/f5d2880ebf41faad4826a059cd7069ea?s=28&d=wavatar&r=g
681 ms740 ms2 KB1 KB200image/pngImage
http://webhost1.ru/design/1/88x31-2.jpg
681 ms955 ms1 KB1 KB200image/jpegImage
http://matkan.ru/wp-includes/js/comment-reply.min.js?ver=5.3.2
508 ms647 ms1 KB2 KB200application/javascriptScript
http://matkan.ru/wp-includes/js/wp-embed.min.js?ver=5.3.2
635 ms774 ms1 KB1 KB200application/javascriptScript
http://matkan.ru/wp-includes/js/wp-emoji-release.min.js?ver=5.3.2
682 ms824 ms5 KB14 KB200application/javascriptScript
http://matkan.ru/wp-content/themes/voidy/img/bg_header.png
688 ms829 ms3 KB3 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/twitter.png
688 ms827 ms7 KB6 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/rss.png
688 ms828 ms7 KB7 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/menu-bg.png
689 ms828 ms2 KB2 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/menu-bottom-bg.png?m
690 ms829 ms1 KB1 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/menu-curve-bg.png
690 ms968 ms0 KB0 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/bg.png
690 ms830 ms1 KB0 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/icon_comments.gif
691 ms830 ms0 KB0 KB200image/gifImage
http://matkan.ru/wp-content/themes/voidy/img/widget-title-bg.png
693 ms832 ms1 KB1 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/bullet.png
743 ms882 ms1 KB0 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/bg_footer.png
745 ms884 ms2 KB2 KB200image/pngImage
http://counter.yadro.ru/hit?t19.2;r;s800*600*24;uhttp%3A//matkan.ru/;0.2080495138811731
779 ms922 ms0 KB0 KB302text/html
http://counter.yadro.ru/p.gif
922 ms1061 ms0 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 23 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://2.gravatar.com/avatar/81632dd73ad927d02bf28c3c4f95cb38?s=28&d=wavatar&r=g
300000 ms2 KB
http://0.gravatar.com/avatar/39642b2f1ea2f36fba9898a3eac8aec8?s=28&d=wavatar&r=g
300000 ms2 KB
http://0.gravatar.com/avatar/f5d2880ebf41faad4826a059cd7069ea?s=28&d=wavatar&r=g
300000 ms2 KB
http://matkan.ru/wp-includes/css/dist/block-library/style.min.css?ver=5.3.2
2592000000 ms8 KB
http://matkan.ru/wp-content/themes/voidy/img/rss.png
2592000000 ms7 KB
http://matkan.ru/wp-content/themes/voidy/img/twitter.png
2592000000 ms7 KB
http://matkan.ru/wp-includes/js/wp-emoji-release.min.js?ver=5.3.2
2592000000 ms5 KB
http://matkan.ru/wp-content/themes/voidy/style.css
2592000000 ms5 KB
http://matkan.ru/wp-content/uploads/2014/11/%D0%AF.jpg
2592000000 ms5 KB
http://matkan.ru/wp-content/themes/voidy/img/bg_header.png
2592000000 ms3 KB
http://matkan.ru/wp-content/themes/voidy/img/bg_footer.png
2592000000 ms2 KB
http://matkan.ru/wp-content/themes/voidy/img/menu-bg.png
2592000000 ms2 KB
http://matkan.ru/wp-includes/js/comment-reply.min.js?ver=5.3.2
2592000000 ms1 KB
http://webhost1.ru/design/1/88x31-2.jpg
2592000000 ms1 KB
http://matkan.ru/wp-content/plugins/contact-form-plugin/css/form_style.css?ver=4.1.8
2592000000 ms1 KB
http://matkan.ru/wp-content/themes/voidy/img/menu-bottom-bg.png?m
2592000000 ms1 KB
http://matkan.ru/wp-content/themes/voidy/img/widget-title-bg.png
2592000000 ms1 KB
http://matkan.ru/wp-includes/js/wp-embed.min.js?ver=5.3.2
2592000000 ms1 KB
http://matkan.ru/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
2592000000 ms1 KB
http://matkan.ru/wp-content/themes/voidy/img/bg.png
2592000000 ms1 KB
http://matkan.ru/wp-content/themes/voidy/img/bullet.png
2592000000 ms1 KB
http://matkan.ru/wp-content/themes/voidy/img/menu-curve-bg.png
2592000000 ms0 KB
http://matkan.ru/wp-content/themes/voidy/img/icon_comments.gif
2592000000 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
500 ms
10 ms
663 ms
50 ms
713 ms
41 ms
770 ms
31 ms
804 ms
7 ms
854 ms
8 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
147 ms4 ms1 ms
Remove unused CSS
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.

Serve images in next-gen formats
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.

Avoid chaining critical requests - 6 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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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 470 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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)2.5s 0% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 23% 55% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 55% 21% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 21%
First Input Delay (FID)259ms 1% of loads for this page have a fast (<100ms) First Input Delay (FID) 1% 97% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 97% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an AVERAGE 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)1.8s 40% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 40% 49% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 49% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)276ms 0% of loads for this page have a fast (<100ms) First Input Delay (FID) 3% 93% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 93% 2% of loads for this page have a slow (>300ms) First Input Delay (FID) 2%

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 160 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 1.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
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.
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 2514 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 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.
Speed Index 2.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.4 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 1.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 195 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
195
Maximum DOM Depth
11
Maximum Child Elements
13
Keep request counts low and transfer sizes small - 26 requests • 77 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
2677 KB
Image
1747 KB
Stylesheet
415 KB
Script
38 KB
Document
17 KB
Other
10 KB
Media
00 KB
Font
00 KB
Third-party
617 KB
Eliminate render-blocking resources - Potential savings of 680 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.

URL
SizePotential Savings
http://matkan.ru/wp-content/themes/voidy/style.css
5 KB180
http://matkan.ru/wp-includes/css/dist/block-library/style.min.css?ver=5.3.2
8 KB480
http://matkan.ru/wp-content/plugins/contact-form-plugin/css/form_style.css?ver=4.1.8
1 KB330
http://matkan.ru/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
1 KB330
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://matkan.ru/
0 ms703 ms7 KB19 KB200text/htmlDocument
http://matkan.ru/wp-content/themes/voidy/style.css
716 ms1086 ms5 KB14 KB200text/cssStylesheet
http://matkan.ru/wp-includes/css/dist/block-library/style.min.css?ver=5.3.2
717 ms858 ms8 KB40 KB200text/cssStylesheet
http://matkan.ru/wp-content/plugins/contact-form-plugin/css/form_style.css?ver=4.1.8
717 ms972 ms1 KB5 KB200text/cssStylesheet
http://matkan.ru/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
717 ms1085 ms1 KB0 KB200text/cssStylesheet
http://matkan.ru/wp-content/uploads/2014/11/%D0%AF.jpg
717 ms1013 ms5 KB5 KB200image/jpegImage
http://2.gravatar.com/avatar/81632dd73ad927d02bf28c3c4f95cb38?s=56&d=wavatar&r=g
718 ms734 ms6 KB5 KB200image/pngImage
http://0.gravatar.com/avatar/39642b2f1ea2f36fba9898a3eac8aec8?s=56&d=wavatar&r=g
1125 ms1141 ms5 KB5 KB200image/pngImage
http://0.gravatar.com/avatar/f5d2880ebf41faad4826a059cd7069ea?s=56&d=wavatar&r=g
1125 ms1142 ms4 KB4 KB200image/pngImage
http://webhost1.ru/design/1/88x31-2.jpg
1125 ms1495 ms1 KB1 KB200image/jpegImage
http://matkan.ru/wp-includes/js/comment-reply.min.js?ver=5.3.2
735 ms1113 ms1 KB2 KB200application/javascriptScript
http://matkan.ru/wp-includes/js/wp-embed.min.js?ver=5.3.2
1014 ms1153 ms1 KB1 KB200application/javascriptScript
http://matkan.ru/wp-includes/js/wp-emoji-release.min.js?ver=5.3.2
1125 ms1503 ms5 KB14 KB200application/javascriptScript
http://matkan.ru/wp-content/themes/voidy/img/bg_header.png
1129 ms1267 ms3 KB3 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/twitter.png
1130 ms1268 ms7 KB6 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/rss.png
1130 ms1269 ms7 KB7 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/menu-bg.png
1131 ms1274 ms2 KB2 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/menu-bottom-bg.png?m
1131 ms1269 ms1 KB1 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/menu-curve-bg.png
1131 ms1269 ms0 KB0 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/bg.png
1131 ms1270 ms1 KB0 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/icon_comments.gif
1132 ms1274 ms0 KB0 KB200image/gifImage
http://matkan.ru/wp-content/themes/voidy/img/widget-title-bg.png
1133 ms1406 ms1 KB1 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/bullet.png
1155 ms1427 ms1 KB0 KB200image/pngImage
http://matkan.ru/wp-content/themes/voidy/img/bg_footer.png
1156 ms1430 ms2 KB2 KB200image/pngImage
http://counter.yadro.ru/hit?t19.2;r;s412*660*24;uhttp%3A//matkan.ru/;0.6532441289381798
1171 ms1309 ms0 KB0 KB302text/html
http://counter.yadro.ru/p.gif
1313 ms1451 ms0 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 23 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://2.gravatar.com/avatar/81632dd73ad927d02bf28c3c4f95cb38?s=56&d=wavatar&r=g
300000 ms6 KB
http://0.gravatar.com/avatar/39642b2f1ea2f36fba9898a3eac8aec8?s=56&d=wavatar&r=g
300000 ms5 KB
http://0.gravatar.com/avatar/f5d2880ebf41faad4826a059cd7069ea?s=56&d=wavatar&r=g
300000 ms4 KB
http://matkan.ru/wp-includes/css/dist/block-library/style.min.css?ver=5.3.2
2592000000 ms8 KB
http://matkan.ru/wp-content/themes/voidy/img/rss.png
2592000000 ms7 KB
http://matkan.ru/wp-content/themes/voidy/img/twitter.png
2592000000 ms7 KB
http://matkan.ru/wp-includes/js/wp-emoji-release.min.js?ver=5.3.2
2592000000 ms5 KB
http://matkan.ru/wp-content/themes/voidy/style.css
2592000000 ms5 KB
http://matkan.ru/wp-content/uploads/2014/11/%D0%AF.jpg
2592000000 ms5 KB
http://matkan.ru/wp-content/themes/voidy/img/bg_header.png
2592000000 ms3 KB
http://matkan.ru/wp-content/themes/voidy/img/bg_footer.png
2592000000 ms2 KB
http://matkan.ru/wp-content/themes/voidy/img/menu-bg.png
2592000000 ms2 KB
http://matkan.ru/wp-includes/js/comment-reply.min.js?ver=5.3.2
2592000000 ms1 KB
http://webhost1.ru/design/1/88x31-2.jpg
2592000000 ms1 KB
http://matkan.ru/wp-content/plugins/contact-form-plugin/css/form_style.css?ver=4.1.8
2592000000 ms1 KB
http://matkan.ru/wp-content/themes/voidy/img/menu-bottom-bg.png?m
2592000000 ms1 KB
http://matkan.ru/wp-content/themes/voidy/img/widget-title-bg.png
2592000000 ms1 KB
http://matkan.ru/wp-includes/js/wp-embed.min.js?ver=5.3.2
2592000000 ms1 KB
http://matkan.ru/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70
2592000000 ms1 KB
http://matkan.ru/wp-content/themes/voidy/img/bg.png
2592000000 ms1 KB
http://matkan.ru/wp-content/themes/voidy/img/bullet.png
2592000000 ms1 KB
http://matkan.ru/wp-content/themes/voidy/img/menu-curve-bg.png
2592000000 ms0 KB
http://matkan.ru/wp-content/themes/voidy/img/icon_comments.gif
2592000000 ms0 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
731 ms
8 ms
1112 ms
40 ms
1152 ms
24 ms
1179 ms
12 ms
1529 ms
7 ms
JavaScript execution time - 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
382 ms11 ms4 ms
http://matkan.ru/
147 ms143 ms3 ms
Avoids enormous network payloads - Total size was 77 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://matkan.ru/wp-includes/css/dist/block-library/style.min.css?ver=5.3.2
8 KB
http://matkan.ru/
7 KB
http://matkan.ru/wp-content/themes/voidy/img/rss.png
7 KB
http://matkan.ru/wp-content/themes/voidy/img/twitter.png
7 KB
http://2.gravatar.com/avatar/81632dd73ad927d02bf28c3c4f95cb38?s=56&d=wavatar&r=g
6 KB
http://matkan.ru/wp-includes/js/wp-emoji-release.min.js?ver=5.3.2
5 KB
http://0.gravatar.com/avatar/39642b2f1ea2f36fba9898a3eac8aec8?s=56&d=wavatar&r=g
5 KB
http://matkan.ru/wp-content/themes/voidy/style.css
5 KB
http://matkan.ru/wp-content/uploads/2014/11/%D0%AF.jpg
5 KB
http://0.gravatar.com/avatar/f5d2880ebf41faad4826a059cd7069ea?s=56&d=wavatar&r=g
4 KB
Minimizes main-thread work - 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
182 ms
Other
144 ms
Style & Layout
128 ms
Rendering
60 ms
Parse HTML & CSS
34 ms
Script Parsing & Compilation
14 ms
Avoid chaining critical requests - 6 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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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.

Reduce server response times (TTFB) - Root document took 700 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

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.

Remove unused CSS
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.

Serve images in next-gen formats
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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use 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 5 pixels tall (13 CSS pixels) .
Об авторе and 1 others render only 6 pixels tall (16 CSS pixels) .
Карта сайта and 1 others render only 6 pixels tall (16 CSS pixels) .
вует на своем…воим коллегам. and 1 others render only 5 pixels tall (14 CSS pixels) .
3 комментария renders only 5 pixels tall (14 CSS pixels) .
12021959 renders only 5 pixels tall (13 CSS pixels) .
29.10.2019 в 23:40 and 2 others render only 3 pixels tall (9 CSS pixels) .
Александр Нико…рных учеников. and 2 others render only 5 pixels tall (14 CSS pixels) .
Войдите, чтобы ответить and 2 others render only 4 pixels tall (10 CSS pixels) .
AliyaZhakenova and 1 others render only 5 pixels tall (13 CSS pixels) .
чтобы оставить комментарий. and 1 others render only 5 pixels tall (13 CSS pixels) .
ввойти renders only 5 pixels tall (13 CSS pixels) .
Календарь and 2 others render only 6 pixels tall (16 CSS pixels) .
Архивы renders only 5 pixels tall (14 CSS pixels) .
Календарно-тем…е планирование and 9 others render only 5 pixels tall (14 CSS pixels) .
(10) and 9 others render only 5 pixels tall (14 CSS pixels) .
Февраль 2020 renders only 5 pixels tall (14 CSS pixels) .
Пн and 6 others render only 5 pixels tall (14 CSS pixels) .
« Янв renders only 5 pixels tall (14 CSS pixels) .
10 and 27 others render only 5 pixels tall (14 CSS pixels) .
9 renders only 5 pixels tall (14 CSS pixels) .
Thanx: and 1 others render only 3 pixels tall (9 CSS pixels) .
. Учителям мат…по обновленке and 1 others render only 4 pixels tall (11 CSS pixels) .
Блог Курочка А.Н. renders only 4 pixels tall (11 CSS pixels) .

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

Your page has 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.Optimize CSS Delivery of the following:

http://matkan.ru/wp-content/themes/voidy/style.css
http://matkan.ru/wp-includes/css/dist/block-library/style.min.css?ver=5.3.2
http://matkan.ru/wp-content/plugins/contact-form-plugin/css/form_style.css?ver=4.1.8
http://matkan.ru/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70

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

The element <a href="http://twitter.com/"></a> falls outside the viewport.
The element <a href="http://matkan.ru/feed/rss/"></a> falls outside the viewport.
The element <a href="http://matkan.ru/karta-sajta/">Карта сайта</a> falls outside the viewport.
The element <h2 class="widgettitle">Архивы</h2> falls outside the viewport.
The element <h2 class="widgettitle">Рубрики</h2> falls outside the viewport.
The element <li class="cat-item cat-item-171">Анализ СОР и СОЧ (1)</li> falls outside the viewport.
The element <li class="cat-item cat-item-26">Календарно-тем…анирование (1)</li> falls outside the viewport.
The element <li class="cat-item cat-item-1">Математика в школе (6)</li> falls outside the viewport.
The element <li class="cat-item cat-item-7">Нормативные документы (5)</li> falls outside the viewport.
The element <li class="cat-item cat-item-12">Олимпиада (10)</li> falls outside the viewport.
The element <li class="cat-item cat-item-27">Поурочное планирование (1)</li> falls outside the viewport.
The element <li class="cat-item cat-item-160">СОР (2)</li> falls outside the viewport.
The element <li class="cat-item cat-item-161">СОЧ (1)</li> falls outside the viewport.
The element <li class="cat-item cat-item-112">Среднесрочное планирование (6)</li> falls outside the viewport.
The element <li class="cat-item cat-item-162">Формативное оценивание (1)</li> falls outside the viewport.
The element <h2 class="widgettitle">Календарь</h2> falls outside the viewport.
The element <div id="calendar_wrap" class="calendar_wrap">Февраль 2020…242526272829</div> falls outside the viewport.
The element <div class="textwidget"></div> falls outside the viewport.
The element <a href="http://runetbi…s-secrets.com/">Runetbiz</a> falls outside the viewport.

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.

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="http://twitter.com/"></a> and 1 others are close to other tap targets .
The tap target <a href="http://matkan.…iz-soch-i-sor/">Анализ СОР и СОЧ</a> and 10 others are close to other tap targets .

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://0.gravatar.com/avatar/39642b2f1ea2f36fba9898a3eac8aec8?s=56&d=wavatar&r=g (5 minutes)
http://0.gravatar.com/avatar/f5d2880ebf41faad4826a059cd70***ea?s=56&d=wavatar&r=g (5 minutes)
http://2.gravatar.com/avatar/81632dd73ad927d02bf28c3c4f95cb38?s=56&d=wavatar&r=g (5 minutes)

Reduce server response time

In our test, your server responded in 0.35 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Optimize images

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

Optimize the following images to reduce their size by 8.2KiB (44% reduction).

Compressing http://matkan.ru/wp-content/themes/voidy/img/twitter.png could save 3.1KiB (49% reduction).
Compressing http://matkan.ru/wp-content/themes/voidy/img/rss.png could save 3.1KiB (46% reduction).
Compressing http://matkan.ru/wp-content/uploads/2014/11/%D0%AF.jpg could save 1.9KiB (42% reduction).
Compressing http://webhost1.ru/design/1/88x31-2.jpg could save 155B (15% reduction).

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 1.1KiB (28% reduction).

Minifying http://matkan.ru/wp-content/themes/voidy/style.css could save 1.1KiB (28% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
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.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does matkan.ru use compression?

matkan.ru use gzip compression.
Original size: 19.16 KB
Compressed size: 6.81 KB
File reduced by: 12.35 KB (64%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

matkan.ru does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

matkan.ru does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Sat, 08 Feb 2020 21:39:04 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: PHPSESSID=da0c468bcf2ad042f580a54afdcb4fdd; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
X-Pingback: http://matkan.ru/xmlrpc.php
Link: <http://matkan.ru/wp-json/>; rel="https://api.w.org/"
Link: <http://matkan.ru/>; rel=shortlink
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
SOA 3600
Mname ns1.webhost1.ru
Rname root.matkan.ru
Serial Number 2014081123
Refresh 10800
Retry 3600
Expire 1209600
Minimum TTL 0
TXT 3600
MX mail.matkan.ru 3600
A 91.236.136.43 3577
NS ns3.webhost1.net 3577
NS ns4.webhost1.net 3577
NS ns1.webhost1.ru 3577
NS ns2.webhost1.ru 3577

+ Whois Lookup

Domain Created:
2012-01-10
Domain Age:
8 years 29 days  
WhoIs:
 

whois lookup at whois.tcinet.ru...
% 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: MATKAN.RU
nserver: ns1.webhost1.ru.
nserver: ns2.webhost1.ru.
state: REGISTERED, DELEGATED, VERIFIED
person: Private Person
registrar: REGRU-RU
admin-contact: http://www.reg.ru/whois/admin_contact
created: 2012-01-10T09:49:09Z
paid-till: 2021-01-10T10:49:09Z
free-date: 2021-02-10
source: TCI

Last updated on 2020-02-08T21:36:33Z
Last update was 115 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with matkan.ru in any way. Only publicly available statistics data are displayed.
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

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