nytimes.com The New York Times

Mobile Usability



Mobile Speed



Last tested: 2017-08-27

nytimes.com Mobile Usability: 99/100
nytimes.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 <div id="header-login" class="header-login">SubscribeorMy accountLog in</div> is close to 1 other tap targets.
The tap target <div id="header-login" class="header-login">SubscribeorMy accountLog in</div> and 1 others are close to other tap targets.
The tap target <div id="header-login" class="header-login">SubscribeorMy accountLog in</div> and 1 others are close to other tap targets.
The tap target <a href="https://myacco…253Dsaved-card" class="saved-tout">Save</a> and 1 others are close to other tap targets.
The tap target <a href="/" class="active">Home</a> and 16 others are close to other tap targets.
The tap target <a href="http://www.nyt…F%3Freferer%3D">Subscribe</a> and 2 others are close to other tap targets.
The tap target <a href="http://www.nyt…ml?nytmobile=0">© 2017</a> is close to 1 other tap targets.
nytimes.com Mobile Speed: 45/100
nytimes.com Mobile Speed Test Quick Overview

Avoid landing page redirects

Your page has 3 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
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://et.nytimes.com/ (expiration not specified)
https://load.s3.amazonaws.com/pixel.gif (expiration not specified)
https://s.yimg.com/wi/ytc.js (expiration not specified)
https://web-player.art19.com/assets/art19-logo-dar…01e33c5094b6c21dae.png (expiration not specified)
https://www.nytimes.com/svc/video/api/v3/video/100000005035684 (expiration not specified)
https://www.nytimes.com/svc/video/api/v3/video/100000005076753 (expiration not specified)
https://www.nytimes.com/svc/video/api/v3/video/100000005078300 (expiration not specified)
https://static01.nyt.com/packages/html/mobile/2017…player-template.min.js (5 minutes)
https://static01.nyt.com/packages/html/mobile/2017…t-micro-player.min.css (5 minutes)
https://static01.nyt.com/services/json/taxonomy/v2…k=jsonTaxonomyCallback (10 minutes)
https://imasdk.googleapis.com/js/sdkloader/ima3.js (15 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://cdn.krxd.net/controltag/HrUwtkcl.js (20 minutes)
https://cdn.krxd.net/controltag/IquZvfNl.js (20 minutes)
https://cdn.krxd.net/controltag?confid=IquZvfNl (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/100468016962764?v=2.7.6 (20 minutes)
https://connect.facebook.net/signals/config/592202027582499?v=2.7.6 (20 minutes)
https://beacon.krxd.net/cookie2json?callback=Krux.…fault.kxjsonp_3pevents (30 minutes)
https://cdn.krxd.net/userdata/get?pub=79816aa8-435…fault.kxjsonp_userdata (30 minutes)
https://contextual.media.net/bidexchange.js?cid=8CULO58R6&https=1 (30 minutes)
https://secure-assets.rubiconproject.com/utils/xapi/multi-sync.js?&cs=1 (93 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://z.moatads.com/googleessencenyt485873431/mo…me_bsg=0&referral_bsg= (7.2 hours)
Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 66% of the final above-the-fold content could be rendered with the full HTML response.
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 107.8KiB (74% reduction).
Compressing https://79423.analytics.edgekey.net/html5/akamaihtml5-min.js could save 91.4KiB (73% reduction).
Compressing https://rec.api.nytimes.com/svc/recommendations/v4…&loc=mobileweb&limit=3 could save 16.5KiB (79% reduction).
Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 76.7KiB (25% reduction).
Compressing https://static01.nyt.com/images/2017/05/03/world/3…hanimage-square640.jpg could save 31.7KiB (26% reduction).
Compressing https://static01.nyt.com/images/2017/05/08/world/3…ON-VIDEO-square640.jpg could save 19KiB (26% reduction).
Compressing https://cdn1.nyt.com/images/2017/05/09/world/08USB…cron1-articleLarge.jpg could save 11.6KiB (27% reduction).
Compressing https://cdn1.nyt.com/images/2017/05/08/world/Jp-FR…RANCE-articleLarge.jpg could save 4.1KiB (16% reduction).
Compressing https://static01.nyt.com/images/2017/01/29/podcast…lbum-art-master315.jpg could save 3.4KiB (30% reduction).
Compressing https://cdn1.nyt.com/images/2017/05/03/world/360-a…animage-thumbLarge.jpg could save 2.4KiB (22% reduction).
Compressing https://cdn1.nyt.com/images/2017/05/08/world/360-M…N-VIDEO-thumbLarge.jpg could save 1.8KiB (22% reduction).
Compressing https://static01.nyt.com/images/2017/05/07/world/e…-thumbStandard-v14.png could save 1.2KiB (11% reduction).
Compressing https://contextual.media.net/cksync.php?cs=1&vsid=…40af-1b31-a386018fbcde could save 742B (91% reduction).
Compressing https://qsearch-a.akamaihd.net/log?logid=prlog&dn=…%2F%3Freferer%3D&kwrf= could save 739B (91% 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 12.7KiB (23% reduction).
Minifying https://tagx.nytimes.com/?url=https%3A%2F%2Fwww.ny…_buster_=1494243485540 could save 3.9KiB (20% reduction) after compression.
Minifying https://tagx.nytimes.com/?url=https%3A%2F%2Fmobile…484839&_=1494243484753 could save 3.3KiB (21% reduction) after compression.
Minifying https://static01.nyt.com/bi/js/analytics/EventTracker.js could save 2.1KiB (30% reduction) after compression.
Minifying https://static01.nyt.com/bi/js/analytics/EventTracker.js?_=1494243484754 could save 2.1KiB (30% reduction) after compression.
Minifying https://dc8xl0ndzn2cb.cloudfront.net/js/nytimes/v1/keywee.js could save 1.3KiB (23% reduction) after compression.
Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 862B (11% reduction).
Minifying https://tap-secure.rubiconproject.com/partner/scri…l?rtb_ext=1&geo=&co=US could save 862B (11% reduction) after compression.

nytimes.com Mobile Resources

Total Resources214
Number of Hosts71
Static Resources74
JavaScript Resources75
CSS Resources6

nytimes.com Mobile Resource Breakdown