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

47

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
home-c52.nice-incontact.com/inContact/ChatClient/js/bundle.min.js0.0 ms262.8 KiB
js-cdn.dynatrace.com/jstag/16294a69b33/bf19966hyx/4ce8449b9991fc50_complete.js3600.0 s148.9 KiB
consent.trustarc.com/v2/autoblock?cmId=3p3tmg3600.0 s63.2 KiB
consent.trustarc.com/v2/notice/3p3tmg?pcookie3600.0 s32.0 KiB
cdn.raygun.io/raygun4js/raygun.min.js0.0 ms22.7 KiB
/inContact/ChatClient/styles/themes/inContact/screen.css0.0 ms8.5 KiB
consent.trustarc.com/v2/autoblockasset/core.min.js?cmId=3p3tmg3600.0 s6.6 KiB
home-c52.nice-incontact.com/inContact/ChatClient/js/embed.min.js0.0 ms4.0 KiB
home-c52.nice-incontact.com/inContact/ChatClient/js/lib/fetch.min.js0.0 ms3.7 KiB
script.crazyegg.com/pages/scripts/0113/7173.js300.0 s2.7 KiB
www.byu.edu/override-fonts.css0.0 ms2.2 KiB
home-c52.nice-incontact.com/inContact/ChatClient/js/lib/classListPolyfill.min.js0.0 ms2.1 KiB
brightspot.byu.edu/override-styles.css0.0 ms1.4 KiB
home-c52.nice-incontact.com/inContact/ChatClient/js/chatClient-v2.js0.0 ms1.3 KiB
/inContact/ChatClient/styles/themes/inContact/screen.css0.0 ms0 B

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.

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:2.957 source:map[column:133 line:159 type:source-location url:https://www.byu.edu/ruxitagentjs_ICA15789NPRTUVXfqrux_10335260306043831.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:1.069 source:map[column:291 line:367 type:source-location url:https://www.byu.edu/ruxitagentjs_ICA15789NPRTUVXfqrux_10335260306043831.js urlProvider:network]] map[reflowTime:38.936 source:map[type:text value:[unattributed]]] map[reflowTime:2.957 source:map[column:368 line:598 type:source-location url:https://www.byu.edu/ruxitagentjs_ICA15789NPRTUVXfqrux_10335260306043831.js urlProvider:network]]]

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
value: No additional origins are good candidates for preconnecting

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.

URLTransfer SizeDuration
home-c52.nice-incontact.com/inContact/ChatClient/js/embed.min.js4.0 KiB1.3 s
brightspot.byu.edu/override-styles.css1.4 KiB1.2 s
www.byu.edu/ruxitagentjs_ICA15789NPRTUVXfqrux_10335260306043831.js128.2 KiB1.8 s
www.byu.edu/override-fonts.css2.2 KiB
/resource/00000173-da06-d043-a7ff-dece7d790000/styleguide...0 B780 ms
/resource/00000173-da06-d043-a7ff-dece7d790000/styleguide...0 B731 ms
/css2?family=IBM+Plex+Sans:ital,wght@0,100..700;1,100..70...1.2 KiB863 ms

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.

URLProtocol
home-c52.nice-incontact.com/inContact/ChatClient/js/embed.min.jshttp/1.1
/inContact/ChatClient/ChatClient.aspx?poc=1c3ca980-8c5c-4...http/1.1
home-c52.nice-incontact.com/inContact/ChatClient/chatButton.htmlhttp/1.1
home-c52.nice-incontact.com/inContact/ChatClient/js/chatClient-v2.jshttp/1.1
/inContact/ChatClient/styles/themes/inContact/screen.csshttp/1.1
home-c52.nice-incontact.com/inContact/ChatClient/index.htmlhttp/1.1
home-c52.nice-incontact.com/inContact/ChatClient/js/lib/fetch.min.jshttp/1.1
home-c52.nice-incontact.com/inContact/ChatClient/js/lib/classListPolyfill.min.jshttp/1.1
home-c52.nice-incontact.com/inContact/ChatClient/js/bundle.min.jshttp/1.1
home-c52.nice-incontact.com/inContact/ChatClient/locales/en-US/translation.jsonhttp/1.1
home-c52.nice-incontact.com/inContact/ChatClient/locales/en/translation.jsonhttp/1.1

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.5 s
URLTime Spent
byu.edu/1.2 s
www.byu.edu/1.3 s
www.byu.edu/0.0 ms

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 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: 310 ms 277.1 KiB
URLTransfer SizeEst Savings
js-cdn.dynatrace.com/jstag/16294a69b33/bf19966hyx/4ce8449b9991fc50_complete.js148.4 KiB131.5 KiB
www.googletagmanager.com/gtag/js?id=G-FVREXEDRZ9156.1 KiB65.5 KiB
www.byu.edu/ruxitagentjs_ICA15789NPRTUVXfqrux_10335260306043831.js128.1 KiB51.9 KiB
/pages/versioned/common-scripts/4ce8c7df8d425cc5046457682...55.1 KiB28.2 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.

URLTotal CPU TimeScript EvaluationScript Parse
www.byu.edu/ruxitagentjs_ICA15789NPRTUVXfqrux_10335260306043831.js918 ms766 ms63 ms
Unattributable643 ms28 ms0.0 ms
consent.trustarc.com/v2/notice/3p3tmg?pcookie481 ms268 ms14 ms
www.byu.edu/447 ms61 ms10 ms
/pages/versioned/common-scripts/4ce8c7df8d425cc5046457682...442 ms365 ms31 ms
www.googletagmanager.com/gtag/js?id=G-FVREXEDRZ9359 ms287 ms69 ms
js-cdn.dynatrace.com/jstag/16294a69b33/bf19966hyx/4ce8449b9991fc50_complete.js105 ms49 ms55 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.

CategoryTime Spent
Script Evaluation1.9 s
Other737 ms
Style & Layout353 ms
Script Parsing & Compilation257 ms
Garbage Collection116 ms
Rendering94 ms
Parse HTML & CSS57 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
BYU div.Header-contentTop > div.Header-logo > a > img.PageLogo-image
/e4/0a/b679ee0a41d9b1675fc78cd03239/byu-logo-white-small.svg
BYU div.Footer-container > div.Footer-logo > a > img.PageLogo-image
/e4/0a/b679ee0a41d9b1675fc78cd03239/byu-logo-white-small.svg
Brigham Young University div.Footer-container > div.Footer-secondaryLogo > a > img.PageLogo-image
brightspotcdn.byu.edu/0c/14/9fea42874f02a621265d46134903/byu-wordmark-ring.svg

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

●Layout shift culprits
●Optimize DOM size
●Font display
●Improve image delivery
●LCP breakdown
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,254 KiB
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 13 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 200 ms
●Server Backend Latencies 230 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 220 ms
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
○Avoid large layout shifts
89

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

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.Page-body > div.ie-div-position-customer-chat > div.button-iframe-wrap > iframe#icChatButton body.Page-body > div.ie-div-position-customer-chat > div.button-iframe-wrap > iframe#icChatButton

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1_Primary_white.svg div.Header-stickyContainer > ps-header.Header > div.Header-contentTop > h1.Header-home-logo
Contact BYU Info Call or Text: 801-422-4636 Email: byu-info@byu.edu Brigham … span.Enhancement > div.RawHtmlModule > div.RawHtmlModule-html > div#byu-info
801-422-4636 div.RawHtmlModule-html > div#byu-info > p > a
byu-info@byu.edu div.RawHtmlModule-html > div#byu-info > p > a
Brigham Young University Provo, UT 84602 div.RawHtmlModule > div.RawHtmlModule-html > div#byu-info > p.mailing-address

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go Forth to Serve div.PromoCarouselHeadline > div.PromoCarouselHeadline-container > div.PromoCarouselHeadline-content > h3.PromoCarouselHeadline-title

These are opportunities to improve keyboard navigation in your application.

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
A-Z Index div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU Mobile App (Android) div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU Mobile App (iOS) div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Student Development Services div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Employment at BYU div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Office of Belonging div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Helping Distressed Students div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Library div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Office of IT div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Title IX (sexual misconduct) div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
University Police & Parking div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU-Hawaii div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU-Idaho div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU-Pathway Worldwide div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
Ensign College div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU Alumni div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU Athletics div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU News div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYU Store div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink
BYUtv div.NavigationItem > div.NavigationItem-items > div.NavigationItem-items-item > a.NavigationLink

These items highlight common accessibility best practices.

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
More div.PromoCarouselHeadline-container > div.PromoCarouselHeadline-content > div.PromoCarouselHeadline-cta > a.btn
More div.PromoCarouselHeadline-container > div.PromoCarouselHeadline-content > div.PromoCarouselHeadline-cta > a.btn
More div.PromoCarouselHeadline-container > div.PromoCarouselHeadline-content > div.PromoCarouselHeadline-cta > a.btn
More div.PromoCarouselHeadline-container > div.PromoCarouselHeadline-content > div.PromoCarouselHeadline-cta > a.btn
801-422-4636 div.RawHtmlModule-html > div#byu-info > p > a
byu-info@byu.edu div.RawHtmlModule-html > div#byu-info > p > a
○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
●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
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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.
○`<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.
77

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.

Insecure URLRequest Resolution
www.byu.edu/Allowed

General

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
www.byu.edu/ruxitagentjs_ICA15789NPRTUVXfqrux_10335260306043831.js line 410, col 352
[autoblock] Core is unavailable.
●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 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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
92

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
news.byu.edu/byugradMore
/intellect/byu-animation-adlab-students-claim-top-student...More
/character/new-church-commissioned-easter-paintings-creat...More
www.byu.edu/faith-and-educationMore

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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback