whitehouse.gov Website Information
Daily Unique Visits: 6,402,799
Daily Page Views: 51,222,392
Income Per Day: $51,222
Estimated Value: $55,319,760
This website is located in Hong Kong and is using following IP address 2.17.55.177. See the complete list of popular websites hosted in Hong Kong.
whitehouse.gov is registered under .GOV top-level domain. Please check other sites in .GOV zone.
Website whitehouse.gov is using the following name servers:
- usw6.akam.net
- a12-64.akam.net
- ns1-176.akam.net
- a5-64.akam.net
- use6.akam.net
- a20-65.akam.net
- zc.akam.net
- a1-61.akam.net
- a22-66.akam.net
- asia9.akam.net
- ns1-145.akam.net
- usw5.akam.net
- a3-67.akam.net
- usw1.akam.net
and is probably hosted by AUTOMATTIC - Automattic, Inc, US. See the full list of other websites hosted by AUTOMATTIC - Automattic, Inc, US.
The highest website whitehouse.gov position in Alexa rank database was 228 and the lowest rank position was 243. Current position of whitehouse.gov in Alexa rank database is 238.
Desktop speed score of whitehouse.gov (56/100) is better than the results of 30.56% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of whitehouse.gov (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.
Mobile speed score of whitehouse.gov (57/100) is better than the results of 48.04% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
whitehouse.gov 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.
whitehouse.gov 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.
Domain Name: WHITEHOUSE.GOV
Status: ACTIVE
>>> Last update of whois database: 2021-04-24T21:52:50Z
whitehouse.gov server information
Servers Location
whitehouse.gov desktop page speed rank
Last tested: 2016-06-13
whitehouse.gov Desktop Speed Test Quick Summary
priority - 76Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 743.1KiB (93% reduction).
Compressing and resizing https://www.whitehouse.gov/sites/whitehouse.gov/fi…s/potus_phone_tout.jpg could save 241.2KiB (97% reduction).
Compressing and resizing https://www.whitehouse.gov/sites/whitehouse.gov/fi…s_schedule_tout_02.jpg could save 113KiB (92% reduction).
Compressing and resizing https://www.whitehouse.gov/sites/whitehouse.gov/fi…images/usow_tout_0.jpg could save 82.2KiB (78% reduction).
Losslessly compressing https://www.whitehouse.gov/profiles/forall/modules…nhundred/images/hr.jpg could save 2.4KiB (89% reduction).
Compressing and resizing https://www.whitehouse.gov/profiles/forall/modules…icons/wh_logo_seal.png could save 2.2KiB (26% reduction).
priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://www.whitehouse.gov/sites/whitehouse.gov/fi…EF45iPvB4FbvPqCl7I.css
https://www.whitehouse.gov/sites/whitehouse.gov/fi…EF45iPvB4FbvPqCl7I.css
https://www.whitehouse.gov/sites/whitehouse.gov/fi…EF45iPvB4FbvPqCl7I.css
priority - 2Leverage 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://connect.facebook.net/en_US/sdk.js (20 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
whitehouse.gov Desktop Resource Breakdown
Total Resources | 41 |
Number of Hosts | 13 |
Static Resources | 29 |
JavaScript Resources | 13 |
CSS Resources | 5 |
whitehouse.gov mobile page speed rank
Last tested: 2019-12-02
whitehouse.gov Mobile Speed Test Quick Summary
priority - 34Avoid 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.
https://whitehouse.gov/
https://www.whitehouse.gov/
priority - 32Eliminate 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 - 16Leverage 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.whitehouse.gov/wp-content/themes/white…s/img/footer-email.svg (expiration not specified)
https://www.whitehouse.gov/wp-content/themes/white…mg/footer-facebook.svg (expiration not specified)
https://www.whitehouse.gov/wp-content/themes/white…g/footer-instagram.svg (expiration not specified)
https://www.whitehouse.gov/wp-content/themes/white…img/footer-twitter.svg (expiration not specified)
https://www.whitehouse.gov/wp-content/themes/white…sets/img/hamburger.svg (expiration not specified)
https://www.whitehouse.gov/wp-content/themes/white…dential-crest-gray.svg (expiration not specified)
https://www.whitehouse.gov/wp-content/themes/white…/assets/img/search.png (expiration not specified)
https://www.whitehouse.gov/wp-content/themes/white…/assets/img/search.svg (expiration not specified)
https://www.whitehouse.gov/wp-content/themes/white…use-logo-footer-lg.png (expiration not specified)
https://www.whitehouse.gov/wp-content/themes/white…e-house-logo-lg-bl.png (expiration not specified)
https://www.whitehouse.gov/wp-content/themes/white…e-house-logo-lg-wh.png (expiration not specified)
https://www.whitehouse.gov/wp-content/uploads/2017…ouse-Faded-900x600.jpg (expiration not specified)
https://www.whitehouse.gov/wp-content/uploads/2017/11/bitmap-1.jpg (expiration not specified)
https://www.whitehouse.gov/wp-content/uploads/2017/11/bitmap.jpg (expiration not specified)
https://www.whitehouse.gov/wp-content/uploads/2019…fEU8AAPXlw-620x620.jpg (expiration not specified)
https://www.whitehouse.gov/wp-content/uploads/2019…125JB-0485-620x620.jpg (expiration not specified)
https://www.whitehouse.gov/wp-content/uploads/2019…28SC-06847-600x685.jpg (expiration not specified)
https://www.whitehouse.gov/wp-content/uploads/2019…OTD-Nov-26-620x620.jpg (expiration not specified)
https://www.googletagmanager.com/gtag/js?id=UA-12099831-10 (15 minutes)
https://js-agent.newrelic.com/nr-1153.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
whitehouse.gov Mobile Resource Breakdown
Total Resources | 41 |
Number of Hosts | 9 |
Static Resources | 23 |
JavaScript Resources | 10 |
CSS Resources | 2 |
whitehouse.gov mobile page usability
Last tested: 2019-12-02
whitehouse.gov Mobile Usability Test Quick Summary
priority - 0Size 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://www.wh…se.gov/search/" class="header__search">Search WhiteHo…open-search</a>
is close to 1 other tap targets.<button type="button" class="popover__search-toggle"></button>
is close to 1 other tap targets.whitehouse.gov HTML validation
Errors
A “charset” attribute on a “meta” element found after the first 1024 bytes.
"... charset="utf-8" /> <link rel=..."
A “link” element with a “sizes” attribute must have a “rel” attribute that contains the value “icon” or the value “apple-touch-icon”.
"...0.png" /> <link rel="apple-touch-icon-precomposed" sizes="72x72" href="https://www.whitehouse.gov/profiles/forall/themes/custom/fortyfour/images/fortyfour/favicons/apple-touch-icon-72x72-precomposed.png" /> <link..." Line: 25 Column: 1 - 196
"...d.png" /> <link rel="apple-touch-icon-precomposed" sizes="76x76" href="https://www.whitehouse.gov/profiles/forall/themes/custom/fortyfour/images/fortyfour/favicons/apple-touch-icon-76x76-precomposed.png" /> <link..." Line: 26 Column: 1 - 196
"...d.png" /> <link rel="apple-touch-icon-precomposed" sizes="60x60" href="https://www.whitehouse.gov/profiles/forall/themes/custom/fortyfour/images/fortyfour/favicons/apple-touch-icon-60x60-precomposed.png" /> <link..." Line: 27 Column: 1 - 196
"...d.png" /> <link rel="apple-touch-icon-precomposed" sizes="57x57" href="https://www.whitehouse.gov/profiles/forall/themes/custom/fortyfour/images/fortyfour/favicons/apple-touch-icon-57x57-precomposed.png" /> <link..." Line: 42 Column: 1 - 200
"...house" /> <link rel="apple-touch-icon-precomposed" sizes="114x114" href="https://www.whitehouse.gov/profiles/forall/themes/custom/fortyfour/images/fortyfour/favicons/apple-touch-icon-114x114-precomposed.png" /> <link..." Line: 43 Column: 1 - 200
"...d.png" /> <link rel="apple-touch-icon-precomposed" sizes="120x120" href="https://www.whitehouse.gov/profiles/forall/themes/custom/fortyfour/images/fortyfour/favicons/apple-touch-icon-120x120-precomposed.png" /> <link..." Line: 45 Column: 1 - 200
"....icon" /> <link rel="apple-touch-icon-precomposed" sizes="152x152" href="https://www.whitehouse.gov/profiles/forall/themes/custom/fortyfour/images/fortyfour/favicons/apple-touch-icon-152x152-precomposed.png" /> <link..." Line: 46 Column: 1 - 200
"...d.png" /> <link rel="apple-touch-icon-precomposed" sizes="144x144" href="https://www.whitehouse.gov/profiles/forall/themes/custom/fortyfour/images/fortyfour/favicons/apple-touch-icon-144x144-precomposed.png" /> <meta..."
Bad value “cleartype” for attribute “http-equiv” on element “meta”.
"...dth"> <meta http-equiv="cleartype" content="on"> <l..."
Bad value “” for attribute “id” on element “div”: An ID must not be the empty string.
"...> <div class="panel-display panel-single-col-full-width" id=""> <he..."
Element “div” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)
"...ss="menu"><div class="depth-2-wrapper"><li cl..." Line: 204 Column: 220 - 248
"...ss="menu"><div class="depth-2-wrapper"><li cl..." Line: 214 Column: 243 - 271
"...ss="menu"><div class="depth-2-wrapper"><li cl..." Line: 230 Column: 233 - 261
"...ss="menu"><div class="depth-2-wrapper"><li cl..." Line: 245 Column: 224 - 252
"...ss="menu"><div class="depth-2-wrapper"><li cl..."
Attribute “about” not allowed on element “article” at this point.
"...tem even"><article class="node-323491 node node-hero view-mode-default clearfix" about="/node/323491" typeof="sioc:Item foaf:Document"> <di..."
Attribute “content” not allowed on element “span” at this point.
"...</div> <span property="dc:title" content="Home Page Image Centered Text" class="rdf-meta element-hidden"></span..." Line: 328 Column: 108 - 208
"...n"></span><span property="sioc:num_replies" content="0" datatype="xsd:integer" class="rdf-meta element-hidden"></span..."
Attribute “datatype” not allowed on element “span” at this point.
"...n"></span><span property="sioc:num_replies" content="0" datatype="xsd:integer" class="rdf-meta element-hidden"></span..."
Attribute “about” not allowed on element “div” at this point.
"...tem even"><div class="entity entity-paragraphs-item paragraphs-item-featured-content clearfix" about="" typeof=""> ..." Line: 373 Column: 35 - 138
"...item odd"><div class="entity entity-paragraphs-item paragraphs-item-featured-content clearfix" about="" typeof=""> ..."
The element “footer” must not appear as a descendant of the “footer” element.
"...er"> <footer class="panel-pane pane-panels-mini pane-default-sitewide-footer sitewide-footer" > <..."
An element with “role=tab” must be contained in, or owned by, an element with “role=tablist”.
"...r"> <a href="#" role='tab' id="main-menu-toggle"><i cla..."
Warnings
The “name” attribute is obsolete. Consider putting an “id” attribute on the nearest container instead.
"... <a id="content-start" name="content-start" tabindex="-1"></a> ..."
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
"...ntent --> <section id="page"> ..."
whitehouse.gov similar domains
www.whitehouse.net
www.whitehouse.org
www.whitehouse.info
www.whitehouse.biz
www.whitehouse.us
www.whitehouse.mobi
www.hitehouse.gov
www.whitehouse.gov
www.qhitehouse.gov
www.wqhitehouse.gov
www.qwhitehouse.gov
www.ahitehouse.gov
www.wahitehouse.gov
www.awhitehouse.gov
www.shitehouse.gov
www.wshitehouse.gov
www.swhitehouse.gov
www.ehitehouse.gov
www.wehitehouse.gov
www.ewhitehouse.gov
www.witehouse.gov
www.wbitehouse.gov
www.whbitehouse.gov
www.wbhitehouse.gov
www.wgitehouse.gov
www.whgitehouse.gov
www.wghitehouse.gov
www.wyitehouse.gov
www.whyitehouse.gov
www.wyhitehouse.gov
www.wuitehouse.gov
www.whuitehouse.gov
www.wuhitehouse.gov
www.wjitehouse.gov
www.whjitehouse.gov
www.wjhitehouse.gov
www.wnitehouse.gov
www.whnitehouse.gov
www.wnhitehouse.gov
www.whtehouse.gov
www.whutehouse.gov
www.whiutehouse.gov
www.whjtehouse.gov
www.whijtehouse.gov
www.whktehouse.gov
www.whiktehouse.gov
www.whkitehouse.gov
www.whotehouse.gov
www.whiotehouse.gov
www.whoitehouse.gov
www.whiehouse.gov
www.whirehouse.gov
www.whitrehouse.gov
www.whirtehouse.gov
www.whifehouse.gov
www.whitfehouse.gov
www.whiftehouse.gov
www.whigehouse.gov
www.whitgehouse.gov
www.whigtehouse.gov
www.whiyehouse.gov
www.whityehouse.gov
www.whiytehouse.gov
www.whithouse.gov
www.whitwhouse.gov
www.whitewhouse.gov
www.whitwehouse.gov
www.whitshouse.gov
www.whiteshouse.gov
www.whitsehouse.gov
www.whitdhouse.gov
www.whitedhouse.gov
www.whitdehouse.gov
www.whitrhouse.gov
www.whiterhouse.gov
www.whiteouse.gov
www.whitebouse.gov
www.whitehbouse.gov
www.whitebhouse.gov
www.whitegouse.gov
www.whitehgouse.gov
www.whiteghouse.gov
www.whiteyouse.gov
www.whitehyouse.gov
www.whiteyhouse.gov
www.whiteuouse.gov
www.whitehuouse.gov
www.whiteuhouse.gov
www.whitejouse.gov
www.whitehjouse.gov
www.whitejhouse.gov
www.whitenouse.gov
www.whitehnouse.gov
www.whitenhouse.gov
www.whitehuse.gov
www.whitehiuse.gov
www.whitehoiuse.gov
www.whitehiouse.gov
www.whitehkuse.gov
www.whitehokuse.gov
www.whitehkouse.gov
www.whitehluse.gov
www.whiteholuse.gov
www.whitehlouse.gov
www.whitehpuse.gov
www.whitehopuse.gov
www.whitehpouse.gov
www.whitehose.gov
www.whitehoyse.gov
www.whitehouyse.gov
www.whitehoyuse.gov
www.whitehohse.gov
www.whitehouhse.gov
www.whitehohuse.gov
www.whitehojse.gov
www.whitehoujse.gov
www.whitehojuse.gov
www.whitehoise.gov
www.whitehouise.gov
www.whitehoue.gov
www.whitehouwe.gov
www.whitehouswe.gov
www.whitehouwse.gov
www.whitehouee.gov
www.whitehousee.gov
www.whitehouese.gov
www.whitehoude.gov
www.whitehousde.gov
www.whitehoudse.gov
www.whitehouze.gov
www.whitehousze.gov
www.whitehouzse.gov
www.whitehouxe.gov
www.whitehousxe.gov
www.whitehouxse.gov
www.whitehouae.gov
www.whitehousae.gov
www.whitehouase.gov
www.whitehous.gov
www.whitehousw.gov
www.whitehousew.gov
www.whitehouss.gov
www.whitehouses.gov
www.whitehousse.gov
www.whitehousd.gov
www.whitehoused.gov
www.whitehousr.gov
www.whitehouser.gov
www.whitehousre.gov
whitehouse.gov 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.
whitehouse.gov 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.