Zmzm.Org - Info zmzm.org

zmzm.org receives about 458 unique visitors and 458 (1.00 per visitor) page views per day which should earn about $1.87/day from advertising revenue. Estimated site value is $1,364.45. According to Alexa Traffic Rank zmzm.org is ranked number 1,712,659 in the world and 2.7E-5% of global Internet users visit it. Site is hosted in Lansing, Michigan, 48917, United States and links to network IP address 67.225.188.143. This server supports HTTPS and HTTP/2.

About - zmzm.org


Technologies used on Website

Currently Not Available

zmzm.org Profile

Title: جمعية زمزم للخدمات الصحية التطوعية
Last update was 30 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is zmzm.org?

458 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
458
Monthly Unique Visitors:
10,992
Pages per Visit:
1.00
Daily Pageviews:
458
Alexa Rank:
1,712,659 visit alexa
Alexa Reach:
2.7E-5%   (of global internet users)
Avg. visit duration:
00:00
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:
  zmzm.org
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 zmzm.org?

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:
zmzm.org
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:
zmzm.org
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 zmzm.org can earn?

Daily Revenue:
$1.87
Monthly Revenue:
$56.10
Yearly Revenue:
$682.55
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do zmzm.org 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 zmzm.org worth?

Website Value:
$1,364.45

+ Where is zmzm.org hosted?

Server IP:
67.225.188.143
ASN:
AS32244 
ISP:
Liquid Web, L.L.C 
Server Location:
Lansing
Michigan, MI
48917
United States, US
 

Other sites hosted on 67.225.188.143

+ How fast does zmzm.org load?

Average Load Time:
(3033 ms) 22 % 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 SLOW 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)10.6s 4% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 4% 18% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 18% 76% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 76%
First Input Delay (FID)602ms 88% of loads for this page have a fast (<50ms) First Input Delay (FID) 88% 4% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 4% 6% of loads for this page have a slow (>250ms) First Input Delay (FID) 6%

Origin Data

All pages served from this origin have an SLOW 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)10.6s 4% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 4% 18% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 18% 76% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 76%
First Input Delay (FID)602ms 88% of loads for this page have a fast (<50ms) First Input Delay (FID) 88% 4% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 4% 6% of loads for this page have a slow (>250ms) First Input Delay (FID) 6%

Lab Data

First Meaningful Paint 0.5 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.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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 0.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.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 0.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.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 7 requests • 99 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
799 KB
Image
478 KB
Stylesheet
120 KB
Document
11 KB
Other
10 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 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.

URL
SizePotential Savings
https://www.zmzm.org/html_files/bootstrap.css
20 KB110
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://zmzm.org/
0 ms78 ms0 KB0 KB302text/html
https://www.zmzm.org/
79 ms221 ms1 KB1 KB200text/htmlDocument
https://www.zmzm.org/html_files/bootstrap.css
238 ms431 ms20 KB118 KB200text/cssStylesheet
https://www.zmzm.org/html_files/1.png
238 ms424 ms20 KB20 KB200image/pngImage
https://www.zmzm.org/html_files/2.png
239 ms312 ms26 KB26 KB200image/pngImage
https://www.zmzm.org/html_files/3.png
241 ms387 ms11 KB11 KB200image/pngImage
https://www.zmzm.org/html_files/4.png
241 ms435 ms21 KB20 KB200image/pngImage
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
259 ms
10 ms
467 ms
8 ms
476 ms
6 ms
482 ms
11 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
52 ms3 ms1 ms
Remove unused CSS - Potential savings of 19 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.

URL
SizePotential Savings
https://www.zmzm.org/html_files/bootstrap.css
20 KB19 KB
Avoids enormous network payloads - Total size was 99 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.zmzm.org/html_files/2.png
26 KB
https://www.zmzm.org/html_files/4.png
21 KB
https://www.zmzm.org/html_files/1.png
20 KB
https://www.zmzm.org/html_files/bootstrap.css
20 KB
https://www.zmzm.org/html_files/3.png
11 KB
https://www.zmzm.org/
1 KB
http://zmzm.org/
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.

Category
Time Spent
Other
21 ms
Style & Layout
13 ms
Parse HTML & CSS
12 ms
Script Evaluation
3 ms
Script Parsing & Compilation
2 ms
Rendering
1 ms
Serve images in next-gen formats - Potential savings of 34 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.zmzm.org/html_files/2.png
26 KB15 KB
https://www.zmzm.org/html_files/1.png
20 KB10 KB
https://www.zmzm.org/html_files/4.png
20 KB9 KB
Avoids an excessive DOM size - 26 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.

Statistic
ElementValue
Total DOM Elements
26
Maximum DOM Depth
7
Maximum Child Elements
12
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://zmzm.org/)
0
https://www.zmzm.org/
190
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 140 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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

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

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. 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.

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


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 SLOW 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)9.1s 4% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 7% 13% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 13% 79% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 79%
First Input Delay (FID)2.9s 75% of loads for this page have a fast (<50ms) First Input Delay (FID) 75% 7% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 7% 17% of loads for this page have a slow (>250ms) First Input Delay (FID) 17%

Origin Data

All pages served from this origin have an SLOW 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)9.1s 7% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 7% 13% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 13% 79% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 79%
First Input Delay (FID)2.9s 88% of loads for this page have a fast (<50ms) First Input Delay (FID) 75% 7% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 7% 17% of loads for this page have a slow (>250ms) First Input Delay (FID) 17%

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.7 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.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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.
First Contentful Paint (3G) 3390 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.7 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.7 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 - 26 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.

Statistic
ElementValue
Total DOM Elements
26
Maximum DOM Depth
7
Maximum Child Elements
12
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://zmzm.org/)
0
https://www.zmzm.org/
630
Keep request counts low and transfer sizes small - 7 requests • 58 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
758 KB
Image
437 KB
Stylesheet
120 KB
Document
11 KB
Other
10 KB
Media
00 KB
Font
00 KB
Script
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 330 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
https://www.zmzm.org/html_files/bootstrap.css
20 KB330
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://zmzm.org/
0 ms106 ms0 KB0 KB302text/html
https://www.zmzm.org/
106 ms281 ms1 KB1 KB200text/htmlDocument
https://www.zmzm.org/html_files/bootstrap.css
294 ms508 ms20 KB118 KB200text/cssStylesheet
https://www.zmzm.org/html_files/1.png
294 ms297 ms0 KB0 KB-1Image
https://www.zmzm.org/html_files/2.png
295 ms503 ms26 KB26 KB200image/pngImage
https://www.zmzm.org/html_files/3.png
296 ms336 ms11 KB11 KB200image/pngImage
https://www.zmzm.org/html_files/4.png
295 ms298 ms0 KB0 KB-1Image
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
314 ms
9 ms
539 ms
7 ms
547 ms
5 ms
552 ms
6 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
158 ms10 ms3 ms
Remove unused CSS - Potential savings of 19 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.

URL
SizePotential Savings
https://www.zmzm.org/html_files/bootstrap.css
20 KB19 KB
Avoids enormous network payloads - Total size was 58 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.zmzm.org/html_files/2.png
26 KB
https://www.zmzm.org/html_files/bootstrap.css
20 KB
https://www.zmzm.org/html_files/3.png
11 KB
https://www.zmzm.org/
1 KB
http://zmzm.org/
0 KB
https://www.zmzm.org/html_files/1.png
0 KB
https://www.zmzm.org/html_files/4.png
0 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.

Category
Time Spent
Other
67 ms
Parse HTML & CSS
39 ms
Style & Layout
35 ms
Script Evaluation
10 ms
Rendering
4 ms
Script Parsing & Compilation
4 ms
Serve images in next-gen formats - Potential savings of 15 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.zmzm.org/html_files/2.png
26 KB15 KB
Minimize Critical Requests Depth - 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 180 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.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. 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) - v2

Suggestions Summary

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

Your page has 1 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:

https://www.zmzm.org/html_files/bootstrap.css

Optimize images

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

Optimize the following images to reduce their size by 17.7KiB (27% reduction).

Compressing https://www.zmzm.org/html_files/2.png could save 8.5KiB (34% reduction).
Compressing https://www.zmzm.org/html_files/4.png could save 4.6KiB (23% reduction).
Compressing https://www.zmzm.org/html_files/1.png could save 4.6KiB (24% 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.
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.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
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.
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.
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 zmzm.org use compression?

zmzm.org use gzip compression.
Original size: 1.44 KB
Compressed size: 531 B
File reduced by: 947 B (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

zmzm.org supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: zmzm.org
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Oct 12 15:44:05 2019 GMT
Valid until: Jan 10 15:44:05 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

zmzm.org supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sun, 20 Oct 2019 11:22:04 GMT
Server: Apache
Location: https://www.zmzm.org/
Cache-Control: max-age=3600
Expires: Sun, 20 Oct 2019 12:22:04 GMT
Content-Length: 205
Content-Type: text/html; charset=iso-8859-1

HTTP/2 200 
date: Sun, 20 Oct 2019 11:22:04 GMT
server: Apache
last-modified: Mon, 08 Oct 2018 12:20:54 GMT
accept-ranges: bytes
cache-control: public, must-revalidate, proxy-revalidate
expires: Sun, 20 Oct 2019 12:22:04 GMT
vary: Accept-Encoding,User-Agent
content-encoding: gzip
content-length: 531
content-type: text/html

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
NS ray.ns.cloudflare.com 3574
NS jocelyn.ns.cloudflare.com 3574

+ Whois Lookup

Domain Created:
2005-05-09
Domain Age:
14 years 5 months 11 days  
WhoIs:
 

whois lookup at whois.pir.org...
Domain Name: ZMZM.ORG
Registry Domain ID: D106278315-LROR
Registrar WHOIS Server: whois.name.com
Registrar URL: http://www.name.com
Updated Date: 2019-10-07T16:50:50Z
Creation Date: 2005-05-09T18:56:59Z
Registry Expiry Date: 2020-05-09T18:56:59Z
Registrar Registration Expiration Date:
Registrar: Name.com, Inc.
Registrar IANA ID: 625
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.7203101849
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Organization: Hani Felemban
Registrant State/Province: -
Registrant Country: SA
Name Server: RAY.NS.CLOUDFLARE.COM
Name Server: JOCELYN.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2019-10-20T11:21:28Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no cir***stances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Last update was 30 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

yoursuperconverter.com
12 secs
turystyka.gazeta.pl
35 secs
flypgs.com
41 secs
gagasanriau.com
55 secs
jobwebtanzania.com
1 min
terranovacoin.wixsite.com
1 min
flvto.com
1 min
finablr.com
2 mins
gravuregirlz.com
2 mins
cox.taleo.net
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.
Make custom Widget for your website
Get the code now!
zmzm.org widget