Querycom.Ru - Info querycom.ru

querycom.ru receives about 1,561 unique visitors and 1,873 (1.20 per visitor) page views per day which should earn about $2.14/day from advertising revenue. Estimated site value is $1,562.83. According to Alexa Traffic Rank querycom.ru is ranked number 631,575 in the world and 9.2E-5% of global Internet users visit it. Site is hosted in Germany and links to network IP address This server supports HTTPS and doesn't support HTTP/2.

About - querycom.ru

Квериком - профессиональная система бизнес-аналитики. Информация по рынкам и компаниям.
Edit Site Info

Technologies used on Website

Web Servers
Phusion Passenger
Reverse Proxy
Web Frameworks
Ruby on Rails
Programming Languages

querycom.ru Profile

Title: Квериком - профессиональная система бизнес-аналитики
Keywords: квериком, бизнес, аналитика, анализ, компании
Last update was 58 days ago
This can take up to 60 seconds. Please wait...

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

How popular is querycom.ru?

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

Alexa Traffic Ranks
Search Traffic

Visitors by country

Russian Federation 52.6%56.3%86485

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 querycom.ru?

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 querycom.ru can earn?

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

Daily earning by country

Russian Federation 1,054$2.14

How much money do querycom.ru 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 63$0.13

How much is querycom.ru worth?

Website Value:

+ Where is querycom.ru hosted?

Server IP:
Hetzner Online GmbH 
Server Location:

Germany, DE

Other sites hosted on

+ How fast does querycom.ru load?

Average Load Time:
(12848 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

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.
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.6 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.6 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.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 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.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Third-Party usage - Third-party code blocked the main thread for 0 ms
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.

SizeMain-Thread Blocking Time
0 KB0 ms
0 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
663 ms
19 ms
687 ms
6 ms
1026 ms
18 ms
1044 ms
66 ms
1111 ms
6 ms
1118 ms
12 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.

Total CPU TimeScript EvaluationScript Parse
131 ms3 ms1 ms
Remove unused CSS - Potential savings of 142 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
/* * # Semantic UI - 2.4.0 * https://github.com/Semantic-Org/Semantic-UI * http://www.semantic-ui...
142 KB142 KB
Avoids enormous network payloads - Total size was 86 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

70 KB
9 KB
7 KB
0 KB
0 KB
0 KB
0 KB
0 KB
0 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Time Spent
Style & Layout
60 ms
36 ms
17 ms
Parse HTML & CSS
15 ms
Script Evaluation
10 ms
Script Parsing & Compilation
7 ms
Avoids an excessive DOM size - 556 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](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.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
(Initial: http://querycom.ru/)
Keep request counts low and transfer sizes small - 9 requests • 86 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
986 KB
370 KB
29 KB
17 KB
10 KB
20 KB
00 KB
00 KB
20 KB
Eliminate render-blocking resources - Potential savings of 80 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
70 KB270
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms122 ms0 KB0 KB301text/html
122 ms640 ms7 KB32 KB200text/htmlDocument
668 ms674 ms0 KB0 KB-1Stylesheet
668 ms673 ms0 KB0 KB-1Stylesheet
668 ms674 ms0 KB0 KB-1Script
669 ms990 ms70 KB269 KB200application/javascriptScript
670 ms784 ms9 KB9 KB200image/pngImage
670 ms674 ms0 KB0 KB-1Image
1096 ms1109 ms0 KB0 KB-1Script
Serve static assets with an efficient cache policy - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
0 ms70 KB
2592000000 ms9 KB
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.

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

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

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 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:

Optimize CSS Delivery of the following:


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

The element <a href="/legal-basis" class="ui item">Правовые основания</a> falls outside the viewport.
The element <a href="/" class="ui item">О проекте</a> falls outside the viewport.
The element <i class="key icon"> falls outside the viewport.
The element <h1 class="ui horizontal…medium header">СИСТЕМА БИЗНЕС…ИКИ &quot;КВЕРИКОМ&quot;</h1> falls outside the viewport.
The element <img src="/images/statistics.png"> falls outside the viewport.
The element <span class="underlined">Предпринимателей:</span> falls outside the viewport.
The element <span class="underlined">Посещаемость, за неделю:</span> falls outside the viewport.

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://querycom.ru/application.css (expiration not specified)
https://querycom.ru/semantic.chartist.min.css (expiration not specified)
https://querycom.ru/semantic.min.js (expiration not specified)
https://mc.yandex.ru/metrika/advert.gif (60 minutes)
https://mc.yandex.ru/metrika/tag.js (60 minutes)

Reduce server response time

In our test, your server responded in 0.27 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 2.7KiB (15% reduction).

Compressing https://querycom.ru/images/logo.png could save 1.6KiB (19% reduction).
Compressing https://querycom.ru/images/statistics.png could save 1.2KiB (12% reduction).

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="/legal-basis">Правовые основ…й деятельности</a> is close to 1 other tap targets.

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 121B (12% reduction).

Minifying https://querycom.ru/application.css could save 121B (12% 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.
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.
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.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does querycom.ru use compression?

querycom.ru use gzip compression.
Original size: 32.38 KB
Compressed size: 6.43 KB
File reduced by: 25.95 KB (80%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify

querycom.ru supports HTTPS
Verifying SSL Support. Please wait...
Common Name: querycom.net
Issuer: Let's Encrypt Authority X3
Valid from: Aug 17 03:57:25 2019 GMT
Valid until: Nov 15 03:57:25 2019 GMT
Authority: Is not a CA
Common Name: Let's Encrypt Authority X3
Organization: Let's Encrypt
Location: US
Issuer: DST Root CA X3
Valid from: Mar 17 16:40:46 2016 GMT
Valid until: Mar 17 16:40:46 2021 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support

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

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx/1.12.0
Date: Wed, 16 Oct 2019 15:33:41 GMT
Content-Type: text/html
Content-Length: 185
Connection: keep-alive
Location: https://querycom.ru/

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Status: 200 OK
Cache-Control: max-age=0, private, must-revalidate
Referrer-Policy: strict-origin-when-cross-origin
X-Permitted-Cross-Domain-Policies: none
X-XSS-Protection: 1; mode=block
X-Request-Id: 919824d8-321c-4d14-aac3-4d69535bf8d9
X-Download-Options: noopen
ETag: W/"8af2c33843d2dee4d021451beedc9f16"
X-Frame-Options: SAMEORIGIN
X-Runtime: 0.008504
X-Content-Type-Options: nosniff
Date: Wed, 16 Oct 2019 15:33:42 GMT
Set-Cookie: _querycom_session=esVmCPOlhRR134p5%2FksfYA8zebKIbH0n5aCQnmtV7i0aeXvM2duxR5oqAAXF8lcPqg3Xgalx0B5cWFSSg%2BYFCo1n7Oun1Qz1rYg%2FA3H4930dySRSObOsx1fd8K0BJmw7CzVeNf0UUHLFM2Z0v1I%3D--0FGvoXF8GCUhvUp6--U4T1DXnemNZb4JLlgkJ7aA%3D%3D; path=/; HttpOnly
X-Powered-By: Phusion Passenger 5.1.5
Server: nginx/1.12.0 + Phusion Passenger 5.1.5
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
NS dns1.yandex.net 900
NS dns2.yandex.net 900

+ Whois Lookup

Domain Created:
Domain Age:
8 years 8 months 15 days  

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

nserver: dns1.yandex.ru.
nserver: dns2.yandex.ru.
person: Private Person
registrar: REGRU-RU
admin-contact: http://www.reg.ru/whois/admin_contact
created: 2011-02-01T19:07:39Z
paid-till: 2020-02-01T19:07:39Z
free-date: 2020-03-03
source: TCI

Last updated on 2019-10-16T15:31:32Z
Last update was 58 days ago
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

6 secs
15 secs
16 secs
59 secs
1 min
1 min
1 min
1 min
1 min
2 mins

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.


Install HypeStat extension in your browser to see statistics and technologies used with one click.
Make custom Widget for your website
Get the code now!
querycom.ru widget