Lighthouse Mobile
· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.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.
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
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
head > link head > link | tpc.googlesyndication.com/simgad/17731416731659647415? | 580.9 KiB | 450.9 KiB |
head > link head > link | tpc.googlesyndication.com/simgad/5343183098169938608? | 383.7 KiB | 303.0 KiB |
Featured body > main.gnt_cw > div.gnt_m_dl | s0.2mdn.net/simgad/9689343450994833771 | 33.4 KiB | 30.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.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time 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.
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.
Performance issues directly impact user engagement and conversion rates.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 15.9 s |
| Other | 4.4 s |
| Script Parsing & Compilation | 1.7 s |
| Style & Layout | 982 ms |
| Garbage Collection | 748 ms |
| Rendering | 124 ms |
| Parse HTML & CSS | 119 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.taboola.com/libtrc/gannett-network/loader.js | 454.2 KiB | 89.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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| .trc_rbox_container { direction: ltr; text-align: left; } … | 22.2 KiB | 17.5 KiB |
| :root { --cm-video-brand-primary: var(--yb-grape-jelly, #7e1fff); --cm-video-brand-secondary: v… | 16.0 KiB | 15.5 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.
Performance issues directly impact user engagement and conversion rates.
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
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 |
Best Practices
General
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| 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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
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 () |
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
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.