Skip to content
https://olemiss.edu

Lighthouse Desktop

· 0 checks — Desktop 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.

41

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.

RequestCache TTLTransfer Size
olemiss.edu/assets/fontawesome-pro-6.5.1-web/webfonts/fa-light-300.woff20.0 ms447.7 KiB
olemiss.edu/assets/fontawesome-pro-6.5.1-web/webfonts/fa-regular-400.woff20.0 ms409.5 KiB
olemiss.edu/assets/images/slider-16.jpg0.0 ms282.7 KiB
olemiss.edu/assets/img/cheerleading-endzone.jpg0.0 ms258.7 KiB
olemiss.edu/assets/fonts/HandelsonOne/font.woff20.0 ms180.1 KiB
olemiss.edu/assets/images/sc_0187-ac.jpg0.0 ms146.9 KiB
olemiss.edu/assets/js/dist/app.js0.0 ms133.0 KiB
olemiss.edu/assets/js/dist/jquery.nanogallery2.js0.0 ms122.2 KiB
olemiss.edu/assets/fontawesome-pro-6.5.1-web/webfonts/fa-brands-400.woff20.0 ms115.7 KiB
olemiss.edu/assets/fontawesome-pro-6.5.1-web/css/all.css0.0 ms105.4 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
olemiss.edu/assets/css/theme.css0.0 ms66.6 KiB
/signals/config/670913880199834?v=2.9.303&r=stable&domain...1200.0 s44.8 KiB
olemiss.edu/assets/fonts/Matrole/font.woff20.0 ms29.6 KiB
cdn.bc0a.com/autopilot/f00000000246364/autopilot_sdk.js360.0 s27.4 KiB
/signals/config/3410033819250384?v=2.9.303&r=stable&domai...1200.0 s18.3 KiB
olemiss.edu/assets/images/new-lockup.webp0.0 ms15.5 KiB
/signals/config/197401438639739?v=2.9.303&r=stable&domain...1200.0 s16.4 KiB
scripts.clarity.ms/0.8.59/clarity.js86400.0 s26.2 KiB
olemiss.edu/assets/css/blog.css0.0 ms9.0 KiB
olemiss.edu/assets/news-redesign/css/hh-custom.css0.0 ms7.9 KiB
olemiss.edu/assets/css/subsite.css0.0 ms7.9 KiB
olemiss.edu/assets/js/dist/app.css0.0 ms7.8 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
static.hotjar.com/c/hotjar-4983596.js?sv=660.0 s6.2 KiB
consents-cf.bc0a.com/consentbar/corejs/becookiebar.js0.0 ms5.8 KiB
olemiss.edu/assets/css/media-gallery.css0.0 ms4.6 KiB
cdn.jsdelivr.net/npm/swiper@11/swiper-bundle.min.js604800.0 s43.8 KiB
js.ipredictive.com/viant_universal_pixel.js0.0 ms3.5 KiB
olemiss.edu/assets/js/dist/modernizr.js0.0 ms3.4 KiB
cse.google.com/cse.js?cx=009456705617115137650:3dblej_ayl80.0 ms3.4 KiB
olemiss.edu/assets/news-redesign/js/news-redesign-um-site.js0.0 ms1.2 KiB
www.google.com/cse/static/style/look/v6/default.css3000.0 s1.2 KiB
cdn.jsdelivr.net/npm/swiper@11/swiper-bundle.min.css604800.0 s5.0 KiB
/config/edu/c09f05f4-d3ca-4e68-8697-ab5f13ea19a5.js?v=3.5...0.0 ms469 B
/collect?v=2&fmt=js&pid=8951020%2C8978236&time=1776901765...0.0 ms437 B
/collect?v=2&fmt=js&pid=8951020%2C8978236&time=1776901765...0.0 ms272 B
/tr/?id=670913880199834&ev=PageView&dl=https%3A%2F%2Folem...0.0 ms19 B
/p.css?s=1&k=rmt3wly&ht=tk&f=28965.28966.28971.28977.2898...604800.0 s172 B
/tr/?id=197401438639739&ev=PageView&dl=https%3A%2F%2Folem...0.0 ms16 B
/tr/?id=3410033819250384&ev=PageView&dl=https%3A%2F%2Fole...0.0 ms16 B
olemiss.edu/assets/images/new-lockup.webp0.0 ms0 B
olemiss.edu/assets/slider-12.jpg0.0 ms0 B
olemiss.edu/assets/audeince-2.jpg0.0 ms0 B
olemiss.edu/assets/images/audience-1.jpg0.0 ms0 B
olemiss.edu/assets/images/20231106_ctg_9568.jpg0.0 ms0 B
olemiss.edu/assets/images/lyceum.jpg0.0 ms0 B

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:20.727 source:map[column:257840 line:39 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:155.61 source:map[type:text value:[unattributed]]] map[reflowTime:2.035 source:map[column:4686 line:0 type:source-location url:https://olemiss.edu/assets/js/dist/modernizr.js urlProvider:network]] map[reflowTime:46.774 source:map[column:4711 line:0 type:source-location url:https://olemiss.edu/assets/js/dist/modernizr.js urlProvider:network]] map[reflowTime:3.104 source:map[column:6409 line:0 type:source-location url:https://olemiss.edu/assets/js/dist/modernizr.js urlProvider:network]] map[reflowTime:0.877 source:map[column:6440 line:0 type:source-location url:https://olemiss.edu/assets/js/dist/modernizr.js urlProvider:network]] map[reflowTime:1.102 source:map[column:1502 line:38 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]] map[reflowTime:2.987 source:map[column:202152 line:38 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]] map[reflowTime:173.689 source:map[column:228325 line:38 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]] map[reflowTime:1.181 source:map[column:234494 line:38 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]] map[reflowTime:1.641 source:map[column:54544 line:38 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]] map[reflowTime:0.287 source:map[column:54641 line:38 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]] map[reflowTime:0.174 source:map[column:54871 line:38 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]] map[reflowTime:0.173 source:map[column:55321 line:38 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]] map[reflowTime:0.217 source:map[column:55469 line:38 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]] map[reflowTime:0.172 source:map[column:55614 line:38 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]] map[reflowTime:0.249 source:map[column:1183 line:28 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]] map[reflowTime:0.445 source:map[column:17707 line:0 type:source-location url:https://consents-cf.bc0a.com/consentbar/corejs/becookiebar.js urlProvider:network]] map[reflowTime:18.574 source:map[column:32112 line:38 type:source-location url:https://olemiss.edu/assets/js/dist/app.js urlProvider:network]]]

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
students conducting research on honey bees div.card__media > figure > div.aspect-ratio-frame > img.js-processed
marvel-b1-cdn.bc0a.com/f00000000246364/olemiss.edu/assets/slider-12.jpg1.3 MiB1.3 MiB
Ole Miss students stand up and cheer during a football game in Vaught Hemingway… div.card__media > figure > div.aspect-ratio-frame > img
marvel-b1-cdn.bc0a.com/f00000000246364/olemiss.edu/assets/audeince-2.jpg154.4 KiB94.1 KiB
student participating in the annual tradition of rebel run div.card__media > figure > div.aspect-ratio-frame > img
marvel-b1-cdn.bc0a.com/f00000000246364/olemiss.edu/assets/images/audience-1.jpg139.8 KiB85.2 KiB
student celebrating at a graduation ceremony div.card__media > figure > div.aspect-ratio-frame > img.js-processed
marvel-b1-cdn.bc0a.com/f00000000246364/olemiss.edu/assets/images/slider-8.jpg90.8 KiB77.4 KiB
Students dance at night at the rebelthon fundraiser div.card__media > figure > div.aspect-ratio-frame > img.js-processed
/f00000000246364/olemiss.edu/assets/img/rebelthon-slider.jpg64.9 KiB55.4 KiB
image 4 alt text div.card__media > figure > div.aspect-ratio-frame > img.js-processed
/f00000000246364/olemiss.edu/assets/img/home_intown_rkj_2...59.1 KiB50.6 KiB
Ole miss Football Players Lifting the Sugar Bowl Trophy div.card__media > figure > div.aspect-ratio-frame > img.js-processed
/f00000000246364/olemiss.edu/assets/images/sugar-bowl_cel...65.2 KiB49.5 KiB
UM student working on a brainstorm session div.card__media > figure > div.aspect-ratio-frame > img.js-processed
marvel-b1-cdn.bc0a.com/f00000000246364/olemiss.edu/assets/images/slider-5.jpg52.1 KiB43.6 KiB
image 3 alt div.card__media > figure > div.aspect-ratio-frame > img.js-processed
/f00000000246364/olemiss.edu/assets/img/home_inthegrove_s...41.7 KiB35.7 KiB
Student doing research on equipment div.card__media > figure > div.aspect-ratio-frame > img.js-processed
marvel-b1-cdn.bc0a.com/f00000000246364/olemiss.edu/assets/images/slider-16.jpg31.8 KiB23.2 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-10-IMG
nodeLabel: lyceum with sun in background
path: 1,HTML,1,BODY,6,DIV,1,MAIN,1,SECTION,0,DIV,1,DIV,0,DIV,0,DIV,0,IMG
selector: div.hero__media > div.aspect-ratio-frame > div.aspect-ratio-frame__inner > img.js-processed
snippet: <img alt="lyceum with sun in background" class="js-processed" loading="lazy" src="https://marvel-b1-cdn.bc0a.com/f00000000246364/olemiss.edu/assets/images/l…" be_marvel="1" onerror="this.onerror=null;this.src='https://olemiss.edu/assets/images/lyceum.jpg'">

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

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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.

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

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.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 80 ms 57.3 KiB
URLTransfer SizeEst Savings
olemiss.edu/assets/js/dist/jquery.nanogallery2.js121.8 KiB57.3 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: 150 ms 171.3 KiB

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
Other1.3 s
Script Evaluation1.1 s
Style & Layout487 ms
Script Parsing & Compilation244 ms
Garbage Collection64 ms
Parse HTML & CSS60 ms
Rendering33 ms

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
●LCP breakdown
●Optimize viewport for mobile
●User Timing marks and measures 18 user timings
●JavaScript execution time 1.0 s
●Avoid long main-thread tasks 10 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 70 ms
●Server Backend Latencies 130 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 50 ms
●Avoid large layout shifts 3 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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Way down south in Mississippi, there's a spot that ever calls. div.location-highilight__grid__inner > div.location-highilight__grid__column-right > div.image-grid-item > a.image-grid-item__link
○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
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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>`).
●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
○`[accesskey]` values are unique
○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
○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.
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
●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
○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
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback