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
a.pub.network/tucson-com/prebid.js	1800.0 s	188.0 KiB
a.pub.network/tucson-com/pubfig.engine.mobile.js	1800.0 s	151.9 KiB
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	90.8 KiB
tucson.com/shared-content/art/tncms/api/access.bc44532080f114b4be74.js	600.0 s	31.0 KiB
a.pub.network/tucson-com/pubfig.min.js	1800.0 s	26.3 KiB
tagan.adlightning.com/leeenterprises/op.js	3600.0 s	15.0 KiB
cmp.osano.com/16CVqQSid6k3038vU/fef0f8b2-698d-45ee-89c5-d8fbf51fbfb7/osano-ui.js	86400.0 s	29.2 KiB
freestar.solutions.cdn.optable.co/public-assets/freestar-sdk.js	86400.0 s	16.6 KiB
config.aps.amazon-adsystem.com/configs/0ab198dd-b265-462a-ae36-74e163ad6159	3600.0 s	6.8 KiB
tucson.com/shared-content/art/stats/common/tracker.js	600.0 s	3.4 KiB
tucson.com/shared-content/art/tncms/user/user.js	600.0 s	1.8 KiB
tucson.com/shared-content/art/tncms/tracking.js	600.0 s	1.4 KiB
tucson.com/shared-content/art/tncms/api/messaging662.js	600.0 s	1.1 KiB
tucson.com/shared-content/art/tncms/api/csrf.js	600.0 s	796 B
a.pub.network/core/imgs/1.png?x=2026-04-22T23%3A07%3A12.522	3600.0 s	641 B
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB
tucson.com/shared-content/art/tncms/api/access.bc44532080f114b4be74.js	600.0 s	0 B
tucson.com/shared-content/art/stats/common/tracker.js	600.0 s	0 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:25.221 source:map[column:185009 line:2 type:source-location url:https://cmp.osano.com/16CVqQSid6k3038vU/fef0f8b2-698d-45ee-89c5-d8fbf51fbfb7/osano.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:88.876 source:map[type:text value:[unattributed]]] map[reflowTime:0.219 source:map[column:323439 line:0 type:source-location url:https://a.pub.network/tucson-com/pubfig.engine.mobile.js urlProvider:network]] map[reflowTime:1.249 source:map[column:380 line:580 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]] map[reflowTime:2.453 source:map[column:47 line:303 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]] map[reflowTime:0.113 source:map[column:27 line:48 type:source-location url:https://bloximages.chicago2.vip.townnews.com/tucson.com/content/tncms/live/libraries/flex/components/ads_dfp/resources/scripts/fs.js?_dc=1776754933 urlProvider:network]] map[reflowTime:25.221 source:map[column:51681 line:1 type:source-location url:https://bloximages.chicago2.vip.townnews.com/tucson.com/shared-content/art/tncms/templates/libraries/flex/components/jquery/resources/scripts/jquery.min.d6d18fcf88750a16d256e72626e676a6.js urlProvider:network]] map[reflowTime:1.68 source:map[column:30031 line:1 type:source-location url:https://cmp.osano.com/16CVqQSid6k3038vU/fef0f8b2-698d-45ee-89c5-d8fbf51fbfb7/osano-ui.js urlProvider:network]] map[reflowTime:1.35 source:map[column:62355 line:1 type:source-location url:https://cmp.osano.com/16CVqQSid6k3038vU/fef0f8b2-698d-45ee-89c5-d8fbf51fbfb7/osano-ui.js urlProvider:network]] map[reflowTime:0.624 source:map[column:62714 line:1 type:source-location url:https://cmp.osano.com/16CVqQSid6k3038vU/fef0f8b2-698d-45ee-89c5-d8fbf51fbfb7/osano-ui.js urlProvider:network]] map[reflowTime:0.238 source:map[column:3528 line:6 type:source-location url:https://bloximages.chicago2.vip.townnews.com/tucson.com/shared-content/art/tncms/templates/libraries/flex/components/plugins/resources/scripts/common.08a61544f369cc43bf02e71b2d10d49f.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

items: [map[duration:207.798 label:Time to first byte subpart:timeToFirstByte] map[duration:2296.451 label:Resource load delay subpart:resourceLoadDelay] map[duration:75.285 label:Resource load duration subpart:resourceLoadDuration] map[duration:169.68 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Tucson Sugar Skulls end home skid ahead of rematch with San Diego

path: 1,HTML,1,BODY,18,DIV,4,DIV,2,DIV,2,SECTION,3,DIV,0,DIV,0,DIV,0,SECTION,0,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,FIGURE,0,DIV,0,A,0,IMG

selector: figure.photo > div.image > a.tnt-asset-link > img.img-responsive

snippet: <img src="https://bloximages.chicago2.vip.townnews.com/tucson.com/content/tncms/asse…" alt="Tucson Sugar Skulls end home skid ahead of rematch with San Diego" class="img-responsive full lazyautosizes lazyloaded" width="1823" height="1025" data-sizes="auto" data-srcset="https://bloximages.chicago2.vip.townnews.com/tucson.com/content/tncms/asse…" sizes="412px" srcset="https://bloximages.chicago2.vip.townnews.com/tucson.com/content/tncms/asse…">

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

nodeLabel: Tucson Sugar Skulls end home skid ahead of rematch with San Diego

path: 1,HTML,1,BODY,18,DIV,4,DIV,2,DIV,2,SECTION,3,DIV,0,DIV,0,DIV,0,SECTION,0,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,FIGURE,0,DIV,0,A,0,IMG

selector: figure.photo > div.image > a.tnt-asset-link > img.img-responsive

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
cmp.osano.com/16CVqQSid6k3038vU/fef0f8b2-698d-45ee-89c5-d8fbf51fbfb7/osano.js	78.1 KiB	2.5 s
/tucson.com/content/tncms/live/libraries/flex/components/...	3.8 KiB
/tucson.com/shared-content/art/tncms/templates/libraries/...	312 B
/tucson.com/shared-content/art/tncms/templates/libraries/...	12.7 KiB	152 ms
/recaptcha/enterprise.js?render=6LdF3BEhAAAAAEQUmLciJe0Qw...	1.1 KiB	786 ms
tucson.com/shared-content/art/stats/common/tracker.js	3.4 KiB
/tucson.com/content/tncms/live/libraries/flex/components/...	818 B
/tucson.com/shared-content/art/tncms/templates/libraries/...	1.5 KiB	152 ms
tucson.com/shared-content/art/tncms/tracking.js	1.4 KiB

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	5.0 ms

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
Arizona Daily Star `div.site-logo-container > a > figure > img.img-responsive`	/tucson.com/content/tncms/custom/image/109f1e80-afaf-11ec...	7.1 KiB	5.1 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 600 ms 70.4 KiB

URL	Transfer Size	Est Savings
/tucson.com/shared-content/art/tncms/templates/libraries/...	33.9 KiB	32.9 KiB
/tucson.com/shared-content/art/tncms/templates/libraries/...	21.0 KiB	19.3 KiB
/tucson.com/content/tncms/live/libraries/flex/components/...	21.4 KiB	18.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: 5.4 s 961.7 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.6 KiB	176.9 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	130.4 KiB
a.pub.network/tucson-com/prebid.js	187.4 KiB	126.9 KiB
a.pub.network/tucson-com/pubfig.engine.mobile.js	151.4 KiB	75.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-TDWDC2	203.1 KiB	68.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-5MTD44X&gtm=4e64m0h2	119.9 KiB	66.5 KiB
www.googletagmanager.com/gtag/js?id=G-QH8XG9MLHK&cx=c&gtm=4e64k1	171.1 KiB	65.1 KiB
www.googletagmanager.com/gtag/js?id=G-4T2EB147B8&cx=c&gtm=4e64m0h2	152.0 KiB	64.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-PDQV3N	120.8 KiB	61.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-WXMV2VZ&gtm=4e64m0h2	134.2 KiB	51.9 KiB
c.amazon-adsystem.com/aax2/apstag.js	90.4 KiB	50.2 KiB
tucson.com/shared-content/art/tncms/api/access.bc44532080f114b4be74.js	30.8 KiB	25.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
c.amazon-adsystem.com/aax2/apstag.js	2.2 s	2.1 s	33 ms
Unattributable	2.0 s	75 ms	0.0 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	1.9 s	1.7 s	95 ms
cmp.osano.com/16CVqQSid6k3038vU/fef0f8b2-698d-45ee-89c5-d8fbf51fbfb7/osano.js	1.6 s	1.2 s	56 ms
freestar.solutions.cdn.optable.co/public-assets/freestar-sdk.js	1.2 s	864 ms	6.1 ms
tucson.com/	1.0 s	128 ms	30 ms
/tucson.com/shared-content/art/tncms/templates/libraries/...	929 ms	814 ms	3.2 ms
www.googletagmanager.com/gtm.js?id=GTM-WXMV2VZ&gtm=4e64m0h2	847 ms	699 ms	65 ms
tagan.adlightning.com/leeenterprises/op.js	763 ms	693 ms	3.3 ms
config.aps.amazon-adsystem.com/configs/0ab198dd-b265-462a-ae36-74e163ad6159	664 ms	642 ms	12 ms
www.googletagmanager.com/gtm.js?id=GTM-TDWDC2	608 ms	481 ms	122 ms
a.pub.network/tucson-com/pubfig.engine.mobile.js	555 ms	486 ms	45 ms
www.googletagmanager.com/gtag/js?id=G-4T2EB147B8&cx=c&gtm=4e64m0h2	432 ms	372 ms	57 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	359 ms	259 ms	92 ms
www.googletagmanager.com/gtm.js?id=GTM-PDQV3N	310 ms	273 ms	34 ms
www.googletagmanager.com/gtag/js?id=G-QH8XG9MLHK&cx=c&gtm=4e64k1	291 ms	239 ms	49 ms
tagan.adlightning.com/leeenterprises/b-2d8eee8-5fbd0057.js	288 ms	254 ms	9.1 ms
a.pub.network/tucson-com/prebid.js	251 ms	187 ms	54 ms
/tucson.com/shared-content/art/tncms/templates/libraries/...	246 ms	177 ms	9.3 ms
www.googletagmanager.com/gtm.js?id=GTM-5MTD44X&gtm=4e64m0h2	213 ms	171 ms	40 ms
cmp.osano.com/16CVqQSid6k3038vU/fef0f8b2-698d-45ee-89c5-d8fbf51fbfb7/osano-ui.js	187 ms	131 ms	14 ms
/tucson.com/shared-content/art/tncms/templates/libraries/...	152 ms	82 ms	29 ms
a.pub.network/tucson-com/pubfig.min.js	144 ms	134 ms	6.6 ms
tagan.adlightning.com/leeenterprises/bl-0d6ee0c-81382bd7.js	136 ms	111 ms	24 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	101 ms	90 ms	9.9 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	13.0 s
Other	2.4 s
Script Parsing & Compilation	929 ms
Style & Layout	745 ms
Garbage Collection	661 ms
Parse HTML & CSS	248 ms
Rendering	197 ms

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
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.9 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-TDWDC2	203.2 KiB
a.pub.network/tucson-com/prebid.js	188.0 KiB
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB
www.googletagmanager.com/gtag/js?id=G-QH8XG9MLHK&cx=c&gtm=4e64k1	171.1 KiB
www.googletagmanager.com/gtag/js?id=G-4T2EB147B8&cx=c&gtm=4e64m0h2	152.0 KiB
a.pub.network/tucson-com/pubfig.engine.mobile.js	151.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-WXMV2VZ&gtm=4e64m0h2	134.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-PDQV3N	121.2 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Arizona Daily Star `div.offcanvas-menu-inner > div.in-drawer-logo > a > img.img-responsive`	/tucson.com/content/tncms/custom/image/109f1e80-afaf-11ec...
Arizona Daily Star `div.site-logo-container > a > figure > img.img-responsive`	/tucson.com/content/tncms/custom/image/109f1e80-afaf-11ec...
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`	/tucson.com/content/tncms/live/libraries/flex/components/...
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`	/tucson.com/content/tncms/live/libraries/flex/components/...
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`	/tucson.com/content/tncms/live/libraries/flex/components/...
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`	/tucson.com/content/tncms/live/libraries/flex/components/...

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 36 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 2 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 600 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 100 ms

○INP breakdown

○Avoid large layout shifts

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.

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
Deny Non-Essential `div.osano-cm-window > div#649b7539-a0e9-42ce-b2f0-18339f2e2847 > div.osano-cm-dialog__buttons > button.osano-cm-deny`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
cookie preferences `div.evvnt-widget-container > div#lee-consent-banner-events > div.panel-body > a`

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
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#site-container > div#tncms-region-global-above-header > div#tncms-block-2681787 > iframe `div#site-container > div#tncms-region-global-above-header > div#tncms-block-2681787 > iframe`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PARTNER `div.media-preview-ae17194e-e1b3-5f44-89eb-207867ea89bc > figure.photo > div.image > a.tnt-asset-link`
CONTRIBUTOR `div.media-preview-42a671b4-91f8-501d-bae2-e36882efa5bd > figure.photo > div.image > a.tnt-asset-link`

○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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

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

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

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

○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
Topics	a.pub.network/tucson-com/prebid.js line 88, col 1157

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
tucson.com/	`Access to fetch at 'https://api.rlcdn.com/api/identity/envelope?pid=106' from origin 'https://tucson.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
tucson.com/	`Access to fetch at 'https://api.rlcdn.com/api/identity/envelope?pid=106' from origin 'https://tucson.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
tucson.com/	`Access to fetch at 'https://api.rlcdn.com/api/identity/envelope?pid=106' from origin 'https://tucson.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
tucson.com/	`Access to fetch at 'https://api.rlcdn.com/api/identity/envelope?pid=106' from origin 'https://tucson.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
api.rlcdn.com/api/identity/envelope?pid=106	`Failed to load resource: net::ERR_FAILED`
api.rlcdn.com/api/identity/envelope?pid=106	`Failed to load resource: net::ERR_FAILED`
api.rlcdn.com/api/identity/envelope?pid=106	`Failed to load resource: net::ERR_FAILED`
api.rlcdn.com/api/identity/envelope?pid=106	`Failed to load resource: net::ERR_FAILED`

●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

●Page has valid source maps

○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
cookie preferences. `div.modal-body > ul > li > a`

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
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`
div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon `div.card-headline > h3.tnt-headline > a.tnt-asset-link > img.premium-icon`

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`