Skip to content
https://umd.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.

53

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.005926] map[node:map[boundingRect:map[bottom:8037 height:8037 left:0 right:1350 top:0 width:1350] lhId:page-1-BODY nodeLabel:body path:1,HTML,1,BODY selector:body snippet:<body> type:node] score:0.005926 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:0 height:0 left:0 right:0 top:0 width:0] lhId:page-8-IMG nodeLabel:dogoodinstitute at thurgood path:1,HTML,1,BODY,3,MAIN,0,DIV,4,SECTION,1,DIV,0,UMD-ELEMENT-CARD-OVERLAY,0,IMG selector:section#section-26152 > div#masonry-grid-26153 > umd-element-card-overlay.size-large > img snippet:<img src="https://umd-main.transforms.svdcdn.com/production/umd/images/default/Thurg…" alt="dogoodinstitute at thurgood" slot="image"> type:node]]] type:subitems]]]
headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.256264] map[node:map[boundingRect:map[bottom:6545 height:6392 left:0 right:1350 top:153 width:1350] lhId:page-2-MAIN nodeLabel:DO GOOD path:1,HTML,1,BODY,3,MAIN selector:body > main#main snippet:<main id="main"> type:node] score:0.253423] map[node:map[boundingRect:map[bottom:613 height:175 left:271 right:1079 top:438 width:808] lhId:page-4-H1 nodeLabel:APRIL IS DO GOOD MONTH path:1,HTML,1,BODY,3,MAIN,0,DIV,0,UMD-ELEMENT-HERO,a,#document-fragment,1,DIV,1,DIV,0,DIV,0,DIV,0,H1 selector:div.umd-layout-space-horizontal-larger > div.umd-hero-default__text > div.text-lockup-large > h1.umd-campaign-extralarge-dark snippet:<h1 class="umd-campaign-extralarge-dark"> type:node] score:0.002841]]

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

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
2 male students walking outside div.pathway-image-container-wrapper > div.umd-asset-image-wrapper-scaled > div.image-container > img
/production/umd/images/default/2-students-walking.jpg?w=1...318.8 KiB278.4 KiB
FORWARD: The University of Maryland Campaign for the Fearless text on top of br… div.pathway-image-container-wrapper > div.umd-asset-image-wrapper > div.image-container > img
/production/umd/images/default/forward-square.jpg?w=1920&...77.9 KiB60.6 KiB
View of UMD m circle div.umd-asset-image-wrapper > div.image-container > a > img
/production/umd/images/default/placeholder-2.webp?w=600&h...50.6 KiB46.6 KiB
Two students holding maryland day swag div.umd-asset-image-wrapper > div.image-container > a > img
/production/umd/images/default/MarylandDay_04262025_JC_44...47.2 KiB42.5 KiB
do good challenge stage div.card-overlay-image-container > div.umd-asset-image-wrapper-scaled > div.image-container > img
/production/umd/images/default/2018-do-good-challenge_269...64.4 KiB36.6 KiB
Students inside the Do Good accelerator div.card-overlay-image-container > div.umd-asset-image-wrapper-scaled > div.image-container > img
/production/umd/images/default/2019-Do-Good-Accelerator-1...63.3 KiB35.4 KiB
Do Good Service Challange Graphic div > umd-element-event > a > img
/production/umd/images/default/TV-Screen-Graphics-and-Yar...48.1 KiB15.1 KiB
dogoodinstitute at thurgood div.card-overlay-image-container > div.umd-asset-image-wrapper-scaled > div.image-container > img
/production/umd/images/default/ThurgoodMarshallHall_12052...42.4 KiB14.5 KiB
Safe Drinking WATER Study team members Leena Malayil and Rianna Murray hold a p… div.card-overlay-image-container > div.umd-asset-image-wrapper-scaled > div.image-container > img
/production/umd/images/default/LeenaMalayil_RiannaMurray_...40.8 KiB12.9 KiB

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
DO GOOD body > main#main
0.253
body body
0.006
APRIL IS DO GOOD MONTH div.umd-layout-space-horizontal-larger > div.umd-hero-default__text > div.text-lockup-large > h1.umd-campaign-extralarge-dark
0.003

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

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.

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.

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.

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 Evaluation1.4 s
Other398 ms
Style & Layout170 ms
Parse HTML & CSS51 ms
Script Parsing & Compilation50 ms
Rendering42 ms
Garbage Collection37 ms

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
University of Maryland div.umd-layout-space-horizontal-full > umd-element-navigation-header > a > img
/production/umd/logos/default/primary-logo-dark.svg?dm=17...

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

Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
LCP request discovery
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 5 user timings
Avoid long main-thread tasks 5 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 10 ms
Server Backend Latencies 350 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 100 ms
INP breakdown
Avoid non-composited animations
94

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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.quote-featured-container-spacer > div.quote-featured-container-wrapper > div.quote-featured-texture > img.quote-background-texture div.quote-featured-container-spacer > div.quote-featured-container-wrapper > div.quote-featured-texture > img.quote-background-texture

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.

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
`[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
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
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[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.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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.
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.
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.
100

Best Practices

General

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 deprecated APIs
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
Redirects HTTP traffic to HTTPS
Detected JavaScript libraries
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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.quote-featured-container-spacer > div.quote-featured-container-wrapper > div.quote-featured-texture > img.quote-background-texture div.quote-featured-container-spacer > div.quote-featured-container-wrapper > div.quote-featured-texture > img.quote-background-texture

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
Document has a meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback