Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/video/hlsfmp4/2026/04/02/165188_1_03vid-iowa-farmer-war_...	60.0 s	4.8 MiB
/video/hlsfmp4/2026/04/02/165188_1_03vid-iowa-farmer-war_...	60.0 s	3.9 MiB
/video/hlsfmp4/2026/04/03/166086_1_03vid-jet-search-and-r...	60.0 s	3.7 MiB
/video/hlsfmp4/2026/04/03/166086_1_03vid-jet-search-and-r...	60.0 s	3.6 MiB
/js/tags/clientag.js?cid=8CU26C87G&dn=www.nytimes.com&yse...	1800.0 s	193.0 KiB
/images/2026/03/31/arts/SOTW_BTS/SOTW_BTS-verticalTwoByTh...	604800.0 s	787.3 KiB
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	90.0 KiB
/images/2026/02/20/world/africa/RV_Thumbnail-John-Cape-To...	604800.0 s	700.9 KiB
/images/2026/03/23/smarter-living/wirecutter/THMB_260316_...	604800.0 s	526.9 KiB
/images/2026/05/01/arts/Screenshot-2026-04-02-at-10/Scree...	604800.0 s	519.7 KiB
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	14400.0 s	58.3 KiB
dd.nytimes.com/tags.js	3600.0 s	43.3 KiB
static.nytimes.com/assets-oma/images/devices.png	0.0 ms	18.5 KiB
/scripts/bundle/65568.js?sid=4486dfe2-780e-4dfa-a60a-2a94...	3600.0 s	20.4 KiB
/images/2026/04/03/multimedia/03israel-iran-tehran-voices...	604800.0 s	135.8 KiB
/images/2023/02/13/multimedia/afg-chicken-with-salmorigli...	604800.0 s	133.5 KiB
static.chartbeat.com/js/chartbeat_video.js	86400.0 s	24.8 KiB
a1.nyt.com/analytics/comscore-streaming.js	86400.0 s	18.8 KiB
static.nytimes.com/assets-oma/images/the-new-york-times.svg	0.0 ms	6.5 KiB
/images/2026/03/31/multimedia/00int-deportations-1-vtpw-H...	604800.0 s	57.4 KiB
eus.rubiconproject.com/usync.js	59868.0 s	11.5 KiB
rumcdn.geoedge.be/b3960cc6-bfd2-4adc-910c-6e917e8a6a0e/grumi-ip.js	14400.0 s	7.1 KiB
cdn.brandmetrics.com/tag/85a1ebf79602421aa1c2c2f24d32cb6c/nyt.js	3600.0 s	3.9 KiB
sb.scorecardresearch.com/internal-cs/default/beacon-and.js	86400.0 s	7.8 KiB
/video/hlsfmp4/2026/04/02/165188_1_03vid-iowa-farmer-war_...	60.0 s	2.5 KiB
/9fab0bf6-df63-42ca-acc5-caf4de668f40/launchpad-liveramp.js	0.0 ms	1.7 KiB
/video/hlsfmp4/2026/04/03/166086_1_03vid-jet-search-and-r...	60.0 s	1.1 KiB
/images/2026/04/16/video/165188_03vid-arkansas-farmer-war...	604800.0 s	8.0 KiB
platform.iteratehq.com/loader.js	1800.0 s	935 B
config.aps.amazon-adsystem.com/configs/3030	3600.0 s	990 B
/images/2026/04/03/multimedia/03israel-iran-F15-explainer...	604800.0 s	7.5 KiB
/images/2019/12/13/reader-center/author-eileen-sullivan/a...	604800.0 s	5.5 KiB
/c.js?siteid=4486dfe2-780e-4dfa-a60a-2a948887658f&toploc=...	0.0 ms	296 B
a1.nyt.com/analytics/show-ads.js	86400.0 s	385 B
cdn.indexww.com/ht/htw-pixel.gif?0	86400.0 s	223 B
/images/2026/04/16/video/165188_03vid-arkansas-farmer-war...	604800.0 s	382 B

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:120.155 source:map[column:22667 line:1 type:source-location url:https://static01.nyt.com/video-static/betamax/player-UG6pU0z7.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:121.977 source:map[column:19922 line:0 type:source-location url:https://static01.nyt.com/video-static/betamax/player-UG6pU0z7.js urlProvider:network]] map[reflowTime:3.5 source:map[column:47594 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202603310101/pubads_impl.js urlProvider:network]] map[reflowTime:53.112 source:map[type:text value:[unattributed]]] map[reflowTime:30.645 source:map[column:1851 line:0 type:source-location url:https://static01.nyt.com/video-static/betamax/pool-0.2.39-Dzy2PfXr.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/02/20/world/africa/RV_Thumbnail-John-Cape-To...	700.1 KiB	686.0 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/03/23/smarter-living/wirecutter/THMB_260316_...	526.2 KiB	512.0 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/05/01/arts/Screenshot-2026-04-02-at-10/Scree...	518.3 KiB	504.2 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2023/02/13/multimedia/afg-chicken-with-salmorigli...	132.4 KiB	118.2 KiB
People move among debris and the ruins of several multistory buildings against … `div > div.css-ax1e1o > picture.css-hdqqnp > img.css-o9w048`	/images/2026/04/03/multimedia/03israel-iran-tehran-voices...	135.3 KiB	101.5 KiB
President Trump gestures as he talks to Secretary of State Marco Rubio and the … `div > div.css-hjiaw4 > picture.css-hdqqnp > img.css-yf0ys`	/images/2026/03/31/multimedia/00int-deportations-1-vtpw-H...	56.9 KiB	37.7 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/04/16/video/165188_03vid-arkansas-farmer-war...	7.1 KiB	4.5 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:336.039 label:Time to first byte subpart:timeToFirstByte] map[duration:2182.749 label:Element render delay subpart:elementRenderDelay]]

lhId: page-7-P

nodeLabel: U.S. Searches for Missing Airman as Trump Repeats Threats Over Strait

path: 1,HTML,1,BODY,2,DIV,2,DIV,1,DIV,0,MAIN,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,1,DIV,0,DIV,1,DIV,0,A,0,DIV,0,P

selector: div.css-cfnhvx > a.tpl-lbl > div.css-xdandi > p.indicate-hover

snippet: <p class="indicate-hover css-1l9mhqb">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
g1.nyt.com/fonts/css/web-fonts.c851560786173ad206e1f76c1901be7e096e8f8b.css	6.8 KiB	939 ms
g1.nyt.com/fonts/css/web-fonts.css	6.8 KiB
/vi-assets/static-assets/cssModulesStyles-39f3b9296e42fd6...	49.1 KiB	918 ms
/vi-assets/static-assets/global-bf55b3b62e74478ad48892213...	3.8 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 180 ms 96.9 KiB

URL	Transfer Size	Est Savings
.css-1pg5jir { max-width: calc(100% - 40px); margin: auto; } …	50.2 KiB	49.8 KiB
/vi-assets/static-assets/cssModulesStyles-39f3b9296e42fd6...	47.5 KiB	47.0 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 6.2 s 1.4 MiB

URL	Transfer Size	Est Savings
www.nytimes.com/vi-assets/static-assets/main-a199ce4d0aae1f18e1f1.js	921.1 KiB	397.2 KiB
www.nytimes.com/vi-assets/static-assets/home-ea23c461835fcbe6fad1.js	454.3 KiB	200.0 KiB
static01.nyt.com/video-static/betamax/hlsjs-CLmy88XX.js	146.2 KiB	139.6 KiB
/pagead/managed/js/gpt/m202603310101/pubads_impl.js	182.4 KiB	129.5 KiB
www.nytimes.com/vi-assets/static-assets/vendor-a174c85d4d9cb7e7c988.js	105.8 KiB	91.0 KiB
/gtm.js?id=GTM-P528B3&gtm_auth=tfAzqo1rYDLgYhmTnSjPqw&gtm...	190.0 KiB	69.9 KiB
/js/tags/clientag.js?cid=8CU26C87G&dn=www.nytimes.com&yse...	192.8 KiB	69.8 KiB
accounts.google.com/gsi/client	92.6 KiB	69.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-N5P6T9S&gtm=4e6411	116.8 KiB	63.6 KiB
www.googletagmanager.com/gtag/destination?id=DC-5290727&cx=c&gtm=4e6411	130.3 KiB	60.4 KiB
c.amazon-adsystem.com/aax2/apstag.js	89.6 KiB	36.4 KiB
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	57.9 KiB	29.0 KiB
pay.google.com/gp/p/js/pay.js	57.3 KiB	24.7 KiB
securepubads.g.doubleclick.net/tag/js/gpt.js	34.2 KiB	23.9 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
www.nytimes.com/vi-assets/static-assets/main-a199ce4d0aae1f18e1f1.js	12.2 s	9.8 s	467 ms
Unattributable	3.0 s	413 ms	0.0 ms
www.nytimes.com/	2.3 s	594 ms	165 ms
static01.nyt.com/video-static/betamax/betamax-shared-sTKBl65Y.js	2.1 s	1.6 s	0.4 ms
www.nytimes.com/vi-assets/static-assets/adslot-4321ed7379557de6ae06.js	1.7 s	1.4 s	3.9 ms
/js/tags/clientag.js?cid=8CU26C87G&dn=www.nytimes.com&yse...	1.1 s	931 ms	79 ms
/gtm.js?id=GTM-P528B3&gtm_auth=tfAzqo1rYDLgYhmTnSjPqw&gtm...	1.1 s	763 ms	122 ms
/vi-assets/static-assets/vendors~audio~byline~capsule~car...	842 ms	782 ms	11 ms
static01.nyt.com/video-static/betamax/video-element-lQZyLhgl.js	673 ms	494 ms	6.8 ms
static01.nyt.com/video-static/betamax/player-UG6pU0z7.js	662 ms	144 ms	4.0 ms
dd.nytimes.com/tags.js	400 ms	340 ms	16 ms
/pagead/managed/js/gpt/m202603310101/pubads_impl.js	336 ms	192 ms	74 ms
www.googletagmanager.com/gtag/destination?id=DC-5290727&cx=c&gtm=4e6411	332 ms	281 ms	48 ms
www.nytimes.com/vi-assets/static-assets/home-ea23c461835fcbe6fad1.js	300 ms	43 ms	215 ms
c.amazon-adsystem.com/aax2/apstag.js	275 ms	216 ms	47 ms
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	253 ms	223 ms	22 ms
static.chartbeat.com/js/chartbeat_video.js	194 ms	133 ms	9.7 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	170 ms	117 ms	50 ms
rumcdn.geoedge.be/b3960cc6-bfd2-4adc-910c-6e917e8a6a0e/grumi.js	168 ms	87 ms	80 ms
www.googletagmanager.com/gtm.js?id=GTM-N5P6T9S&gtm=4e6411	104 ms	59 ms	45 ms
/scripts/bundle/65568.js?sid=4486dfe2-780e-4dfa-a60a-2a94...	87 ms	73 ms	9.8 ms
launchpad.privacymanager.io/latest/launchpad.bundle.js	85 ms	60 ms	24 ms
accounts.google.com/gsi/client	84 ms	35 ms	35 ms
pay.google.com/gp/p/js/pay.js	70 ms	43 ms	26 ms
rumcdn.geoedge.be/b3960cc6-bfd2-4adc-910c-6e917e8a6a0e/grumi-ip.js	68 ms	52 ms	3.0 ms
platform.iteratehq.com/match-prod-b1f8cece5e4f2a8d3b80.js	59 ms	48 ms	10.0 ms
/9fab0bf6-df63-42ca-acc5-caf4de668f40/launchpad-liveramp.js	57 ms	54 ms	0.7 ms
www.nytimes.com/vi-assets/static-assets/vendor-a174c85d4d9cb7e7c988.js	54 ms	2.4 ms	52 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	19.1 s
Other	5.0 s
Script Parsing & Compilation	1.7 s
Style & Layout	1.5 s
Garbage Collection	734 ms
Parse HTML & CSS	577 ms
Rendering	463 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
The page has an unload handler in the main frame.	Actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.5 KiB

URL	Transfer Size	Est Savings
.css-1pg5jir { max-width: calc(100% - 40px); margin: auto; } …	50.2 KiB	5.5 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 14.2 KiB

URL	Transfer Size	Est Savings
launchpad.privacymanager.io/latest/launchpad.bundle.js	45.0 KiB	14.2 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/video/hlsfmp4/2026/04/02/165188_1_03vid-iowa-farmer-war_...	4.8 MiB
/video/hlsfmp4/2026/04/02/165188_1_03vid-iowa-farmer-war_...	3.9 MiB
/video/hlsfmp4/2026/04/03/166086_1_03vid-jet-search-and-r...	3.7 MiB
/video/hlsfmp4/2026/04/03/166086_1_03vid-jet-search-and-r...	3.6 MiB
www.nytimes.com/vi-assets/static-assets/main-a199ce4d0aae1f18e1f1.js	923.5 KiB
/images/2026/03/31/arts/SOTW_BTS/SOTW_BTS-verticalTwoByTh...	787.3 KiB
/images/2026/02/20/world/africa/RV_Thumbnail-John-Cape-To...	700.9 KiB
/images/2026/03/23/smarter-living/wirecutter/THMB_260316_...	526.9 KiB
/images/2026/05/01/arts/Screenshot-2026-04-02-at-10/Scree...	519.7 KiB
www.nytimes.com/vi-assets/static-assets/home-ea23c461835fcbe6fad1.js	455.9 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Modern HTTP

