WAITBUTWHY.COM Wait But Why


waitbutwhy.com website information.

waitbutwhy.com website servers are located in United States and are responding from following IP address 104.196.198.88. Check the full list of most visited websites located in United States.

waitbutwhy.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

Following name servers are specified for waitbutwhy.com domain:

  • eric.ns.cloudflare.com
  • gene.ns.cloudflare.com

and probably website waitbutwhy.com is hosted by cloudflare.com web hosting company. Check the complete list of other most popular websites hosted by cloudflare.com hosting company.

According to Alexa traffic rank the highest website waitbutwhy.com position was 4108 (in the world). The lowest Alexa rank position was 83080. Now website waitbutwhy.com ranked in Alexa database as number 41932 (in the world).

Website waitbutwhy.com Desktop speed measurement score (81/100) is better than the results of 75.25% of other sites and shows that the page is performing great on desktop computers.

waitbutwhy.com Mobile usability score (98/100) is better than the results of 68.65% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of waitbutwhy.com (76/100) is better than the results of 87.16% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
May-21-2019 N/AN/A
May-20-2019 41,932-5,562
May-19-2019 36,370254
May-18-2019 36,624-13,178
May-17-2019 23,4466,617
May-16-2019 30,0637,243
May-15-2019 37,306-10,306

Advertisement

waitbutwhy.com Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.


waitbutwhy.com whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


Domain Name: WAITBUTWHY.COM
Registry Domain ID: 1787548931_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Update Date: 2014-01-24T21:53:42Z
Creation Date: 2013-03-20T01:34:49Z
Registrar Registration Expiration Date: 2019-03-20T01:34:49Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registry Registrant ID:
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 14747 N Northsight Blvd Suite 111, PMB 309
Registrant City: Scottsdale
Registrant State/Province: Arizona
Registrant Postal Code: 85260
Registrant Country: United States
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: WAITBUTWHY.COM@domainsbyproxy.com
Registry Admin ID:
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 14747 N Northsight Blvd Suite 111, PMB 309
Admin City: Scottsdale
Admin State/Province: Arizona
Admin Postal Code: 85260
Admin Country: United States
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: WAITBUTWHY.COM@domainsbyproxy.com
Registry Tech ID:
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 14747 N Northsight Blvd Suite 111, PMB 309
Tech City: Scottsdale
Tech State/Province: Arizona
Tech Postal Code: 85260
Tech Country: United States
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: WAITBUTWHY.COM@domainsbyproxy.com
Name Server: DEMI.NS.CLOUDFLARE.COM
Name Server: JUSTIN.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2015-06-21T15:00:00Z

waitbutwhy.com server information

Servers Location

waitbutwhy.com desktop page speed rank

Last tested: 2016-07-13


Desktop Speed Medium
81/100

waitbutwhy.com Desktop Speed Test Quick Summary


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

http://sumome.com/api/load/ (expiration not specified)
http://cdn.optimizely.com/js/2572440331.js (2 minutes)
http://assets.pinterest.com/js/pinit.js (5 minutes)
http://assets.pinterest.com/js/pinit.js?ver=4.5.3 (5 minutes)
http://assets.pinterest.com/js/pinit_main.js?0.6401291275396943 (5 minutes)
http://load.sumome.com/ (10 minutes)
http://waitbutwhyforum.disqus.com/count-data.js?1=…twhy.com%2F%3Fp%3D5241 (10 minutes)
http://waitbutwhyforum.disqus.com/count-data.js?1=…twhy.com%2F%3Fp%3D5371 (10 minutes)
http://connect.facebook.net/en_US/all.js?ver=4.5.3 (20 minutes)
http://connect.facebook.net/en_US/fbds.js (20 minutes)
http://connect.facebook.net/en_US/sdk.js (20 minutes)
http://apis.google.com/js/plusone.js (30 minutes)
https://platform.twitter.com/widgets.js?ver=4.5.3 (30 minutes)
http://static.chartbeat.com/js/chartbeat.js (2 hours)
http://www.google-analytics.com/analytics.js (2 hours)
http://waitbutwhy.com/ (3 hours)
http://connect.cointent.com/style.css?ver=4.5.3 (4 hours)

priority - 5 Optimize images

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

