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 forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:32.622 source:map[type:text value:[unattributed]]]]

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: Tale of a Riderless Horse

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

selector: article.gh-card > a.gh-card-link > figure.gh-card-image > img

snippet: <img srcset="https://storage.ghost.io/c/51/f8/51f871d8-b6be-4a73-b958-0ca4fff0110a/cont…" sizes="(max-width: 767px) calc(100vw - max(8vmin, 40px)), 640px" src="https://storage.ghost.io/c/51/f8/51f871d8-b6be-4a73-b958-0ca4fff0110a/cont…" alt="Tale of a Riderless Horse">

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.

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

value: no origins were preconnected

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.

Request	Cache TTL	Transfer Size
cdn.jsdelivr.net/ghost/portal@~2.68/umd/portal.min.js	600.0 s	436.9 KiB
js.stripe.com/v3/	120.0 s	225.7 KiB
cdn.jsdelivr.net/ghost/sodo-search@~1.8/umd/sodo-search.min.js	600.0 s	98.0 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	73.1 KiB
m.stripe.network/out-4.5.45.js	300.0 s	16.5 KiB
pagead2.googlesyndication.com/pagead/show_companion_ad.js?fcd=true	3600.0 s	11.7 KiB
/pagead/js/r20260422/r20110914/client/window_focus_fy2021.js	1209600.0 s	1.6 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	3600.0 s	0 B
/pagead/js/r20260422/r20110914/client/window_focus_fy2021.js	1209600.0 s	0 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.

	URL	Resource Size	Est Savings
body > div#google_image_div > a#aw0 > img.img_ad `body > div#google_image_div > a#aw0 > img.img_ad`	tpc.googlesyndication.com/simgad/7480398006598912911	195.8 KiB	170.8 KiB
Hyperallergic `div.gh-navigation-inner > div.gh-navigation-brand > a.gh-navigation-logo > img`	/c/51/f8/51f871d8-b6be-4a73-b958-0ca4fff0110a/content/ima...	8.4 KiB	5.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
hyperallergic.com/public/cards.min.css?v=ecfb130846	7.7 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	986 ms	283 ms	0.0 ms
hyperallergic.com/	740 ms	30 ms	12 ms
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	702 ms	514 ms	92 ms
/pagead/managed/js/activeview/current/ufs_web_display.js	700 ms	574 ms	65 ms
cdn.jsdelivr.net/ghost/portal@~2.68/umd/portal.min.js	656 ms	394 ms	253 ms
fundingchoicesmessages.google.com/i/16307266?ers=3	523 ms	486 ms	25 ms
js.stripe.com/v3/	385 ms	253 ms	125 ms
hyperallergic.com/public/comment-counts.min.js?v=ecfb130846	338 ms	325 ms	0.4 ms
assets.context.ly/kit/6.latest/loader.js	257 ms	188 ms	2.3 ms
cdn.jsdelivr.net/ghost/sodo-search@~1.8/umd/sodo-search.min.js	168 ms	131 ms	31 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	146 ms	111 ms	34 ms
/_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads...	80 ms	16 ms	0.0 ms
ep2.adtrafficquality.google/sodar/sodar2.js	69 ms	64 ms	2.2 ms
/f/AGSKWxXdpxBR6S8mGDqEsxj-8lerv2RIMKWx-PK7dqqdEnEXmx1Jtp...	53 ms	42 ms	0.5 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	3.7 s
Other	1.1 s
Script Parsing & Compilation	673 ms
Style & Layout	511 ms
Parse HTML & CSS	130 ms
Garbage Collection	91 ms
Rendering	76 ms

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 24.2 KiB

URL	Transfer Size	Est Savings
.ctx-overlay{position:fixed!important;top:0!important;left:0!important;width:100%!important; … } …	24.2 KiB	24.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 496.5 KiB

URL	Transfer Size	Est Savings
js.stripe.com/v3/	225.3 KiB	163.9 KiB
/pagead/managed/js/gpt/m202604170101/pubads_impl.js?cb=31...	187.4 KiB	98.9 KiB
cdn.jsdelivr.net/ghost/portal@~2.68/umd/portal.min.js	366.7 KiB	84.1 KiB
cdn.jsdelivr.net/ghost/sodo-search@~1.8/umd/sodo-search.min.js	91.8 KiB	51.2 KiB
fundingchoicesmessages.google.com/i/16307266?ers=3	68.5 KiB	36.4 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	73.1 KiB	31.0 KiB
/pagead/managed/js/activeview/current/ufs_web_display.js	73.1 KiB	31.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Hyperallergic `div.gh-navigation-inner > div.gh-navigation-brand > a.gh-navigation-logo > img`	/c/51/f8/51f871d8-b6be-4a73-b958-0ca4fff0110a/content/ima...
Hyperallergic `div.gh-footer-inner > div.gh-footer-bar > span.gh-footer-logo > img`	/c/51/f8/51f871d8-b6be-4a73-b958-0ca4fff0110a/content/ima...

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,372 KiB

●Avoid long main-thread tasks 19 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 290 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

○INP breakdown

○User Timing marks and measures

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Sponsored `article.gh-card > a.gh-card-link > div.gh-card-wrapper > p.gh-card-tag`

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

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

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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

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

●Elements use only permitted ARIA attributes

●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 have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

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

○Elements with visible text labels have matching accessible names.

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

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	/pagead/managed/js/activeview/current/ufs_web_display.js line 252, col 234

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

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

100

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.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`