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

35

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
case.edu/app-ab9f16e66a93cbeaf23d.js0.0 ms229.3 KiB
case.edu/framework-dec20595894a8c0f69a7.js0.0 ms137.4 KiB
case.edu/a8ef1c6e0816d2ab98798ff782fd2b50b3ecbd2c-19d46042c8c8491297c0.js0.0 ms101.6 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
case.edu/108-2ad37d8d720b7cf08b59.js0.0 ms70.8 KiB
/cwru/fonts/Arizona-Fonts/Arizona-Sans/ABCArizonaSans-Reg...0.0 ms44.6 KiB
/cwru/fonts/Arizona-Fonts/Arizona-Sans/ABCArizonaSans-Bol...0.0 ms42.2 KiB
/cwru/fonts/Arizona-Fonts/Arizona-Sans/ABCArizonaSans-Med...0.0 ms41.1 KiB
/cwru/fonts/Arizona-Fonts/Arizona-Sans/ABCArizonaSans-Reg...0.0 ms40.6 KiB
/signals/config/285202632763628?v=2.9.303&r=stable&domain...1200.0 s44.5 KiB
/cwru/fonts/Arizona-Fonts/Arizona-Sans/ABCArizonaSans-Bol...0.0 ms39.3 KiB
cdn.blueconic.net/case.js600.0 s40.4 KiB
f.vimeocdn.com/p/4.46.41/js/player.module.js1209600.0 s210.2 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
dudbm6bcnmy8e.cloudfront.net/cwru/img/cwru_logo_primary_white.svg0.0 ms16.4 KiB
dudbm6bcnmy8e.cloudfront.net/cwru/img/bicentennial-logo-horizontal-white.png0.0 ms16.1 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
case.edu/161f9f66cc94f5b5cc83b7f1dbe8b70b34b79769-dbc5dd88ddac9239ffb0.js0.0 ms12.5 KiB
f.vimeocdn.com/p/4.46.41/js/vendor.module.js1209600.0 s93.5 KiB
player.vimeo.com/api/player.js1800.0 s9.0 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
case.edu/webpack-runtime-8711b00a326a200806fa.js0.0 ms6.5 KiB
static.hotjar.com/c/hotjar-2954518.js?sv=760.0 s6.2 KiB
dudbm6bcnmy8e.cloudfront.net/cwru/fonts/Arizona-Fonts/arizona.css0.0 ms3.4 KiB
f.vimeocdn.com/p/4.46.41/css/player.css1209600.0 s23.9 KiB
case.edu/262-b956f32438d3de24ac37.js0.0 ms1.4 KiB
case.edu/553-21f935f77770692e3946.js0.0 ms1.4 KiB
case.edu/68-f2684614fc986488fba7.js0.0 ms908 B
applygrad.case.edu/ping1789.0 s969 B
go.case.edu/ping1789.0 s952 B
/collect?v=2&fmt=js&pid=945234&time=1776808327218&url=htt...0.0 ms693 B
/rp.gif?ts=1776808327212&id=a2_hatpyjw6kj1f&event=PageVis...0.0 ms666 B
case.edu/depot/depot.css0.0 ms419 B
webapps.case.edu/t4/rave/add_banner0.0 ms305 B
hello.myfonts.net/count/372e74604800.0 s370 B
/tr/?id=285202632763628&ev=PageView&dl=https%3A%2F%2Fcase...0.0 ms16 B

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:53.496 source:map[type:text value:[unattributed]]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:345.237 label:Time to first byte subpart:timeToFirstByte] map[duration:1418.299 label:Resource load delay subpart:resourceLoadDelay] map[duration:25.003 label:Resource load duration subpart:resourceLoadDuration] map[duration:1404.233 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: Aerial photo of Case Western Reserve University's campus
path: 1,HTML,1,BODY,12,DIV,0,DIV,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,2,PICTURE,1,IMG
selector: div.vimeo-video-container > div.gatsby-image-wrapper > picture > img
snippet: <img layout="fullWidth" data-main-image="" style="opacity: 1;" sizes="100vw" decoding="async" loading="lazy" alt="Aerial photo of Case Western Reserve University's campus" src="https://case.edu/static/255cbb9bf47dc9e11185dd202def8f67/b9516/Vimeoplaceh…" srcset="/static/255cbb9bf47dc9e11185dd202def8f67/8f9d4/VimeoplaceholderSpring2026.…">

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: Aerial photo of Case Western Reserve University's campus
path: 1,HTML,1,BODY,12,DIV,0,DIV,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,2,PICTURE,1,IMG
selector: div.vimeo-video-container > div.gatsby-image-wrapper > picture > img
snippet: <img layout="fullWidth" data-main-image="" style="opacity: 1;" sizes="100vw" decoding="async" loading="lazy" alt="Aerial photo of Case Western Reserve University's campus" src="https://case.edu/static/255cbb9bf47dc9e11185dd202def8f67/b9516/Vimeoplaceh…" srcset="/static/255cbb9bf47dc9e11185dd202def8f67/8f9d4/VimeoplaceholderSpring2026.…">

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.

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.

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
Happy Class of 2025 graduates walk through bubbles at CWRU&#039;s annual clap o… div.styles-module--container--903fb > a > div.styles-module--frame--8aa89 > img
/news/sites/default/files/styles/article_480x480_/public/...47.7 KiB22.5 KiB
Reid Tileston celebrating after the successful defense of his thesis div.styles-module--container--903fb > a > div.styles-module--frame--8aa89 > img
/news/sites/default/files/styles/article_480x480_/public/...39.4 KiB14.2 KiB
CWRU bicentennial logo a.styles-module--link--bf1a5 > span > span.bi-link-container > img.bi-logo
/static/bicentennial-logo-horizontal-dd58ae4455db6a22eebe...15.0 KiB13.6 KiB
People stand for a ribbon cutting of the new Sherwin-Williams Paint and Coating… div.styles-module--container--903fb > a > div.styles-module--frame--8aa89 > img
/news/sites/default/files/styles/article_480x480_/public/...36.9 KiB11.7 KiB
Bob Pavey div.styles-module--container--903fb > a > div.styles-module--frame--8aa89 > img
/news/sites/default/files/styles/article_480x480_/public/...31.1 KiB6.0 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

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 Evaluation3.7 s
Other834 ms
Script Parsing & Compilation715 ms
Style & Layout417 ms
Rendering214 ms
Garbage Collection89 ms
Parse HTML & CSS59 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 reasonFailure type
The page has an unload handler in a sub frame.Actionable

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: 0.0 ms 60.5 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
Case Western Reserve University Bicentennial Logo div.container > div.styles-module--footer-top--46556 > div.col-xs-12 > img.undefined
dudbm6bcnmy8e.cloudfront.net/cwru/img/bicentennial-logo-horizontal-white.png
CWRU bicentennial logo a.styles-module--link--bf1a5 > span > span.bi-link-container > img.bi-logo
/static/bicentennial-logo-horizontal-dd58ae4455db6a22eebe...
CWRU Logo div.styles-module--row--9c23b > div.col-xs-12 > a > img.styles-module--logo--8d4fa
dudbm6bcnmy8e.cloudfront.net/cwru/img/cwru_logo_primary_white.svg

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

●Layout shift culprits
●Optimize DOM size
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 15 user timings
●Avoid long main-thread tasks 20 long tasks found
●Network Requests
●Network Round Trip Times 120 ms
●Server Backend Latencies 160 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 340 ms
●Avoid large layout shifts 1 layout shift 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
●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
●`<frame>` or `<iframe>` elements have a title
●`<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
●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
●Identical links have the same purpose.
○`[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
○`<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
○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.
○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.
○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.
54

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
SharedStorage
cdn.blueconic.net/case.js line 62, col 205

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Mixed Content: The page at 'https://case.edu/' was loaded over HTTPS, but requested an insecure script 'http://gdata.youtube.com/feeds/api/videos/https://youtu.be/uCIzFXPHeXw?v=2&alt=jsonc&callback=storeInfo'. This request has been blocked; the content must be served over HTTPS.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content
●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
●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
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