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.

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
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-solid-900-22.woff2	95 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-brands-400-1.woff2	95 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-2.woff2	85 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-19.woff2	85 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-11.woff2	80 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-16.woff2	80 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-13.woff2	75 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-22.woff2	75 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-1.woff2	75 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-3.woff2	75 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-regular-400-13.woff2	70 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-14.woff2	70 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-18.woff2	70 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-0.woff2	65 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-solid-900-12.woff2	60 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-brands-400-0.woff2	60 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-regular-400-10.woff2	30 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-solid-900-13.woff2	25 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-regular-400-1.woff2	20 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-solid-900-0.woff2	15 ms
ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-light-300-12.woff2	15 ms

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:37.489 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: Imagine RIT, April 27

path: 2,HTML,1,BODY,5,DIV,6,MAIN,5,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,A,1,IMG

selector: div.carousel-item > div.has-video > a.cta-imagine-link > img.d-md-none

snippet: <img src="/sites/rit.edu/files/images/custom/hero-ready/imagine/2026/2026_ImagineRIT…" class="d-md-none" alt="Imagine RIT, April 27">

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

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.rit.edu/sites/all/modules/google_tag/js/gtm.js?tdue7f	612 B
/sites/rit.edu/files/css/css_g2Jw5nlKZnZGvru27tzHATavBNj9...	69.1 KiB	452 ms
www.rit.edu/sites/all/modules/google_tag/js/gtag.js?tdue7f	762 B
/sites/rit.edu/files/js/js_KT3GQm2saK8fuEk0QrinE-XRzCNMCN...	326 B
/sites/rit.edu/files/css/css_U6l6yGyL0dq6J2GxXDC3sKB2B-0H...	619 B
/sites/rit.edu/files/css/css_jNz-m-VUuduIHbP70rD4aRsOl513...	1.9 KiB

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/1051510815041414?v=2.9.303&r=stable&domai...	1200.0 s	46.1 KiB
cdn.walls.io/assets/js/wall-fluid-libs.23b20a1679.js	0.0 ms	37.2 KiB
cdn.walls.io/assets/js/wallsio-components.c065d9578b.js	0.0 ms	25.1 KiB
cdn.walls.io/assets/css/wall-fluid.4ab0ba9098.css	0.0 ms	22.5 KiB
js.adsrvr.org/up_loader.1.1.0.js	0.0 ms	12.5 KiB
siteimproveanalytics.com/js/siteanalyze_66356383.js	86400.0 s	13.0 KiB
walls.io/js/wallsio-widget-1.2.js	3600.0 s	6.1 KiB
dpt5udl8tkpo9.cloudfront.net/files/walls/logo/YyssGeD9hP-1-1.png	0.0 ms	3.0 KiB
script.crazyegg.com/pages/scripts/0000/2879.js	300.0 s	2.7 KiB
cdn.walls.io/assets/js/modernizr-webp.ccaa019ad8.js	0.0 ms	2.0 KiB
cdn.walls.io/assets/messages/messages-frontend-en_US.7e17453284.js	0.0 ms	1.7 KiB
kit.fontawesome.com/ae149fa543.css	300.0 s	1.7 KiB
cdn.walls.io/assets/js/i18n.b3546cff4b.js	0.0 ms	1.2 KiB
js.adsrvr.org/universal_pixel.js	0.0 ms	934 B
join.rit.edu/ping	1785.0 s	950 B
/config/edu/9874e9ad-33cc-4519-bd1f-7557ec150a5e.js?v=3.5...	0.0 ms	460 B
/pixel/?ad_log=referer&action=content&pixid=0c354ef2-7653...	0.0 ms	131 B
/tr/?id=1051510815041414&ev=PageView&dl=https%3A%2F%2Fwww...	0.0 ms	19 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
a crowd of people walk under a sign for Imagine R I T `div.card-body > a.d-block > div.position-relative > img.card-img-top`	/sites/rit.edu/files/styles/news_thumbnail/https/cdn.rit....	74.2 KiB	42.6 KiB
Three people photograph equipment inside NASA training facility. `div.card-body > a.d-block > div.position-relative > img.card-img-top`	/sites/rit.edu/files/styles/news_thumbnail/https/cdn.rit....	53.5 KiB	21.9 KiB
a woman sits in a brightly lit cubicle with a mirror image shown on the right. `div.card-body > a.d-block > div.position-relative > img.card-img-top`	/sites/rit.edu/files/styles/news_thumbnail/https/cdn.rit....	47.6 KiB	15.9 KiB
U.S. News and World Report Badge for Best National Universities for 2026. `div.position-relative > div.position-relative > a.d-block > img.card-img-top`	/sites/rit.edu/files/images/paragraph/image-card/Badge-Co...	19.4 KiB	9.0 KiB
Imagine RIT, April 27 `div.carousel-item > div.has-video > a.cta-imagine-link > img.d-md-none`	/sites/rit.edu/files/images/custom/hero-ready/imagine/202...	22.0 KiB	4.1 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.4 s

URL	Time Spent
rit.edu/	1.4 s
www.rit.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 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: 320 ms 142.0 KiB

URL	Transfer Size	Est Savings
ka-p.fontawesome.com/releases/v6.7.2/css/pro.min.css?token=ae149fa543	80.6 KiB	79.8 KiB
/sites/rit.edu/files/css/css_g2Jw5nlKZnZGvru27tzHATavBNj9...	69.0 KiB	62.2 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
www.rit.edu/	2.4 s	31 ms	4.7 ms
/sites/rit.edu/files/js/js_m7riXzT7dg1q6lksZDxLHbP4c7ZYR9...	1.1 s	452 ms	19 ms
www.googletagmanager.com/gtm.js?id=GTM-TKNM7FX	782 ms	626 ms	85 ms
Unattributable	736 ms	87 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-DY6XXZS0V2&cx=c&gtm=4e64h1	597 ms	485 ms	102 ms
/pages/versioned/common-scripts/4ce8c7df8d425cc5046457682...	385 ms	333 ms	32 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	297 ms	231 ms	61 ms
connect.facebook.net/en_US/fbevents.js	196 ms	146 ms	48 ms
/signals/config/1051510815041414?v=2.9.303&r=stable&domai...	191 ms	161 ms	29 ms
sc-static.net/scevent.min.js	161 ms	146 ms	8.5 ms
/pages/versioned/tracking-scripts/158692313dc4b9f2e28d9e9...	112 ms	89 ms	22 ms
ka-p.fontawesome.com/releases/v6.7.2/css/pro.min.css?token=ae149fa543	72 ms	0.0 ms	0.0 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js	63 ms	42 ms	20 ms
/sites/rit.edu/files/css/css_g2Jw5nlKZnZGvru27tzHATavBNj9...	57 ms	0.0 ms	0.0 ms
walls.io/js/wallsio-widget-1.2.js	57 ms	53 ms	2.8 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.1 s
Other	1.9 s
Style & Layout	1.4 s
Script Parsing & Compilation	481 ms
Rendering	334 ms
Parse HTML & CSS	239 ms
Garbage Collection	95 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

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

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-DY6XXZS0V2&cx=c&gtm=4e64h1	176.4 KiB	67.1 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	109.0 KiB	56.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-TKNM7FX	152.1 KiB	54.4 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	30.5 KiB
/pages/versioned/common-scripts/4ce8c7df8d425cc5046457682...	55.1 KiB	28.6 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
Imagine RIT, April 27 `div.carousel-item > div.has-video > a.cta-imagine-link > img.d-md-none`	/sites/rit.edu/files/images/custom/hero-ready/imagine/202...
Advancing the Exception Through tagline `div.row > div.col-lg-2dot4 > a > img.w-100`
Students working together `div.col-6 > div.card > div.position-relative > img.w-100`
Students framing a house `div.col-6 > div.card > div.position-relative > img.w-100`
Student working in a lab `div.col-6 > div.card > div.position-relative > img.w-100`
Student working with lab equipment `div.col-6 > div.card > div.position-relative > img.w-100`
Student posing in front of flags `div.col-6 > div.card > div.position-relative > img.w-100`
Windmills on RIT Campus `div.col-6 > div.card > div.position-relative > img.w-100`
A large group of first year RIT students posing for a photo with RITchie during… `div.col-6 > div.card > div.position-relative > img.w-100`

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 250 ms

●Server Backend Latencies 270 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

100

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.

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

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

●ARIA `progressbar` elements have accessible names

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

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

○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

○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

○Form elements have associated labels

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

○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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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`