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
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/signals/config/2095060143879058?v=2.9.303&r=stable&domai...	1200.0 s	46.2 KiB
static.hotjar.com/c/hotjar-380178.js?sv=6	60.0 s	6.2 KiB
apply.psu.edu/ping	1754.0 s	947 B
/tr/?id=2095060143879058&ev=PageView&dl=https%3A%2F%2Fwww...	0.0 ms	16 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: Students walking outside with yellow leaves in background

path: 1,HTML,1,BODY,8,MAIN,1,DIV,3,DIV,0,DIV,1,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,0,A,1,IMG

selector: div.theme-cache-p2lif8 > div.h-full > a.theme-cache-1ag8aku > img.w-full

snippet: <img alt="Students walking outside with yellow leaves in background" loading="lazy" width="500" height="500" decoding="async" data-nimg="1" class="w-full object-cover theme-cache-1628tse" style="color:transparent" sizes="(max-width: 768px) 100vw, (max-width: 1080px) 70vw, (max-width: 1440px) 55…" srcset="https://images.ctfassets.net/ni9rh5nu0d99/659UpS14dds9Xkmo8VrhGj/e65ebf663…" src="https://images.ctfassets.net/ni9rh5nu0d99/659UpS14dds9Xkmo8VrhGj/e65ebf663…">

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

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.psu.edu/_next/static/css/851e9a401aa65c8a.css	1.1 KiB
www.psu.edu/_next/static/css/4a88a4130ecd0838.css	3.1 KiB
www.psu.edu/_next/static/css/f4e28bc3d4c3174f.css	3.3 KiB
www.psu.edu/_next/static/css/0c003ca29e796b84.css	3.0 KiB
www.psu.edu/_next/static/css/666785ae41fb2366.css	824 B	151 ms

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
Seven students cheering around a Nittany Lion Shrine replica at Penn State Alto… `section.theme-cache-ohjecu > div.theme-cache-rtzamq > div.theme-cache-e9vlks > img.w-full`	/ni9rh5nu0d99/3hYKydhu1r99UKc2C3oB5u/48a9f033b6f6e878b507...	63.2 KiB	49.1 KiB
Students organizing cans in a local food bank `div.theme-cache-p2lif8 > div.h-full > a.theme-cache-1ag8aku > img.w-full`	/ni9rh5nu0d99/3VyxaKrLtv1kDTjHWKG0OF/bfe24e3dcb159558ba3a...	42.4 KiB	31.8 KiB
3D-printed brain sensors may unlock personalized neural monitoring `div.theme-cache-14xsfsf > a.theme-cache-1gxgpwf > div.theme-cache-o4s63m > img.theme-cache-1xb4x4`	/ni9rh5nu0d99/fAvwyk1iBbfwmQJIy4LiA/7a1749728e87c263cc2f0...	42.2 KiB	30.3 KiB
Researcher standing in their lab, looking down and smiling `div.theme-cache-p2lif8 > div.h-full > a.theme-cache-1ag8aku > img.w-full`	/ni9rh5nu0d99/6q1BcCPlXlaWKJYqqieF8Q/fa59862b415c3fe33689...	23.2 KiB	17.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: 850 ms

