wapo.st Website Information
Daily Unique Visits: 171,684
Daily Page Views: 1,373,472
Income Per Day: $1,373
Estimated Value: $1,482,840
This website is located in United States and is using following IP address 67.199.248.12. See the complete list of popular websites hosted in United States.
wapo.st is registered under .ST top-level domain. Please check other sites in .ST zone.
Website wapo.st is using the following name servers:
- dns1.cscdns.net
- dns2.cscdns.net
and is probably hosted by GOOGLE-PRIVATE-CLOUD - Google LLC, US. See the full list of other websites hosted by GOOGLE-PRIVATE-CLOUD - Google LLC, US.
The highest website wapo.st position in Alexa rank database was 8601 and the lowest rank position was 992430. Current position of wapo.st in Alexa rank database is 8876.
Desktop speed score of wapo.st (73/100) is better than the results of 56.16% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of wapo.st (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 wapo.st (51/100) is better than the results of 35.73% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
wapo.st 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.
wapo.st 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.
Whois Server Version 3.2.2
.ST domains can now be registered with many different competing registrars. Go to http://www.registry.st/registrars for detailed information.
Domain Name: wapo.st
Registrar: Corporation Service Company
Name Server: dns2.cscdns.net
Name Server: dns1.cscdns.net
Status: clientTransferProhibited
Updated Date: 2022-04-27
Creation Date: 2010-06-04
Expiration Date: 2023-06-04
>>> Last update of whois database: Sun Sep 25 12:34:59 2022 UTC
.ST domains can now be registered with many different competing registrars. Go to http://www.registry.st/registrars for detailed information.
Domain Name: wapo.st
Registrar: Corporation Service Company
Name Server: dns2.cscdns.net
Name Server: dns1.cscdns.net
Status: clientTransferProhibited
Updated Date: 2022-04-27
Creation Date: 2010-06-04
Expiration Date: 2023-06-04
>>> Last update of whois database: Sun Sep 25 12:34:59 2022 UTC
wapo.st server information
Servers Location
wapo.st desktop page speed rank
Last tested: 2018-01-28
Desktop Speed
Medium
73/100
wapo.st Desktop Speed Test Quick Summary
priority - 14Leverage 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://analytics.posttv.com/trending-videos-overall.json (expiration not specified)
https://load77.exelator.com/pixel.gif (expiration not specified)
https://www.washingtonpost.com/wp-stat/rum/wprum.min.js (57 seconds)
https://h.parrable.com/hawk.js (60 seconds)
https://www.washingtonpost.com/bandito/tests-pb/?ids=0fyKswa2IqY (60 seconds)
https://www.washingtonpost.com/pbox.php?url=https:…st&fmt=png&t=20170517a (60 seconds)
https://www.washingtonpost.com/pbox.php?url=https:…st&fmt=png&t=20170517a (60 seconds)
https://www.washingtonpost.com/wp-stat/visitorsegm…ources/build/latest.js (82 seconds)
https://www.washingtonpost.com/pb/api/v2/render/fe…ge/&outputType=default (2 minutes)
https://www.washingtonpost.com/player/prod/PoWaLoaderWapo.js (5 minutes)
https://www.washingtonpost.com/player/prod/powaBoot.js?_=2f0a499 (5 minutes)
https://www.washingtonpost.com/wp-stat/ad/zeus/wp-ad.min.js (5 minutes)
https://www.washingtonpost.com/wp-stat/advertising…dentity-retargeting.js (5 minutes)
https://www.washingtonpost.com/wp-stat/analytics/l…s?token=201710090909ET (5 minutes)
https://www.washingtonpost.com/wp-stat/pwapi/prod/…?token=201706011309EST (5 minutes)
https://www.washingtonpost.com/wp-stat/apps/national/weather/20001.json (10 minutes)
https://imasdk.googleapis.com/js/sdkloader/ima3.js (15 minutes)
https://s0.2mdn.net/instream/video/client.js (15 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://cdn.krxd.net/controltag/IbWIJ0xh.js (20 minutes)
https://cdn.krxd.net/controltag?confid=IbWIJ0xh (20 minutes)
https://connect.facebook.net/en_US/fbds.js (20 minutes)
https://js-sec.indexww.com/ht/htw-wapo.js (25.6 minutes)
https://cdn.krxd.net/userdata/get?pub=415dda7b-13b…fault.kxjsonp_userdata (30 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://js-agent.newrelic.com/nr-1044.min.js (2 hours)
https://www.washingtonpost.com/video/resources/env…/WapoVideoEmbed.min.js (24 hours)
https://www.washingtonpost.com/video/resources/js/…ndor/underscore-min.js (24 hours)
https://load77.exelator.com/pixel.gif (expiration not specified)
https://www.washingtonpost.com/wp-stat/rum/wprum.min.js (57 seconds)
https://h.parrable.com/hawk.js (60 seconds)
https://www.washingtonpost.com/bandito/tests-pb/?ids=0fyKswa2IqY (60 seconds)
https://www.washingtonpost.com/pbox.php?url=https:…st&fmt=png&t=20170517a (60 seconds)
https://www.washingtonpost.com/pbox.php?url=https:…st&fmt=png&t=20170517a (60 seconds)
https://www.washingtonpost.com/wp-stat/visitorsegm…ources/build/latest.js (82 seconds)
https://www.washingtonpost.com/pb/api/v2/render/fe…ge/&outputType=default (2 minutes)
https://www.washingtonpost.com/player/prod/PoWaLoaderWapo.js (5 minutes)
https://www.washingtonpost.com/player/prod/powaBoot.js?_=2f0a499 (5 minutes)
https://www.washingtonpost.com/wp-stat/ad/zeus/wp-ad.min.js (5 minutes)
https://www.washingtonpost.com/wp-stat/advertising…dentity-retargeting.js (5 minutes)
https://www.washingtonpost.com/wp-stat/analytics/l…s?token=201710090909ET (5 minutes)
https://www.washingtonpost.com/wp-stat/pwapi/prod/…?token=201706011309EST (5 minutes)
https://www.washingtonpost.com/wp-stat/apps/national/weather/20001.json (10 minutes)
https://imasdk.googleapis.com/js/sdkloader/ima3.js (15 minutes)
https://s0.2mdn.net/instream/video/client.js (15 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://cdn.krxd.net/controltag/IbWIJ0xh.js (20 minutes)
https://cdn.krxd.net/controltag?confid=IbWIJ0xh (20 minutes)
https://connect.facebook.net/en_US/fbds.js (20 minutes)
https://js-sec.indexww.com/ht/htw-wapo.js (25.6 minutes)
https://cdn.krxd.net/userdata/get?pub=415dda7b-13b…fault.kxjsonp_userdata (30 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://js-agent.newrelic.com/nr-1044.min.js (2 hours)
https://www.washingtonpost.com/video/resources/env…/WapoVideoEmbed.min.js (24 hours)
https://www.washingtonpost.com/video/resources/js/…ndor/underscore-min.js (24 hours)
priority - 10Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 5 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://www.washingtonpost.com/pb/gr/c/default/rgW…/4697e08d36.js?_=444ae
https://www.washingtonpost.com/pb/resources/js/head.min.js
https://www.washingtonpost.com/pb/gr/c/default/rgW…/ecae3e7968.js?_=b9e93
https://www.washingtonpost.com/pb/gr/c/default/rgW…/70b9918770.js?_=64058
https://www.washingtonpost.com/pb/gr/p/default/rgW…e8P2Iq/head.js?_=83f49
https://www.washingtonpost.com/pb/resources/js/head.min.js
https://www.washingtonpost.com/pb/gr/c/default/rgW…/ecae3e7968.js?_=b9e93
https://www.washingtonpost.com/pb/gr/c/default/rgW…/70b9918770.js?_=64058
https://www.washingtonpost.com/pb/gr/p/default/rgW…e8P2Iq/head.js?_=83f49
Optimize CSS Delivery of the following:
https://www.washingtonpost.com/pb/gr/c/default/rgW…b63f1e9c46.css?_=a0143
https://www.washingtonpost.com/pb/gr/c/default/rgW…608b8b9998.css?_=62e8e
https://www.washingtonpost.com/pb/gr/p/default/rgW…P2Iq/style.css?_=83f49
https://www.washingtonpost.com/pb/gr/c/default/rgW…938c258067.css?_=1bc9d
https://www.washingtonpost.com/pb/gr/c/default/rgW…608b8b9998.css?_=62e8e
https://www.washingtonpost.com/pb/gr/p/default/rgW…P2Iq/style.css?_=83f49
https://www.washingtonpost.com/pb/gr/c/default/rgW…938c258067.css?_=1bc9d
priority - 7Avoid 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.
http://wapo.st/
http://www.washingtonpost.com/
https://www.washingtonpost.com/
http://www.washingtonpost.com/
https://www.washingtonpost.com/
priority - 4Enable 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 40KiB (65% reduction).
Compressing https://www.washingtonpost.com/wp-stat/ad/zeus/wp-ad.min.js could save 22.6KiB (63% reduction).
Compressing https://www.washingtonpost.com/wp-stat/pwapi/prod/…?token=201706011309EST could save 13.9KiB (71% reduction).
Compressing https://www.washingtonpost.com/wp-stat/advertising…dentity-retargeting.js could save 1.5KiB (65% reduction).
Compressing https://pwapi.washingtonpost.com/?callback=jQuery3…mepage&_=1517157850542 could save 732B (63% reduction).
Compressing https://www.washingtonpost.com/wp-stat/visitorsegm…ources/build/latest.js could save 640B (52% reduction).
Compressing https://analytics.posttv.com/trending-videos-overall.json could save 485B (64% reduction).
Compressing https://s.effectivemeasure.net/d/6/p?pu=https%3A%2…7.36&ftm=false&tc=true could save 103B (35% reduction).
Compressing https://www.washingtonpost.com/wp-stat/pwapi/prod/…?token=201706011309EST could save 13.9KiB (71% reduction).
Compressing https://www.washingtonpost.com/wp-stat/advertising…dentity-retargeting.js could save 1.5KiB (65% reduction).
Compressing https://pwapi.washingtonpost.com/?callback=jQuery3…mepage&_=1517157850542 could save 732B (63% reduction).
Compressing https://www.washingtonpost.com/wp-stat/visitorsegm…ources/build/latest.js could save 640B (52% reduction).
Compressing https://analytics.posttv.com/trending-videos-overall.json could save 485B (64% reduction).
Compressing https://s.effectivemeasure.net/d/6/p?pu=https%3A%2…7.36&ftm=false&tc=true could save 103B (35% reduction).
priority - 2Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 18.3KiB (69% reduction).
Compressing https://tpc.googlesyndication.com/simgad/5187246763492505524 could save 15.7KiB (70% reduction).
Compressing https://www.washingtonpost.com/pbox.php?url=https:…st&fmt=png&t=20170517a could save 1KiB (93% reduction).
Compressing https://www.washingtonpost.com/pbox.php?url=https:…st&fmt=png&t=20170517a could save 1KiB (93% reduction).
Compressing https://www.washingtonpost.com/wp-apps/imrs.php?sr…&w=60&h=60&t=20170517a could save 562B (28% reduction).
Compressing https://www.washingtonpost.com/pbox.php?url=https:…st&fmt=png&t=20170517a could save 1KiB (93% reduction).
Compressing https://www.washingtonpost.com/pbox.php?url=https:…st&fmt=png&t=20170517a could save 1KiB (93% reduction).
Compressing https://www.washingtonpost.com/wp-apps/imrs.php?sr…&w=60&h=60&t=20170517a could save 562B (28% reduction).
priority - 0Minify 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 1.6KiB (36% reduction).
Minifying https://www.washingtonpost.com/wp-stat/advertising…dentity-retargeting.js could save 901B (38% reduction).
Minifying https://connect.facebook.net/en_US/fbds.js could save 691B (33% reduction) after compression.
Minifying https://connect.facebook.net/en_US/fbds.js could save 691B (33% reduction) after compression.
wapo.st Desktop Resource Breakdown
| Total Resources | 234 |
| Number of Hosts | 65 |
| Static Resources | 99 |
| JavaScript Resources | 86 |
| CSS Resources | 5 |
wapo.st mobile page speed rank
Last tested: 2017-05-30
Mobile Speed
Bad
51/100
wapo.st Mobile Speed Test Quick Summary
priority - 48Eliminate 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.
Remove render-blocking JavaScript:
https://www.washingtonpost.com/pb/gr/c/mobile-home…/4697e08d36.js?_=229be
https://www.washingtonpost.com/pb/resources/js/head.min.js
https://www.washingtonpost.com/pb/gr/c/mobile-home…/ecae3e7968.js?_=b9e93
https://www.washingtonpost.com/pb/gr/c/mobile-home…/70b9918770.js?_=64058
https://www.washingtonpost.com/pb/gr/p/mobile-home…yMkalq/head.js?_=cf9a5
https://www.washingtonpost.com/pb/resources/js/head.min.js
https://www.washingtonpost.com/pb/gr/c/mobile-home…/ecae3e7968.js?_=b9e93
https://www.washingtonpost.com/pb/gr/c/mobile-home…/70b9918770.js?_=64058
https://www.washingtonpost.com/pb/gr/p/mobile-home…yMkalq/head.js?_=cf9a5
Optimize CSS Delivery of the following:
https://www.washingtonpost.com/pb/resources/css/la….css?_=201703221331PST
https://www.washingtonpost.com/pb/resources/css/la….css?_=201703221331PST
https://www.washingtonpost.com/pb/resources/css/la….css?_=201703221331PST
https://www.washingtonpost.com/pb/gr/c/mobile-home…9e1acbfb3f.css?_=78008
https://www.washingtonpost.com/pb/gr/p/mobile-home…kalq/style.css?_=cf9a5
https://www.washingtonpost.com/pb/gr/c/mobile-home…938c258067.css?_=874d9
https://www.washingtonpost.com/pb/resources/css/la….css?_=201703221331PST
https://www.washingtonpost.com/pb/resources/css/la….css?_=201703221331PST
https://www.washingtonpost.com/pb/gr/c/mobile-home…9e1acbfb3f.css?_=78008
https://www.washingtonpost.com/pb/gr/p/mobile-home…kalq/style.css?_=cf9a5
https://www.washingtonpost.com/pb/gr/c/mobile-home…938c258067.css?_=874d9
priority - 26Avoid 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.
http://wapo.st/
http://www.washingtonpost.com/
https://www.washingtonpost.com/
http://www.washingtonpost.com/
https://www.washingtonpost.com/
priority - 16Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 155.1KiB (20% reduction).
Compressing https://tpc.googlesyndication.com/pagead/imgad?id=…xgEQARgBMgjnygVEf4UIMw could save 34.4KiB (71% reduction).
Compressing https://img.washingtonpost.com/rf/image_1248w/2010…gn/Images/05998888.jpg could save 28.4KiB (17% reduction).
Compressing https://www.washingtonpost.com/r/2010-2019/Washing…mages/mexico017-hp.jpg could save 23.4KiB (21% reduction).
Compressing https://www.washingtonpost.com/r/2010-2019/Washing…mages/mexico009-hp.jpg could save 20.5KiB (15% reduction).
Compressing https://www.washingtonpost.com/r/2010-2019/Washing…mages/mexico007-hp.jpg could save 14.7KiB (13% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/20…/AP_17104164938083.jpg could save 9.8KiB (20% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/20…rd170530Trump15917.JPG could save 5.3KiB (17% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/20…-TRUMP-FBI-KUSHNER.jpg could save 5KiB (18% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/20…aly_G7_23902-b16b7.jpg could save 3.6KiB (15% reduction).
Compressing https://img.washingtonpost.com/pb/resources/img/TWPLogos-twp_black-268x.png could save 1.4KiB (19% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…ages/313954173_0-7.jpg could save 1.3KiB (21% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…Street_73260-3d05b.jpg could save 1.3KiB (19% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?sr…ROMO-01.jpg&w=138&h=92 could save 1.2KiB (22% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…gn/Images/05998888.jpg could save 1.1KiB (21% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?sr…o_IMAGE.jpg&w=138&h=92 could save 1KiB (25% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?sr…02.jpg.jpeg&w=138&h=92 could save 1KiB (19% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…ages/313916226_0-4.jpg could save 952B (21% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…USSIA-KUSHNER-2246.jpg could save 859B (21% reduction).
Compressing https://img.washingtonpost.com/rf/image_1248w/2010…gn/Images/05998888.jpg could save 28.4KiB (17% reduction).
Compressing https://www.washingtonpost.com/r/2010-2019/Washing…mages/mexico017-hp.jpg could save 23.4KiB (21% reduction).
Compressing https://www.washingtonpost.com/r/2010-2019/Washing…mages/mexico009-hp.jpg could save 20.5KiB (15% reduction).
Compressing https://www.washingtonpost.com/r/2010-2019/Washing…mages/mexico007-hp.jpg could save 14.7KiB (13% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/20…/AP_17104164938083.jpg could save 9.8KiB (20% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/20…rd170530Trump15917.JPG could save 5.3KiB (17% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/20…-TRUMP-FBI-KUSHNER.jpg could save 5KiB (18% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/20…aly_G7_23902-b16b7.jpg could save 3.6KiB (15% reduction).
Compressing https://img.washingtonpost.com/pb/resources/img/TWPLogos-twp_black-268x.png could save 1.4KiB (19% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…ages/313954173_0-7.jpg could save 1.3KiB (21% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…Street_73260-3d05b.jpg could save 1.3KiB (19% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?sr…ROMO-01.jpg&w=138&h=92 could save 1.2KiB (22% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…gn/Images/05998888.jpg could save 1.1KiB (21% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?sr…o_IMAGE.jpg&w=138&h=92 could save 1KiB (25% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?sr…02.jpg.jpeg&w=138&h=92 could save 1KiB (19% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…ages/313916226_0-4.jpg could save 952B (21% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…USSIA-KUSHNER-2246.jpg could save 859B (21% reduction).
priority - 13Leverage 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://js.washingtonpost.com/wp-stat/rum/wprum.min.js (expiration not specified)
https://js.washingtonpost.com/wp-stat/visitorsegme…ources/build/latest.js (expiration not specified)
https://www.washingtonpost.com/wp-stat/pwapi/prod/wpPwapi1-min.js (expiration not specified)
https://www.washingtonpost.com/pb/api/v2/render/fe…utType=mobile-homepage (2 minutes)
https://js.washingtonpost.com/wp-stat/analytics/la…?token=201703221331PST (5 minutes)
https://www.washingtonpost.com/wp-stat/ad/zeus/wp-ad.min.js (5 minutes)
https://www.washingtonpost.com/wp-stat/advertising…dentity-retargeting.js (5 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://cdn.krxd.net/controltag?confid=IbWIJ0xh (20 minutes)
https://js-sec.indexww.com/ht/htw-wapo.js (41.7 minutes)
http://washingtonpost-d.openx.net/w/1.0/bmr (60 minutes)
https://d2p9l91d5g68ru.cloudfront.net/LoopingVideo/LoopingVideo.min.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://js-agent.newrelic.com/nr-spa-1026.min.js (2 hours)
https://static.chartbeat.com/js/chartbeat.js (2 hours)
https://z.moatads.com/washpostdfpcw45893854/moatad.js (5.7 hours)
https://js.washingtonpost.com/video/resources/env/…/WapoVideoEmbed.min.js (24 hours)
https://js.washingtonpost.com/video/resources/js/p…ndor/underscore-min.js (24 hours)
https://js.washingtonpost.com/wp-stat/rum/wprum.min.js (expiration not specified)
https://js.washingtonpost.com/wp-stat/visitorsegme…ources/build/latest.js (expiration not specified)
https://www.washingtonpost.com/wp-stat/pwapi/prod/wpPwapi1-min.js (expiration not specified)
https://www.washingtonpost.com/pb/api/v2/render/fe…utType=mobile-homepage (2 minutes)
https://js.washingtonpost.com/wp-stat/analytics/la…?token=201703221331PST (5 minutes)
https://www.washingtonpost.com/wp-stat/ad/zeus/wp-ad.min.js (5 minutes)
https://www.washingtonpost.com/wp-stat/advertising…dentity-retargeting.js (5 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://cdn.krxd.net/controltag?confid=IbWIJ0xh (20 minutes)
https://js-sec.indexww.com/ht/htw-wapo.js (41.7 minutes)
http://washingtonpost-d.openx.net/w/1.0/bmr (60 minutes)
https://d2p9l91d5g68ru.cloudfront.net/LoopingVideo/LoopingVideo.min.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://js-agent.newrelic.com/nr-spa-1026.min.js (2 hours)
https://static.chartbeat.com/js/chartbeat.js (2 hours)
https://z.moatads.com/washpostdfpcw45893854/moatad.js (5.7 hours)
https://js.washingtonpost.com/video/resources/env/…/WapoVideoEmbed.min.js (24 hours)
https://js.washingtonpost.com/video/resources/js/p…ndor/underscore-min.js (24 hours)
priority - 2Enable 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 24.4KiB (72% reduction).
Compressing http://washingtonpost-d.openx.net/w/1.0/bmr could save 14.2KiB (67% reduction).
Compressing https://mongo-good-server.ext.nile.works/test-stat…FAog9lq3-c%22%5D%7D%7D could save 9.6KiB (81% reduction).
Compressing https://pwapi.washingtonpost.com/?callback=jQuery3…mepage&_=1496197988453 could save 618B (65% reduction).
Compressing https://mongo-good-server.ext.nile.works/test-stat…FAog9lq3-c%22%5D%7D%7D could save 9.6KiB (81% reduction).
Compressing https://pwapi.washingtonpost.com/?callback=jQuery3…mepage&_=1496197988453 could save 618B (65% reduction).
priority - 1Minify 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 14.1KiB (22% reduction).
Minifying https://js.washingtonpost.com/wp-stat/analytics/la…?token=201703221331PST could save 9.6KiB (19% reduction) after compression.
Minifying https://www.washingtonpost.com/pb/gr/c/mobile-home…/c4d7fa1f35.js?_=2f318 could save 4.5KiB (34% reduction) after compression.
Minifying https://www.washingtonpost.com/pb/gr/c/mobile-home…/c4d7fa1f35.js?_=2f318 could save 4.5KiB (34% reduction) after compression.
wapo.st Mobile Resource Breakdown
| Total Resources | 121 |
| Number of Hosts | 35 |
| Static Resources | 74 |
| JavaScript Resources | 59 |
| CSS Resources | 6 |
wapo.st mobile page usability
Last tested: 2017-05-30
Mobile Usability
Good
99/100
wapo.st 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.
The tap target
<a href="https://www.wa…hael-birnbaum/">Michael Birnbaum</a> and 7 others are close to other tap targets.The tap target
<a href="https://www.wa…ues-continues/" class="">An artist hate…is at her feet</a> and 1 others are close to other tap targets.wapo.st HTML validation
NON-DOCUMENT-ERROR
Read timed out
Line: Column: -
"......"
"......"
wapo.st similar domains
Similar domains:
www.wapo.com
www.wapo.net
www.wapo.org
www.wapo.info
www.wapo.biz
www.wapo.us
www.wapo.mobi
www.apo.st
www.wapo.st
www.qapo.st
www.wqapo.st
www.qwapo.st
www.aapo.st
www.waapo.st
www.awapo.st
www.sapo.st
www.wsapo.st
www.swapo.st
www.eapo.st
www.weapo.st
www.ewapo.st
www.wpo.st
www.wqpo.st
www.waqpo.st
www.wwpo.st
www.wawpo.st
www.wwapo.st
www.wspo.st
www.waspo.st
www.wzpo.st
www.wazpo.st
www.wzapo.st
www.wao.st
www.waoo.st
www.wapoo.st
www.waopo.st
www.walo.st
www.waplo.st
www.walpo.st
www.wap.st
www.wapi.st
www.wapoi.st
www.wapio.st
www.wapk.st
www.wapok.st
www.wapko.st
www.wapl.st
www.wapol.st
www.wapp.st
www.wapop.st
www.wappo.st
www.wapo.net
www.wapo.org
www.wapo.info
www.wapo.biz
www.wapo.us
www.wapo.mobi
www.apo.st
www.wapo.st
www.qapo.st
www.wqapo.st
www.qwapo.st
www.aapo.st
www.waapo.st
www.awapo.st
www.sapo.st
www.wsapo.st
www.swapo.st
www.eapo.st
www.weapo.st
www.ewapo.st
www.wpo.st
www.wqpo.st
www.waqpo.st
www.wwpo.st
www.wawpo.st
www.wwapo.st
www.wspo.st
www.waspo.st
www.wzpo.st
www.wazpo.st
www.wzapo.st
www.wao.st
www.waoo.st
www.wapoo.st
www.waopo.st
www.walo.st
www.waplo.st
www.walpo.st
www.wap.st
www.wapi.st
www.wapoi.st
www.wapio.st
www.wapk.st
www.wapok.st
www.wapko.st
www.wapl.st
www.wapol.st
www.wapp.st
www.wapop.st
www.wappo.st
wapo.st 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.
wapo.st 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.