whowhatwhy.org Website Information
Daily Unique Visits: 28,891
Daily Page Views: 173,346
Income Per Day: $347
Estimated Value: $249,840
This website is located in United States and is using following IP address 45.33.20.99. See the complete list of popular websites hosted in United States.
whowhatwhy.org is registered under .ORG top-level domain. Please check other sites in .ORG zone.
Website whowhatwhy.org is using the following name servers:
- ns2.dotster.com
- ns1.dotster.com
and is probably hosted by LINODE-AP Linode, LLC, US. See the full list of other websites hosted by LINODE-AP Linode, LLC, US.
The highest website whowhatwhy.org position in Alexa rank database was 47097 and the lowest rank position was 129283. Current position of whowhatwhy.org in Alexa rank database is 49643.
Desktop speed score of whowhatwhy.org (35/100) is better than the results of 11.34% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of whowhatwhy.org (96/100) is better than the results of 46.59% of other sites and means that the page is mobile-friendly.
Mobile speed score of whowhatwhy.org (47/100) is better than the results of 28.68% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
whowhatwhy.org Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
whowhatwhy.org whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
Registry Domain ID: d68ae9e57c6a40d09a4d3626b25904cd-LROR
Registrar WHOIS Server: http://whois.domain.com
Registrar URL: http://www.domain.com
Updated Date: 2022-06-11T19:16:15Z
Creation Date: 2009-05-12T18:47:24Z
Registry Expiry Date: 2025-05-12T18:47:24Z
Registrar: Domain.com, LLC
Registrar IANA ID: 886
Registrar Abuse Contact Email: compliance@domain-inc.net
Registrar Abuse Contact Phone: +1.6022262389
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Domain Privacy Service FBO Registrant.
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: FL
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns1.dotster.com
Name Server: ns2.dotster.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-09-27T06:55:45Z
whowhatwhy.org server information
Servers Location
whowhatwhy.org desktop page speed rank
Last tested: 2018-02-01
whowhatwhy.org Desktop Speed Test Quick Summary
priority - 194Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1.9MiB (75% reduction).
Compressing https://whowhatwhy.org/wp-content/uploads/2018/02/image3.jpg could save 394.4KiB (72% reduction).
Compressing https://whowhatwhy.org/wp-content/uploads/2018/02/image5.jpg could save 394.3KiB (76% reduction).
Compressing https://whowhatwhy.org/wp-content/uploads/2018/02/image6.jpg could save 352.2KiB (72% reduction).
Compressing https://whowhatwhy.org/wp-content/uploads/2018/02/image2.jpg could save 145KiB (73% reduction).
priority - 8Eliminate 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.
Optimize CSS Delivery of the following:
priority - 1Leverage 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.google-analytics.com/analytics.js (2 hours)
priority - 0Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 333B (32% reduction).
whowhatwhy.org Desktop Resource Breakdown
Total Resources | 48 |
Number of Hosts | 15 |
Static Resources | 34 |
JavaScript Resources | 9 |
CSS Resources | 5 |
whowhatwhy.org mobile page speed rank
Last tested: 2019-06-14
whowhatwhy.org Mobile Speed Test Quick Summary
priority - 64Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://platform-api.sharethis.com/js/sharethis.js
Optimize CSS Delivery of the following:
https://p.typekit.net/p.css?s=1&k=sfc7gma&ht=tk&f=…3467&app=typekit&e=css
https://whowhatwhy.org/wp-content/cache/autoptimiz…444256f00bdf3c3277.css
https://whowhatwhy.org/wp-content/cache/autoptimiz…5c5473d9f5c71230a1.css
https://whowhatwhy.org/wp-includes/css/dashicons.min.css?ver=5.2.1
priority - 56Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 547.3KiB (75% reduction).
Compressing https://whowhatwhy.org/wp-content/uploads/2015/04/…_Beholder_1088x285.jpg could save 179KiB (77% reduction).
Compressing https://whowhatwhy.org/wp-content/uploads/2015/04/Donate_Promo_1088x285.jpg could save 36.2KiB (56% reduction).
priority - 4Leverage 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://buttons-config.sharethis.com/js/5b67a46e78eb8b00113e38db.js (60 seconds)
https://use.typekit.net/sfc7gma.css (10 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-7290738-4 (15 minutes)
https://platform-api.sharethis.com/js/sharethis.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 0Enable 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 335B (50% reduction).
priority - 0Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 317B (34% reduction).
whowhatwhy.org Mobile Resource Breakdown
Total Resources | 66 |
Number of Hosts | 21 |
Static Resources | 48 |
JavaScript Resources | 14 |
CSS Resources | 7 |
whowhatwhy.org mobile page usability
Last tested: 2019-06-14
whowhatwhy.org Mobile Usability Test Quick Summary
priority - 3Size 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.
<a href="https://whowha…g/free-speech/">free speech</a>
and 49 others are close to other tap targets.The tap target
<a href="https://whowha…s/us-politics/">US Politics</a>
and 4 others are close to other tap targets.The tap target
<a href="https://whowha…chael-freeman/">Michael Freeman</a>
and 2 others are close to other tap targets.The tap target
<input type="checkbox" name="_mc4wp_lists[]">
and 1 others are close to other tap targets.whowhatwhy.org HTML validation
Errors
Bad start tag in “iframe” in “head”.
"...<noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-5VFPLS" height="0" width="0" style="display:none;visibility:hidden"></ifra..."
Stray end tag “noscript”.
"...></iframe></noscript> <scri..."
A “link” element must not appear as a descendant of a “body” element unless the “link” element has an “itemprop” attribute or has a “rel” attribute whose value contains “dns-prefetch”, “pingback”, “preconnect”, “prefetch”, “preload”, “prerender”, or “stylesheet”.
"... URLS --> <link rel="alternate" type="application/rss+xml" title="WhoWhatWhy RSS Feed" href="https://whowhatwhy.org/feed/rss/" /> <link..." Line: 62 Column: 1 - 116
".../rss/" /> <link rel="alternate" type="application/rss+xml" title="WhoWhatWhy RSS2 Feed" href="https://whowhatwhy.org/feed/" /> <link..." Line: 63 Column: 1 - 121
"...feed/" /> <link rel="alternate" type="application/rss+xml" title="WhoWhatWhy Atom Feed" href="https://whowhatwhy.org/feed/atom/" /> <lin..." Line: 75 Column: 1 - 55
".../seo/ --> <link rel="canonical" href="https://whowhatwhy.org/" /> <link..." Line: 76 Column: 1 - 57
"....org/" /> <link rel="next" href="https://whowhatwhy.org/page/2/" /> <meta..." Line: 114 Column: 1 - 72
"...</script> <link rel='https://api.w.org/' href='https://whowhatwhy.org/wp-json/' /> <link..." Line: 115 Column: 1 - 106
"...json/' /> <link rel="EditURI" type="application/rsd+xml" title="RSD" href="https://whowhatwhy.org/xmlrpc.php?rsd" /> <link..." Line: 116 Column: 1 - 119
"...p?rsd" /> <link rel="wlwmanifest" type="application/wlwmanifest+xml" href="https://whowhatwhy.org/wp-includes/wlwmanifest.xml" /> <sty..."
Element “style” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)
"...s.com --> <style>@font-..." Line: 117 Column: 1 - 23
"....xml" /> <style type='text/css'>img#wp..." Line: 132 Column: 1 - 7
"...</script> <style>button..."
Attribute “name” not allowed on element “meta” at this point.
"...58652" /> <meta name="twitter:card" content="summary" /> <meta..." Line: 84 Column: 1 - 60
"...mmary" /> <meta name="twitter:title" content="WhoWhatWhy - Welcome" /> <meta..." Line: 85 Column: 1 - 50
"...lcome" /> <meta name="twitter:site" content="@whowhatwhy" /> <scri..." Line: 88 Column: 1 - 74
"...</script> <meta name="p:domain_verify" content="19c7772d461a1d0b3b0d91c946f86bd3" /> <!-- ..."
Element “meta” is missing one or more of the following attributes: “itemprop”, “property”.
"...58652" /> <meta name="twitter:card" content="summary" /> <meta..." Line: 84 Column: 1 - 60
"...mmary" /> <meta name="twitter:title" content="WhoWhatWhy - Welcome" /> <meta..." Line: 85 Column: 1 - 50
"...lcome" /> <meta name="twitter:site" content="@whowhatwhy" /> <scri..." Line: 88 Column: 1 - 74
"...</script> <meta name="p:domain_verify" content="19c7772d461a1d0b3b0d91c946f86bd3" /> <!-- ..."
Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.
"...</script> <link rel='https://api.w.org/' href='https://whowhatwhy.org/wp-json/' /> <link..."
Stray end tag “head”.
"...}}</style></head> <body..."
Start tag “body” seen but an element of the same type was already open.
"...e></head> <body> <div..."
Element “style” not allowed as child of element “noscript” in this context. (Suppressing further errors from this subtree.)
"...<noscript><style type="text/css" scoped>#solil..."
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
"...utin/"> <img src="https://whowhatwhy.org/wp-content/themes/www2015/images/russiagate_latest.jpg" /></a> <..." Line: 389 Column: 102 - 196
"...no-ads"><img src="https://whowhatwhy.org/wp-content/themes/www2015/images/donate_banner_oct2017.png" /></a> </s..."
Stray end tag “div”.
"...> </div> </div> <div ..."
Warnings
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
"...debar"> <section class="russiagate"> <a h..." Line: 388 Column: 1 - 22
"...tion> --> <section class="give"> <a h..." Line: 528 Column: 2 - 10
"...oter-2"> <section><div c..."
The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.
"...one;"> <img src="//pixel.quantserve.com/pixel/p-Fvx18-z8PqSqY.gif" border="0" height="1" width="1" alt="Quantcast"/> </d..."
This document appears to be written in English. Consider adding “lang="en"” (or variant) to the “html” start tag.
"...TYPE html> <html> <head..."
whowhatwhy.org similar domains
www.whowhatwhy.net
www.whowhatwhy.org
www.whowhatwhy.info
www.whowhatwhy.biz
www.whowhatwhy.us
www.whowhatwhy.mobi
www.howhatwhy.org
www.whowhatwhy.org
www.qhowhatwhy.org
www.wqhowhatwhy.org
www.qwhowhatwhy.org
www.ahowhatwhy.org
www.wahowhatwhy.org
www.awhowhatwhy.org
www.showhatwhy.org
www.wshowhatwhy.org
www.swhowhatwhy.org
www.ehowhatwhy.org
www.wehowhatwhy.org
www.ewhowhatwhy.org
www.wowhatwhy.org
www.wbowhatwhy.org
www.whbowhatwhy.org
www.wbhowhatwhy.org
www.wgowhatwhy.org
www.whgowhatwhy.org
www.wghowhatwhy.org
www.wyowhatwhy.org
www.whyowhatwhy.org
www.wyhowhatwhy.org
www.wuowhatwhy.org
www.whuowhatwhy.org
www.wuhowhatwhy.org
www.wjowhatwhy.org
www.whjowhatwhy.org
www.wjhowhatwhy.org
www.wnowhatwhy.org
www.whnowhatwhy.org
www.wnhowhatwhy.org
www.whwhatwhy.org
www.whiwhatwhy.org
www.whoiwhatwhy.org
www.whiowhatwhy.org
www.whkwhatwhy.org
www.whokwhatwhy.org
www.whkowhatwhy.org
www.whlwhatwhy.org
www.wholwhatwhy.org
www.whlowhatwhy.org
www.whpwhatwhy.org
www.whopwhatwhy.org
www.whpowhatwhy.org
www.whohatwhy.org
www.whoqhatwhy.org
www.whowqhatwhy.org
www.whoqwhatwhy.org
www.whoahatwhy.org
www.whowahatwhy.org
www.whoawhatwhy.org
www.whoshatwhy.org
www.whowshatwhy.org
www.whoswhatwhy.org
www.whoehatwhy.org
www.whowehatwhy.org
www.whoewhatwhy.org
www.whowatwhy.org
www.whowbatwhy.org
www.whowhbatwhy.org
www.whowbhatwhy.org
www.whowgatwhy.org
www.whowhgatwhy.org
www.whowghatwhy.org
www.whowyatwhy.org
www.whowhyatwhy.org
www.whowyhatwhy.org
www.whowuatwhy.org
www.whowhuatwhy.org
www.whowuhatwhy.org
www.whowjatwhy.org
www.whowhjatwhy.org
www.whowjhatwhy.org
www.whownatwhy.org
www.whowhnatwhy.org
www.whownhatwhy.org
www.whowhtwhy.org
www.whowhqtwhy.org
www.whowhaqtwhy.org
www.whowhqatwhy.org
www.whowhwtwhy.org
www.whowhawtwhy.org
www.whowhwatwhy.org
www.whowhstwhy.org
www.whowhastwhy.org
www.whowhsatwhy.org
www.whowhztwhy.org
www.whowhaztwhy.org
www.whowhzatwhy.org
www.whowhawhy.org
www.whowharwhy.org
www.whowhatrwhy.org
www.whowhartwhy.org
www.whowhafwhy.org
www.whowhatfwhy.org
www.whowhaftwhy.org
www.whowhagwhy.org
www.whowhatgwhy.org
www.whowhagtwhy.org
www.whowhaywhy.org
www.whowhatywhy.org
www.whowhaytwhy.org
www.whowhathy.org
www.whowhatqhy.org
www.whowhatwqhy.org
www.whowhatqwhy.org
www.whowhatahy.org
www.whowhatwahy.org
www.whowhatawhy.org
www.whowhatshy.org
www.whowhatwshy.org
www.whowhatswhy.org
www.whowhatehy.org
www.whowhatwehy.org
www.whowhatewhy.org
www.whowhatwy.org
www.whowhatwby.org
www.whowhatwhby.org
www.whowhatwbhy.org
www.whowhatwgy.org
www.whowhatwhgy.org
www.whowhatwghy.org
www.whowhatwyy.org
www.whowhatwhyy.org
www.whowhatwyhy.org
www.whowhatwuy.org
www.whowhatwhuy.org
www.whowhatwuhy.org
www.whowhatwjy.org
www.whowhatwhjy.org
www.whowhatwjhy.org
www.whowhatwny.org
www.whowhatwhny.org
www.whowhatwnhy.org
www.whowhatwh.org
www.whowhatwht.org
www.whowhatwhyt.org
www.whowhatwhty.org
www.whowhatwhg.org
www.whowhatwhyg.org
www.whowhatwhh.org
www.whowhatwhyh.org
www.whowhatwhhy.org
www.whowhatwhu.org
www.whowhatwhyu.org
whowhatwhy.org Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
whowhatwhy.org TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.