Washingtonpost.Com - Info washingtonpost.com

washingtonpost.com receives about 2,308,500 unique visitors and 4,755,510 (2.06 per visitor) page views per day which should earn about $43,321.03/day from advertising revenue. Estimated site value is $29,627,414.89. According to Alexa Traffic Rank washingtonpost.com is ranked number 188 in the world and 0.4617% of global Internet users visit it. Site is hosted in Palo Alto, CA, 94306, United States and links to network IP address 192.33.31.56.

About - washingtonpost.com

Breaking news and analysis on politics, business, world national news, entertainment more. In-depth DC, Virginia, Maryland news coverage including traffic, weather, crime, education, restaurant reviews and more.
How did washingtonpost.com look in the past? Edit Site Info

How popular is washingtonpost.com?

Daily Unique Visitors:
2,308,500
Monthly Unique Visitors:
69,255,000
Daily Pageviews:
4,755,510 (2.06 per visitor)
Alexa Rank:
188 visit alexa
Alexa Reach:
0.4617% (Percent of global Internet users)
*All traffic values are estimates only.

Alexa
majestic
Quantcast

Visitors by country

Users%Pageviews%Rank
United States 74.9%72.7%44
Japan 4.2%8.2%282
Canada 2.4%1.9%169
United Kingdom 2.2%1.6%325
Korea, Republic of 1.8%3.8%194
China 1.3%0.8%1903
Germany 1.3%1.0%648
France 0.9%0.7%766
Australia 0.9%0.7%322
India 0.8%0.5%2281
Taiwan 0.5%1.1%520

Where do visitors go on this site?

Reach%Pageviews%PerUser
washingtonpost.com
98.91%95.77%2.05
subscribe.washingtonpost.com
3.09%1.99%1.36
feeds.washingtonpost.com
0.58%0.28%1.0
games.washingtonpost.com
0.54%0.48%1.9
live.washingtonpost.com
0.46%0.23%1.1
doonesbury.washingtonpost.com
0.37%0.25%1.4
img.washingtonpost.com
0.31%0.15%1.0
jobs.washingtonpost.com
0.15%0.12%1.7
link.washingtonpost.com
0.11%0.06%1.0
wpcomics.washingtonpost.com
0.08%0.15%3.8
helpcenter.washingtonpost.com
0.06%0.06%2.2
id.washingtonpost.com
0.04%0.06%2.6
syndication.washingtonpost.com
0.03%0.07%5.8
stats.washingtonpost.com
0.03%0.06%4.1
OTHER
0%0.27%0

Competitive Data

SEMrush washingtonpost.com
Domain:
  washingtonpost.com
Rank:
  121
Organic Keywords:
  7,361,309
Organic Traffic:
  21,665,347
Organic Cost:
  $24,675,888.00
Adwords Keywords:
  304
Adwords Traffic:
  84,466
Adwords Cost:
  $161,140.00

Data

Domain Authority:
  96
Page Authority:
  80
MozRank:
  6

Backlinks Report

Total Sites Linking In (Alexa):
92,755
Total Backlinks:
  22,964,071
Follow Links:
  14,507,844
Nofollow Links:
  8,456,227
Referring Domains:
  188,593
Referring IPs:
  140,407

How socially engaged is washingtonpost.com?

Facebook:
  209,300
Google +:
  2,419
Linkedin:
  1,083
Stumbles:
  37,130
Buffer:
  236
Pins:
  2

How much washingtonpost.com can earn?

Daily Revenue:
$43,321.03
Monthly Revenue:
$1,299,630.90
Yearly Revenue:
$15,812,175.95
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 3,457,256$39,654.72
Japan 389,952$1,247.85
Canada 90,355$633.39
United Kingdom 76,088$474.03
Korea, Republic of 180,709$419.25
Australia 33,289$250.66
Germany 47,555$229.69
France 33,289$156.46
China 38,044$117.56
Taiwan 52,311$99.39
India 23,778$38.04

How much money do washingtonpost.com lose due to Adblock?

Daily Revenue Loss:
$7,602.04
Monthly Revenue Loss:
$228,061.11
Yearly Revenue Loss:
$2,774,743.51
Daily Pageviews Blocked:
720,079
Monthly Pageviews Blocked:
21,602,380
Yearly Pageviews Blocked:
262,828,953
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 622,306$7,137.85
Canada 22,589$158.35
United Kingdom 12,174$75.84
Germany 13,791$66.61
Australia 6,658$50.13
Japan 11,699$37.44
France 3,662$17.21
Korea, Republic of 7,228$16.77
Taiwan 8,370$15.90
China 4,946$15.28
India 6,658$10.65

How much is washingtonpost.com worth?

Website Value:
$29,627,414.89

Where is washingtonpost.com hosted?

Server location
Server IP:
192.33.31.56
ASN:
AS33047 
ISP:
Instart Logic, Inc 
Server Location:
Palo Alto
CA
94306
United States
 

Other sites hosted on 192.33.31.56

How fast does washingtonpost.com load?

Average Load Time:
(3292 ms) 18 % of sites are slower

Page Speed (Google PageSpeed Insights)

Suggestions Summary

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

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

https://www.washingtonpost.com/pb/gr/c/mobile-homepage/rPiAEy1neMRXgq/load_immediately/b1811100e1.js?_=c2f5a
https://www.washingtonpost.com/pb/resources/js/head.min.js
https://www.washingtonpost.com/pb/gr/c/mobile-homepage/rPiAEy1neMRXgq/global/95f829e22e.js?_=ed3f2
https://www.washingtonpost.com/pb/gr/c/mobile-homepage/rPiAEy1neMRXgq/headjs/70b9918770.js?_=64058
https://www.washingtonpost.com/pb/gr/p/mobile-homepage/rPiAEy1neMRXgq/head.js?_=a6de6
Optimize CSS Delivery of the following:

https://www.washingtonpost.com/pb/resources/css/latest/headerfonts.0.latest.css?_=201703223350PST
https://www.washingtonpost.com/pb/resources/css/latest/headerfonts.1.latest.css?_=201703223350PST
https://www.washingtonpost.com/pb/resources/css/latest/headerfonts.2.latest.css?_=201703223350PST
https://www.washingtonpost.com/pb/gr/c/mobile-homepage/rPiAEy1neMRXgq/css/9e1acbfb3f.css?_=242c9
https://www.washingtonpost.com/pb/gr/p/mobile-homepage/rPiAEy1neMRXgq/style.css?_=a6de6
https://www.washingtonpost.com/pb/gr/c/mobile-homepage/rPiAEy1neMRXgq/modal-css/938c258067.css?_=874d9

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://cdn-api.arcpublishing.com/v1.0/loxodo/datapoint/save (expiration not specified)
https://css.washingtonpost.com/wp-stat/ad/loaders/latest/css/wp_mobile.css (expiration not specified)
https://js.washingtonpost.com/wp-stat/rum/wprum.min.js (expiration not specified)
https://js.washingtonpost.com/wp-stat/visitorsegment/shared/resources/build/latest.js (expiration not specified)
https://www.washingtonpost.com/wp-stat/ad/loaders/latest/js/min/loader.min.js (expiration not specified)
https://www.washingtonpost.com/wp-stat/pwapi/prod/wpPwapi1-min.js (expiration not specified)
https://js.washingtonpost.com/wp-stat/***ytics/latest/main.js?token=201703223350PST (5 minutes)
https://www.washingtonpost.com/wp-stat/advertising/pseudo-static/identity-retargeting.js (5 minutes)
https://www.washingtonpost.com/wp-stat/advertising/subscribe.png (5 minutes)
https://s-jsonp.moatads.com/ocr/WASHPOSTCW1/level3/57952378-57952378?t=201731665 (13.4 minutes)
https://js-sec.indexww.com/ht/htw-wapo.js (17.9 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://washingtonpost-d.openx.net/w/1.0/jstag?nc=701-WashPo_Mobile (60 minutes)
https://js-agent.newrelic.com/nr-1016.min.js (2 hours)
https://static.chartbeat.com/js/chartbeat.js (2 hours)
https://z.moatads.com/washpostdfpcw45893854/moatad.js (6.3 hours)
https://js.washingtonpost.com/video/resources/env/WapoVideo/dist/WapoVideoEmbed.min.js (24 hours)
https://js.washingtonpost.com/video/resources/js/posttv/vendor/underscore-min.js (24 hours)

Optimize images

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

Optimize the following images to reduce their size by 61.3KiB (18% reduction).

