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
/js/tags/clientag.js?cid=8CU26C87G&dn=www.nytimes.com&yse...	1800.0 s	193.0 KiB
/newsgraphics/weather-hp-strip/00473cac-d3e8-4d63-b1ea-f9...	5.0 s	154.1 KiB
/images/2026/04/20/world/middleeast/RV_Thumbnail/RV_Thumb...	604800.0 s	1.3 MiB
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	90.8 KiB
/images/2026/04/21/arts/ColbySmith_RVThumb/ColbySmith_RVT...	604800.0 s	677.3 KiB
/vi-assets/static-assets/fides-gpp-18c79946e738fa1a62b99a...	0.0 ms	63.0 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	39.4 KiB
static.chartbeat.com/js/chartbeat_video.js	7200.0 s	24.8 KiB
static.nytimes.com/assets-oma/images/devices.png	0.0 ms	18.5 KiB
/scripts/bundle/65568.js?sid=4486dfe2-780e-4dfa-a60a-2a94...	3600.0 s	20.5 KiB
/images/2026/04/22/multimedia/22xp-chemical-fhvg/22xp-che...	604800.0 s	117.1 KiB
/images/2025/10/28/podcasts/the-ezra-klen-show-album-art/...	604800.0 s	107.7 KiB
/images/2026/04/22/arts/OPDOC_EARTHRISE_CLIP_THUMB_CLEAN/...	604800.0 s	106.5 KiB
/newsgraphics/weather-hp-strip/00473cac-d3e8-4d63-b1ea-f9...	5.0 s	10.5 KiB
/images/2026/03/18/podcasts/serial-the-idiot-album-art/se...	604800.0 s	101.6 KiB
/images/2025/04/02/podcasts/ross-douthat-album-art/ross-d...	604800.0 s	87.3 KiB
/images/2023/04/08/podcasts/modernlove-album-art/modernlo...	604800.0 s	76.4 KiB
a1.nyt.com/analytics/comscore-streaming.js	86400.0 s	18.9 KiB
static.nytimes.com/assets-oma/images/the-new-york-times.svg	0.0 ms	6.6 KiB
/images/2026/04/22/multimedia/22dc-cong-stuck-top-pgzc/22...	604800.0 s	57.2 KiB
/images/2026/02/09/multimedia/09FD-Guava-and-Cream-Cheese...	604800.0 s	56.4 KiB
/images/2018/03/27/books/book-review-album-art-v2/book-re...	604800.0 s	54.3 KiB
rumcdn.geoedge.be/b3960cc6-bfd2-4adc-910c-6e917e8a6a0e/grumi-ip.js	14400.0 s	7.1 KiB
/images/2026/04/22/multimedia/22dc-patel-top-ltgk/22dc-pa...	604800.0 s	37.0 KiB
cdn.brandmetrics.com/tag/85a1ebf79602421aa1c2c2f24d32cb6c/nyt.js	3600.0 s	4.3 KiB
/images/2017/01/29/podcasts/the-daily-album-art/the-daily...	604800.0 s	33.8 KiB
sb.scorecardresearch.com/internal-cs/default/beacon-and.js	86400.0 s	7.9 KiB
/images/2026/04/21/arts/HF-190-9x16-Social-This-AI-Moment...	604800.0 s	28.4 KiB
/images/2026/04/22/multimedia/22vid-pol-virginia-fhql/22v...	604800.0 s	21.8 KiB
/vi-assets/static-assets/iab-gpp-stub-02a14dbfddf7bec445a...	0.0 ms	2.1 KiB
/9fab0bf6-df63-42ca-acc5-caf4de668f40/launchpad-liveramp.js	0.0 ms	1.7 KiB
/images/2025/10/10/multimedia/22int-israel-rabbi/10vid-ga...	604800.0 s	16.4 KiB
/images/2026/04/22/multimedia/22iran-brinkmanship-assess-...	604800.0 s	14.6 KiB
/newsgraphics/weather-hp-strip/00473cac-d3e8-4d63-b1ea-f9...	5.0 s	898 B
/newsgraphics/weather-hp-strip/00473cac-d3e8-4d63-b1ea-f9...	5.0 s	854 B
/newsgraphics/weather-hp-strip/00473cac-d3e8-4d63-b1ea-f9...	5.0 s	843 B
config.aps.amazon-adsystem.com/configs/3030	3600.0 s	1023 B
/images/2026/04/22/multimedia/22Biz-Iran-Airlines-jqwg/22...	604800.0 s	7.8 KiB
platform.iteratehq.com/loader.js	1800.0 s	915 B
/images/2026/04/22/multimedia/22dc-uae-swap-tgfh/22dc-uae...	604800.0 s	7.1 KiB
/newsgraphics/weather-hp-strip/00473cac-d3e8-4d63-b1ea-f9...	5.0 s	722 B
/images/2026/04/22/multimedia/22biz-iran-ship-count-wlpj/...	604800.0 s	6.6 KiB
/images/2026/04/22/multimedia/22evening-nl-iran-hormuz-st...	604800.0 s	5.5 KiB
/c.js?siteid=4486dfe2-780e-4dfa-a60a-2a948887658f&toploc=...	0.0 ms	292 B
a1.nyt.com/analytics/show-ads.js	86400.0 s	334 B

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.

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:122.188 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
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/04/20/world/middleeast/RV_Thumbnail/RV_Thumb...	1.3 MiB	1.3 MiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/04/21/arts/ColbySmith_RVThumb/ColbySmith_RVT...	675.8 KiB	642.0 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/04/22/arts/OPDOC_EARTHRISE_CLIP_THUMB_CLEAN/...	105.3 KiB	94.0 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/02/09/multimedia/09FD-Guava-and-Cream-Cheese...	55.9 KiB	49.9 KiB
The Capitol this week. `div > div.css-hjiaw4 > picture.css-hdqqnp > img.css-yf0ys`	/images/2026/04/22/multimedia/22dc-cong-stuck-top-pgzc/22...	56.3 KiB	37.3 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/04/21/arts/HF-190-9x16-Social-This-AI-Moment...	27.4 KiB	24.5 KiB
Kash Patel in a blue suit. `div > div.css-hjiaw4 > picture.css-hdqqnp > img.css-yf0ys`	/images/2026/04/22/multimedia/22dc-patel-top-ltgk/22dc-pa...	36.4 KiB	24.1 KiB
img._poster_13tnt_20 `img._poster_13tnt_20`	/images/2026/04/22/multimedia/22vid-pol-virginia-fhql/22v...	21.4 KiB	19.1 KiB

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
/vi-assets/static-assets/cssModulesStyles-194a4f08b37a2be...	51.8 KiB
g1.nyt.com/fonts/css/web-fonts.css	6.7 KiB
/newsgraphics/weather-hp-strip/00473cac-d3e8-4d63-b1ea-f9...	10.5 KiB
/vi-assets/static-assets/global-bf55b3b62e74478ad48892213...	3.6 KiB
g1.nyt.com/fonts/css/web-fonts.c851560786173ad206e1f76c1901be7e096e8f8b.css	6.8 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

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

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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
/images/2026/04/20/world/middleeast/RV_Thumbnail/RV_Thumb...	1.3 MiB
www.nytimes.com/vi-assets/static-assets/main-f4ede41ba47e537fbd07.js	1.0 MiB
/images/2026/04/21/arts/ColbySmith_RVThumb/ColbySmith_RVT...	677.3 KiB
www.nytimes.com/vi-assets/static-assets/home-6f9e88822c63b5707c6e.js	458.3 KiB
pay.google.com/gp/p/ui/pay	389.1 KiB
www.nytimes.com/	280.7 KiB
/js/tags/clientag.js?cid=8CU26C87G&dn=www.nytimes.com&yse...	193.0 KiB
/gtm.js?id=GTM-P528B3&gtm_auth=tfAzqo1rYDLgYhmTnSjPqw&gtm...	192.0 KiB
/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31...	187.7 KiB
rumcdn.geoedge.be/b3960cc6-bfd2-4adc-910c-6e917e8a6a0e/grumi.js	187.6 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-f4ede41ba47e537fbd07.js	14.5 s	12.1 s	465 ms
/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31...	3.2 s	3.0 s	75 ms
www.nytimes.com/	2.4 s	619 ms	160 ms
Unattributable	2.1 s	623 ms	0.0 ms
static01.nyt.com/video-static/betamax/betamax-shared-sTKBl65Y.js	1.5 s	1.3 s	0.4 ms
www.nytimes.com/vi-assets/static-assets/adslot-85f75cbf48b1162ebdbb.js	1.1 s	991 ms	22 ms
/gtm.js?id=GTM-P528B3&gtm_auth=tfAzqo1rYDLgYhmTnSjPqw&gtm...	909 ms	647 ms	115 ms
/js/tags/clientag.js?cid=8CU26C87G&dn=www.nytimes.com&yse...	799 ms	706 ms	73 ms
/vi-assets/static-assets/fides-gpp-18c79946e738fa1a62b99a...	761 ms	690 ms	31 ms
/vi-assets/static-assets/vendors~audio~byline~capsule~car...	720 ms	710 ms	9.8 ms
c.amazon-adsystem.com/aax2/apstag.js	395 ms	320 ms	54 ms
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	370 ms	213 ms	20 ms
dd.nytimes.com/tags.js	304 ms	257 ms	13 ms
www.googletagmanager.com/gtag/destination?id=DC-5290727&cx=c&gtm=4e64k1	275 ms	229 ms	43 ms
www.nytimes.com/vi-assets/static-assets/home-6f9e88822c63b5707c6e.js	245 ms	26 ms	205 ms
/newsgraphics/weather-hp-strip/00473cac-d3e8-4d63-b1ea-f9...	210 ms	108 ms	3.8 ms
rumcdn.geoedge.be/b3960cc6-bfd2-4adc-910c-6e917e8a6a0e/grumi.js	142 ms	72 ms	69 ms
/ats-modules/087423d8-0b74-47f4-a79b-03ddad419681/ats.js	138 ms	91 ms	44 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	133 ms	91 ms	41 ms
/scripts/bundle/65568.js?sid=4486dfe2-780e-4dfa-a60a-2a94...	123 ms	80 ms	39 ms
static.chartbeat.com/js/chartbeat_video.js	117 ms	105 ms	8.7 ms
/9fab0bf6-df63-42ca-acc5-caf4de668f40/launchpad-liveramp.js	113 ms	111 ms	0.7 ms
www.googletagmanager.com/gtm.js?id=GTM-N5P6T9S&gtm=4e64k1	103 ms	61 ms	41 ms
accounts.google.com/gsi/client	76 ms	45 ms	31 ms
config.aps.amazon-adsystem.com/configs/3030	70 ms	68 ms	0.5 ms
launchpad.privacymanager.io/latest/launchpad.bundle.js	70 ms	43 ms	25 ms
pay.google.com/gp/p/js/pay.js	61 ms	36 ms	24 ms
rumcdn.geoedge.be/b3960cc6-bfd2-4adc-910c-6e917e8a6a0e/grumi-ip.js	53 ms	42 ms	2.5 ms
/vi-assets/static-assets/cssModulesStyles-194a4f08b37a2be...	51 ms	0.0 ms	0.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	23.6 s
Other	3.1 s
Script Parsing & Compilation	1.7 s
Style & Layout	1.4 s
Garbage Collection	746 ms
Parse HTML & CSS	502 ms
Rendering	326 ms

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

●Modern HTTP

●Network dependency tree

●Optimize viewport for mobile

●User Timing marks and measures 43 user timings

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

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 150 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○LCP breakdown

○LCP request discovery

○Avoid non-composited animations

Accessibility

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

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`

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

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

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

○`[accesskey]` values are unique

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	www.nytimes.com/vi-assets/static-assets/adslot-85f75cbf48b1162ebdbb.js
Topics	dd.nytimes.com/tags.js line 1, col 32233

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.`
vp.nyt.com/video/2026/04/22/167412_1_00vid-rv-warsh-confirmation_wg_1080p.vtt	`Failed to load resource: the server responded with a status of 404 ()`
www.nytimes.com/	`Not signed in with the identity provider.`
www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js	`UserInfoAgentID unavailable.`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

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

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

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

Content Best Practices

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

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`