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
/assets-oma/images/welcomead_bandit_25Q4_download_trio_la...	0.0 ms	590.2 KiB
/js/tags/clientag.js?cid=8CU26C87G&dn=www.nytimes.com&yse...	1800.0 s	193.5 KiB
/vi-assets/static-assets/fides-1182b3743d46b6ae880fe21733...	0.0 ms	101.2 KiB
/images/2026/05/08/us/politics/trump-v-pope/trump-v-pope-...	604800.0 s	527.8 KiB
/images/2026/05/06/arts/TO_FRENCH_GORSUCH_thumb-cover/TO_...	604800.0 s	526.1 KiB
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	14400.0 s	59.2 KiB
dd.nytimes.com/tags.js	3600.0 s	39.2 KiB
/images/2018/08/24/multimedia/author-jonathan-wolfe/autho...	604800.0 s	311.3 KiB
/images/2026/04/02/multimedia/AS-Creamy-Cottage-Cheese-Ba...	604800.0 s	111.7 KiB
/images/2026/05/09/multimedia/09int-russia-victory-day-qz...	604800.0 s	65.7 KiB
/images/2026/05/09/business/09biz-fcc-view-1/09biz-fcc-vi...	604800.0 s	56.5 KiB
rumcdn.geoedge.be/b3960cc6-bfd2-4adc-910c-6e917e8a6a0e/grumi-ip.js	14400.0 s	7.3 KiB
/images/2026/05/08/multimedia/08live-ukelection-header-kg...	604800.0 s	31.8 KiB
/images/2026/05/07/multimedia/07nat-tenn-redistricting-tl...	604800.0 s	30.0 KiB
/images/2026/04/29/multimedia/00int-china-xi-military-01-...	604800.0 s	23.1 KiB
/images/2026/05/08/world/middleeast/aric-still/aric-still...	604800.0 s	16.2 KiB
/images/2026/05/07/arts/HORIZONTAL_3x2-29/HORIZONTAL_3x2-...	604800.0 s	9.2 KiB
/images/2026/05/07/magazine/17mag-interview-sethi-homepag...	604800.0 s	6.5 KiB
a1.nyt.com/analytics/show-ads.js	86400.0 s	677 B
/video/2026/05/07/168921_1_17mag-interview-sethi-homepage...	60.0 s	119 B
/video/2026/05/07/168921_1_17mag-interview-sethi-homepage...	60.0 s	0 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.000233] map[node:map[boundingRect:map[bottom:692 height:12 left:169 right:392 top:680 width:223] lhId:page-5-SPAN nodeLabel:Pedro Pardo/Agence France-Presse — Getty Images path:1,HTML,1,BODY,3,DIV,3,DIV,1,DIV,0,MAIN,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,DIV,1,FIGCAPTION,0,SPAN selector:figure.container-margin > div > figcaption.css-1p5yz2j > span.css-1yg7u8y snippet:<span class="css-1yg7u8y"> type:node] score:0.000233]]