●Optimize viewport for mobile

●User Timing marks and measures 31 user timings

●Avoid long main-thread tasks 20 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 250 ms

●Server Backend Latencies 320 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 220 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
timeline `div._container_gk23c_16 > div._scrubber_19d53_1 > div._track_19d53_28`

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
seek `div._container_gk23c_16 > div._scrubber_19d53_1 > div._track_19d53_28 > div._ariaPlaceholder_19d53_152`

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div._container_gk23c_16 > div._scrubber_19d53_1 > div._track_19d53_28 > div._progressHandle_19d53_80 `div._container_gk23c_16 > div._scrubber_19d53_1 > div._track_19d53_28 > div._progressHandle_19d53_80`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
img._poster_13tnt_20 `img._poster_13tnt_20`
img._poster_13tnt_20 `img._poster_13tnt_20`
img._poster_13tnt_20 `img._poster_13tnt_20`
img._poster_13tnt_20 `img._poster_13tnt_20`
img._poster_13tnt_20 `img._poster_13tnt_20`
img._poster_13tnt_20 `img._poster_13tnt_20`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`
ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR `ol.carousel-ol > li.kyt-SgEEq > figure > a.kyt-tdFHR`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NYTCo `nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6`
Contact Us `nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6`
Accessibility `nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6`
Work with us `nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6`
Advertise `nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6`
T Brand Studio `nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6`
Privacy Policy `nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6`
Cookie Policy `nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6`
Terms of Service `nav#footer > ul.css-t8x4fj > li.css-a7htku > a.css-jq1cx6`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	www.nytimes.com/vi-assets/static-assets/adslot-4321ed7379557de6ae06.js
Topics	/js/tags/clientag.js?cid=8CU26C87G&dn=www.nytimes.com&yse... line 34, col 34324

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	`[GSI_LOGGER]: FedCM get() rejects with NetworkError: Error retrieving a token.`
/video/2026/04/03/166086_1_03vid-jet-search-and-rescue_wg...	`Failed to load resource: the server responded with a status of 404 ()`
www.nytimes.com/	`Not signed in with the identity provider.`
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	`UserInfoAgentID unavailable.`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.nytimes.com/2026/03/12/business/war-iran-farmers-agriculture-costs.html	Read more

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
img._poster_13tnt_20 `img._poster_13tnt_20`
img._poster_13tnt_20 `img._poster_13tnt_20`
img._poster_13tnt_20 `img._poster_13tnt_20`
img._poster_13tnt_20 `img._poster_13tnt_20`
img._poster_13tnt_20 `img._poster_13tnt_20`
img._poster_13tnt_20 `img._poster_13tnt_20`

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`
div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl `div > div.css-1wzkfo3 > div.css-cfnhvx > a.tpl-lbl`

To appear in search results, crawlers need access to your app.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`