washingtonpost.com Washington Post: Breaking News, World, US, DC News & Analysis - The Washington Post

Mobile Usability

99/100

Good

Mobile Speed

61/100

Bad

Last tested: 2017-08-27

Rescan
washingtonpost.com Mobile Usability: 99/100
washingtonpost.com Mobile Usability Test Quick Overview

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.wa…hael-birnbaum/">Michael Birnbaum</a> and 10 others are close to other tap targets.
The tap target <a href="https://www.wa…393_story.html"></a> is close to 1 other tap targets.
The tap target <a href="https://www.wa…393_story.html" class="">A political bo…leon Bonaparte</a> and 2 others are close to other tap targets.
The tap target <a href="https://www.wa…rolyn-johnson/">Carolyn Y. Johnson</a> is close to 1 other tap targets.
The tap target <a href="https://www.wa…alth-care-act/" class="">Fact Checker:…ealth Care Act</a> and 3 others are close to other tap targets.
The tap target <a id="aw0" href="https://google…/%3Fkeyword%3D"></a> is close to 2 other tap targets.
washingtonpost.com Mobile Speed: 61/100
washingtonpost.com Mobile Speed Test Quick Overview

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.
https://www.washingtonpost.com/pb/gr/c/mobile-home…/b1811100e1.js?_=c2f5a
https://www.washingtonpost.com/pb/resources/js/head.min.js
https://www.washingtonpost.com/pb/gr/c/mobile-home…/95f829e22e.js?_=ed3f2
https://www.washingtonpost.com/pb/gr/c/mobile-home…/70b9918770.js?_=64058
https://www.washingtonpost.com/pb/gr/p/mobile-home…EYi2jq/head.js?_=1a2c1
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?_=242c9
https://www.washingtonpost.com/pb/gr/p/mobile-home…i2jq/style.css?_=1a2c1
https://www.washingtonpost.com/pb/gr/c/mobile-home…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/visitorsegme…ources/build/latest.js (expiration not specified)
https://www.washingtonpost.com/wp-stat/ad/loaders/…t/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/analytics/la…?token=201703221331PST (5 minutes)
https://www.washingtonpost.com/wp-stat/advertising…dentity-retargeting.js (5 minutes)
https://www.washingtonpost.com/wp-stat/advertising/subscribe.png (5 minutes)
https://js-sec.indexww.com/ht/htw-wapo.js (14 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-spa-1026.min.js (2 hours)
https://static.chartbeat.com/js/chartbeat.js (2 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)
Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 64.4KiB (18% reduction).
Compressing https://img.washingtonpost.com/rf/image_1248w/2010…ges/AFP_O702B-4806.jpg could save 39KiB (17% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/20…n/Images/668169314.jpg could save 7KiB (19% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/20…s/crop_90680289290.jpg could save 4.5KiB (16% reduction).
Compressing https://img.washingtonpost.com/rf/image_480x320/20…ergency_Center0903.jpg could save 3.5KiB (16% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…s/Images/AFP_O679N.jpg could save 1.8KiB (24% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?sr…MAGE_v1.jpg&w=138&h=92 could save 1.7KiB (21% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…_Texas_29335-9c02f.jpg could save 1.5KiB (22% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?sr…0119286.jpg&w=138&h=92 could save 1.4KiB (19% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…n/Images/668169314.jpg could save 1.2KiB (20% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?sr…eaddocs.jpg&w=138&h=92 could save 1KiB (21% reduction).
Compressing https://img.washingtonpost.com/rf/image_138x92/201…gn/Images/05950349.jpg could save 1,006B (20% reduction).
Compressing https://img.washingtonpost.com/wp-apps/imrs.php?sr…Promo_1.jpg&w=138&h=92 could save 857B (22% reduction).
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 9.7KiB (20% reduction).
Minifying https://js.washingtonpost.com/wp-stat/analytics/la…?token=201703221331PST could save 9.7KiB (20% reduction) after compression.
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 517B (64% reduction).
Compressing https://pwapi.washingtonpost.com/?callback=jQuery3…mepage&_=1494247198996 could save 517B (64% reduction).

washingtonpost.com Mobile Resources


Total Resources120
Number of Hosts35
Static Resources73
JavaScript Resources56
CSS Resources7

washingtonpost.com Mobile Resource Breakdown