Skip to content
Audit Complete

Results for https://detroitnews.com

Visit site
Corporate / Enterprise · estimated Tracking: leads
Singapore Singapore · Singapore Completed: Apr 21, 2026 22:59 UTC
Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Room to improve — your 3.5s 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.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

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

Backbone.js · 32 peers
You 72
·
Avg 71
At average
0 50 100
Better than 59% of Backbone.js sites See full Backbone.js benchmark →
Confiant · 13 peers
You 72
·
Avg 72
At average
0 50 100
Better than 23% of Confiant sites See full Confiant benchmark →

Top Priorities (5)

1

HSTS header is missing

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

Security › Security Headers
2

Page weighs 13.6 MB (4.3 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
3

21 link(s) with no accessible text

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

Accessibility › Link & Button Quality
4

57 image-only link(s) without alt text

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

Accessibility › Link & Button Quality
5

578 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

1

High impact, low effort — start here.

Strategic

4

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fdetroitnews.com)](https://beavercheck.com/results/a90a3dd2-3fd8-4bf9-9c0e-c9f337f28f8b)
<a href="https://beavercheck.com/results/a90a3dd2-3fd8-4bf9-9c0e-c9f337f28f8b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdetroitnews.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fdetroitnews.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 3.5s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

1 security gap detected — browsers may warn visitors about your site.
Your LCP is 3.5s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

2 critical 6 warning

8 barrier(s) likely increasing bounce by ~25%.

Speed (2)

Page loads in 3.5s

+5% bounce

Every additional 100ms above 2.5s costs conversions — you're 1.0s over

Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image

Page feels frozen for 6.6s

+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 (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

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 (3)

21 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

30 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

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

Return on Investment

$750 investment → $1,948/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +3016%

Investment

$750

8h · 5 findings

Monthly returns

$1,948 /mo

~$23,372 / year

  • Conversions recovered $1,947
  • Bandwidth savings $1.07

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$50 — 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

$750

7.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$50 1 fixes in ~30 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,513 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • 7 advertising/retargeting trackers detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+4 more

Bandwidth Waste

$1.07 /mo

13435.7 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.3 MB per page load
    Saves $1.07/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

Unique monthly visitors from your analytics

Purchases, signups, or key actions

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

45
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

3.38 s

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

3.53 s

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

6.58 s

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

0.000

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

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

35.20 s

Detailed Report

Audit breakdown by category with detailed findings.

45

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:10.626 source:map[column:265327 line:1 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.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:0.556 source:map[column:193 line:4 type:source-location url:https://www.detroitnews.com/ urlProvider:network]] map[reflowTime:56.383 source:map[type:text value:[unattributed]]] map[reflowTime:4.898 source:map[column:805229 line:0 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:22.041 source:map[column:174866 line:0 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:0.546 source:map[column:174613 line:0 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:11.689 source:map[column:265799 line:0 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:25.335 source:map[column:463327 line:0 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:6.206 source:map[column:466484 line:0 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:4.103 source:map[column:468349 line:0 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:0.237 source:map[column:143578 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31097964 urlProvider:network]] map[reflowTime:0.709 source:map[column:241859 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31097964 urlProvider:network]] map[reflowTime:1.046 source:map[column:150036 line:0 type:source-location url:https://pixel.adsafeprotected.com/jload?anId=922805&campId=&pubId=36761088&chanId=mi-detroit-mobile-C1561%2Fmobileweb-adhesion%2Fhomepage&placementId=4507547420&pubCreative=138548531666&pubOrder=2197134673&cb=1776812157775&ias_adpath=%23ad-slot-7103-mi-detroit-C1561-mobileweb-adhesion-homepage-1-ac1 urlProvider:network]] map[reflowTime:0.163 source:map[column:213289 line:0 type:source-location url:https://pixel.adsafeprotected.com/jload?anId=922805&campId=&pubId=36761088&chanId=mi-detroit-mobile-C1561%2Fmobileweb-adhesion%2Fhomepage&placementId=4507547420&pubCreative=138548531666&pubOrder=2197134673&cb=1776812157775&ias_adpath=%23ad-slot-7103-mi-detroit-C1561-mobileweb-adhesion-homepage-1-ac1 urlProvider:network]] map[reflowTime:0.509 source:map[column:158104 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31097964 urlProvider:network]]]

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
value: No additional origins are good candidates for preconnecting

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.

RequestCache TTLTransfer Size
/r5TdgVvkbv-PeaJCKaQfCh5Xsto/gpt_and_prebid/config.js900.0 s92.3 KiB
client.aps.amazon-adsystem.com/publisher.js3600.0 s82.5 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s73.1 KiB
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js900.0 s21.7 KiB
/scripts/bundle/65568.js?sid=6384de98-7e2a-4671-b441-6ea4...3600.0 s18.0 KiB
www.detroitnews.com/gcdn/dcjs/prod/main.js3800.0 s17.4 KiB
c2.taboola.com/nr/gannettcompany-detroitnews/newsroom.js14400.0 s18.1 KiB
ep2.adtrafficquality.google/sodar/VFc2VJAc.js3000.0 s14.4 KiB
/jload?anId=922805&campId=0x0&pubId=5786919772&chanId=188...604800.0 s92.3 KiB
/jload?anId=922805&campId=&pubId=36761088&chanId=mi-detro...604800.0 s92.3 KiB
/jload?anId=922805&campId=&pubId=36761088&chanId=mi-detro...604800.0 s92.3 KiB
connectid.analytics.yahoo.com/connectId-gpt.js3600.0 s9.0 KiB
/publisher/922805/e8d59411-27ac-11f1-aa09-0e6958f30139.mi...0.0 ms6.9 KiB
static.criteo.net/js/ld/publishertag.ids.js86400.0 s14.8 KiB
eus.rubiconproject.com/usync.js54092.0 s11.5 KiB
/jsconfig/jload/922805?cbName=__IntegralAS__6552&anId=922...0.0 ms4.5 KiB
/jsconfig/jload/922805?cbName=__IntegralAS__1680&anId=922...0.0 ms4.5 KiB
/jsconfig/jload/922805?cbName=__IntegralAS__7066&anId=922...0.0 ms4.5 KiB
config.aps.amazon-adsystem.com/configs/30623600.0 s4.4 KiB
/1699216/trc/3/json?tim=1776812158764&data=%7B%22id%22%3A...0.0 ms2.2 KiB
cdn.brandmetrics.com/tag/f5e47f5ae82e4c48bbc1a7f9281ed95b/gannett_net.js3600.0 s2.6 KiB
pm-widget.taboola.com/gannett-network/load.js3600.0 s2.0 KiB
/pagead/js/r20260420/r20110914/client/qs_click_protection...1209600.0 s8.9 KiB
pagead2.googlesyndication.com/pagead/js/r20260420/r20110914/abg_lite_fy2021.js1209600.0 s8.4 KiB
sync.cootlogix.com/api/cookie?partnerId=rubiconut&userId=MO982YEH-F-1ADK0.0 ms496 B
static.adsafeprotected.com/iasADX.js604800.0 s4.5 KiB
/pagead/js/r20260420/r20110914/elements/html/omrhp_fy2021.js1209600.0 s3.3 KiB
/newsroom/1.0/gannettcompany-detroitnews/get-action?page....0.0 ms310 B
/p2?c1=2&cs_fpid=bf30810e-7115-4e3d-9092-0162bdbe9964&c2=...0.0 ms299 B
/track/cmb/generic?ttd_pid=sirnsvg&ttd_tpi=1&gdpr=0&gdpr_...0.0 ms254 B
/track/cmb/generic?gdpr=0&ttd_pid=054f32o&us_privacy=1---...0.0 ms254 B
/s/20611?bidder_id=246515&bidder_uuid=bf30810e-7115-4e3d-...0.0 ms208 B
/pagead/js/r20260420/r20110914/client/window_focus_fy2021.js1209600.0 s1.3 KiB
creativecdn.com/cm-notify?pi=taboola&tc=10.0 ms124 B
event.clientgear.com/cookie/taboola?partner=taboola0.0 ms106 B
/sg/casale-network/1/rtb-h/?taboola_hm=0&orig=video&us_pr...0.0 ms97 B
sync.taboola.com/sg/temurtbnative-network/1/rtb/0.0 ms97 B
sync.taboola.com/sg/unrulyrtb-network/1/rtb-h/?taboola_hm=OPTOUT0.0 ms97 B
/sg/stackadaptrtb-network/1/rtb-h?taboola_hm=o59n26EcVYBF...0.0 ms97 B
/st?cijs=convusmp&ttype=45&cisd=convusmp&cipid=66361655&c...0.0 ms43 B
/st?cijs=convusmp&ttype=157&cisd=convusmp&cipid=66361655&...0.0 ms43 B
/AdServer/ImgSync?p=160318&gdpr=&gdpr_consent=&pu=https%3...0.0 ms40 B
/AdServer/ImgSync?p=159706&gdpr=&gdpr_consent=&us_privacy...0.0 ms40 B
/sync?redirect=https%3A%2F%2Ftrc.taboola.com%2Fsg%2Finmob...0.0 ms17 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
eus.rubiconproject.com/usync.js54092.0 s0 B
ep2.adtrafficquality.google/sodar/VFc2VJAc.js3000.0 s0 B
pagead2.googlesyndication.com/pagead/js/r20260420/r20110914/abg_lite_fy2021.js1209600.0 s0 B
/pagead/js/r20260420/r20110914/client/qs_click_protection...1209600.0 s0 B
/pagead/js/r20260420/r20110914/elements/html/omrhp_fy2021.js1209600.0 s0 B
/pagead/js/r20260420/r20110914/client/window_focus_fy2021.js1209600.0 s0 B

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.

URLResource SizeEst Savings
head > link head > link
tpc.googlesyndication.com/simgad/17731416731659647415?580.9 KiB450.9 KiB
head > link head > link
tpc.googlesyndication.com/simgad/5343183098169938608?383.7 KiB303.0 KiB
Featured body > main.gnt_cw > div.gnt_m_dl
s0.2mdn.net/simgad/968934345099483377133.4 KiB30.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.

Estimated savings: 1.3 s
URLTime Spent
detroitnews.com/1.3 s
www.detroitnews.com/0.0 ms

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

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.

URLTotal CPU TimeScript EvaluationScript Parse
Unattributable4.7 s1.1 s0.0 ms
cdn.taboola.com/libtrc/gannett-network/loader.js3.4 s2.3 s505 ms
cdn.confiant-integrations.net/gptprebidnativevideo/202603241056/wrap.js2.3 s1.9 s76 ms
/pagead/managed/js/gpt/m202604200101/pubads_impl.js?cb=31...2.1 s1.8 s84 ms
www.detroitnews.com/1.7 s661 ms66 ms
/jsconfig/jload/922805?cbName=__IntegralAS__6552&anId=922...1.5 s1.3 s0.9 ms
vidstat.taboola.com/vpaid/units/36_0_9/infra/cmTagFEED_MANAGER.js967 ms828 ms89 ms
vidstat.taboola.com/lite-unit/5.7.0/UnitFeedManagerMobile.min.js890 ms795 ms15 ms
/jsconfig/jload/922805?cbName=__IntegralAS__1680&anId=922...696 ms633 ms1.1 ms
www.detroitnews.com/tangstatic/js/pbjsandwichdirecta9-q1a2z3a44d3739.min.js590 ms425 ms29 ms
www.googletagmanager.com/gtag/destination?id=AW-994302621&cx=c&gtm=4e64h1501 ms330 ms121 ms
www.detroitnews.com/gcdn/dcjs/prod/main.js499 ms486 ms7.8 ms
www.googletagmanager.com/gtag/destination?id=DC-9782452&cx=c&gtm=4e64h1429 ms310 ms104 ms
static.adsafeprotected.com/sca.17.6.4.js416 ms342 ms60 ms
client.aps.amazon-adsystem.com/publisher.js399 ms293 ms48 ms
www.detroitnews.com/gcdn/dcjs/prod/p/p-q1a2z3aQ7mR2Kx.min.js295 ms230 ms8.1 ms
www.googletagmanager.com/gtag/js?id=G-5JJXNTWR1D251 ms187 ms62 ms
pm-widget.taboola.com/gannett-network/pmk-20220605.23.js197 ms179 ms13 ms
vidstat.taboola.com/vpaid/vPlayer/player/v18.0.4/OvaMediaPlayer.js197 ms126 ms62 ms
/jload?anId=922805&campId=&pubId=36761088&chanId=mi-detro...178 ms104 ms44 ms
/jload?anId=922805&campId=&pubId=36761088&chanId=mi-detro...168 ms107 ms57 ms
vidstat.taboola.com/vpaid/vPlayer/player/v18.0.4/TBPrebidHandler.js163 ms127 ms30 ms
/scripts/bundle/65568.js?sid=6384de98-7e2a-4671-b441-6ea4...163 ms136 ms9.8 ms
securepubads.g.doubleclick.net/tag/js/gpt.js131 ms116 ms15 ms
c2.taboola.com/nr/gannettcompany-detroitnews/newsroom.js126 ms112 ms12 ms
static.criteo.net/js/ld/publishertag.ids.js120 ms113 ms5.6 ms
ep2.adtrafficquality.google/sodar/sodar2.js117 ms109 ms3.2 ms
/r5TdgVvkbv-PeaJCKaQfCh5Xsto/gpt_and_prebid/config.js100 ms39 ms61 ms
vidstat.taboola.com/vpaid/vPlayer/player/v18.0.4/TBamxPrebidHandler.js96 ms74 ms18 ms
vidstat.taboola.com/vpaid/vPlayer/player/v18.0.4/TBrubiconPrebidHandler.js86 ms57 ms25 ms
vidstat.taboola.com/vpaid/units/36_0_9/infra/cmAdService.js85 ms76 ms6.3 ms
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js80 ms70 ms9.4 ms
config.aps.amazon-adsystem.com/configs/306278 ms59 ms11 ms
connectid.analytics.yahoo.com/connectId-gpt.js59 ms54 ms1.4 ms
www.detroitnews.com/tangstatic/js/mainm-q1a2z38bc52415.min.js58 ms44 ms11 ms
static.adsafeprotected.com/iasADX.js55 ms53 ms2.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.

CategoryTime Spent
Script Evaluation15.9 s
Other4.4 s
Script Parsing & Compilation1.7 s
Style & Layout982 ms
Garbage Collection748 ms
Rendering124 ms
Parse HTML & CSS119 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 reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 89.8 KiB
URLTransfer SizeEst Savings
cdn.taboola.com/libtrc/gannett-network/loader.js454.2 KiB89.8 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.

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

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
Render blocking requests
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 52 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 250 ms
Server Backend Latencies 1,890 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 240 ms
INP breakdown
LCP request discovery
Avoid non-composited animations
Avoid large layout shifts
96

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.

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
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link

These items highlight common accessibility best practices.

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
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_mobile_disclosure_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
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
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
`<frame>` or `<iframe>` elements have a title
`<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
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
Identical links have the same purpose.
`[accesskey]` values are unique
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
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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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.
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.
77

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 / WarningSource
Topics

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.

SourceDescription
Access to fetch at 'https://rp.liadm.com/p?aid=a-048s&pu=https%3A%2F%2Fwww.detroitnews.com%2F&ext_gannett=bf30810e-7115-4e3d-9092-0162bdbe9964&n3pc=true' from origin 'https://www.detroitnews.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 400 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
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
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
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
92

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
Image for Taboola Advertising Unit div#rbox-h2v > div#internal_trc_6268672689 > div.videoCube > a.item-thumbnail-href
This may be of interest to you! Ad div#rbox-h2v > div#internal_trc_6268672689 > div.videoCube > a.item-label-href

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
Links have descriptive text
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

57
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
93
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.34 s

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

1.47 s

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

597 ms

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

0.070

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

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

8.71 s

Detailed Report

Audit breakdown by category with detailed findings.

57

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.203 source:map[column:326551 line:19 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.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:85.988 source:map[column:165 line:121 type:source-location url:https://www.detroitnews.com/ urlProvider:network]] map[reflowTime:27.986 source:map[type:text value:[unattributed]]] map[reflowTime:0.257 source:map[column:11 line:249 type:source-location url:https://www.detroitnews.com/tangstatic/js/pbjsandwichdirecta9-q1a2z3a44d3739.min.js urlProvider:network]] map[reflowTime:0.354 source:map[column:237248 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.js urlProvider:network]] map[reflowTime:2.491 source:map[column:241855 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.js urlProvider:network]] map[reflowTime:0.1 source:map[column:243205 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.js urlProvider:network]] map[reflowTime:0.087 source:map[column:241695 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.js urlProvider:network]] map[reflowTime:0.133 source:map[column:713957 line:80 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:19.164 source:map[column:102033 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.js urlProvider:network]] map[reflowTime:0.402 source:map[column:709 line:300 type:source-location url:https://pagead2.googlesyndication.com/pagead/managed/js/activeview/current/ufs_web_display.js urlProvider:network]] map[reflowTime:0.154 source:map[column:143046 line:18 type:source-location url:https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.js urlProvider:network]] map[reflowTime:0.683 source:map[column:117700 line:80 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:0.143 source:map[column:213289 line:0 type:source-location url:https://pixel.adsafeprotected.com/jload?anId=922805&campId=&pubId=36761088&chanId=mi-detroit-C1561%2Fadhesion%2Fhomepage&placementId=4507547420&pubCreative=138548531666&pubOrder=2197134673&cb=1776812244928&ias_adpath=%23ad-slot-7103-mi-detroit-C1561-adhesion-homepage-13-ac1 urlProvider:network]] map[reflowTime:2.424 source:map[column:521869 line:80 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:0.494 source:map[column:521925 line:80 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:29.291 source:map[column:462502 line:80 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:4.25 source:map[column:488377 line:80 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]] map[reflowTime:1.16 source:map[column:465659 line:80 type:source-location url:https://cdn.taboola.com/libtrc/gannett-network/loader.js urlProvider:network]]]

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
value: No additional origins are good candidates for preconnecting

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.

RequestCache TTLTransfer Size
/r5TdgVvkbv-PeaJCKaQfCh5Xsto/gpt_and_prebid/config.js900.0 s92.3 KiB
client.aps.amazon-adsystem.com/publisher.js3600.0 s82.5 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s73.1 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s73.1 KiB
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js900.0 s21.7 KiB
s0.2mdn.net/879366/express_html_inpage_rendering_lib_200_287.js86400.0 s40.5 KiB
/scripts/bundle/65568.js?sid=6384de98-7e2a-4671-b441-6ea4...3600.0 s18.0 KiB
www.detroitnews.com/gcdn/dcjs/prod/main.js3800.0 s17.6 KiB
c2.taboola.com/nr/gannettcompany-detroitnews/newsroom.js14400.0 s18.1 KiB
ep2.adtrafficquality.google/sodar/VFc2VJAc.js3000.0 s14.4 KiB
/jload?anId=922805&campId=0x0&pubId=5786919772&chanId=151...604800.0 s92.3 KiB
/jload?anId=922805&campId=&pubId=36761088&chanId=mi-detro...604800.0 s92.3 KiB
/jload?anId=922805&campId=&pubId=36761088&chanId=mi-detro...604800.0 s92.3 KiB
/jload?anId=922805&campId=300x600&pubId=13220208&chanId=1...604800.0 s92.3 KiB
connectid.analytics.yahoo.com/connectId-gpt.js3600.0 s9.0 KiB
/publisher/922805/e8d59411-27ac-11f1-aa09-0e6958f30139.mi...0.0 ms6.9 KiB
static.criteo.net/js/ld/publishertag.ids.js86400.0 s14.8 KiB
eus.rubiconproject.com/usync.js54004.0 s11.5 KiB
/jsconfig/jload/922805?cbName=__IntegralAS__1539&anId=922...0.0 ms4.5 KiB
/jsconfig/jload/922805?cbName=__IntegralAS__7886&anId=922...0.0 ms4.5 KiB
/jsconfig/jload/922805?cbName=__IntegralAS__8357&anId=922...0.0 ms4.5 KiB
/jsconfig/jload/922805?cbName=__IntegralAS__3779&anId=922...0.0 ms4.4 KiB
config.aps.amazon-adsystem.com/configs/30623600.0 s4.4 KiB
/1699216/trc/3/json?tim=1776812246616&data=%7B%22id%22%3A...0.0 ms2.3 KiB
cdn.brandmetrics.com/tag/f5e47f5ae82e4c48bbc1a7f9281ed95b/gannett_net.js3600.0 s2.6 KiB
pm-widget.taboola.com/gannett-network/load.js3600.0 s2.0 KiB
pagead2.googlesyndication.com/pagead/js/r20260420/r20110914/abg_lite.js1209600.0 s10.5 KiB
/s/464/9.gif?puid=eab638cc-5c62-48b2-9e5f-91d85979204f-tu...0.0 ms916 B
/pagead/js/r20260420/r20110914/client/qs_click_protection...1209600.0 s8.5 KiB
pagead2.googlesyndication.com/pagead/js/r20260420/r20110914/abg_lite_fy2021.js1209600.0 s8.4 KiB
/image/v1.0.0/bin/695bce48b45f0f3d893eed9d?v=8dacc&h=118&...432000.0 s5.4 KiB
sync.cootlogix.com/api/cookie?partnerId=rubiconut&userId=MO984V0N-1F-5HSM0.0 ms497 B
/pagead/js/r20260420/r20110914/elements/html/omrhp.js1209600.0 s4.7 KiB
static.adsafeprotected.com/iasADX.js604800.0 s4.5 KiB
/pagead/js/r20260420/r20110914/elements/html/omrhp_fy2021.js1209600.0 s3.3 KiB
cs.media.net/cksync.php?cs=80.0 ms330 B
/p2?c1=2&cs_fpid=c2a54d0b-e868-4212-8d3e-962ecb1a6440&c2=...0.0 ms298 B
/newsroom/1.0/gannettcompany-detroitnews/get-action?page....0.0 ms291 B
/track/cmb/generic?ttd_pid=sirnsvg&ttd_tpi=1&gdpr=0&gdpr_...0.0 ms254 B
/track/cmb/generic?gdpr=0&ttd_pid=054f32o&us_privacy=1---...0.0 ms254 B
/s/20611?bidder_id=246515&bidder_uuid=c2a54d0b-e868-4212-...0.0 ms208 B
/pagead/js/r20260420/r20110914/client/window_focus_fy2021.js1209600.0 s1.6 KiB
creativecdn.com/cm-notify?pi=taboola&tc=10.0 ms124 B
/pagead/js/r20260420/r20110914/client/window_focus_fy2021.js1209600.0 s1.2 KiB
event.clientgear.com/cookie/taboola?partner=taboola0.0 ms106 B
/sg/casale-network/1/rtb-h/?taboola_hm=0&orig=video&us_pr...0.0 ms97 B
sync.taboola.com/sg/temurtbnative-network/1/rtb/0.0 ms97 B
sync.taboola.com/sg/unrulyrtb-network/1/rtb-h/?taboola_hm=OPTOUT0.0 ms97 B
/sg/stackadaptrtb-network/1/rtb-h?taboola_hm=o59n26EcVYBF...0.0 ms97 B
/st?cijs=convusmp&ttype=45&cisd=convusmp&cipid=66361655&c...0.0 ms43 B
/st?cijs=convusmp&ttype=157&cisd=convusmp&cipid=66361655&...0.0 ms43 B
/AdServer/ImgSync?p=160318&gdpr=&gdpr_consent=&pu=https%3...0.0 ms40 B
/AdServer/ImgSync?p=159706&gdpr=&gdpr_consent=&us_privacy...0.0 ms40 B
/AdServer/ImgSync?p=158355&gdpr=0&us_privacy=1---&pu=http...0.0 ms40 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
/pagead/managed/js/activeview/current/ufs_web_display.js3600.0 s0 B
eus.rubiconproject.com/usync.js54004.0 s0 B
ep2.adtrafficquality.google/sodar/VFc2VJAc.js3000.0 s0 B
/pagead/js/r20260420/r20110914/client/qs_click_protection...1209600.0 s0 B
/pagead/js/r20260420/r20110914/client/window_focus_fy2021.js1209600.0 s0 B

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.

URLResource SizeEst Savings
head > link head > link
tpc.googlesyndication.com/simgad/17731416731659647415?580.9 KiB450.9 KiB
head > link head > link
s0.2mdn.net/simgad/10476725157585828394131.9 KiB121.2 KiB
Featured body > main.gnt_cw > div.gnt_pr > div.gnt_m_dl
s0.2mdn.net/simgad/14043767416109488940100.7 KiB90.1 KiB
/sadbundle/11131669312510405423/images/fd90a2157c81e0e266...24.0 KiB13.4 KiB

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: 762 ms
URLTime Spent
detroitnews.com/762 ms
www.detroitnews.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

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.

URLTotal CPU TimeScript EvaluationScript Parse
Unattributable1.1 s160 ms0.0 ms
cdn.taboola.com/libtrc/gannett-network/loader.js1.0 s778 ms106 ms
cdn.confiant-integrations.net/gptprebidnativevideo/202603241056/wrap.js954 ms828 ms29 ms
www.detroitnews.com/413 ms147 ms11 ms
vidstat.taboola.com/vpaid/units/36_0_9/infra/cmTagFEED_MANAGER.js238 ms194 ms33 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js205 ms137 ms21 ms
www.detroitnews.com/tangstatic/js/pbjsandwichdirecta9-q1a2z3a44d3739.min.js182 ms127 ms7.8 ms
vidstat.taboola.com/lite-unit/5.7.0/UnitFeedManagerDesktop.min.js181 ms162 ms3.3 ms
/pagead/managed/js/activeview/current/ufs_web_display.js172 ms134 ms8.2 ms
/jsconfig/jload/922805?cbName=__IntegralAS__7886&anId=922...131 ms113 ms0.3 ms
/jload?anId=922805&campId=300x600&pubId=13220208&chanId=1...123 ms101 ms12 ms
/jsconfig/jload/922805?cbName=__IntegralAS__8357&anId=922...114 ms104 ms0.3 ms
www.detroitnews.com/gcdn/dcjs/prod/main.js108 ms104 ms1.9 ms
www.googletagmanager.com/gtag/destination?id=AW-994302621&cx=c&gtm=4e64h1104 ms87 ms16 ms
static.adsafeprotected.com/sca.17.6.4.js97 ms80 ms13 ms
/jsconfig/jload/922805?cbName=__IntegralAS__3779&anId=922...95 ms92 ms0.2 ms
www.googletagmanager.com/gtag/destination?id=DC-9782452&cx=c&gtm=4e64h191 ms72 ms18 ms
client.aps.amazon-adsystem.com/publisher.js89 ms67 ms12 ms
www.detroitnews.com/gcdn/dcjs/prod/p/p-q1a2z3aQ7mR2Kx.min.js83 ms66 ms2.4 ms
www.googletagmanager.com/gtag/js?id=G-5JJXNTWR1D70 ms50 ms19 ms
pm-widget.taboola.com/gannett-network/pmk-20220605.23.js58 ms53 ms3.6 ms
static.criteo.net/js/ld/publishertag.ids.js57 ms55 ms1.7 ms
/jload?anId=922805&campId=&pubId=36761088&chanId=mi-detro...53 ms30 ms13 ms
vidstat.taboola.com/vpaid/vPlayer/player/v18.0.4/OvaMediaPlayer.js52 ms31 ms19 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.

CategoryTime Spent
Script Evaluation4.1 s
Other1.2 s
Script Parsing & Compilation424 ms
Style & Layout270 ms
Garbage Collection177 ms
Rendering45 ms
Parse HTML & CSS40 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 reasonFailure type
The page has an unload handler in the main frame.Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable
An iframe on the page started a navigation that did not complete.Not actionable
The page did not finish loading before navigating away.Not actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 90.2 KiB
URLTransfer SizeEst Savings
cdn.taboola.com/libtrc/gannett-network/loader.js455.9 KiB90.2 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.

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

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
Render blocking requests
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 49 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 250 ms
Server Backend Latencies 2,030 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 250 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
LCP request discovery
Avoid non-composited animations
93

Accessibility

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

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Jalen Duren scored just four points on 3-of-4 shooting in Sunday's 112-101 loss… div.gnt_pr > div.gnt_m > aside.gnt_em > div.gnt_em_vb

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

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > header.gnt_n > div.gnt_n_sm > a.gnt_n_sm_a body > header.gnt_n > div.gnt_n_sm > a.gnt_n_sm_a

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
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_desktop_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_desktop_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_desktop_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_desktop_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_desktop_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_desktop_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_desktop_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_desktop_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_desktop_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_desktop_disclosure_link
Ad span.video-label-box > span.branding > div.logoDiv > a.trc_desktop_disclosure_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
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
All heading elements contain content.
Identical links have the same purpose.
`[accesskey]` values are unique
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
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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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>`.
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.
77

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.

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.

SourceDescription
Access to fetch at 'https://rp.liadm.com/p?aid=a-048s&pu=https%3A%2F%2Fwww.detroitnews.com%2F&ext_gannett=c2a54d0b-e868-4212-8d3e-962ecb1a6440&n3pc=true' from origin 'https://www.detroitnews.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 400 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 429 ()
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
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
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
92

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
Image for Taboola Advertising Unit div#rbox-h2v > div#internal_trc_7646197646 > div.videoCube > a.item-thumbnail-href
Brought to you by Ad div#rbox-h2v > div#internal_trc_7646197646 > div.videoCube > a.item-label-href

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
Links have descriptive text
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback