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.

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: div.flickity-slider > div.Slide_slide__rCm5b > figure > img.object-cover

path: 1,HTML,1,BODY,4,MAIN,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,IMG

selector: div.flickity-slider > div.Slide_slide__rCm5b > figure > img.object-cover

snippet: <img alt="" loading="lazy" decoding="async" data-nimg="fill" class="object-cover" style="position: absolute; height: 100%; width: 100%; inset: 0px;" sizes="(min-width: 1440px) 1440px, 100vw" srcset="/_next/image?url=https%3A%2F%2Fcraft-assets-ucpress-production.s3.amazonaw…" src="https://www.ucpress.edu/_next/image?url=https%3A%2F%2Fcraft-assets-ucpress…">

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

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
www.ucpress.edu/_next/static/css/70363724b3929a5a.css	899 B
www.ucpress.edu/_next/static/css/5409ca8d1befd620.css	1.6 KiB
www.ucpress.edu/_next/static/css/d26cfd1c0122b5e6.css	1.4 KiB
www.ucpress.edu/_next/static/css/a4daba70e9c32d7d.css	9.1 KiB
www.ucpress.edu/_next/static/css/030a9d0cb98909ff.css	954 B
www.ucpress.edu/_next/static/css/0e08852c6f8d5e76.css	464 B
www.ucpress.edu/_next/static/css/294ac286e084dc30.css	4.0 KiB
www.ucpress.edu/_next/static/css/e779ab8d57497496.css	1002 B
www.ucpress.edu/_next/static/css/78720366cca2d000.css	7.0 KiB	299 ms

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
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB

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
div.Slide_slide__rCm5b > a.FeaturedItems_slideshow__slideLink__WkCAC > figure.CoverImage_figure__g9g40 > img `div.Slide_slide__rCm5b > a.FeaturedItems_slideshow__slideLink__WkCAC > figure.CoverImage_figure__g9g40 > img`	/_next/image?url=https%3A%2F%2Fwebfiles.ucpress.edu%2Fcov...	65.9 KiB	46.2 KiB
div.flex > a.PodcastBlock_bookLink__aiP8C > figure.CoverImage_figure__g9g40 > img `div.flex > a.PodcastBlock_bookLink__aiP8C > figure.CoverImage_figure__g9g40 > img`	/_next/image?url=https%3A%2F%2Fwebfiles.ucpress.edu%2Fcov...	26.7 KiB	16.8 KiB
div.Slide_slide__rCm5b > a.FeaturedItems_slideshow__slideLink__WkCAC > figure.CoverImage_figure__g9g40 > img `div.Slide_slide__rCm5b > a.FeaturedItems_slideshow__slideLink__WkCAC > figure.CoverImage_figure__g9g40 > img`	/_next/image?url=https%3A%2F%2Fwebfiles.ucpress.edu%2Fcov...	18.9 KiB	13.2 KiB
div.flex > a.PodcastBlock_bookLink__aiP8C > figure.CoverImage_figure__g9g40 > img `div.flex > a.PodcastBlock_bookLink__aiP8C > figure.CoverImage_figure__g9g40 > img`	/_next/image?url=https%3A%2F%2Fwebfiles.ucpress.edu%2Fcov...	20.1 KiB	12.1 KiB
li.mt-rowMd > div.Content_card__cTve3 > div.BlogPost_post__image__16p_p > img.object-cover `li.mt-rowMd > div.Content_card__cTve3 > div.BlogPost_post__image__16p_p > img.object-cover`	/_next/image?url=https%3A%2F%2Fcraft-assets-ucpress-produ...	35.2 KiB	5.9 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: 1.3 s

URL	Time Spent
ucpress.edu/	1.3 s
www.ucpress.edu/	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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.ucpress.edu/	871 ms	25 ms	26 ms
Unattributable	571 ms	105 ms	0.0 ms
www.ucpress.edu/_next/static/chunks/2117-20652d18b489048f.js	492 ms	429 ms	11 ms
www.ucpress.edu/_next/static/chunks/8629-2178701f3c2d0682.js	369 ms	287 ms	81 ms
www.googletagmanager.com/gtag/js?id=G-4V7DMTJFQH&cx=c&gtm=4e64k0h1	196 ms	149 ms	46 ms
www.googletagmanager.com/gtm.js?id=GTM-TWP2FC7	175 ms	137 ms	29 ms
www.ucpress.edu/_next/static/chunks/fd9d1056-5bae34bee59f3468.js	155 ms	133 ms	12 ms
www.ucpress.edu/_next/static/chunks/8463.930052e3b086997c.js	88 ms	39 ms	3.2 ms
www.google-analytics.com/analytics.js	53 ms	42 ms	4.1 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	1.4 s
Other	656 ms
Style & Layout	465 ms
Script Parsing & Compilation	247 ms
Rendering	212 ms
Parse HTML & CSS	109 ms

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

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-4V7DMTJFQH&cx=c&gtm=4e64k0h1	171.8 KiB	68.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-TWP2FC7	130.9 KiB	65.4 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/NBNK8642181015.mp3?key=e7efd255a0f467351c851808b154a693&...	1.5 MiB
/NBNK9836693842.mp3?key=cca1d82f0a70bcecada3d080bdd5b0d0&...	843.5 KiB
www.googletagmanager.com/gtag/js?id=G-4V7DMTJFQH&cx=c&gtm=4e64k0h1	171.8 KiB
/_next/image?url=https%3A%2F%2Fwebfiles.ucpress.edu%2Fcov...	158.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-TWP2FC7	131.2 KiB
/_next/image?url=https%3A%2F%2Fwebfiles.ucpress.edu%2Fcov...	90.2 KiB
/_next/image?url=https%3A%2F%2Fwebfiles.ucpress.edu%2Fcov...	82.5 KiB
/_next/image?url=https%3A%2F%2Fwebfiles.ucpress.edu%2Fcov...	66.2 KiB
/_next/image?url=https%3A%2F%2Fwebfiles.ucpress.edu%2Fcov...	52.9 KiB
www.ucpress.edu/_next/static/chunks/fd9d1056-5bae34bee59f3468.js	52.8 KiB

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 6 user timings

●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 170 ms

●Server Backend Latencies 580 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Brand New Beat `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
The Middle-Class New Deal `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
The Moys of New York and Shanghai `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Smog and Sunshine `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Boom to Bust `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Trans Cinema `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Anti-Eviction `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Teaching Solidarity `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Can We Laugh at That? `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Making Care Work `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Leave If You Can `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
In the Hour of Chaos `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Swiftynomics `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
The Hidden Lives of Lab Animals `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Overcoming Bias Habits `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Trans Pleasure `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Art-Science Undisciplined `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Food Justice Undone `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`
Acts of Love `div#:R2rjttukvfa: > div.flickity-viewport > div.flickity-slider > div.Slide_slide__rCm5b`

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.

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

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

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

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

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

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

○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

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
traffic.megaphone.fm/NBNK8154883059.mp3?updated=1776629686	`Failed to load resource: the server responded with a status of 500 ()`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.ucpress.edu/_next/static/chunks/8629-2178701f3c2d0682.js

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

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`