Skip to content
https://depaul.edu

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

33

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.

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.

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.

URLResource SizeEst Savings
Graduation​_Students_Wide​_canto_L0_about_09242025.png div.feature-banner__image > div.feature-banner__image-wrapper > picture.image > img
/api/public/content/1b07c33cd3aa415fb2ce5c2c08948b00511.1 KiB471.2 KiB
div.row > section#235b4644-8c59-4d0d-a845-d851995c9aa1 > div.statistics-banner__container > div.statistics-banner__block div.row > section#235b4644-8c59-4d0d-a845-d851995c9aa1 > div.statistics-banner__container > div.statistics-banner__block
/api/public/content/6fc8839a85c7475d9bf0708db0823339506.7 KiB463.1 KiB
div.row > section#2e085413-f9af-4d68-b99c-4b8fb8ce0b04 > div.statistics-banner__container > div.statistics-banner__block div.row > section#2e085413-f9af-4d68-b99c-4b8fb8ce0b04 > div.statistics-banner__container > div.statistics-banner__block
/api/public/content/3b44e171413a43acaec16aacace919ac430.8 KiB387.2 KiB
Students_campus_lifestyle_internal_L0_home_09232025.png div.basic-card__wrapper > div.basic-card__image > picture.image > img
/api/public/content/5884df77a27e456ba708d10b85727fd6258.3 KiB241.8 KiB
Students_community_action_internal_L0_home_09232025.png div.basic-card__wrapper > div.basic-card__image > picture.image > img
/api/public/content/9ee002e85f17478f9df0cfd40658da7e209.2 KiB192.6 KiB
Students_career_environmental_internal_L0_home_09232025.png div.basic-card__wrapper > div.basic-card__image > picture.image > img
/api/public/content/4a31647551f846449277769712058c41175.0 KiB158.4 KiB
div.row > section#6bf87e8a-aa5b-4102-9299-5dd2b7e62f7d > div.statistics-banner__container > div.statistics-banner__block div.row > section#6bf87e8a-aa5b-4102-9299-5dd2b7e62f7d > div.statistics-banner__container > div.statistics-banner__block
/api/public/content/36f318db1c1645fe8c93486f0f0c092a197.2 KiB153.6 KiB
div.row > section#9e93d4f9-ef4f-43b3-9240-e5221485b5f2 > div.statistics-banner__container > div.statistics-banner__block div.row > section#9e93d4f9-ef4f-43b3-9240-e5221485b5f2 > div.statistics-banner__container > div.statistics-banner__block
/api/public/content/ea5270f1033648af942bc2c6960ab95b220.7 KiB89.5 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.

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: 788 ms
URLTime Spent
depaul.edu/788 ms
www.depaul.edu/0.0 ms

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: 1.1 s 114.1 KiB
URLTransfer SizeEst Savings
www.depaul.edu/_next/static/css/88e4a41d76c321d3.css121.2 KiB114.1 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: 2.7 s 2.1 MiB
URLTransfer SizeEst Savings
sgtm.depaul.edu/gtm.js?id=GTM-WC95XP4Q584.3 KiB335.8 KiB
www.depaul.edu/_next/static/chunks/345-01bac38d7543056c.js314.2 KiB229.6 KiB
/gtag/js?id=G-642L3PSQN8&cx=c&gtm=4e64k0&sign=4c867b7eba6...553.2 KiB206.5 KiB
sgtm.depaul.edu/gtm.js?id=GTM-WC95XP4Q584.3 KiB199.0 KiB
www.depaul.edu/_next/static/chunks/422-3f2f246ea4d9ac1f.js170.7 KiB96.5 KiB
www.depaul.edu/_next/static/chunks/dc9bbfe9-088f873886f1f62b.js90.0 KiB75.6 KiB
www.depaul.edu/_next/static/chunks/0f34fbf1-b0f0a4beed3f3d09.js68.9 KiB64.6 KiB
www.depaul.edu/_next/static/chunks/4cce89e7-6dff7d4cb7b932cc.js68.8 KiB64.5 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwOQ.js120.9 KiB62.6 KiB
/gtag/js?id=AW-842031037&cx=c&gtm=4e64k0&sign=4c867b7eba6...144.4 KiB62.4 KiB
/gtag/js?id=AW-16672879264&cx=c&gtm=4e64k0&sign=4c867b7eb...147.3 KiB61.1 KiB
/gtag/js?id=DC-15624628&cx=c&gtm=4e64k0&sign=4c867b7eba68...129.2 KiB61.1 KiB
/gtag/js?id=DC-15194154&cx=c&gtm=4e64k0&sign=4c867b7eba68...130.6 KiB59.8 KiB
www.depaul.edu/_next/static/chunks/pages/_app-c5a50d54c4e8d99d.js84.4 KiB57.6 KiB
/gtag/js?id=DC-8928774&cx=c&gtm=4e64k0&sign=4c867b7eba680...129.7 KiB56.8 KiB
www.depaul.edu/_next/static/chunks/e9c2506b-681917e308d81521.js88.9 KiB56.6 KiB
www.depaul.edu/_next/static/chunks/155e84d2-e59464db483bb1bb.js68.5 KiB56.5 KiB
www.depaul.edu/_next/static/chunks/c7e47101-5bea55a15b36a91d.js67.3 KiB55.4 KiB
www.depaul.edu/_next/static/chunks/4799a7fb-c3df98d26fda10dc.js65.9 KiB54.0 KiB
www.depaul.edu/_next/static/chunks/88131b38-c56b0bf6bd6d57b4.js65.0 KiB53.3 KiB
www.depaul.edu/_next/static/chunks/d89f4e84-e33ecb64c614b37b.js63.5 KiB51.8 KiB
www.depaul.edu/_next/static/chunks/50577595-855db110af3d5cbe.js59.6 KiB48.4 KiB
connect.facebook.net/en_US/fbevents.js96.5 KiB32.6 KiB
www.depaul.edu/_next/static/chunks/framework-718211d705583582.js59.1 KiB26.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.

URLTotal CPU TimeScript EvaluationScript Parse
www.depaul.edu/_next/static/chunks/pages/%5B%5B...path%5D%5D-793f48be683de8bb.js1.4 s1.4 s0.6 ms
Unattributable1.2 s142 ms0.0 ms
www.depaul.edu/_next/static/chunks/framework-718211d705583582.js835 ms668 ms16 ms
www.depaul.edu/794 ms10 ms0.5 ms
sgtm.depaul.edu/gtm.js?id=GTM-WC95XP4Q704 ms468 ms222 ms
/gtag/js?id=DC-15194154&cx=c&gtm=4e64k0&sign=4c867b7eba68...306 ms260 ms42 ms
/gtag/js?id=G-642L3PSQN8&cx=c&gtm=4e64k0&sign=4c867b7eba6...295 ms248 ms43 ms
/gtag/js?id=AW-16672879264&cx=c&gtm=4e64k0&sign=4c867b7eb...270 ms189 ms35 ms
/gtag/js?id=AW-842031037&cx=c&gtm=4e64k0&sign=4c867b7eba6...260 ms213 ms46 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwOQ.js211 ms167 ms42 ms
/gtag/js?id=DC-8928774&cx=c&gtm=4e64k0&sign=4c867b7eba680...211 ms174 ms35 ms
scripts.clarity.ms/0.8.59/clarity.js173 ms151 ms6.3 ms
/signals/config/2184913605104093?v=2.9.303&r=stable&domai...167 ms149 ms16 ms
connect.facebook.net/en_US/fbevents.js157 ms117 ms39 ms
/gtag/js?id=DC-15624628&cx=c&gtm=4e64k0&sign=4c867b7eba68...152 ms120 ms31 ms
www.depaul.edu/_next/static/chunks/345-01bac38d7543056c.js136 ms5.1 ms125 ms
bat.bing.com/bat.js110 ms90 ms19 ms
sc-static.net/scevent.min.js106 ms92 ms5.3 ms
www.depaul.edu/_next/static/chunks/e9c2506b-681917e308d81521.js80 ms8.6 ms40 ms
s.pinimg.com/ct/lib/main.10d2511a.js76 ms59 ms10 ms
www.depaul.edu/_next/static/chunks/pages/_app-c5a50d54c4e8d99d.js74 ms49 ms25 ms
static.ads-twitter.com/uwt.js73 ms67 ms3.9 ms
www.depaul.edu/_next/static/chunks/main-f4126c42c913d29a.js63 ms50 ms11 ms
www.depaul.edu/_next/static/css/88e4a41d76c321d3.css62 ms0.0 ms0.0 ms
www.depaul.edu/_next/static/chunks/422-3f2f246ea4d9ac1f.js54 ms1.1 ms52 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.

CategoryTime Spent
Script Evaluation5.1 s
Other1.2 s
Script Parsing & Compilation1.2 s
Style & Layout704 ms
Garbage Collection149 ms
Rendering134 ms
Parse HTML & CSS87 ms

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
●User Timing marks and measures 13 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 130 ms
●Server Backend Latencies 470 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 20 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
92

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Find a Major That
 Moves You div.row > div#32c42a3b-79ea-403c-baf6-a93858f5bbad > div.card-banner__hero > h6.card-banner__title
Hear About DePaul From Our Students div.row > div#9215e160-a886-45f4-b3d6-7fbe3e593dbd > div.card-listing__header > h5

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Collapsed Information for accordion Information for div#row-1 > div#f71b176d-2d8f-49c2-848d-5dfc816718fa > div#f71b176d-2d8f-49c2-848d-5dfc816718fa-column-2 > li#9eef020e-2725-453b-b9e4-61c0c1b2d09d
Collapsed Academic Resources accordion Academic Resources div#row-1 > div#f71b176d-2d8f-49c2-848d-5dfc816718fa > div#f71b176d-2d8f-49c2-848d-5dfc816718fa-column-3 > li#420b6a6f-c2e2-468e-bfe8-e6824bbdd211
Collapsed Campus Resources accordion Campus Resources div#row-1 > div#f71b176d-2d8f-49c2-848d-5dfc816718fa > div#f71b176d-2d8f-49c2-848d-5dfc816718fa-column-4 > li#dc458ccb-31c9-4172-bf09-3cdd22ecfed3
Collapsed University Resources accordion University Resources div#row-1 > div#f71b176d-2d8f-49c2-848d-5dfc816718fa > div#f71b176d-2d8f-49c2-848d-5dfc816718fa-column-5 > li#f54b5940-1c1f-45d8-99c2-205183f05992

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search div.search-widget-faq--search-with-carousel__search-container > div.component > div.faq-search__input-wrapper > button.faq-search__button

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
●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
●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>`).
●No element has a `[tabindex]` value greater than 0
●Skip links are focusable.
●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
○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
○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>`.
○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.
81

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 / WarningSource
AttributionReporting

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.

●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
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
85

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Page has successful HTTP status code
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback