Zemis.Hr - Info zemis.hr

zemis.hr receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank zemis.hr is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in Zagreb, City of Zagreb, 10110, Croatia and links to network IP address 185.62.75.165. This server supports HTTPS and doesn't support HTTP/2.

About - zemis.hr


Technologies used on Website

Web Servers
Apache

zemis.hr Profile

Title: ZEMIS d.o.o. Grada Gualdo Tadino, 20 | 10000 Zagreb | HRC
Last update was 4 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is zemis.hr?

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Unique Visitors:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (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

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  zemis.hr
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 zemis.hr?

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:
zemis.hr
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:
zemis.hr
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 zemis.hr can earn?

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

Daily earning by country

Currently Not Available

How much money do zemis.hr lose due to Adblock?

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

Daily revenue loss by country

Currently Not Available

How much is zemis.hr worth?

Website Value:
n/a

+ Where is zemis.hr hosted?

Server IP:
185.62.75.165
ASN:
AS61211 
ISP:
IT SOFT d.o.o. 
Server Location:
Zagreb
City of Zagreb, 21
10110
Croatia, HR
 

Other sites hosted on 185.62.75.165

+ How fast does zemis.hr load?

Average Load Time:
n/a ms n/a % 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

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

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 45 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
45
Maximum DOM Depth
7
Maximum Child Elements
11
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://zemis.hr/)
0
https://www.zemis.hr/
190
Keep request counts low and transfer sizes small - 3 requests • 19 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
319 KB
Image
116 KB
Document
13 KB
Other
10 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Efficiently encode images - Potential savings of 7 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
https://www.zemis.hr/logo_small.jpg
15 KB7 KB
Enable text compression - Potential savings of 2 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://www.zemis.hr/
3 KB2 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://zemis.hr/
0 ms295 ms0 KB0 KB302text/html
https://www.zemis.hr/
295 ms805 ms3 KB3 KB200text/htmlDocument
https://www.zemis.hr/logo_small.jpg
817 ms1077 ms16 KB15 KB200image/jpegImage
Uses efficient cache policy on static assets - 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://www.zemis.hr/logo_small.jpg
0 ms16 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
832 ms
8 ms
843 ms
15 ms
Avoids enormous network payloads - Total size was 19 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.zemis.hr/logo_small.jpg
16 KB
https://www.zemis.hr/
3 KB
http://zemis.hr/
0 KB
Minimizes main-thread work - 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.

Category
Time Spent
Other
13 ms
Style & Layout
13 ms
Script Evaluation
2 ms
Rendering
2 ms
Parse HTML & CSS
2 ms
Script Parsing & Compilation
1 ms
Serve images in next-gen formats - Potential savings of 11 KB
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.

URL
SizePotential Savings
https://www.zemis.hr/logo_small.jpg
15 KB11 KB
Avoid chaining critical requests - 1 chain 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 510 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. 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.

JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. 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.


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

First Contentful Paint (3G) 2760 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.
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 2.7 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.
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 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 1.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.

Screenshot Thumbnails

This is what the load of your site looked like.

Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1060 ms
8 ms
1071 ms
15 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
127 ms8 ms4 ms
Avoids enormous network payloads - Total size was 19 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.zemis.hr/logo_small.jpg
16 KB
https://www.zemis.hr/
3 KB
http://zemis.hr/
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. Learn more.

Category
Time Spent
Other
51 ms
Style & Layout
50 ms
Rendering
9 ms
Script Evaluation
8 ms
Parse HTML & CSS
6 ms
Script Parsing & Compilation
4 ms
Serve images in next-gen formats - Potential savings of 11 KB
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.

URL
SizePotential Savings
https://www.zemis.hr/logo_small.jpg
15 KB11 KB
Avoids an excessive DOM size - 45 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
45
Maximum DOM Depth
7
Maximum Child Elements
11
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://zemis.hr/)
0
https://www.zemis.hr/
630
Keep request counts low and transfer sizes small - 3 requests • 19 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
319 KB
Image
116 KB
Document
13 KB
Other
10 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Efficiently encode images - Potential savings of 7 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
https://www.zemis.hr/logo_small.jpg
15 KB7 KB
Enable text compression - Potential savings of 2 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://www.zemis.hr/
3 KB2 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://zemis.hr/
0 ms391 ms0 KB0 KB302text/html
https://www.zemis.hr/
391 ms1039 ms3 KB3 KB200text/htmlDocument
https://www.zemis.hr/logo_small.jpg
1052 ms1835 ms16 KB15 KB200image/jpegImage
Uses efficient cache policy on static assets - 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://www.zemis.hr/logo_small.jpg
0 ms16 KB
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.

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

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

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. 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.

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.

under construction and 1 others render only 6 pixels tall (15 CSS pixels) .
Samoborska 15…00 Zagreb | HR and 4 others render only 6 pixels tall (15 CSS pixels) .
www.sailadria.com renders only 6 pixels tall (15 CSS pixels) .
info[at]zemis[dot]hr renders only 6 pixels tall (16 CSS pixels) .
http://www.zemis.hr/ renders only 6 pixels tall (16 CSS pixels) .

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.

Optimize images

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

Optimize the following images to reduce their size by 8KiB (51% reduction).

Compressing https://www.zemis.hr/logo_small.jpg could save 8KiB (51% reduction).

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.zemis.hr/logo_small.jpg (expiration not specified)

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 2.2KiB (***% reduction).

Compressing https://www.zemis.hr/ could save 2.2KiB (***% reduction).
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.
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.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
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.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does zemis.hr use compression?

zemis.hr does not use compression.
Original size: 3.11 KB
Compressed size: n/a
File reduced by: n/a

+ 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

zemis.hr supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: zemis.hr
Organization:
Location:
Issuer: cPanel, Inc. Certification Authority
Valid from: Dec 17 00:00:00 2019 GMT
Valid until: Mar 16 23:59:59 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

zemis.hr does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Tue, 14 Jan 2020 13:52:23 GMT
Server: Apache
Location: https://www.zemis.hr/
Content-Length: 205
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 200 OK
Date: Tue, 14 Jan 2020 13:52:24 GMT
Server: Apache
Last-Modified: Mon, 02 Jul 2018 09:06:40 GMT
Accept-Ranges: bytes
Content-Length: 3188
Content-Type: text/html

+ DNS Lookup

Type Ip Target TTL
MX zemis.hr 3600
SOA 3600
Mname ns1.pfc.hr
Rname silvio.martinec.gmail.com
Serial Number 2019060406
Refresh 3600
Retry 7200
Expire 1209600
Minimum TTL 0
TXT 3600
A 185.62.75.165 3573
NS ns1.pfc.hr 3573
NS ns2.pfc.hr 3573

+ Whois Lookup

Domain Created:
2017-11-15
Domain Age:
2 years 1 months 29 days  
WhoIs:
 

whois lookup at whois.dns.hr...
%
% From May 25, 2018, it is mandatory to apply the provisions of the
% General Data Protection Regulation (EU) 2016/679. The basic purpose of
% the regulation is greater control for individuals over their personal
% information.
%
% In accordance with the provisions of the General Data Protection
% Regulation (EU) 2016/679, we inform you that the personal data of the
% domain holder and the contact persons under the domain holder are no
% longer publicly available through the domain search engine.
%
% If you believe that there is a legitimate reason for which you need to
% be provided with the data about the domain holder please fill in the
% Request form for personal data disclosure :
% https://domene.hr/portal/files/Request_personal_data_disclosure.pdf
%

Domain Name: zemis.hr
Registrar WHOIS Server: whois.dns.hr
Registrar URL: http://whois.dns.hr
Updated Date: 2019-10-22T22:00:00Z
Creation Date: 2017-11-15T23:00:00Z
Registrar Registration Expiration Date: 2020-10-22T22:00:00Z
Registrant Name: ZEMIS d.o.o.
Registrant Street: Gualdo Tadino 20
Registrant City: Zagreb
Registrant State/Province: HR
Registrant Postal Code: 10000
Name Server: ns1.pfc.hr
Name Server: ns2.pfc.hr
Last update was 4 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

dvdvilla.com
5 secs
zemun.rs
14 secs
rosemounthockey.org
27 secs
techvint.tk
48 secs
youtubemp3.biz
59 secs
roseladamadragon.blogspot.com
1 min
rosegarden***party.com
2 mins
roseforever.com
3 mins
beograd.rs
4 mins
rosebud.ai
4 mins
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!
zemis.hr widget