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

20

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.

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:1.0461360000000004] map[node:map[boundingRect:map[bottom:10464 height:10381 left:0 right:412 top:83 width:412] lhId:page-1-BODY nodeLabel:body.menuBg1 path:1,HTML,1,BODY selector:body.menuBg1 snippet:<body class="menuBg1"> type:node] score:1 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:259 height:176 left:0 right:412 top:83 width:412] lhId:page-0-IMG nodeLabel:The iconic silhouette of Fraser Hall on KU’s Lawrence campus is set against the… path:1,HTML,1,BODY,2,DIV,0,DIV,5,MAIN,1,DIV,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,SECTION,0,PICTURE,6,IMG selector:div > section#section692 > picture > img snippet:<img loading="eager" width="1" height="1" src="https://ku.edu/sites/ku_new_homepage/files/styles/hero_full_sm/public/imag…" alt="The iconic silhouette of Fraser Hall on KU’s Lawrence campus is set agains…" typeof="foaf:Image"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:823 height:299 left:0 right:412 top:525 width:412] lhId:page-2-SECTION nodeLabel:This website uses cookies and other technologies to improve the functionality a… path:1,HTML,1,BODY,0,SECTION selector:body.menuBg1 > section#sliding-popup snippet:<section id="sliding-popup" class="sliding-popup-bottom show"> type:node] score:0.002471] map[node:map[boundingRect:map[bottom:823 height:299 left:0 right:412 top:525 width:412] lhId:page-2-SECTION nodeLabel:This website uses cookies and other technologies to improve the functionality a… path:1,HTML,1,BODY,0,SECTION selector:body.menuBg1 > section#sliding-popup snippet:<section id="sliding-popup" class="sliding-popup-bottom show"> type:node] score:0.002469] map[node:map[boundingRect:map[bottom:823 height:299 left:0 right:412 top:525 width:412] lhId:page-2-SECTION nodeLabel:This website uses cookies and other technologies to improve the functionality a… path:1,HTML,1,BODY,0,SECTION selector:body.menuBg1 > section#sliding-popup snippet:<section id="sliding-popup" class="sliding-popup-bottom show"> type:node] score:0.002377] map[node:map[boundingRect:map[bottom:823 height:299 left:0 right:412 top:525 width:412] lhId:page-2-SECTION nodeLabel:This website uses cookies and other technologies to improve the functionality a… path:1,HTML,1,BODY,0,SECTION selector:body.menuBg1 > section#sliding-popup snippet:<section id="sliding-popup" class="sliding-popup-bottom show"> type:node] score:0.002305]]

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:18.355 source:map[column:21960 line:31 type:source-location url:https://ku.edu/libraries/ku-web-styleguide/dist/main.min.js?tduv00 urlProvider:network]] map[reflowTime:68.256 source:map[column:28282 line:31 type:source-location url:https://ku.edu/libraries/ku-web-styleguide/dist/main.min.js?tduv00 urlProvider:network]]]

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: The iconic silhouette of Fraser Hall on KU’s Lawrence campus is set against the…
path: 1,HTML,1,BODY,2,DIV,0,DIV,5,MAIN,1,DIV,0,DIV,0,DIV,0,ARTICLE,0,DIV,0,SECTION,0,PICTURE,6,IMG
selector: div > section#section692 > picture > img
snippet: <img loading="eager" width="1" height="1" src="https://ku.edu/sites/ku_new_homepage/files/styles/hero_full_sm/public/imag…" alt="The iconic silhouette of Fraser Hall on KU’s Lawrence campus is set agains…" typeof="foaf:Image">

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

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
A collage of photos focused on the many avenues of innovation and research fost… div.row > div.col-12 > picture > img
/sites/ku_new_homepage/files/styles/wide_full_sm/public/i...481.8 KiB440.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
body.menuBg1 body.menuBg1
1.000
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002
This website uses cookies and other technologies to improve the functionality a… body.menuBg1 > section#sliding-popup
0.002

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

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 91.7 KiB
URLTransfer SizeEst Savings
/sites/ku_new_homepage/files/css/css_jHZKheemfUxsOfHmvCE4...96.4 KiB91.7 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.1 s 118.6 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
Script Evaluation661 ms
Other495 ms
Style & Layout471 ms
Script Parsing & Compilation311 ms
Parse HTML & CSS97 ms
Rendering60 ms
Garbage Collection8.5 ms

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: 0.0 ms 4.1 KiB
URLTransfer SizeEst Savings
webmedia.ku.edu/cookie-consent/cookie-consent.js6.0 KiB4.1 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
KU The University of Kansas div.col-12 > div.footer__logo > a > img.footer__logo--white
ku.edu/libraries/ku-web-styleguide/images/logos/KUSig_Horz_Web_White.png
KU degree stats logo div.col-12 > div.footer__degree-stats > a > img.footer-degree-stats-logo--white
ku.edu/libraries/ku-web-styleguide/images/logos/KSDegreeStats_Logo_Std.png

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

●Document request latency
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Avoids enormous network payloads Total size was 1,916 KiB
●User Timing marks and measures 5 user timings
●JavaScript execution time 0.9 s
●Avoid long main-thread tasks 8 long tasks found
●Avoid non-composited animations 2 animated elements found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 60 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 90 ms
○INP breakdown
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.
●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
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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.
○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.
100

Best Practices

●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 DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
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