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
siteimproveanalytics.com/js/siteanalyze_66356667.js	86400.0 s	107.3 KiB
/signals/config/960184152198754?v=2.9.303&r=stable&domain...	1200.0 s	44.8 KiB
/signals/config/1438055863158990?v=2.9.303&r=stable&domai...	1200.0 s	16.3 KiB
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	26.2 KiB
cbe.capturehighered.net/cbe/cbe.js	7200.0 s	8.6 KiB
assets.sc.edu/?v1	3600.0 s	7.5 KiB
apply.sc.edu/ping	1793.0 s	1.7 KiB
/cbe/footprint?v=1.3&n=_cbe&id=d54185b7&new=1&vid=2523648...	0.0 ms	268 B
insight.adsrvr.org/track/pxl/?adv=75p86ce&ct=0:m8uuaom&fmt=3/	0.0 ms	149 B
/tr/?id=960184152198754&ev=PageView&dl=https%3A%2F%2Fsc.e...	0.0 ms	19 B
/tr/?id=1438055863158990&ev=PageView&dl=https%3A%2F%2Fsc....	0.0 ms	16 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
div.column > div.full-width-hero > figure > div.full-width-hero_img `div.column > div.full-width-hero > figure > div.full-width-hero_img`	sc.edu/imgs/background/background-college-school-bottom.jpg	1.4 MiB	1.0 MiB
group of people together in front of a window with three standing and two sitti… `li.aos-init > a > div.li-img > img.post-image`	sc.edu/uofsc/images/large_post_images/2026/03-large-post-goldwater.jpg	452.9 KiB	394.3 KiB
div.column > div.full-width-hero > figure > div.full-width-hero_img `div.column > div.full-width-hero > figure > div.full-width-hero_img`	sc.edu/imgs/background/background-walkabout-17.jpg	567.1 KiB	369.1 KiB
smokestack with white `li.aos-init > a > div.li-img > img.post-image`	sc.edu/uofsc/images/large_post_images/uofsc_large_post_smokestack_180823-002.jpg	168.0 KiB	115.1 KiB
students walking along brick pathway `li.aos-init > a > div.li-img > img.post-image`	sc.edu/uofsc/images/large_post_images/uofsc_large_post_students_180328-407.jpg	149.4 KiB	96.5 KiB

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-5-FIGURE

nodeLabel: Championship Rein Congrats to South Carolina Equestrian — four-time National C…

path: 5,HTML,2,BODY,3,DIV,2,MAIN,1,SECTION,0,DIV,2,FIGURE

selector: main#main-content > section > div.hero-wrapper > figure.hero

snippet: <figure class="hero" style="display: block; background-image: url("https://assets.sc.edu/imgs/home_pag…");">

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

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
sc.edu/_resources/js/direct-edit.js	312 B
sc.edu/_resources/css/jquery.fancybox.css	2.9 KiB
sc.edu/_resources/js/libs/modernizr-2.6.2-respond-1.1.0.min.js	7.7 KiB
sc.edu/_resources/css/style.css	29.5 KiB	521 ms
sc.edu/_resources/css/foundation.min.css	1.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.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 260 ms 8.0 KiB

URL	Transfer Size	Est Savings
sc.edu/_resources/css/style.css	29.5 KiB	8.0 KiB

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: 260 ms 26.2 KiB

URL	Transfer Size	Est Savings
sc.edu/_resources/css/style.css	29.4 KiB	26.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: 1.6 s 241.6 KiB

URL	Transfer Size	Est Savings
siteimproveanalytics.com/js/siteanalyze_66356667.js	106.6 KiB	77.6 KiB
www.googletagmanager.com/gtag/js?id=G-L3YTP5R48L	169.2 KiB	68.6 KiB
www.googletagmanager.com/gtm.js?id=GTM-NJ732CJ	185.5 KiB	61.5 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	33.9 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.googletagmanager.com/gtag/js?id=G-L3YTP5R48L	401 ms	346 ms	43 ms
www.googletagmanager.com/gtm.js?id=GTM-NJ732CJ	359 ms	282 ms	67 ms
Unattributable	324 ms	28 ms	0.0 ms
sc.edu/	196 ms	12 ms	4.0 ms
scripts.clarity.ms/0.8.59/clarity.js	181 ms	157 ms	9.5 ms
/signals/config/960184152198754?v=2.9.303&r=stable&domain...	176 ms	118 ms	21 ms
connect.facebook.net/en_US/fbevents.js	127 ms	96 ms	30 ms
sc.edu/_resources/js/libs/jquery.min.js	120 ms	103 ms	6.7 ms
siteimproveanalytics.com/js/siteanalyze_66356667.js	112 ms	80 ms	31 ms
sc.edu/_resources/js/libs/modernizr-2.6.2-respond-1.1.0.min.js	67 ms	36 ms	1.9 ms
assets.sc.edu/?v1	64 ms	40 ms	1.7 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	411 ms
Script Parsing & Compilation	236 ms
Style & Layout	161 ms
Parse HTML & CSS	41 ms
Garbage Collection	36 ms
Rendering	33 ms

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
sc.edu/imgs/background/background-college-school-bottom.jpg	1.4 MiB
sc.edu/imgs/background/background-walkabout-17.jpg	567.5 KiB
sc.edu/uofsc/images/large_post_images/2026/03-large-post-goldwater.jpg	454.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-NJ732CJ	185.6 KiB
www.googletagmanager.com/gtag/js?id=G-L3YTP5R48L	169.5 KiB
sc.edu/uofsc/images/large_post_images/uofsc_large_post_smokestack_180823-002.jpg	169.2 KiB
sc.edu/uofsc/images/large_post_images/uofsc_large_post_students_180328-407.jpg	150.5 KiB
siteimproveanalytics.com/js/siteanalyze_66356667.js	107.3 KiB
sc.edu/_global_resources/fonts/BerlingskeSerif-Bd.woff2	104.9 KiB
sc.edu/_global_resources/fonts/BerlingskeSans-XBd.woff2	98.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
group of people together in front of a window with three standing and two sitti… `li.aos-init > a > div.li-img > img.post-image`	sc.edu/uofsc/images/large_post_images/2026/03-large-post-goldwater.jpg
students walking along brick pathway `li.aos-init > a > div.li-img > img.post-image`	sc.edu/uofsc/images/large_post_images/uofsc_large_post_students_180328-407.jpg
smokestack with white `li.aos-init > a > div.li-img > img.post-image`	sc.edu/uofsc/images/large_post_images/uofsc_large_post_smokestack_180823-002.jpg

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

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 10 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 110 ms

●Server Backend Latencies 220 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 400 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.

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
Privacy `div.row > div.column > small.copyright > a`
Transparency Initiative `div.row > div.column > small.copyright > a`

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

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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

○Form elements have associated labels

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

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

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

○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

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.

Line #	Content	Error
2	`Disallow: ~`	`Pattern should either be empty, start with "/" or "*"`

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`