paseka42.Ru - Info receives about 51 unique visitors and 81 (1.60 per visitor) page views per day which should earn about $0.17/day from advertising revenue. Estimated site value is $68.54. According to Alexa Traffic Rank is ranked number 5,917,371 in the world and 3.0E-6% of global Internet users visit it. Site is hosted in Russia and links to network IP address This server doesn't support HTTPS and doesn't support HTTP/2.

About -

Technologies used on Website

Currently Not Available Profile

Title: Купить пчелопакеты 2019 по цене от 2500 рублей. Карника, карпатка
Last update was 147 days ago
This can take up to 60 seconds. Please wait...

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

How popular is

51 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
5,917,371 visit alexa
Alexa Reach:
3.0E-6%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources


Visitors by country

Russian Federation 100.0%100.0%895526

Where do visitors go on this site?


Competitive Data

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

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

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

Desktop summary

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

Mobile summary

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

+ Abusive Experience Report

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

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Russian Federation 81$0.16

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Russian Federation 5$0.01

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Domain names registrar REG.RU, Ltd 
Server Location:

Russia, RU

Other sites hosted on

+ How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

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 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.5 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.5 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 1.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 40 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.
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.

Screenshot Thumbnails

This is what the load of your site looked like.

Remove unused CSS - Potential savings of 927 KB
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.

SizePotential Savings;merriweather,1,2cm8z6:W:n4,2cm8z8:W:n7;open-sans,1,VvH:W:n4;roboto,1,2clz4T:W:i4,2clz4W:W:n4,2clz4b:W:n7;ubuntu,1,2cm5RR:W:i4,2cm5RQ:W:n4/l
903 KB903 KB
8 KB7 KB
7 KB6 KB
6 KB5 KB
5 KB5 KB
Avoids enormous network payloads - Total size was 1,162 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

903 KB
82 KB
33 KB
17 KB
16 KB
14 KB;merriweather:n4,n7:all;ubuntu:n4,i4:all;roboto:n4,n7,i4:all.js
9 KB
9 KB
8 KB
7 KB
Minimizes main-thread work - 0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Time Spent
Script Evaluation
337 ms
219 ms
Style & Layout
191 ms
Parse HTML & CSS
36 ms
Script Parsing & Compilation
22 ms
20 ms
Avoids an excessive DOM size - 809 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Keep request counts low and transfer sizes small - 41 requests • 2,056 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
412056 KB
9977 KB
6931 KB
14109 KB
923 KB
116 KB
21 KB
00 KB
191940 KB
Eliminate render-blocking resources - Potential savings of 110 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.