items: [map[node:map[type:text value:Total] score:0.17499599999999998] map[score:0.155127 subItems:map[items:[map[cause:Unsized image element]] type:subitems]] map[node:map[boundingRect:map[bottom:20877 height:20774 left:0 right:412 top:103 width:412] lhId:page-6-DIV nodeLabel:New York Times - Top Stories Pedro Pardo/Agence France-Presse — Getty Images H… path:1,HTML,1,BODY,3,DIV,3,DIV,1,DIV selector:body.fides-overlay-modal-link-shown > div#app > div > div snippet:<div> type:node] score:0.019869 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:674 height:372 left:20 right:392 top:302 width:372] lhId:page-4-IMG nodeLabel:A man standing in a limousine with his head and torso coming out of an opening … path:1,HTML,1,BODY,3,DIV,3,DIV,1,DIV,0,MAIN,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,DIV,0,DIV,0,PICTURE,1,IMG selector:div > div.css-hjiaw4 > picture.css-hdqqnp > img.css-o9w048 snippet:<img class="css-o9w048" src="https://static01.nyt.com/images/2026/04/29/multimedia/00int-china-xi-milit…" alt="A man standing in a limousine with his head and torso coming out of an ope…" fetchpriority="high"> type:node]]] type:subitems]]]

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:98.36 source:map[type:text value:[unattributed]]]]

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
	/assets-oma/images/welcomead_bandit_25Q4_download_trio_la...	589.2 KiB	560.7 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/05/08/us/politics/trump-v-pope/trump-v-pope-...	527.1 KiB	483.7 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/05/06/arts/TO_FRENCH_GORSUCH_thumb-cover/TO_...	525.4 KiB	482.0 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/04/02/multimedia/AS-Creamy-Cottage-Cheese-Ba...	111.3 KiB	74.7 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/05/07/multimedia/07nat-tenn-redistricting-tl...	29.0 KiB	19.5 KiB

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	753 ms
/vi-assets/static-assets/global-bf55b3b62e74478ad48892213...	3.8 KiB
/vi-assets/static-assets/cssModulesStyles-178ce219ee867ee...	54.0 KiB	902 ms

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.

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
	0.155
New York Times - Top Stories Pedro Pardo/Agence France-Presse — Getty Images H… `body.fides-overlay-modal-link-shown > div#app > div > div`	0.020
Pedro Pardo/Agence France-Presse — Getty Images `figure.container-margin > div > figcaption.css-1p5yz2j > span.css-1yg7u8y`	0.000

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: 150 ms 106.3 KiB

URL	Transfer Size	Est Savings
.css-1pg5jir { max-width: calc(100% - 40px); margin: auto; } …	55.5 KiB	55.1 KiB
/vi-assets/static-assets/cssModulesStyles-178ce219ee867ee...	52.3 KiB	51.2 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-5c77575efee767bb0da4.js	8.9 s	7.0 s	256 ms
www.nytimes.com/	1.7 s	163 ms	101 ms
Unattributable	1.1 s	67 ms	0.0 ms
static01.nyt.com/video-static/betamax/betamax-shared-sTKBl65Y.js	856 ms	720 ms	0.3 ms
www.nytimes.com/vi-assets/static-assets/adslot-e85928c0940ad6d2a465.js	582 ms	481 ms	1.7 ms
/js/tags/clientag.js?cid=8CU26C87G&dn=www.nytimes.com&yse...	558 ms	400 ms	35 ms
pagead2.googlesyndication.com/pagead/managed/js/gpt/m202604300101/pubads_impl.js	477 ms	374 ms	40 ms
/gtm.js?id=GTM-P528B3&gtm_auth=tfAzqo1rYDLgYhmTnSjPqw&gtm...	423 ms	327 ms	63 ms
/vi-assets/static-assets/vendors~audio~byline~capsule~car...	403 ms	397 ms	5.2 ms
dd.nytimes.com/tags.js	295 ms	244 ms	6.9 ms
/vi-assets/static-assets/fides-1182b3743d46b6ae880fe21733...	277 ms	230 ms	25 ms
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	229 ms	189 ms	11 ms
www.nytimes.com/vi-assets/static-assets/home-66ab4a1ec2adca23603c.js	183 ms	54 ms	114 ms
rumcdn.geoedge.be/b3960cc6-bfd2-4adc-910c-6e917e8a6a0e/grumi-ip.js	173 ms	141 ms	1.2 ms
pagead2.googlesyndication.com/tag/js/gpt.js	97 ms	65 ms	31 ms
rumcdn.geoedge.be/b3960cc6-bfd2-4adc-910c-6e917e8a6a0e/grumi.js	80 ms	47 ms	33 ms
accounts.google.com/gsi/client	57 ms	31 ms	26 ms
pay.google.com/gp/p/js/pay.js	50 ms	34 ms	16 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	11.0 s
Other	2.8 s
Style & Layout	1.2 s
Script Parsing & Compilation	781 ms
Garbage Collection	404 ms
Rendering	292 ms
Parse HTML & CSS	286 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 6.1 KiB

URL	Transfer Size	Est Savings
.css-1pg5jir { max-width: calc(100% - 40px); margin: auto; } …	55.5 KiB	6.1 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: 0.0 ms 1.2 MiB

URL	Transfer Size	Est Savings
www.nytimes.com/vi-assets/static-assets/main-5c77575efee767bb0da4.js	1.0 MiB	467.5 KiB
www.nytimes.com/vi-assets/static-assets/home-66ab4a1ec2adca23603c.js	465.5 KiB	196.7 KiB
pagead2.googlesyndication.com/pagead/managed/js/gpt/m202604300101/pubads_impl.js	188.9 KiB	131.5 KiB
/gtm.js?id=GTM-P528B3&gtm_auth=tfAzqo1rYDLgYhmTnSjPqw&gtm...	193.9 KiB	74.7 KiB
accounts.google.com/gsi/client	95.6 KiB	68.1 KiB
/js/tags/clientag.js?cid=8CU26C87G&dn=www.nytimes.com&yse...	137.3 KiB	66.5 KiB
static01.nyt.com/video-static/betamax/hlsjs-DB1I5Sio.js	67.1 KiB	64.1 KiB
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	58.8 KiB	29.1 KiB
pay.google.com/gp/p/js/pay.js	57.7 KiB	25.0 KiB
pagead2.googlesyndication.com/tag/js/gpt.js	34.3 KiB	24.1 KiB
/vi-assets/static-assets/fides-1182b3743d46b6ae880fe21733...	96.1 KiB	23.7 KiB
www.nytimes.com/vi-assets/static-assets/vendor-9916e8df8eecbd757328.js	22.8 KiB	20.4 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/2026/05/07/168921_1_17mag-interview-sethi-homepage...	3.3 MiB
www.nytimes.com/vi-assets/static-assets/main-5c77575efee767bb0da4.js	1.0 MiB
/assets-oma/images/welcomead_bandit_25Q4_download_trio_la...	590.2 KiB
/images/2026/05/08/us/politics/trump-v-pope/trump-v-pope-...	527.8 KiB
/images/2026/05/06/arts/TO_FRENCH_GORSUCH_thumb-cover/TO_...	526.1 KiB
www.nytimes.com/vi-assets/static-assets/home-66ab4a1ec2adca23603c.js	467.2 KiB
pay.google.com/gp/p/ui/pay	389.6 KiB
/images/2018/08/24/multimedia/author-jonathan-wolfe/autho...	311.3 KiB
www.nytimes.com/	248.1 KiB
/gtm.js?id=GTM-P528B3&gtm_auth=tfAzqo1rYDLgYhmTnSjPqw&gtm...	194.3 KiB

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

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 34 user timings

●Avoid long main-thread tasks 20 long tasks found

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

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 120 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 60 ms

○INP breakdown

○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.

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`
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`

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-*]` attributes match their 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]`s are contained by their required parent element

●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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

●Links are distinguishable without relying on color.

●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

●ARIA IDs are unique

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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

○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.

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

○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-e85928c0940ad6d2a465.js

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.`
www.nytimes.com/	`Not signed in with the identity provider.`

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.

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.

Content Best Practices

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`
img._poster_13tnt_20 `img._poster_13tnt_20`

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

○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

●Links have descriptive text

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`