C — https://nytimes.com | BeaverCheck Audit

Site Health

Score: 77 / 100

Based on 8 categories, 0 sections

Room to improve — your 29.4s load time is above Google's 2.5s 'Good' threshold.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Strong compliance posture across regulations.

Rich content metadata — your pages look great everywhere.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

WordPress sites average 74

At average

Better than 66% of WordPress sites See full WordPress benchmark →

Amazon Route 53 sites average 72

At average

Better than 86% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

'unsafe-eval' found in script source

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

'unsafe-inline' found in script source

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

Cookie 'nyt-gdpr' is missing the Secure flag

Security gaps expose your site and users to attacks, eroding trust.

Security › Cookie Security

Page weighs 27.6 MB (16.6 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

20 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fnytimes.com)](https://beavercheck.com/results/fb68e8b9-1cd8-4c82-b24c-ed85ad232942)

HTML

<a href="https://beavercheck.com/results/fb68e8b9-1cd8-4c82-b24c-ed85ad232942"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnytimes.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fnytimes.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 29.4s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

Your LCP is 29.4s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

1 accessibility issue excludes users who rely on assistive technology.

Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 4 warning

6 barrier(s) likely increasing bounce by ~26%.

Speed (2)

Page takes 29.4s to load

+12% bounce

Users abandon at ~3s — you're 26.9s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 4.9s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

20 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€425 investment → €3.86/month returns + EUR 500,000 risk avoided

Payback period: > 2 years First-year ROI: -89%

Investment

€425

5h · 5 findings

Monthly returns

€3.86 /mo

~€46 / year

Bandwidth savings €3.86

Regulatory risk avoided

EUR 500,000

if kept compliant

EAA EUR 500,000

€128 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€425

5.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins

€128 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€41,671 / month at risk

~€500,046 / year if left unfixed

Compliance Risk

€500,000

EAA

2 of 8 <nav> elements are unlabeled
EAA: EUR 1,000 – EUR 500,000
Skip navigation link is missing (WCAG 2.4.1)
EAA: EUR 1,000 – EUR 500,000
9 image-only link(s) without alt text
EAA: EUR 1,000 – EUR 500,000

Bandwidth Waste

€3.86 /mo

52109.2 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~5.2 MB per page load
Saves €3.86/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

6.79 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

29.39 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

4.91 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.022

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

13.27 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

31.65 s

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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/15/166816_1_00vid-rv-Iran-China_wg...	60.0 s	3.7 MiB
/video/hlsfmp4/2026/04/15/166816_1_00vid-rv-Iran-China_wg...	60.0 s	3.5 MiB
/video/2026/04/15/167010_1_26-HORMUZ-CHANGE-HP-PROMO_wg_m...	60.0 s	3.4 MiB
/vi-assets/static-assets/fides-e7243ebfa531534e8ccb023358...	0.0 ms	99.6 KiB
/images/2026/04/15/arts/DS_Thumbnail/DS_Thumbnail-vertica...	604800.0 s	632.5 KiB
/images/2026/04/15/arts/Screenshot-2026-04-15-at-5/Screen...	604800.0 s	529.3 KiB
/images/2026/04/13/arts/RV_Thumbnail-groupchat/RV_Thumbna...	604800.0 s	482.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	40.7 KiB
static.nytimes.com/assets-oma/images/devices.png	0.0 ms	18.5 KiB
/images/2026/02/10/multimedia/AS-One-pan-white-wine-pasta...	604800.0 s	77.2 KiB
/images/2026/04/16/multimedia/16nat-french-detained-jvtp/...	604800.0 s	69.9 KiB
static.nytimes.com/assets-oma/images/the-new-york-times.svg	0.0 ms	6.5 KiB
/images/2026/04/16/multimedia/16int-pope-cameroon-plgm/16...	604800.0 s	56.4 KiB
/images/2026/04/15/multimedia/15cul-picasso-winner-qzkt/1...	604800.0 s	39.6 KiB
/images/2026/04/15/multimedia/15DC-ARCH-TOP-vtlm/15DC-ARC...	604800.0 s	33.9 KiB
/video/hlsfmp4/2026/04/15/166816_1_00vid-rv-Iran-China_wg...	60.0 s	1.2 KiB
a1.nyt.com/analytics/show-ads.js	86400.0 s	630 B
/images/2026/04/15/arts/DS_Thumbnail/DS_Thumbnail-vertica...	604800.0 s	466 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:4.162 source:map[column:102592 line:2 type:source-location url:https://dd.nytimes.com/tags.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:3.243 source:map[column:1851 line:0 type:source-location url:https://static01.nyt.com/video-static/betamax/pool-0.2.40-D37jd-c4.js urlProvider:network]] map[reflowTime:5.489 source:map[type:text value:[unattributed]]] map[reflowTime:0.194 source:map[column:78958 line:1 type:source-location url:https://dd.nytimes.com/tags.js urlProvider:network]] map[reflowTime:2.153 source:map[column:86186 line:1 type:source-location url:https://dd.nytimes.com/tags.js urlProvider:network]] map[reflowTime:0.3 source:map[column:86227 line:1 type:source-location url:https://dd.nytimes.com/tags.js urlProvider:network]] map[reflowTime:0.202 source:map[column:88141 line:1 type:source-location url:https://dd.nytimes.com/tags.js urlProvider:network]] map[reflowTime:1.313 source:map[column:88567 line:1 type:source-location url:https://dd.nytimes.com/tags.js urlProvider:network]] map[reflowTime:1.684 source:map[column:17353 line:58 type:source-location url:https://www.nytimes.com/ 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/04/15/arts/DS_Thumbnail/DS_Thumbnail-vertica...	631.1 KiB	616.9 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/04/15/arts/Screenshot-2026-04-15-at-5/Screen...	528.6 KiB	494.8 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/04/13/arts/RV_Thumbnail-groupchat/RV_Thumbna...	481.4 KiB	467.3 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/02/10/multimedia/AS-One-pan-white-wine-pasta...	76.1 KiB	68.0 KiB
Marie-Thérèse Ross-Mahé and Bill Ross pose in front of a large truck. `div > div.css-hjiaw4 > picture.css-hdqqnp > img.css-yf0ys`	/images/2026/04/16/multimedia/16nat-french-detained-jvtp/...	68.8 KiB	46.3 KiB
The pope, dressed in white robes, sits on a platform. A crowd fills the foregro… `div > div.css-hjiaw4 > picture.css-hdqqnp > img.css-yf0ys`	/images/2026/04/16/multimedia/16int-pope-cameroon-plgm/16...	55.9 KiB	37.0 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/04/15/multimedia/15cul-picasso-winner-qzkt/1...	39.2 KiB	35.0 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/04/15/multimedia/15DC-ARCH-TOP-vtlm/15DC-ARC...	32.7 KiB	29.2 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.css	6.7 KiB	151 ms
g1.nyt.com/fonts/css/web-fonts.c851560786173ad206e1f76c1901be7e096e8f8b.css	6.8 KiB	756 ms
/vi-assets/static-assets/cssModulesStyles-194a4f08b37a2be...	52.1 KiB	902 ms
/vi-assets/static-assets/global-bf55b3b62e74478ad48892213...	3.8 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 753 ms

URL	Time Spent
nytimes.com/	753 ms
www.nytimes.com/	0.0 ms

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: 480 ms 102.3 KiB

URL	Transfer Size	Est Savings
.css-1pg5jir { max-width: calc(100% - 40px); margin: auto; } …	52.3 KiB	52.0 KiB
/vi-assets/static-assets/cssModulesStyles-194a4f08b37a2be...	50.5 KiB	50.4 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 6.9 s 1.2 MiB

URL	Transfer Size	Est Savings
www.nytimes.com/vi-assets/static-assets/main-d9016001b7d9c9ed2c45.js	929.3 KiB	401.0 KiB
www.nytimes.com/vi-assets/static-assets/home-7ec14230b5e40376466c.js	457.3 KiB	204.0 KiB
static01.nyt.com/video-static/betamax/hlsjs-Bt8316rQ.js	146.2 KiB	139.6 KiB
/pagead/managed/js/gpt/m202604140101/pubads_impl.js?cb=31...	187.7 KiB	134.3 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...	191.7 KiB	74.7 KiB
accounts.google.com/gsi/client	95.4 KiB	71.1 KiB
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	57.9 KiB	28.6 KiB
pay.google.com/gp/p/js/pay.js	57.4 KiB	24.7 KiB
pagead2.googlesyndication.com/tag/js/gpt.js	34.2 KiB	24.0 KiB
/vi-assets/static-assets/fides-e7243ebfa531534e8ccb023358...	94.8 KiB	23.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-d9016001b7d9c9ed2c45.js	7.8 s	6.4 s	352 ms
www.nytimes.com/	2.0 s	503 ms	182 ms
Unattributable	1.6 s	128 ms	0.0 ms
static01.nyt.com/video-static/betamax/betamax-shared-sTKBl65Y.js	1.3 s	1.0 s	0.3 ms
/pagead/managed/js/gpt/m202604140101/pubads_impl.js?cb=31...	739 ms	553 ms	71 ms
www.nytimes.com/vi-assets/static-assets/adslot-59e729d7c8593a1554b2.js	651 ms	585 ms	2.2 ms
/gtm.js?id=GTM-P528B3&gtm_auth=tfAzqo1rYDLgYhmTnSjPqw&gtm...	645 ms	416 ms	80 ms
/vi-assets/static-assets/vendors~audio~byline~capsule~car...	573 ms	565 ms	6.4 ms
/vi-assets/static-assets/fides-e7243ebfa531534e8ccb023358...	452 ms	319 ms	36 ms
dd.nytimes.com/tags.js	399 ms	356 ms	9.1 ms
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	387 ms	338 ms	17 ms
www.nytimes.com/vi-assets/static-assets/home-7ec14230b5e40376466c.js	196 ms	13 ms	178 ms
pagead2.googlesyndication.com/tag/js/gpt.js	121 ms	88 ms	32 ms
static01.nyt.com/video-static/betamax/video-element-CUyF9-im.js	71 ms	18 ms	0.1 ms
pay.google.com/gp/p/js/pay.js	66 ms	43 ms	22 ms
accounts.google.com/gsi/client	66 ms	34 ms	31 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.4 s
Other	2.6 s
Style & Layout	1.2 s
Script Parsing & Compilation	1.1 s
Parse HTML & CSS	366 ms
Garbage Collection	322 ms
Rendering	250 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.8 KiB

URL	Transfer Size	Est Savings
.css-1pg5jir { max-width: calc(100% - 40px); margin: auto; } …	52.3 KiB	5.8 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/15/166816_1_00vid-rv-Iran-China_wg...	3.7 MiB
/video/hlsfmp4/2026/04/15/166816_1_00vid-rv-Iran-China_wg...	3.5 MiB
/video/2026/04/15/167010_1_26-HORMUZ-CHANGE-HP-PROMO_wg_m...	3.4 MiB
www.nytimes.com/vi-assets/static-assets/main-d9016001b7d9c9ed2c45.js	931.6 KiB
/images/2026/04/15/arts/DS_Thumbnail/DS_Thumbnail-vertica...	632.5 KiB
/images/2026/04/15/arts/Screenshot-2026-04-15-at-5/Screen...	529.3 KiB
/images/2026/04/13/arts/RV_Thumbnail-groupchat/RV_Thumbna...	482.7 KiB
www.nytimes.com/vi-assets/static-assets/home-7ec14230b5e40376466c.js	459.0 KiB
pay.google.com/gp/p/ui/pay	388.6 KiB
www.nytimes.com/	289.6 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 36 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○LCP request discovery

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`

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.

●Links have a discernible name

●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"]`

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

○Uses ARIA roles only on compatible elements

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

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/04/14/us/politics/trump-iran-blockade-china.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`

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.25 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.70 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

1.22 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.019

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.53 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

7.33 s

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.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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
vp.nyt.com/video/2026/04/15/167010_1_26-HORMUZ-CHANGE-HP-PROMO_wg_720p.mp4	60.0 s	3.9 MiB
/video/hlsfmp4/2026/04/15/166816_1_00vid-rv-Iran-China_wg...	60.0 s	3.7 MiB
/video/hlsfmp4/2026/04/15/166816_1_00vid-rv-Iran-China_wg...	60.0 s	3.5 MiB
vp.nyt.com/video/2026/04/14/166823_1_15mag-onlanguage-coded-hp-82970_wg_720p.mp4	60.0 s	1.3 MiB
static.nytimes.com/email-images/newsletters/Weekender/NYT-TheWeekender-Icon.jpg	3600.0 s	176.0 KiB
static.nytimes.com/email-images/Sub_Only_Icons/NYT-OnTech-Icon.png	3600.0 s	128.5 KiB
/vi-assets/static-assets/fides-e7243ebfa531534e8ccb023358...	0.0 ms	99.6 KiB
static.nytimes.com/email-images/NYT-Newsletters-Serial-Icon-500px.jpg	3600.0 s	89.8 KiB
/email-images/Newsletter Icons/NYT-Newsletters-TheWorld-I...	3600.0 s	80.1 KiB
/images/2026/04/15/arts/DS_Thumbnail/DS_Thumbnail-vertica...	604800.0 s	632.1 KiB
static.nytimes.com/email-images/NYT-Newsletters-TheEvening-Icon.jpg	3600.0 s	78.2 KiB
/images/2025/09/04/podcasts/Reporter-Reads-album-art/Repo...	604800.0 s	577.4 KiB
/images/2026/04/15/arts/Screenshot-2026-04-15-at-5/Screen...	604800.0 s	529.3 KiB
/images/2026/04/13/arts/RV_Thumbnail-groupchat/RV_Thumbna...	604800.0 s	482.1 KiB
/images/2022/09/28/podcasts/hard-fork-album-art/hard-fork...	604800.0 s	468.3 KiB
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	14400.0 s	58.3 KiB
static01.nyt.com/email-images/newsletters/books/Books-REV.png	3600.0 s	44.9 KiB
dd.nytimes.com/tags.js	3600.0 s	40.7 KiB
/images/2026/03/18/podcasts/serial-the-idiot-album-art/se...	604800.0 s	101.7 KiB
/images/2023/11/03/podcasts/week-in-opinion-art/week-in-o...	604800.0 s	90.1 KiB
/images/2025/04/02/podcasts/ross-douthat-album-art/ross-d...	604800.0 s	87.4 KiB
/images/2026/02/10/multimedia/AS-One-pan-white-wine-pasta...	604800.0 s	77.2 KiB
/images/2023/04/08/podcasts/modernlove-album-art/modernlo...	604800.0 s	76.3 KiB
/images/2026/04/16/multimedia/16nat-french-detained-jvtp/...	604800.0 s	44.3 KiB
static.chartbeat.com/js/chartbeat_mab.js	86400.0 s	10.1 KiB
/images/2026/04/15/multimedia/15cul-picasso-winner-qzkt/1...	604800.0 s	40.2 KiB
/images/2023/04/05/podcasts/ezra-klein-album-art/ezra-kle...	604800.0 s	37.6 KiB
/images/2026/04/16/multimedia/16int-pope-cameroon-plgm/16...	604800.0 s	37.4 KiB
/images/2025/06/09/podcasts/cannonball-album-art/cannonba...	604800.0 s	35.4 KiB
/images/2026/04/15/multimedia/15DC-ARCH-TOP-vtlm/15DC-ARC...	604800.0 s	33.9 KiB
/images/2022/09/28/podcasts/hard-fork-album-art/hard-fork...	604800.0 s	30.7 KiB
/images/2018/04/02/opinion/linda-greenhouse/linda-greenho...	604800.0 s	25.2 KiB
/images/2026/03/26/podcasts/serial-the-idiot-episodic-art...	604800.0 s	23.0 KiB
/images/2026/04/16/multimedia/16int-europe-right-01-mcqt/...	604800.0 s	20.6 KiB
/images/2026/04/15/multimedia/2026-04-14-dc-triumphal-arc...	604800.0 s	20.5 KiB
/images/2026/04/14/the-athletic/tamc-041526-viral-Pacers-...	604800.0 s	18.7 KiB
/images/2026/04/13/multimedia/13well-healthy-oats-hp-bgcp...	604800.0 s	18.6 KiB
/images/2026/04/12/multimedia/12ST-ALPINE-DIVORCE-btzk/12...	604800.0 s	13.7 KiB
/images/2022/10/12/podcasts/headlines-albumartwork-audioa...	604800.0 s	13.7 KiB
/images/2026/04/16/multimedia/16biz-iran-jet-fuel-01-gkql...	604800.0 s	13.5 KiB
/images/2025/04/02/podcasts/ross-douthat-album-art/ross-d...	604800.0 s	12.3 KiB
/video/hlsfmp4/2026/04/15/166816_1_00vid-rv-Iran-China_wg...	60.0 s	1.2 KiB
/images/2026/04/14/multimedia/14xp-florida-promo/14xp-flo...	604800.0 s	10.9 KiB
/images/2023/11/27/opinion/the-opinions-art/the-opinions-...	604800.0 s	10.0 KiB
/images/2026/04/16/multimedia/16Bedard-lzqf/16Bedard-lzqf...	604800.0 s	9.6 KiB
/images/2026/04/16/multimedia/16int-iran-srilanka-sailors...	604800.0 s	9.4 KiB
/images/2026/04/16/travel/16trippedup-illo/16trippedup-il...	604800.0 s	9.3 KiB
/images/2026/04/15/multimedia/15wheels-evs-top-lctw/15whe...	604800.0 s	9.2 KiB
/images/2026/04/15/multimedia/15int-italy-meloni-01-jzbm/...	604800.0 s	8.7 KiB
/images/2026/04/16/multimedia/16DC-WARPOWERS-blpm/16DC-WA...	604800.0 s	7.6 KiB
/images/2026/04/16/multimedia/16israel-iran-vought-cost-o...	604800.0 s	6.9 KiB
/images/2026/04/12/multimedia/12tbr-nelio-biedermann-01-t...	604800.0 s	5.4 KiB
/images/2020/09/21/podcasts/modernlove-logo/modernlove-lo...	604800.0 s	4.7 KiB
/images/2011/05/20/multimedia/music-popcast/music-popcast...	604800.0 s	4.6 KiB
/images/2026/03/26/well/WELL-UPLIFTING-BOOKS-image/WELL-U...	604800.0 s	4.1 KiB
/images/2018/03/27/books/book-review-album-art-v2/book-re...	604800.0 s	3.5 KiB
/images/2017/01/29/podcasts/the-daily-album-art/the-daily...	604800.0 s	2.5 KiB
a1.nyt.com/analytics/show-ads.js	86400.0 s	630 B
vp.nyt.com/video/2026/04/15/166814_1_16opinions-age-gaps-cine_wg_720p.mp4	60.0 s	94 B
/images/2026/04/15/arts/DS_Thumbnail/DS_Thumbnail-vertica...	604800.0 s	466 B
vp.nyt.com/video/2026/04/15/166814_1_16opinions-age-gaps-cine_wg_720p.mp4	60.0 s	0 B

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:10.818 source:map[column:140474 line:53 type:source-location url:https://www.nytimes.com/vi-assets/static-assets/main-d9016001b7d9c9ed2c45.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:186.474 source:map[type:text value:[unattributed]]] map[reflowTime:2.578 source:map[column:88567 line:1 type:source-location url:https://dd.nytimes.com/tags.js urlProvider:network]] map[reflowTime:2.011 source:map[column:17353 line:58 type:source-location url:https://www.nytimes.com/ urlProvider:network]] map[reflowTime:1.821 source:map[column:89146 line:1 type:source-location url:https://dd.nytimes.com/tags.js urlProvider:network]] map[reflowTime:0.279 source:map[column:95303 line:0 type:source-location url:https://www.nytimes.com/vi-assets/static-assets/home-7ec14230b5e40376466c.js urlProvider:network]] map[reflowTime:2.181 source:map[column:131808 line:27 type:source-location url:https://www.nytimes.com/vi-assets/static-assets/main-d9016001b7d9c9ed2c45.js urlProvider:network]] map[reflowTime:0.279 source:map[column:1851 line:0 type:source-location url:https://static01.nyt.com/video-static/betamax/pool-0.2.40-D37jd-c4.js urlProvider:network]] map[reflowTime:3.85 source:map[column:457080 line:0 type:source-location url:https://www.nytimes.com/vi-assets/static-assets/home-7ec14230b5e40376466c.js urlProvider:network]] map[reflowTime:4.508 source:map[column:457007 line:0 type:source-location url:https://www.nytimes.com/vi-assets/static-assets/home-7ec14230b5e40376466c.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/04/15/arts/Screenshot-2026-04-15-at-5/Screen...	528.6 KiB	500.9 KiB
Linda Greenhouse `div.css-4se1tq > div.css-hjiaw4 > picture > img.css-1kx59a0`	/images/2018/04/02/opinion/linda-greenhouse/linda-greenho...	24.3 KiB	24.0 KiB
Marie-Thérèse Ross-Mahé and Bill Ross pose in front of a large truck. `div > div.css-q70vsu > picture.css-hdqqnp > img.css-yf0ys`	/images/2026/04/16/multimedia/16nat-french-detained-jvtp/...	43.8 KiB	4.7 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-3-VIDEO

nodeLabel: div > div.css-11kuxu4 > div.css-122y91a > video.cinemagraph_video

path: 1,HTML,1,BODY,2,DIV,3,DIV,1,DIV,0,MAIN,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,SECTION,0,A,0,DIV,0,FIGURE,0,DIV,0,DIV,0,DIV,0,DIV,0,VIDEO

selector: div > div.css-11kuxu4 > div.css-122y91a > video.cinemagraph_video

snippet: <video data-testid="cinemagraph" data-play="true" src="https://vp.nyt.com/video/2026/04/15/167010_1_26-HORMUZ-CHANGE-HP-PROMO_wg_…" class="cinemagraph_video css-gvnats" muted="" loop="" autoplay="" playsinline="">

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.

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
/vi-assets/static-assets/cssModulesStyles-194a4f08b37a2be...	52.1 KiB	162 ms
g1.nyt.com/fonts/css/web-fonts.c851560786173ad206e1f76c1901be7e096e8f8b.css	6.8 KiB	203 ms
/vi-assets/static-assets/global-bf55b3b62e74478ad48892213...	3.8 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 239 ms

URL	Time Spent
nytimes.com/	239 ms
www.nytimes.com/	0.0 ms

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 130 ms 1.2 MiB

URL	Transfer Size	Est Savings
www.nytimes.com/vi-assets/static-assets/main-d9016001b7d9c9ed2c45.js	929.3 KiB	401.8 KiB
www.nytimes.com/vi-assets/static-assets/home-7ec14230b5e40376466c.js	457.3 KiB	196.9 KiB
/pagead/managed/js/gpt/m202604140101/pubads_impl.js?cb=31...	187.7 KiB	130.4 KiB
static01.nyt.com/video-static/betamax/hlsjs-Bt8316rQ.js	106.9 KiB	102.1 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...	191.7 KiB	74.7 KiB
accounts.google.com/gsi/client	95.4 KiB	71.1 KiB
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	57.9 KiB	28.5 KiB
pay.google.com/gp/p/js/pay.js	57.4 KiB	25.4 KiB
pagead2.googlesyndication.com/tag/js/gpt.js	34.2 KiB	24.0 KiB
pagead2.googlesyndication.com/tag/js/gpt.js	34.2 KiB	24.0 KiB
/vi-assets/static-assets/fides-e7243ebfa531534e8ccb023358...	94.8 KiB	23.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-d9016001b7d9c9ed2c45.js	2.7 s	2.2 s	90 ms
www.nytimes.com/	739 ms	106 ms	32 ms
Unattributable	508 ms	53 ms	0.0 ms
static01.nyt.com/video-static/betamax/betamax-shared-sTKBl65Y.js	315 ms	249 ms	0.1 ms
/vi-assets/static-assets/vendors~audio~byline~capsule~car...	236 ms	212 ms	2.3 ms
www.nytimes.com/vi-assets/static-assets/adslot-59e729d7c8593a1554b2.js	200 ms	173 ms	0.5 ms
/gtm.js?id=GTM-P528B3&gtm_auth=tfAzqo1rYDLgYhmTnSjPqw&gtm...	189 ms	148 ms	27 ms
/pagead/managed/js/gpt/m202604140101/pubads_impl.js?cb=31...	122 ms	83 ms	13 ms
dd.nytimes.com/tags.js	98 ms	79 ms	3.2 ms
/vi-assets/static-assets/fides-e7243ebfa531534e8ccb023358...	94 ms	70 ms	9.4 ms
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	83 ms	72 ms	4.0 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	3.5 s
Other	756 ms
Style & Layout	518 ms
Script Parsing & Compilation	261 ms
Garbage Collection	167 ms
Rendering	133 ms
Parse HTML & CSS	76 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.9 KiB

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

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: 0.0 ms 67.7 KiB

URL	Transfer Size	Est Savings
.css-1pg5jir { max-width: calc(100% - 40px); margin: auto; } …	53.3 KiB	51.9 KiB
/vi-assets/static-assets/cssModulesStyles-194a4f08b37a2be...	15.9 KiB	15.8 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
vp.nyt.com/video/2026/04/15/166814_1_16opinions-age-gaps-cine_wg_720p.mp4	4.5 MiB
vp.nyt.com/video/2026/04/15/167010_1_26-HORMUZ-CHANGE-HP-PROMO_wg_720p.mp4	3.9 MiB
/video/hlsfmp4/2026/04/15/166816_1_00vid-rv-Iran-China_wg...	3.7 MiB
/video/hlsfmp4/2026/04/15/166816_1_00vid-rv-Iran-China_wg...	3.5 MiB
vp.nyt.com/video/2026/04/14/166823_1_15mag-onlanguage-coded-hp-82970_wg_720p.mp4	1.3 MiB
www.nytimes.com/vi-assets/static-assets/main-d9016001b7d9c9ed2c45.js	931.6 KiB
/images/2026/04/15/arts/DS_Thumbnail/DS_Thumbnail-vertica...	632.1 KiB
/images/2025/09/04/podcasts/Reporter-Reads-album-art/Repo...	577.4 KiB
/images/2026/04/15/arts/Screenshot-2026-04-15-at-5/Screen...	529.3 KiB
/images/2026/04/13/arts/RV_Thumbnail-groupchat/RV_Thumbna...	482.1 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 32 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 5 layout shifts found

○INP breakdown

Accessibility

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
+0.22% `div.css-27ffgo > div.css-m7oyll > div.css-1ooqyr8 > div.css-ke4w0y`

These are opportunities to improve the legibility of your content.

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`

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
U.S. `nav > ul.css-17j7fe1 > li.css-1bo3wsb > a.css-u90q6n`
open U.S. `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`
open World `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`
open Business `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`
Arts `nav > ul.css-17j7fe1 > li.css-1bo3wsb > a.css-u90q6n`
open Arts `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`
open Lifestyle `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`
open Opinion `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`
Video `nav > ul.css-17j7fe1 > li.css-1bo3wsb > a.css-u90q6n`
open Video `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`
open Audio `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`
open Games `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`
open Cooking `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`
open Wirecutter `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`
open The Athletic `nav > ul.css-17j7fe1 > li.css-1bo3wsb > button.css-19wyrnd`

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

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

●Links have a discernible name

●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

●`[lang]` attributes have a valid value

●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"]`

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

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

○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-59e729d7c8593a1554b2.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.`

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

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/04/14/us/politics/trump-iran-blockade-china.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.

○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 are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://nytimes.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (1)

Content (1)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Best practices

Best Practices

General

SEO

Content Best Practices

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best practices

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts