Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

Request	Cache TTL	Transfer Size
www.yale.edu/sites/default/files/googleanalytics/js?td4wqg	0.0 ms	55.1 KiB
siteimproveanalytics.com/js/siteanalyze_66356571.js	86400.0 s	39.4 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB

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.

URL	Est Savings
www.yale.edu/sites/all/themes/yale_blue/fonts/yalenew-roman-webfont.woff2	40 ms
/sites/all/themes/yale_blue/fonts_new/Mallory/Mallory/Mal...	40 ms
/sites/all/themes/yale_blue/fonts_new/Mallory/Mallory/Mal...	40 ms
/sites/all/themes/yale_blue/fonts_new/Mallory/Mallory/Mal...	35 ms
www.yale.edu/sites/all/themes/yale_blue/fonts/fontawesome-webfont.woff2?v=4.6.3	30 ms
/sites/all/themes/yale_blue/fonts_new/Mallory/Mallory/Mal...	30 ms

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:93.247 source:map[column:54 line:9 type:source-location url:https://www.yale.edu/sites/all/themes/yale_blue/js/site.js?t=202604070135 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: AZA Allsop and fellow musicians performing

path: 1,HTML,1,BODY,3,DIV,5,MAIN,6,ASIDE,1,DIV,0,DIV,1,SECTION,1,DIV,1,DIV,1,DIV,0,FIGURE,0,PICTURE,6,IMG

selector: div.single_flex_callout_media > figure.single_flex_callout_figure > picture.single_flex_callout_picture > img.single_flex_callout_image

snippet: <img class="single_flex_callout_image single_flex_feature_image " src="https://www.yale.edu/sites/default/files/styles/homepage_feature_840x590/p…" alt="AZA Allsop and fellow musicians performing">

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

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.

URL	Transfer Size	Duration
ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js	32.8 KiB	310 ms
/sites/default/files/js/js_Hfha9RCTNm8mqMDLXriIsKGMaghzs4...	14.9 KiB
www.yale.edu/sites/all/themes/yale_blue/css/site.css?t=202604070135	59.9 KiB	120 ms
/sites/default/files/js/js_rpAwC7cddiEuKQzuro46QwxuNJ50C4...	538 B
/sites/default/files/js/js_zDrhTCYsC_8pVOJuGALtlm88oNEaqv...	18.7 KiB
www.yale.edu/sites/default/files/googleanalytics/js?td4wqg	55.1 KiB
/sites/default/files/css/css_8R_0pUYRsUgcn_DqYThF9sN84SOt...	420 B
www.yale.edu/sites/all/libraries/respondjs/respond.min.js?td4wqg	2.5 KiB
/sites/default/files/js/js_HR7LuITZhSc9MfBClZ7kkiN4YCNnhr...	19.7 KiB
maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css	7.4 KiB	276 ms
/sites/default/files/css/css_xE-rWrJf-fncB6ztZfd2huxqgxu4...	2.7 KiB
/sites/default/files/js/js_Xp42x4IeuhdbL6uORzJ6WS2Q7LigXF...	4.1 KiB
www.yale.edu/sites/default/files/css_injector/css_injector_28.css?td4wqg	419 B
/sites/default/files/js/js_f_6-OzlFXjayKlsU5sJKLwjz7LFQvd...	1008 B
www.yale.edu/sites/default/files/css_injector/css_injector_26.css?td4wqg	544 B
/sites/default/files/css/css_wTttUvLLkpbnKFb8mVr2FiTMc9bX...	1.7 KiB
www.yale.edu/sites/default/files/css_injector/css_injector_25.css?td4wqg	1.0 KiB
/sites/default/files/css/css_LJcGPs70sA8Q5YJ2kbPV0zbY7Ksw...	878 B
/sites/default/files/css/css_RuHKBBm6OYqkjSeQK2mF9fQpeWuc...	5.2 KiB
www.yale.edu/sites/default/files/css_injector/css_injector_34.css?td4wqg	603 B
/sites/default/files/css/css_GokYvum1WD4rmNWBuxVsmJ6gm9uM...	1.3 KiB

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.

	URL	Resource Size	Est Savings
div.explore_overlay > figure.explore_story_figure > picture.explore_story_picture > img.explore_story_image `div.explore_overlay > figure.explore_story_figure > picture.explore_story_picture > img.explore_story_image`	/sites/default/files/styles/explore_yale_294/public/2013_...	30.8 KiB	16.8 KiB
Yale Camerata performing in Woolsey Hall `article.content_card > figure.content_card_figure > picture.content_card_picture > img.content_card_image`	/sites/default/files/styles/carousel_image_575x404/public...	49.6 KiB	11.8 KiB
A group of people sit outside in nice weather at Beinecke Plaza. `a.instagram_teaser > figure.instagram_teaser_figure > span.instagram_teaser_image > img`	www.yale.edu/sites/default/files/images/IG-2818-n.jpg	26.5 KiB	10.8 KiB
div.explore_overlay > figure.explore_story_figure > picture.explore_story_picture > img.explore_story_image `div.explore_overlay > figure.explore_story_figure > picture.explore_story_picture > img.explore_story_image`	/sites/default/files/styles/explore_yale_294/public/bulld...	19.1 KiB	5.0 KiB

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

Diagnostics

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: 40 ms 22.4 KiB

URL	Transfer Size	Est Savings
/sites/default/files/js/js_Hfha9RCTNm8mqMDLXriIsKGMaghzs4...	14.6 KiB	10.1 KiB
/sites/default/files/js/js_zDrhTCYsC_8pVOJuGALtlm88oNEaqv...	18.5 KiB	7.9 KiB
/sites/default/files/js/js_HR7LuITZhSc9MfBClZ7kkiN4YCNnhr...	19.4 KiB	4.4 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: 40 ms 50.6 KiB

URL	Transfer Size	Est Savings
www.yale.edu/sites/all/themes/yale_blue/css/site.css?t=202604070135	59.6 KiB	50.6 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: 80 ms 264.6 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-MCLMJ9V	124.5 KiB	65.3 KiB
www.googletagmanager.com/gtag/js?id=UA-991898-23&l=dataLayer&cx=c	115.0 KiB	64.1 KiB
www.googletagmanager.com/gtag/js?id=G-D491W728G4&cx=c&gtm=4e6460h1	152.8 KiB	63.7 KiB
www.yale.edu/sites/all/themes/yale_blue/js/site.js?t=202604070135	72.7 KiB	37.7 KiB
www.yale.edu/sites/default/files/googleanalytics/js?td4wqg	54.8 KiB	33.8 KiB

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

●Time to Interactive 2.1 s

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 1,705 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 1 animated element found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 100 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 10 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Info for... Students Faculty Staff Alumni INFO FOR... `div.region > div.deskHeader > form.gateway_form > div.fs-dropdown`
All News Alumni Arts & Humanities Business Campus & Community Environment Healt… `div.news_explore_row > header.news_explore_header > form.news_explore_form > div.fs-dropdown`
Explore by Topic Everything Academics Collections Discoveries Experiences Place… `div.explore_controls_row > div.explore_controls_cell > form#views-exposed-form-explore-yale-block-2 > div.fs-dropdown`

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
An American Songbook SACRED MUSIC On April 12, the Yale Camerata will perform … `div.fs-carousel-wrapper > div.fs-carousel-container > div.fs-carousel-canister > article.content_card`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Dwight Hall at Yale LEARN MORE `div.fs-carousel-canister > div.explore_carousel_item > article.explore_story > a.explore_story_link`
Afro-American Cultural Center EXPLORE THE CENTER `div.fs-carousel-canister > div.explore_carousel_item > article.explore_story > a.explore_story_link`
The Yale Stradivari EXPLORE THE COLLECTION `div.fs-carousel-canister > div.explore_carousel_item > article.explore_story > a.explore_story_link`
Brewing history LEARN MORE `div.fs-carousel-canister > div.explore_carousel_item > article.explore_story > a.explore_story_link`
Bulldog Days LEARN MORE `div.explore_grid_wrapper > div.explore_grid_large_content > article.explore_story > a.explore_story_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

●`[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.

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●ARIA input fields have accessible names

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[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

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○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

○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.

○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`