Compressing https://img.washingtonpost.com/rf/image_1248w/2010-2019/WashingtonPost/2017/04/15/Foreign/Images/North_Korea_Founders_Birthday_62213-65a43.jpg could save 34.7KiB (16% reduction).
Compressing https://tpc.googlesyndication.com/simgad/13001764339919182*** could save 6.9KiB (50% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/2010-2019/Wires/Images/2017-04-15/Bloomberg/05909132.jpg could save 6.6KiB (18% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/2010-2019/WashingtonPost/2017/04/14/Editorial-Opinion/Images/Trump_57162-79089-2033.jpg could save 3.2KiB (17% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/2010-2019/WashingtonPost/2017/04/12/Interactivity/Images/border04-H.jpg could save 3.2KiB (18% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/2010-2019/WashingtonPost/2017/04/14/Production/Daily/Style/Images/Trump-01a6e.jpg could save 1.5KiB (20% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/2010-2019/WashingtonPost/2017/04/15/Foreign/Images/North_Korea_Founders_Birthday_62213-65a43.jpg could save 1.1KiB (19% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?src=http://img.washingtonpost.com/sf/brand-connect/wp-content/uploads/sites/3/2017/04/Promo_A_Image.jpg&w=138&h=92 could save 1.1KiB (23% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/2010-2019/Wires/Images/2016-02-27/Getty/AFP_8B2U1.jpg could save 1.1KiB (21% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?src=http://img.washingtonpost.com/sf/brand-connect/wp-content/uploads/sites/3/2017/02/Gifting_Equity_in_a_Home_lg.jpg&w=138&h=92 could save 1KiB (21% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?src=https://img.washingtonpost.com/blogs/style-blog/files/2017/04/fallon-kushner.jpg&w=138&h=92 could save 970B (21% reduction).

Minify JavaScript

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

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

Minifying https://js.washingtonpost.com/wp-stat/***ytics/latest/main.js?token=201703223350PST could save 8.1KiB (18% reduction) after compression.

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="https://www.washingtonpost.com" class="wp-logo-link">Democracy Dies in Darkness</a> is close to 2 other tap targets .
The tap target <a href="#" class="section-menu-btn"></a> is close to 2 other tap targets .
The tap target <a href="https://www.wa…/anna-fifield/">Anna Fifield</a> and 9 others are close to other tap targets .
The tap target <a href="https://www.wa…c84_story.html" class="">@PKCapitol: GO…for the fences</a> and 3 others are close to other tap targets.

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 518B (65% reduction).

Compressing https://pwapi.washingtonpost.com/?callback=jQuery311014881141134537756_1492349243171&referrer=&pwapi_contentsection=homepage&_=1492349243172 could save 518B (65% reduction).
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
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.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Download optimized image, JavaScript, and CSS resources for this page.

Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  93
Vendor reliability:
  93
Privacy:
  93
Child safety:
  93

Site Categories (dmoz)

Regional/United States

What sites are related to washingtonpost.com?

Http Header

HTTP/1.1 302 Moved Temporarily
Server: instart/nginx
Date: Mon, 24 Apr 2017 14:44:58 GMT
Content-Type: text/html
Content-Length: 156
Connection: close
Location: https://www.washingtonpost.com/
X-Instart-Request-ID: 7346549087380510296:BEQ01-NPPRY26:1493045098:165
HTTP/1.1 200 OK
Content-Type: text/html;ch***t=UTF-8
Connection: close
X-Served-By: pb
Server: nginx
PB-RID: rVfkKq127NXIhq
x-instart-cache-id: 12:6759983542271063122::1493044993
PB-PID: pPcRfs1Puwpjmp
Date: Mon, 24 Apr 2017 14:43:13 GMT
X-Backend: http://pagebuilder-app.wpprivate.com
Cache-Control: s-maxage=120
Access-Control-Allow-Origin: *
Age: 105
X-Instart-Request-ID: 8059467112481200874:BEQ01-NPPRY47:1493045098:165
X-Instart-Debug-Header: auth_status:200, origin:origin-web.washingtonpost.com, cache key modifier:0, num_auth_cookies:6
Set-Cookie: de=;Expires=Wednesday, 24-April-2019 14:44:58 GMT; path=/; domain=.washingtonpost.com
Set-Cookie: client_region=0;Expires=Monday, 24-April-2017 14:54:58 GMT; path=/; domain=.washingtonpost.com
Set-Cookie: X-WP-Split=X;Expires=Thursday, 01-January-1970 00:00:00 GMT; path=/; domain=.washingtonpost.com
Set-Cookie: devicetype=0;Expires=Thursday, 25-May-2017 01:13:58 GMT; path=/; domain=.washingtonpost.com
Set-Cookie: osfam=0;Expires=Thursday, 25-May-2017 01:13:58 GMT; path=/; domain=.washingtonpost.com
Set-Cookie: rpld1=21:il|22:chicago|23:41.878201|24:-87.625397|0:hypehoster.com|20:usa|;Expires=Monday, 24-April-2017 15:44:58 GMT; path=/; domain=.washingtonpost.com
Content-Security-Policy: upgrade-insecure-requests

DNS Lookup

Currently Not Available

Whois Lookup

Domain Created:
1995-11-13
Domain Age:
21 years 7 months 21 days  
WhoIs:
 