URL	Time Spent
psu.edu/	850 ms
www.psu.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

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: 3.0 s 608.9 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-4YY6NWZJSM&cx=c&gtm=4e64h1	177.1 KiB	67.0 KiB
www.googletagmanager.com/gtag/js?id=AW-870914452&cx=c&gtm=4e64h1	144.5 KiB	62.4 KiB
www.googletagmanager.com/gtag/js?id=DC-6108309&cx=c&gtm=4e64h1	129.4 KiB	61.0 KiB
www.googletagmanager.com/gtag/js?id=DC-15529822&cx=c&gtm=4e64h1	129.4 KiB	60.9 KiB
www.googletagmanager.com/gtag/js?id=AW-982386578&cx=c&gtm=4e64h1	137.5 KiB	60.8 KiB
www.psu.edu/_next/static/chunks/2216-24f966dfb5453572.js	88.6 KiB	60.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-P3SBL5	167.9 KiB	59.9 KiB
www.psu.edu/_next/static/chunks/6016-82769d89c4b0e86a.js	84.6 KiB	57.2 KiB
www.psu.edu/_next/static/chunks/5168-5dae27bc77ab4fdd.js	69.2 KiB	41.2 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	32.4 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	56.1 KiB	24.7 KiB
www.psu.edu/_next/static/chunks/14aeac6e-99806b3cf8c74589.js	43.9 KiB	20.8 KiB

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	1.0 s	36 ms	0.0 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	891 ms	739 ms	20 ms
www.psu.edu/_next/static/chunks/1528-f6ff037bf6a98646.js	568 ms	511 ms	13 ms
www.psu.edu/	396 ms	83 ms	11 ms
www.googletagmanager.com/gtag/js?id=G-4YY6NWZJSM&cx=c&gtm=4e64h1	334 ms	225 ms	38 ms
www.googletagmanager.com/gtm.js?id=GTM-P3SBL5	307 ms	255 ms	42 ms
www.psu.edu/_next/static/chunks/1dd3208c-5dda107b194ce164.js	263 ms	240 ms	11 ms
www.psu.edu/_next/static/chunks/5416-e0797b595b278ec3.js	194 ms	187 ms	4.1 ms
www.googletagmanager.com/gtag/js?id=AW-870914452&cx=c&gtm=4e64h1	184 ms	154 ms	29 ms
www.psu.edu/_next/static/chunks/5168-5dae27bc77ab4fdd.js	175 ms	154 ms	20 ms
www.googletagmanager.com/gtag/js?id=AW-982386578&cx=c&gtm=4e64h1	172 ms	143 ms	27 ms
www.googletagmanager.com/gtag/js?id=DC-15529822&cx=c&gtm=4e64h1	154 ms	126 ms	26 ms
/signals/config/2095060143879058?v=2.9.303&r=stable&domai...	153 ms	135 ms	16 ms
www.googletagmanager.com/gtag/js?id=DC-6108309&cx=c&gtm=4e64h1	127 ms	103 ms	23 ms
connect.facebook.net/en_US/fbevents.js	125 ms	96 ms	28 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.3 s
Other	1.0 s
Script Parsing & Compilation	490 ms
Style & Layout	281 ms
Garbage Collection	202 ms
Parse HTML & CSS	38 ms
Rendering	37 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 reason	Failure type
Pages with WebSocket cannot enter back/forward cache.	Pending browser support

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
/ni9rh5nu0d99/6IZnxA53tfOL41oXZuhtYx/4eb40cf89fd7c64928e3...	3.1 MiB
www.googletagmanager.com/gtag/js?id=G-4YY6NWZJSM&cx=c&gtm=4e64h1	177.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-P3SBL5	168.2 KiB
www.googletagmanager.com/gtag/js?id=AW-870914452&cx=c&gtm=4e64h1	144.6 KiB
www.googletagmanager.com/gtag/js?id=AW-982386578&cx=c&gtm=4e64h1	137.6 KiB
www.googletagmanager.com/gtag/js?id=DC-6108309&cx=c&gtm=4e64h1	129.5 KiB
www.googletagmanager.com/gtag/js?id=DC-15529822&cx=c&gtm=4e64h1	129.4 KiB
connect.facebook.net/en_US/fbevents.js	96.6 KiB
www.psu.edu/_next/static/chunks/2216-24f966dfb5453572.js	90.0 KiB
www.psu.edu/_next/static/chunks/6016-82769d89c4b0e86a.js	85.1 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
Penn State `div.theme-cache-ke0jlw > div.theme-cache-197wvqq > a.theme-cache-1fz2xng > img.theme-cache-jo0541`	/p7x3ai5plaz1/1wVBvFkhF0ArrdaMlzLiCi/125b0659267cacef241e...

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 5 user timings