Optimize the following images to reduce their size by 45.9KiB (28% reduction).

Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…-FEATURE-2-345x234.png could save 6.8KiB (15% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…d-FEATURE1-345x234.jpg could save 6.6KiB (25% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…15/06/random_posts.png could save 5.9KiB (29% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…08/FEATURE-345x234.png could save 5.7KiB (23% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/2015/02/F-103x70.jpg could save 5.7KiB (63% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…y-2-FEATURE-103x70.jpg could save 4.2KiB (62% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…/01/Feature-103x70.jpg could save 4.2KiB (65% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…/FEATURE-1-345x234.png could save 2.4KiB (17% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…/images/wbw-cn-new.png could save 1KiB (76% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…images/Andrew-Cave.png could save 1,003B (32% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…twhy/images/turtle.png could save 918B (56% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…butwhy/images/home.png could save 815B (63% reduction).
Losslessly compressing http://waitbutwhy.com/wp-content/plugins/floating-…/images/fsb-sprite.png could save 784B (19% reduction).

priority - 4 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 43.3KiB (66% reduction).

Compressing http://staticxx.facebook.com/connect/xd_arbiter.php?version=42 could save 21.7KiB (66% reduction).
Compressing https://staticxx.facebook.com/connect/xd_arbiter.php?version=42 could save 21.7KiB (66% reduction).

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

Your page has 12 blocking script resources and 20 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:

http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…y/jquery.js?ver=1.12.4
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…grate.min.js?ver=1.4.1
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…utils.min.js?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…pster.min.js?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…er_script.js?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…-widget.min.js?ver=4.1
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…low_2.1.2.js?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd….facebook.js?ver=4.5.3
http://connect.facebook.net/en_US/all.js?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…oogleplus.js?ver=4.5.3
https://platform.twitter.com/widgets.js?ver=4.5.3

Use asynchronous versions of the following scripts:

http://assets.pinterest.com/js/pinit.js?ver=4.5.3

Optimize CSS Delivery of the following:

http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…te/style.css?ver=1.0.0
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…ap_style.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…-default.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/common.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…elective.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…lt/style.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…ight_style.css?ver=1.6
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…l_widget.css?ver=4.5.3
http://connect.cointent.com/style.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…hy/style.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…some.min.css?ver=4.5.3
http://fonts.googleapis.com/css?family=Noto+Sans%3…+Sans+Narrow&ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…ss/theme.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/custom.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/slider.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/common.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…lightbox.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…sic.min.css?ver=3.1.11
http://waitbutwhy.com/?sccss=1&ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…le_2.1.2.css?ver=4.5.3

priority - 1 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 7.9KiB (36% reduction).

Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…/collapse.js?ver=1.6.2 could save 1.9KiB (51% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…ar/js/fsb.js?ver=1.1.7 could save 1.2KiB (34% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…scrollspy.js?ver=4.5.3 could save 1.1KiB (53% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…gfoot.min.js?ver=1.4.0 could save 911B (22% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/scripts.js?ver=4.5.3 could save 878B (49% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…verIntent.js?ver=4.5.3 could save 693B (56% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…orm/js/sf.js?ver=1.0.1 could save 648B (21% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…er_script.js?ver=4.5.3 could save 635B (26% reduction) after compression.

priority - 1 Minify 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 4.1KiB (25% reduction).

Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…ss/theme.css?ver=4.5.3 could save 3.5KiB (25% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…te/style.css?ver=1.0.0 could save 546B (28% reduction) after compression.

waitbutwhy.com Desktop Resources

Total Resources162
Number of Hosts22
Static Resources146
JavaScript Resources61
CSS Resources20

waitbutwhy.com Desktop Resource Breakdown

waitbutwhy.com mobile page speed rank

Last tested: 2016-07-13


Mobile Speed Medium
76/100

waitbutwhy.com Mobile Speed Test Quick Summary


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

http://sumome.com/api/load/ (expiration not specified)
http://cdn.optimizely.com/js/2572440331.js (2 minutes)
http://assets.pinterest.com/js/pinit.js (5 minutes)
http://assets.pinterest.com/js/pinit.js?ver=4.5.3 (5 minutes)
http://assets.pinterest.com/js/pinit_main.js?0.37875161971896887 (5 minutes)
http://load.sumome.com/ (10 minutes)
http://waitbutwhyforum.disqus.com/count-data.js?1=…twhy.com%2F%3Fp%3D5241 (10 minutes)
http://waitbutwhyforum.disqus.com/count-data.js?1=…twhy.com%2F%3Fp%3D5371 (10 minutes)
http://connect.facebook.net/en_US/all.js?ver=4.5.3 (20 minutes)
http://connect.facebook.net/en_US/fbds.js (20 minutes)
http://connect.facebook.net/en_US/sdk.js (20 minutes)
http://apis.google.com/js/plusone.js (30 minutes)
https://platform.twitter.com/widgets.js?ver=4.5.3 (30 minutes)
http://static.chartbeat.com/js/chartbeat.js (2 hours)
http://www.google-analytics.com/analytics.js (2 hours)
http://waitbutwhy.com/ (3 hours)
http://connect.cointent.com/style.css?ver=4.5.3 (4 hours)

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

Your page has 12 blocking script resources and 20 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:

http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…y/jquery.js?ver=1.12.4
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…grate.min.js?ver=1.4.1
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…utils.min.js?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…pster.min.js?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…er_script.js?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…-widget.min.js?ver=4.1
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…low_2.1.2.js?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd….facebook.js?ver=4.5.3
http://connect.facebook.net/en_US/all.js?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…oogleplus.js?ver=4.5.3
https://platform.twitter.com/widgets.js?ver=4.5.3

Use asynchronous versions of the following scripts:

http://assets.pinterest.com/js/pinit.js?ver=4.5.3

Optimize CSS Delivery of the following:

http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…te/style.css?ver=1.0.0
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…ap_style.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…-default.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/common.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…elective.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…lt/style.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…ight_style.css?ver=1.6
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…l_widget.css?ver=4.5.3
http://connect.cointent.com/style.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…hy/style.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…some.min.css?ver=4.5.3
http://fonts.googleapis.com/css?family=Noto+Sans%3…+Sans+Narrow&ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…ss/theme.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/custom.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/slider.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/common.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…lightbox.css?ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…sic.min.css?ver=3.1.11
http://waitbutwhy.com/?sccss=1&ver=4.5.3
http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…le_2.1.2.css?ver=4.5.3

priority - 4 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 43.3KiB (66% reduction).

Compressing http://staticxx.facebook.com/connect/xd_arbiter.php?version=42 could save 21.7KiB (66% reduction).
Compressing https://staticxx.facebook.com/connect/xd_arbiter.php?version=42 could save 21.7KiB (66% reduction).

priority - 4 Optimize images

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

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

Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…-FEATURE-2-345x234.png could save 6.8KiB (15% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…d-FEATURE1-345x234.jpg could save 6.6KiB (25% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…15/06/random_posts.png could save 5.9KiB (29% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…08/FEATURE-345x234.png could save 5.7KiB (23% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/2015/02/F-103x70.jpg could save 5.7KiB (63% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…y-2-FEATURE-103x70.jpg could save 4.2KiB (62% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…/01/Feature-103x70.jpg could save 4.2KiB (65% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…/FEATURE-1-345x234.png could save 2.4KiB (17% reduction).
Losslessly compressing http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…twhy/images/turtle.png could save 918B (56% reduction).
Losslessly compressing http://waitbutwhy.com/wp-content/plugins/floating-…/images/fsb-sprite.png could save 784B (19% reduction).

priority - 1 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 7.9KiB (36% reduction).

Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…/collapse.js?ver=1.6.2 could save 1.9KiB (51% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…ar/js/fsb.js?ver=1.1.7 could save 1.2KiB (34% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…scrollspy.js?ver=4.5.3 could save 1.1KiB (53% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…gfoot.min.js?ver=1.4.0 could save 911B (22% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…s/scripts.js?ver=4.5.3 could save 878B (49% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…verIntent.js?ver=4.5.3 could save 693B (56% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…orm/js/sf.js?ver=1.0.1 could save 648B (21% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…er_script.js?ver=4.5.3 could save 635B (26% reduction) after compression.

priority - 1 Minify 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 4.1KiB (25% reduction).

Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…ss/theme.css?ver=4.5.3 could save 3.5KiB (25% reduction) after compression.
Minifying http://28oa9i1t08037ue3m1l0i861.wpengine.netdna-cd…te/style.css?ver=1.0.0 could save 546B (28% reduction) after compression.

waitbutwhy.com Mobile Resources

Total Resources159
Number of Hosts22
Static Resources143
JavaScript Resources61
CSS Resources20

waitbutwhy.com Mobile Resource Breakdown

waitbutwhy.com mobile page usability

Last tested: 2016-07-13


Mobile Usability Good
98/100

waitbutwhy.com Mobile Usability Test Quick Summary


priority - 1 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="http://waitbut…nize-mars.html">How (and Why)…Colonize Mars</a> and 15 others are close to other tap targets.
The tap target <a href="http://waitbut….html#comments">853</a> and 29 others are close to other tap targets.
The tap target <a href="http://waitbut….html#comments">853</a> and 29 others are close to other tap targets.
The tap target <a href="https://www.pa…com/waitbutwhy"></a> is close to 1 other tap targets.
The tap target <a href="http://waitbut…haring-policy/">© WaitButWhy 2016</a> and 1 others are close to other tap targets.
The tap target <a href="http://waitbutwhy.com/contact" class="contactLink">Contact</a> and 2 others are close to other tap targets.

waitbutwhy.com Mobile Resources

Total Resources159
Number of Hosts22
Static Resources143
JavaScript Resources61
CSS Resources20

waitbutwhy.com Mobile Resource Breakdown

waitbutwhy.com similar domains

Similar domains:
www.waitbutwhy.com
www.waitbutwhy.net
www.waitbutwhy.org
www.waitbutwhy.info
www.waitbutwhy.biz
www.waitbutwhy.us
www.waitbutwhy.mobi
www.aitbutwhy.com
www.waitbutwhy.com
www.qaitbutwhy.com
www.wqaitbutwhy.com
www.qwaitbutwhy.com
www.aaitbutwhy.com
www.waaitbutwhy.com
www.awaitbutwhy.com
www.saitbutwhy.com
www.wsaitbutwhy.com
www.swaitbutwhy.com
www.eaitbutwhy.com
www.weaitbutwhy.com
www.ewaitbutwhy.com
www.witbutwhy.com
www.wqitbutwhy.com
www.waqitbutwhy.com
www.wwitbutwhy.com
www.wawitbutwhy.com
www.wwaitbutwhy.com
www.wsitbutwhy.com
www.wasitbutwhy.com
www.wzitbutwhy.com
www.wazitbutwhy.com
www.wzaitbutwhy.com
www.watbutwhy.com
www.wautbutwhy.com
www.waiutbutwhy.com
www.wauitbutwhy.com
www.wajtbutwhy.com
www.waijtbutwhy.com
www.wajitbutwhy.com
www.waktbutwhy.com
www.waiktbutwhy.com
www.wakitbutwhy.com
www.waotbutwhy.com
www.waiotbutwhy.com
www.waoitbutwhy.com
www.waibutwhy.com
www.wairbutwhy.com
www.waitrbutwhy.com
www.wairtbutwhy.com
www.waifbutwhy.com
www.waitfbutwhy.com
www.waiftbutwhy.com
www.waigbutwhy.com
www.waitgbutwhy.com
www.waigtbutwhy.com
www.waiybutwhy.com
www.waitybutwhy.com
www.waiytbutwhy.com
www.waitutwhy.com
www.waitvutwhy.com
www.waitbvutwhy.com
www.waitvbutwhy.com
www.waitgutwhy.com
www.waitbgutwhy.com
www.waithutwhy.com
www.waitbhutwhy.com
www.waithbutwhy.com
www.waitnutwhy.com
www.waitbnutwhy.com
www.waitnbutwhy.com
www.waitbtwhy.com
www.waitbytwhy.com
www.waitbuytwhy.com
www.waitbyutwhy.com
www.waitbhtwhy.com
www.waitbuhtwhy.com
www.waitbjtwhy.com
www.waitbujtwhy.com
www.waitbjutwhy.com
www.waitbitwhy.com
www.waitbuitwhy.com
www.waitbiutwhy.com
www.waitbuwhy.com
www.waitburwhy.com
www.waitbutrwhy.com
www.waitburtwhy.com
www.waitbufwhy.com
www.waitbutfwhy.com
www.waitbuftwhy.com
www.waitbugwhy.com
www.waitbutgwhy.com
www.waitbugtwhy.com
www.waitbuywhy.com
www.waitbutywhy.com
www.waitbuthy.com
www.waitbutqhy.com
www.waitbutwqhy.com
www.waitbutqwhy.com
www.waitbutahy.com
www.waitbutwahy.com
www.waitbutawhy.com
www.waitbutshy.com
www.waitbutwshy.com
www.waitbutswhy.com
www.waitbutehy.com
www.waitbutwehy.com
www.waitbutewhy.com
www.waitbutwy.com
www.waitbutwby.com
www.waitbutwhby.com
www.waitbutwbhy.com
www.waitbutwgy.com
www.waitbutwhgy.com
www.waitbutwghy.com
www.waitbutwyy.com
www.waitbutwhyy.com
www.waitbutwyhy.com
www.waitbutwuy.com
www.waitbutwhuy.com
www.waitbutwuhy.com
www.waitbutwjy.com
www.waitbutwhjy.com
www.waitbutwjhy.com
www.waitbutwny.com
www.waitbutwhny.com
www.waitbutwnhy.com
www.waitbutwh.com
www.waitbutwht.com
www.waitbutwhyt.com
www.waitbutwhty.com
www.waitbutwhg.com
www.waitbutwhyg.com
www.waitbutwhh.com
www.waitbutwhyh.com
www.waitbutwhhy.com
www.waitbutwhu.com
www.waitbutwhyu.com
www.waitbutwhy.con

waitbutwhy.com Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


waitbutwhy.com TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.