SizePotential Savings
3 KB70
6 KB70
8 KB70;merriweather:n4,n7:all;ubuntu:n4,i4:all;roboto:n4,n7,i4:all.js
9 KB230
7 KB230
5 KB190
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms297 ms16 KB119 KB200text/htmlDocument
324 ms493 ms3 KB8 KB200text/cssStylesheet
325 ms494 ms6 KB80 KB200text/cssStylesheet
325 ms495 ms8 KB80 KB200text/cssStylesheet;merriweather:n4,n7:all;ubuntu:n4,i4:all;roboto:n4,n7,i4:all.js
325 ms496 ms9 KB24 KB200text/javascriptScript
326 ms496 ms7 KB27 KB200text/cssStylesheet
326 ms496 ms5 KB20 KB200text/cssStylesheet
326 ms504 ms0 KB0 KB200image/gifImage
326 ms609 ms0 KB0 KB301text/html
506 ms679 ms7 KB16 KB200text/javascriptScript;merriweather,1,2cm8z6:W:n4,2cm8z8:W:n7;open-sans,1,VvH:W:n4;roboto,1,2clz4T:W:i4,2clz4W:W:n4,2clz4b:W:n7;ubuntu,1,2cm5RR:W:i4,2cm5RQ:W:n4/l
514 ms788 ms903 KB1194 KB200text/cssStylesheet
532 ms789 ms82 KB82 KB200font/woffFont
570 ms1072 ms0 KB0 KB302
574 ms1056 ms33 KB91 KB200application/x-javascriptScript
609 ms1178 ms4 KB3 KB200image/gifImage
854 ms899 ms35 KB35 KB200font/opentypeFont
855 ms904 ms35 KB35 KB200font/opentypeFont
856 ms910 ms50 KB50 KB200font/opentypeFont
858 ms920 ms195 KB195 KB200font/opentypeFont
860 ms926 ms172 KB172 KB200font/opentypeFont
863 ms933 ms172 KB172 KB200font/opentypeFont
865 ms939 ms122 KB122 KB200font/opentypeFont
866 ms944 ms114 KB114 KB200font/opentypeFont
1053 ms1178 ms0 KB0 KB200image/gifImage
1073 ms1211 ms2 KB1 KB200image/pngImage
1110 ms1262 ms1 KB2 KB200text/javascriptScript
1271 ms1597 ms17 KB60 KB200text/javascriptScript
1271 ms1597 ms1 KB2 KB200text/javascriptScript
1272 ms1598 ms1 KB2 KB200text/javascriptScript
1272 ms1600 ms14 KB52 KB200text/javascriptScript
1273 ms1600 ms9 KB33 KB200text/javascriptScript
1273 ms1600 ms3 KB8 KB200text/javascriptScript
1273 ms1628 ms4 KB10 KB200text/javascriptScript
1274 ms1628 ms2 KB6 KB200text/javascriptScript
1274 ms1645 ms2 KB4 KB200text/javascriptScript
1275 ms1751 ms3 KB6 KB200text/javascriptScript
1786 ms2050 ms3 KB3 KB200image/gifImage
1878 ms2050 ms3 KB3 KB200image/pngImage
1878 ms2051 ms7 KB7 KB200image/jpegImage
1878 ms2051 ms3 KB5 KB200image/svg+xmlImage
2067 ms2233 ms1 KB3 KB404text/htmlImage
Serve static assets with an efficient cache policy - 24 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize;merriweather:n4,n7:all;ubuntu:n4,i4:all;roboto:n4,n7,i4:all.js
86400000 ms9 KB;merriweather,1,2cm8z6:W:n4,2cm8z8:W:n7;open-sans,1,VvH:W:n4;roboto,1,2clz4T:W:i4,2clz4W:W:n4,2clz4b:W:n7;ubuntu,1,2cm5RR:W:i4,2cm5RQ:W:n4/l
604800000 ms903 KB
604800000 ms0 KB
2592000000 ms33 KB
2592000000 ms17 KB
2592000000 ms14 KB
2592000000 ms9 KB
2592000000 ms8 KB
2592000000 ms7 KB
2592000000 ms7 KB
2592000000 ms6 KB
2592000000 ms4 KB
2592000000 ms3 KB
2592000000 ms3 KB
2592000000 ms3 KB
2592000000 ms3 KB
2592000000 ms3 KB
2592000000 ms3 KB
2592000000 ms2 KB
2592000000 ms2 KB
2592000000 ms1 KB
2592000000 ms1 KB
2592000000 ms1 KB
2592000000 ms0 KB
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
328 ms
20 ms
523 ms
6 ms
536 ms
13 ms
549 ms
49 ms
822 ms
16 ms
839 ms
23 ms
863 ms
46 ms
909 ms
18 ms
927 ms
5 ms
933 ms
6 ms
938 ms
7 ms
945 ms
7 ms
952 ms
6 ms
958 ms
7 ms
965 ms
5 ms
970 ms
5 ms
977 ms
24 ms
1002 ms
8 ms
1010 ms
7 ms
1016 ms
13 ms
1029 ms
13 ms
1043 ms
24 ms
1067 ms
14 ms
1082 ms
19 ms
1109 ms
20 ms
1299 ms
6 ms
1305 ms
23 ms
1329 ms
6 ms
1632 ms
28 ms
1782 ms
126 ms
1908 ms
6 ms
2083 ms
11 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
258 ms
JavaScript execution time - 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
424 ms12 ms1 ms
288 ms239 ms1 ms
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.

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.

Minimize Critical Requests Depth - 16 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 300 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.

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.

Page Speed (Google PageSpeed Insights) - Mobile

Currently Not Available

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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

Your page has 2 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:;merriweather:n4,n7:all;ubuntu:n4,i4:all;roboto:n4,n7,i4:all.js
Optimize CSS Delivery of the following:;merriweather,1,2cm8z6:W:n4,2cm8z8:W:n7;open-sans,1,VvH:W:n4;roboto,1,2clz4T:W:i4,2clz4W:W:n4,2clz4b:W:n7;ubuntu,1,2cm5RR:W:i4,2cm5RQ:W:n4/l

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.

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

The element <div id="u798popup" class="popup_anchor a…hrough grpelem"></div> falls outside the viewport.
The element <div id="u45376" class="size_fixed grp…shared_content"></div> falls outside the viewport.

Optimize images

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

Optimize the following images to reduce their size by 6.2KiB (84% reduction).

Compressing and resizing could save 2.9KiB (97% reduction).
Compressing and resizing could save 2.9KiB (97% reduction).
Compressing could save 355B (26% reduction).

Minify HTML

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

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

Minifying could save 2.5KiB (17% reduction) after compression.

Minify JavaScript

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

Minify JavaScript for the following resources to reduce their size by 268B (28% reduction).

Minifying could save 268B (28% reduction) after compression.
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.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
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.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
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.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Enable compression
You have compression enabled. Learn more about enabling compression.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 118.93 KB
Compressed size: 15.23 KB
File reduced by: 103.7 KB (87%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify does not support HTTPS
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Sun, 14 Jul 2019 16:13:05 GMT
Content-Type: text/html
Last-Modified: Tue, 27 Nov 2018 08:21:05 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
ETag: W/"5bfcfe71-1dbb6"
X-Powered-By: PleskLin
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
TXT 3600
MX 3600
MX 3600
SOA 3600
Serial Number 2017090604
Refresh 10800
Retry 3600
Expire 604800
Minimum TTL 0
A 3564
NS 3563
NS 3563

+ Whois Lookup

Domain Created:
Domain Age:
1 years 10 months 13 days  

whois lookup at
% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% (in Russian)
% (in English).

domain: PASEKA42.RU
person: Private Person
registrar: REGRU-RU
created: 2017-09-01T08:49:12Z
paid-till: 2019-09-01T08:49:12Z
free-date: 2019-10-02
source: TCI

Last updated on 2019-07-14T16:11:32Z
Last update was 147 days ago
This can take up to 60 seconds. Please wait...

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

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