●Avoid long main-thread tasks 18 long tasks found

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 140 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 70 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.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Phone: 1-814-865-4700 `div.theme-cache-6wb2vd > div.theme-cache-197wvqq > ul.theme-cache-17sw09l > li#react-aria2520642587-:r3:-option-Phone`
IconButton-to:https://www.instagram.com/pennstate/ `div.theme-cache-6wb2vd > div.theme-cache-197wvqq > ul.theme-cache-igrr55 > li#react-aria2520642587-:rb:-option-instagram`
IconButton-to:https://www.facebook.com/pennstate/ `div.theme-cache-6wb2vd > div.theme-cache-197wvqq > ul.theme-cache-igrr55 > li#react-aria2520642587-:rb:-option-facebook`
IconButton-to:https://www.linkedin.com/school/penn-state-university/ `div.theme-cache-6wb2vd > div.theme-cache-197wvqq > ul.theme-cache-igrr55 > li#react-aria2520642587-:rb:-option-linkedIn`
IconButton-to:https://www.youtube.com/@pennstate `div.theme-cache-6wb2vd > div.theme-cache-197wvqq > ul.theme-cache-igrr55 > li#react-aria2520642587-:rb:-option-youtube`
IconButton-to:https://www.tiktok.com/@pennstate `div.theme-cache-6wb2vd > div.theme-cache-197wvqq > ul.theme-cache-igrr55 > li#react-aria2520642587-:rb:-option-tiktok`
The Pennsylvania State University `div.theme-cache-1z0mioj > div.theme-cache-k9wxnk > ul.theme-cache-1x6v9v1 > li#react-aria-:RjauikqH1:-option-ThePennsylvaniaStateUniversity`
Privacy Statements `div.theme-cache-1z0mioj > div.theme-cache-k9wxnk > ul.theme-cache-1x6v9v1 > li#react-aria-:RjauikqH1:-option-PrivacyStatements`
Non Discrimination `div.theme-cache-1z0mioj > div.theme-cache-k9wxnk > ul.theme-cache-1x6v9v1 > li#react-aria-:RjauikqH1:-option-NonDiscrimination`
Accessibility `div.theme-cache-1z0mioj > div.theme-cache-k9wxnk > ul.theme-cache-1x6v9v1 > li#react-aria-:RjauikqH1:-option-Accessibility`
Legal Statements `div.theme-cache-1z0mioj > div.theme-cache-k9wxnk > ul.theme-cache-1x6v9v1 > li#react-aria-:RjauikqH1:-option-LegalStatements`

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
div.theme-cache-6wb2vd > div.theme-cache-ke0jlw > div.theme-cache-197wvqq > a.hover-underline `div.theme-cache-6wb2vd > div.theme-cache-ke0jlw > div.theme-cache-197wvqq > a.hover-underline`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Phone: 1-814-865-4700 `div.theme-cache-1ykt47k > div.theme-cache-6wb2vd > div.theme-cache-197wvqq > ul.theme-cache-17sw09l`
IconButton-to:https://www.instagram.com/pennstate/ `div.theme-cache-1ykt47k > div.theme-cache-6wb2vd > div.theme-cache-197wvqq > ul.theme-cache-igrr55`
The Pennsylvania State University Privacy Statements Non Discrimination Accessi… `div.theme-cache-f3cvlx > div.theme-cache-1z0mioj > div.theme-cache-k9wxnk > ul.theme-cache-1x6v9v1`

These are opportunities to improve the experience of reading tabular or list data using 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

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

●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

●ARIA toggle fields have accessible names

●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

●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

●ARIA IDs are unique

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

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

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

○Elements with the `role=text` attribute do not have focusable descendents.

○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 buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○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
AttributionReporting	connect.facebook.net/en_US/fbevents.js line 279, col 769

●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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`