whois lookup at whois.corporatedomains.com...
Domain Name: washingtonpost.com
Registry Domain ID: 1707992_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.corporatedomains.com
Registrar URL: www.cscprotectsbrands.com
Updated Date: 2016-11-08T06:48:51Z
Creation Date: 1995-11-13T05:00:00Z
Registrar Registration Expiration Date: 2017-11-12T05:00:00Z
Registrar: CSC CORPORATE DOMAINS, INC.
Registrar IANA ID: 299
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.8887802723
Domain Status: serverTransferProhibited http://www.icann.org/epp#serverTransferProhibited
Domain Status: serverDeleteProhibited http://www.icann.org/epp#serverDeleteProhibited
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: serverUpdateProhibited http://www.icann.org/epp#serverUpdateProhibited
Registry Registrant ID:
Registrant Name: Domain Administrator
Registrant Organization: WP Company LLC
Registrant Street: 1301 K Street, NW
Registrant City: Washington
Registrant State/Province: DC
Registrant Postal Code: 20071
Registrant Country: US
Registrant Phone: +1.2023347868
Registrant Phone Ext:
Registrant Fax: +1.2023345075
Registrant Fax Ext:
Registrant Email: email
Registry Admin ID:
Admin Name: Domain Administrator
Admin Organization: WP Company LLC
Admin Street: 1301 K Street, NW
Admin City: Washington
Admin State/Province: DC
Admin Postal Code: 20071
Admin Country: US
Admin Phone: +1.2023347868
Admin Phone Ext:
Admin Fax: +1.2023345075
Admin Fax Ext:
Admin Email: email
Registry Tech ID:
Tech Name: Administrative Technical Contact
Tech Organization: WP Company LLC
Tech Street: 1301 K Street, NW
Tech City: Washington
Tech State/Province: DC
Tech Postal Code: 20071
Tech Country: US
Tech Phone: +1.2023344530
Tech Phone Ext:
Tech Fax: +1.2023345075
Tech Fax Ext:
Tech Email: email
Name Server: pdns3.ultradns.org
Name Server: ns-1840.awsdns-38.co.uk
Name Server: pdns115.ultradns.net
Name Server: pdns6.ultradns.co.uk
Name Server: ns-404.awsdns-50.com
Name Server: pdns5.ultradns.info
Name Server: pdns2.ultradns.net
Name Server: pdns4.ultradns.org
Name Server: ns-1027.awsdns-00.org
Name Server: ns-***.awsdns-19.net
Name Server: pdns1.ultradns.net
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2016-11-08T06:48:51Z <<<

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

Corporation Service Company(c) (CSC) The Trusted Partner of More than 50% of the 100 Best Global Brands.

Contact us to learn more about our enterprise solutions for Global Domain Name Registration and Management, Trademark Research and Watching, Brand, Logo and Auction Monitoring, as well SSL Certificate Services and DNS Hosting.

NOTICE: You are not authorized to access or query our WHOIS database through the use of high-volume, automated, electronic processes or for the purpose or purposes of using the data in any manner that violates these terms of use. The Data in the CSC WHOIS database is provided by CSC for information purposes only, and to assist persons in obtaining information about or related to a domain name registration record. CSC does not guarantee its accuracy. By submitting a WHOIS query, you agree to abide by the following terms of use: you agree that you may use this Data only for lawful purposes and that under no cir***stances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, e-mail, telephone, or facsimile; or (2) enable high volume, automated, electronic processes that apply to CSC (or its computer systems). CSC reserves the right to terminate your access to the WHOIS database in its sole discretion for any violations by you of these terms of use. CSC reserves the right to modify these terms at any time.

Register your domain name at http://www.cscglobal.com
whois lookup at whois.crsnic.net...
Whois Server Version 2.0

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

Domain Name: WASHINGTONPOST.COM
Registrar: CSC CORPORATE DOMAINS, INC.
Sponsoring Registrar IANA ID: 299
Whois Server: whois.corporatedomains.com
Referral URL: http://www.cscglobal.com/global/web/csc/digital-brand-services.html
Name Server: NS-1027.AWSDNS-00.ORG
Name Server: NS-1840.AWSDNS-38.CO.UK
Name Server: NS-404.AWSDNS-50.COM
Name Server: NS-***.AWSDNS-19.NET
Name Server: PDNS1.ULTRADNS.NET
Name Server: PDNS115.ULTRADNS.NET
Name Server: PDNS2.ULTRADNS.NET
Name Server: PDNS3.ULTRADNS.ORG
Name Server: PDNS4.ULTRADNS.ORG
Name Server: PDNS5.ULTRADNS.INFO
Name Server: PDNS6.ULTRADNS.CO.UK
Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
Updated Date: 08-nov-2016
Creation Date: 13-nov-1995
Expiration Date: 12-nov-2017

>>> Last update of whois database: Mon, 24 Apr 2017 14:45:01 GMT <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no cir***stances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.
Last update was 17 days ago
loader
This can take up to 60 seconds. Please wait...

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!
washingtonpost.com widget