Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
embed.bsky.app/static/post-Dpr8L3vQ.js	3600.0 s	196.4 KiB
/snippet/account/197969654?site=b0837ae46d2e1c5548e98be52	60.0 s	109.2 KiB
/img/feed_thumbnail/plain/did:plc:q5qyswhppr7tiskw43xhcv7...	604800.0 s	50.1 KiB
embed.bsky.app/static/post-Bf-Bk7gq.css	3600.0 s	4.6 KiB
/img/avatar/plain/did:plc:nx7znvoex7ev3wcxn3tipovm/bafkre...	604800.0 s	36.0 KiB
/img/feed_thumbnail/plain/did:plc:nl32untxngcg74dl3w7scd7...	604800.0 s	31.7 KiB
/img/avatar/plain/did:plc:q5qyswhppr7tiskw43xhcv7f/bafkre...	604800.0 s	26.9 KiB
cdn-images.mailchimp.com/embedcode/classic-061523.css	0.0 ms	1.8 KiB
embed.bsky.app/static/post--upFnwpE.js	3600.0 s	2.1 KiB
/img/avatar/plain/did:plc:nl32untxngcg74dl3w7scd74/bafkre...	604800.0 s	16.4 KiB
/mcjs-connected/js/users/d2541b6e3f9f2182b8be74d8f/b0837a...	154.0 s	1.5 KiB
embed.bsky.app/static/embed.js	3600.0 s	1.4 KiB
embed.bsky.app/static/post-Dpr8L3vQ.js	3600.0 s	0 B
embed.bsky.app/static/post-Bf-Bk7gq.css	3600.0 s	0 B
embed.bsky.app/static/post--upFnwpE.js	3600.0 s	0 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: President Trump Holds News Conference With Military Officials

path: 2,HTML,1,BODY,51,DIV,0,DIV,22,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,A,0,IMG

selector: div.rm-col-center > div.widget__head > a.rm-stats-tracked > img.rm-lazyloadable-image

snippet: <img role="img" alt="President Trump Holds News Conference With Military Officials" aria-label="President Trump Holds News Conference With Military Officials" src="https://www.commondreams.org/media-library/president-trump-holds-news-conf…" style="object-fit: cover;" class="rm-lazyloadable-image" width="1245" height="700" data-adjusted-src="true">

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
/s/oswald/v49/TK3IWkUHHAIjg75cFRf3bXL8LICs1_Fv40pKlN4NNSe...	20 ms

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
cdn-images.mailchimp.com/embedcode/classic-061523.css	1.8 KiB	838 ms

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: 1.1 s

URL	Time Spent
commondreams.org/	1.1 s
www.commondreams.org/	0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.2 s 598.7 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-2GRK1GCCCD	169.8 KiB	114.7 KiB
s3.amazonaws.com/downloads.mailchimp.com/js/mc-validate.js	139.9 KiB	91.4 KiB
s3.amazonaws.com/downloads.mailchimp.com/js/mc-validate.js	139.9 KiB	91.4 KiB
s3.amazonaws.com/downloads.mailchimp.com/js/mc-validate.js	139.9 KiB	90.7 KiB
/snippet/account/197969654?site=b0837ae46d2e1c5548e98be52	108.7 KiB	78.6 KiB
www.googletagmanager.com/gtag/js?id=G-2GRK1GCCCD&cx=c&gtm=4e64h1	169.8 KiB	69.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-W7VP43JM	137.3 KiB	62.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 13.0 KiB

URL	Transfer Size	Est Savings
.rm-embed-container{position:relative;} …	23.4 KiB	13.0 KiB

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,505 KiB

●User Timing marks and measures 7 user timings

●JavaScript execution time 1.0 s

●Minimizes main-thread work 1.8 s

●Avoid long main-thread tasks 9 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 120 ms

●Server Backend Latencies 170 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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

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
div#sSHARED_-_Newsletter_0_0_7_0_0_2_1_0_0 > div#sFollow_Block_0_0_2_0_0_0 > div#sFollow_Block_0_0_2_0_0_0_1 > a.social_icon `div#sSHARED_-_Newsletter_0_0_7_0_0_2_1_0_0 > div#sFollow_Block_0_0_2_0_0_0 > div#sFollow_Block_0_0_2_0_0_0_1 > a.social_icon`
div#sSHARED_-_Newsletter_0_0_7_0_0_2_1_0_0 > div#sFollow_Block_0_0_2_0_0_0 > div#sFollow_Block_0_0_2_0_0_0_1 > a.social_icon `div#sSHARED_-_Newsletter_0_0_7_0_0_2_1_0_0 > div#sFollow_Block_0_0_2_0_0_0 > div#sFollow_Block_0_0_2_0_0_0_1 > a.social_icon`
div#sSHARED_-_Newsletter_0_0_7_0_0_2_1_0_0 > div#sFollow_Block_0_0_2_0_0_0 > div#sFollow_Block_0_0_2_0_0_0_1 > a.social_icon `div#sSHARED_-_Newsletter_0_0_7_0_0_2_1_0_0 > div#sFollow_Block_0_0_2_0_0_0 > div#sFollow_Block_0_0_2_0_0_0_1 > a.social_icon`
div#sElement_HomePage_Tabbed_Wrap_0_0_1_0_0_1_0 > div.tabs__body > div#opinion > a `div#sElement_HomePage_Tabbed_Wrap_0_0_1_0_0_1_0 > div.tabs__body > div#opinion > 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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

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

●Input buttons have discernible text.

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

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○No form fields have multiple labels

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

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

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

○No element has a `[tabindex]` value greater than 0

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

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

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●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 browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Guardian op-ed `div.body > div.body-description > p > a`

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`