Polypay.Org - Info polypay.org

polypay.org 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 polypay.org is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in United States and links to network IP address This server supports HTTPS and HTTP/2.

About - polypay.org

Technologies used on Website

Currently Not Available

polypay.org Profile

Title: American Polypay Sheep Association
Description: Website for the American Polypay Sheep Association
Last update was 753 days ago
This can take up to 60 seconds. Please wait...

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

How popular is polypay.org?

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
Bounce rate:
*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

(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 polypay.org?

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

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

Daily earning by country

Currently Not Available

How much money do polypay.org 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

Currently Not Available

How much is polypay.org worth?

Website Value:

+ Where is polypay.org hosted?

Server IP:
Cloudflare Inc 
Server Location:

United States, US

Other sites hosted on

+ How fast does polypay.org load?

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

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

Currently Not Available

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Optimize images

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

Optimize the following images to reduce their size by 2.5MiB (58% reduction).

Compressing https://www.polypay.org/assets/images/2018_large_square.jpg could save 1.3MiB (51% reduction).
Compressing https://www.polypay.org/assets/images/2015_quads.jpg could save 205.6KiB (79% reduction).
Compressing https://www.polypay.org/assets/images/2015_topewe.jpg could save 176.2KiB (73% reduction).
Compressing https://www.polypay.org/assets/images/2010_park_ewes_1.jpg could save 122.9KiB (72% reduction).
Compressing https://www.polypay.org/assets/images/2010_bh_3.jpg could save 117.6KiB (71% reduction).
Compressing https://www.polypay.org/assets/images/2010_jay.jpg could save 108.3KiB (68% reduction).
Compressing https://www.polypay.org/assets/images/2010_park_lambs_1.jpg could save 87.4KiB (70% reduction).
Compressing https://www.polypay.org/assets/images/2010_park_ewes_2.jpg could save 71.2KiB (71% reduction).
Compressing https://www.polypay.org/assets/images/2010_fh2.jpg could save 63.8KiB (73% reduction).
Compressing https://www.polypay.org/assets/images/2010_panarama2003.jpg could save 61.6KiB (72% reduction).
Compressing https://www.polypay.org/assets/images/2010_df_6.jpg could save 57.9KiB (70% reduction).
Compressing https://www.polypay.org/assets/images/2010_baby.jpg could save 56.7KiB (78% reduction).
Compressing https://www.polypay.org/assets/images/2010_park_lambs_2.jpg could save 39.5KiB (71% reduction).
Compressing https://www.polypay.org/assets/images/2010_working_lambs.jpg could save 30.6KiB (33% reduction).
Compressing https://www.polypay.org/assets/images/2010_pasture.jpg could save 15.9KiB (50% reduction).
Compressing https://www.polypay.org/assets/images/2010_df_breeding.jpg could save 15.7KiB (75% reduction).
Compressing https://www.polypay.org/assets/images/2010_WC129.jpg could save 7.6KiB (30% reduction).
Compressing https://www.polypay.org/assets/images/2010_bh_1.jpg could save 3.4KiB (17% reduction).
Compressing https://www.polypay.org/assets/images/2010_ram.jpg could save 1.3KiB (20% reduction).
Compressing https://www.polypay.org/assets/images/2010_group.jpg could save 1.2KiB (14% reduction).
Compressing https://scontent-atl3-1.***.fbcdn.net/v/t1.0-1/p50x50/25498156_1638836176208784_4826222338050288673_n.jpg?oh=d49653f052b68bd9402036682b2019e1&oe=5B34D635 could save 437B (28% reduction).
Compressing https://scontent-atl3-1.***.fbcdn.net/v/t1.0-1/p50x50/28951876_1189886451114567_8307668220021868962_n.jpg?oh=4ea3d7401b9d714aa895175d94a4e7a6&oe=5B3F2789 could save 428B (24% reduction).
Compressing https://scontent-atl3-1.***.fbcdn.net/v/t1.0-1/c90.210.540.540/s50x50/23131881_16638365636***172_2910325968964058545_n.jpg?oh=da98a4925eef97a377e4f072edacb75c&oe=5B3E2A5B could save 420B (26% reduction).
Compressing https://scontent-atl3-1.***.fbcdn.net/v/t1.0-1/p50x50/29136096_179610816154307_***98367796323087565_n.jpg?oh=87eff0bc73c28da16271410c40c48d28&oe=5B47B648 could save 420B (19% reduction).
Compressing https://scontent-atl3-1.***.fbcdn.net/v/t1.0-1/p50x50/28279600_10155776758954818_32774792957***653309_n.jpg?oh=2288cd6608c2841892e8138e7808ba8c&oe=5B3362D5 could save 410B (25% reduction).
Compressing https://scontent-atl3-1.***.fbcdn.net/v/t1.0-1/p50x50/13265952_10153835799063922_5405929107177733789_n.jpg?oh=f9bee66a2efbbffce7f5316cbd91f3fd&oe=5B44C07F could save 397B (20% reduction).
Compressing https://scontent-atl3-1.***.fbcdn.net/v/t1.0-1/p50x50/28959097_740516826141279_992681712736548940_n.jpg?oh=02dfa528e9748338e02530b36ba6e97a&oe=5B3DD7BB could save 394B (20% reduction).
Compressing https://scontent-atl3-1.***.fbcdn.net/v/t1.0-1/c46.46.574.574/s50x50/1000054_567***8603280279_1325478360_n.jpg?oh=f5a52457cab6c5a538f9340eb5802b50&oe=5B443AE0 could save 390B (20% reduction).
Compressing https://scontent-atl3-1.***.fbcdn.net/v/t1.0-1/p50x50/29026376_1783295148424216_852914907950088192_n.jpg?oh=7a0ad6142a40e5ddef1e850b77d2531b&oe=5B347D0C could save 377B (18% reduction).
Compressing https://scontent-atl3-1.***.fbcdn.net/v/t1.0-1/c59.13.158.158/s50x50/972135_104783176395126_1967376285_n.jpg?oh=3068f50132672893a4d2b93292def7f0&oe=5B015744 could save 354B (21% reduction).
Compressing https://static.***.fbcdn.net/rsrc.php/v3/yN/r/WgFKRx0VFOG.png could save 279B (22% reduction).
Compressing https://static.***.fbcdn.net/rsrc.php/v3/yH/r/yNvz5xtKREW.png could save 109B (20% reduction).

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

Your page has 3 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:


Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.


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.googletagmanager.com/gtag/js?id=UA-15493817-2 (15 minutes)
https://www.google-***ytics.com/***ytics.js (2 hours)
https://www.polypay.org/assets/css/main.css (4 hours)
https://www.polypay.org/assets/images/2010_WC129.jpg (4 hours)
https://www.polypay.org/assets/images/2010_babies.jpg (4 hours)
https://www.polypay.org/assets/images/2010_baby.jpg (4 hours)
https://www.polypay.org/assets/images/2010_bh_1.jpg (4 hours)
https://www.polypay.org/assets/images/2010_bh_3.jpg (4 hours)
https://www.polypay.org/assets/images/2010_df_6.jpg (4 hours)
https://www.polypay.org/assets/images/2010_df_breeding.jpg (4 hours)
https://www.polypay.org/assets/images/2010_fh2.jpg (4 hours)
https://www.polypay.org/assets/images/2010_group.jpg (4 hours)
https://www.polypay.org/assets/images/2010_group_sheep.jpg (4 hours)
https://www.polypay.org/assets/images/2010_jay.jpg (4 hours)
https://www.polypay.org/assets/images/2010_lambs2.jpg (4 hours)
https://www.polypay.org/assets/images/2010_panarama2003.jpg (4 hours)
https://www.polypay.org/assets/images/2010_park_ewes_1.jpg (4 hours)
https://www.polypay.org/assets/images/2010_park_ewes_2.jpg (4 hours)
https://www.polypay.org/assets/images/2010_park_lambs_1.jpg (4 hours)
https://www.polypay.org/assets/images/2010_park_lambs_2.jpg (4 hours)
https://www.polypay.org/assets/images/2010_pasture.jpg (4 hours)
https://www.polypay.org/assets/images/2010_pretty_baby.jpg (4 hours)
https://www.polypay.org/assets/images/2010_ram.jpg (4 hours)
https://www.polypay.org/assets/images/2010_sheep.jpg (4 hours)
https://www.polypay.org/assets/images/2010_sheepandlambs.jpg (4 hours)
https://www.polypay.org/assets/images/2010_working_lambs.jpg (4 hours)
https://www.polypay.org/assets/images/2015_10190.jpg (4 hours)
https://www.polypay.org/assets/images/2015_quads.jpg (4 hours)
https://www.polypay.org/assets/images/2015_topewe.jpg (4 hours)
https://www.polypay.org/assets/images/2018_large_square.jpg (4 hours)
https://www.polypay.org/assets/images/banner.png (4 hours)
https://www.polypay.org/cdn-cgi/scripts/d07b1474/cloudflare-static/email-decode.min.js (2 days)

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/" class="nav-link align-middle">Home</a> and 6 others are close to other tap targets .
The tap target <a href="/polypays/" class="nav-link">Polypays</a> and 6 others are close to other tap targets .
The tap target <a href="/polypays/" class="nav-link">Polypays</a> and 7 others are close to other tap targets.
The tap target <a href="mailto:pdschloss@gmail.com"></a> and 1 others are close to other tap targets.
The tap target <a href="mailto:pdschloss@gmail.com"></a> is close to 2 other tap targets.

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 422 CSS pixels wide, but the viewport is only 412 CSS pixels wide.

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 2KiB (76% reduction).

Minifying https://cdnjs.cloudflare.com/ajax/libs/ekko-lightbox/5.3.0/ekko-lightbox.css could save 2KiB (76% reduction) after compression.

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 342B (11% reduction).

Minifying https://www.polypay.org/ could save 342B (11% 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.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Enable compression
You have compression enabled. Learn more about enabling compression.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does polypay.org use compression?

polypay.org does not use compression.
Original size: n/a
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify

polypay.org supports HTTPS
Verifying SSL Support. Please wait...
Common Name: sni854403.cloudflaressl.com
Issuer: GlobalSign CloudSSL CA - SHA256 - G3
Valid from: Jan 25 12:51:27 2018 GMT
Valid until: Jun 23 17:04:06 2018 GMT

+ Verify HTTP/2 Support

polypay.org supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

HTTP/1.1 301 Moved Permanently
Date: Tue, 13 Mar 2018 23:58:34 GMT
Connection: close
Cache-Control: max-age=3600
Expires: Wed, 14 Mar 2018 00:58:34 GMT
Location: https://www.polypay.org/
Server: cloudflare
CF-RAY: 3fb2730c8762551c-ORD
HTTP/1.1 200 OK
Date: Tue, 13 Mar 2018 23:58:35 GMT
Content-Type: text/html; charset=utf-8
Connection: close
Set-Cookie: __cfduid=d8c5aa2c5802cc3b0787b1ee8176b85f41520985515; expires=Wed, 13-Mar-19 23:58:35 GMT; path=/; domain=.polypay.org; HttpOnly
Last-Modified: Sun, 11 Mar 2018 00:51:59 GMT
Access-Control-Allow-Origin: *
Expires: Tue, 13 Mar 2018 23:37:21 GMT
Cache-Control: max-age=600
X-GitHub-Request-Id: DA6E:11CF3:87AF9B4:BA852C7:5AA85E59
Via: 1.1 varnish
Age: 3
X-Served-By: cache-mdw17320-MDW
X-Cache: HIT
X-Cache-Hits: 2
X-Timer: S1520985515.040817,VS0,VE0
Vary: Accept-Encoding
X-Fastly-Request-ID: 60bc953d5e2055889fbb59708831a968e42ae5d7
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 3fb2730cbd4c712b-ORD

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
A 290
A 290
NS linda.ns.cloudflare.com 3590
NS max.ns.cloudflare.com 3590

+ Whois Lookup

Domain Created:
Domain Age:
15 years 6 months 1 days  

whois lookup at whois.pir.org...
Domain Name: POLYPAY.ORG
Registry Domain ID: D90212047-LROR
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2018-01-12T13:23:01Z
Creation Date: 2002-09-12T16:53:55Z
Registry Expiry Date: 2018-09-12T16:54:53Z
Registrar Registration Expiration Date:
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: C201149431-LROR
Registrant Name: Pat Schloss
Registrant Organization: American Polypay Sheep Association
Registrant Street: 5420 Farrell Rd
Registrant City: Dexter
Registrant State/Province: Michigan
Registrant Postal Code: 48130
Registrant Country: US
Registrant Phone: +1.4135484445
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: email
Registry Admin ID: C201149428-LROR
Admin Name: Pat Schloss
Admin Organization: American Polypay Sheep Association
Admin Street: 5420 Farrell Rd
Admin City: Dexter
Admin State/Province: Michigan
Admin Postal Code: 48130
Admin Country: US
Admin Phone: +1.4135484445
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: email
Registry Tech ID: C201149427-LROR
Tech Name: Pat Schloss
Tech Organization: American Polypay Sheep Association
Tech Street: 5420 Farrell Rd
Tech City: Dexter
Tech State/Province: Michigan
Tech Postal Code: 48130
Tech Country: US
Tech Phone: +1.4135484445
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: email
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2018-03-13T23:57:43Z <<<

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.
Last update was 753 days ago
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

36 secs
1 min
1 min
1 min
2 mins
2 mins
3 mins
3 mins
3 mins
4 mins
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


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!
polypay.org widget