C — https://www.yale.edu | BeaverCheck Audit

Site Health

Score: 79 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

1 control(s) without accessible label

Accessibility › Form Accessibility

4 button(s) with no accessible text

Accessibility › Link & Button Quality

7 image-only link(s) without alt text

Accessibility › Link & Button Quality

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.yale.edu)](https://beavercheck.com/results/fccd2d4f-09ce-53dc-2faf-6588e480e407)

HTML

<a href="https://beavercheck.com/results/fccd2d4f-09ce-53dc-2faf-6588e480e407"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.yale.edu" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.yale.edu

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

5.20 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

12.73 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

988 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

6.37 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

12.77 s

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.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

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.

URL	Est Savings
www.yale.edu/sites/all/themes/yale_blue/fonts/yalenew-roman-webfont.woff2	30 ms
/sites/all/themes/yale_blue/fonts_new/Mallory/Mallory/Mal...	30 ms
/sites/all/themes/yale_blue/fonts_new/Mallory/Mallory/Mal...	30 ms
/sites/all/themes/yale_blue/fonts_new/Mallory/Mallory/Mal...	30 ms
www.yale.edu/sites/all/themes/yale_blue/fonts/fontawesome-webfont.woff2?v=4.6.3	25 ms
/sites/all/themes/yale_blue/fonts_new/Mallory/Mallory/Mal...	10 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.

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:81.512 source:map[column:640 line:4 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.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:79.712 source:map[column:30882 line:3 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js urlProvider:network]] map[reflowTime:0.428 source:map[column:30979 line:3 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js urlProvider:network]] map[reflowTime:0.292 source:map[column:31260 line:3 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js urlProvider:network]] map[reflowTime:0.065 source:map[column:31351 line:3 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js urlProvider:network]] map[reflowTime:0.15 source:map[column:31632 line:3 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js urlProvider:network]] map[reflowTime:0.188 source:map[column:31782 line:3 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js urlProvider:network]] map[reflowTime:0.204 source:map[column:31900 line:3 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js urlProvider:network]] map[reflowTime:0.221 source:map[column:41 line:1051 type:source-location url:https://www.yale.edu/sites/default/files/js/js_Hfha9RCTNm8mqMDLXriIsKGMaghzs4ZaqJPLj2esi7s.js urlProvider:network]] map[reflowTime:0.252 source:map[column:3774 line:5 type:source-location url:https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js urlProvider:network]] map[reflowTime:0.595 source:map[column:9663 line:7 type:source-location url:https://www.yale.edu/sites/all/themes/yale_blue/js/site.js?t=202604070135 urlProvider:network]] map[reflowTime:6.373 source:map[column:24618 line:8 type:source-location url:https://www.yale.edu/sites/all/themes/yale_blue/js/site.js?t=202604070135 urlProvider:network]] map[reflowTime:0.62 source:map[column:994 line:8 type:source-location url:https://www.yale.edu/sites/all/themes/yale_blue/js/site.js?t=202604070135 urlProvider:network]] map[reflowTime:0.298 source:map[column:1362 line:8 type:source-location url:https://www.yale.edu/sites/all/themes/yale_blue/js/site.js?t=202604070135 urlProvider:network]] map[reflowTime:0.439 source:map[column:1555 line:8 type:source-location url:https://www.yale.edu/sites/all/themes/yale_blue/js/site.js?t=202604070135 urlProvider:network]] map[reflowTime:0.394 source:map[column:1631 line:8 type:source-location url:https://www.yale.edu/sites/all/themes/yale_blue/js/site.js?t=202604070135 urlProvider:network]] map[reflowTime:0.445 source:map[column:31860 line:7 type:source-location url:https://www.yale.edu/sites/all/themes/yale_blue/js/site.js?t=202604070135 urlProvider:network]] map[reflowTime:0.408 source:map[column:31159 line:8 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

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_500x282/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.

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.

URL	Transfer Size	Duration
www.yale.edu/sites/default/files/googleanalytics/js?td4wqg	55.1 KiB	300 ms
ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js	32.8 KiB	1.1 s
www.yale.edu/sites/all/themes/yale_blue/css/site.css?t=202604070135	59.9 KiB	901 ms
/sites/default/files/css/css_xE-rWrJf-fncB6ztZfd2huxqgxu4...	2.8 KiB
/sites/default/files/js/js_HR7LuITZhSc9MfBClZ7kkiN4YCNnhr...	19.6 KiB	150 ms
www.yale.edu/sites/default/files/css_injector/css_injector_34.css?td4wqg	604 B
/sites/default/files/js/js_rpAwC7cddiEuKQzuro46QwxuNJ50C4...	551 B
/sites/default/files/js/js_Hfha9RCTNm8mqMDLXriIsKGMaghzs4...	14.8 KiB	300 ms
/sites/default/files/js/js_Xp42x4IeuhdbL6uORzJ6WS2Q7LigXF...	4.1 KiB
maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css	7.4 KiB	819 ms
/sites/default/files/css/css_8R_0pUYRsUgcn_DqYThF9sN84SOt...	413 B
/sites/default/files/js/js_f_6-OzlFXjayKlsU5sJKLwjz7LFQvd...	972 B
www.yale.edu/sites/default/files/css_injector/css_injector_28.css?td4wqg	531 B
/sites/default/files/js/js_zDrhTCYsC_8pVOJuGALtlm88oNEaqv...	18.7 KiB
www.yale.edu/sites/all/libraries/respondjs/respond.min.js?td4wqg	2.4 KiB
/sites/default/files/css/css_LJcGPs70sA8Q5YJ2kbPV0zbY7Ksw...	947 B
/sites/default/files/css/css_RuHKBBm6OYqkjSeQK2mF9fQpeWuc...	5.2 KiB
www.yale.edu/sites/default/files/css_injector/css_injector_26.css?td4wqg	499 B
/sites/default/files/css/css_wTttUvLLkpbnKFb8mVr2FiTMc9bX...	1.7 KiB
www.yale.edu/sites/default/files/css_injector/css_injector_25.css?td4wqg	1008 B	150 ms
/sites/default/files/css/css_GokYvum1WD4rmNWBuxVsmJ6gm9uM...	1.4 KiB

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
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	12.4 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_235/public/2013_...	21.3 KiB	12.3 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.

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.

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Estimated savings: 150 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.

Estimated savings: 600 ms 53.4 KiB

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

Estimated savings: 1.5 s 264.4 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=4e6460	152.8 KiB	63.7 KiB
www.yale.edu/sites/all/themes/yale_blue/js/site.js?t=202604070135	72.7 KiB	37.5 KiB
www.yale.edu/sites/default/files/googleanalytics/js?td4wqg	54.8 KiB	33.8 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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.yale.edu/sites/all/themes/yale_blue/js/site.js?t=202604070135	877 ms	396 ms	50 ms
ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js	459 ms	106 ms	20 ms
Unattributable	422 ms	12 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-D491W728G4&cx=c&gtm=4e6460	387 ms	311 ms	73 ms
www.googletagmanager.com/gtm.js?id=GTM-MCLMJ9V	218 ms	165 ms	51 ms
www.googletagmanager.com/gtag/js?id=UA-991898-23&l=dataLayer&cx=c	208 ms	138 ms	68 ms
www.yale.edu/	205 ms	91 ms	22 ms
js-agent.newrelic.com/nr-rum-1.312.1.min.js	185 ms	157 ms	9.5 ms
siteimproveanalytics.com/js/siteanalyze_66356571.js	184 ms	93 ms	29 ms
www.yale.edu/sites/default/files/googleanalytics/js?td4wqg	110 ms	52 ms	26 ms
www.google-analytics.com/analytics.js	83 ms	75 ms	7.8 ms
/sites/default/files/js/js_Xp42x4IeuhdbL6uORzJ6WS2Q7LigXF...	58 ms	14 ms	1.9 ms
www.yale.edu/sites/all/themes/yale_blue/css/site.css?t=202604070135	53 ms	0.0 ms	0.0 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

Category	Time Spent
Script Evaluation	1.7 s
Other	833 ms
Style & Layout	496 ms
Script Parsing & Compilation	387 ms
Parse HTML & CSS	171 ms
Rendering	38 ms

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

●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,462 KiB

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 15 long tasks found

●Avoid non-composited animations 4 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 200 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 20 ms

○INP breakdown

○Avoid large layout shifts

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.

Failing Elements
All News Alumni Arts & Humanities Business Campus & Community Environment Healt… `div.news_explore_row > div.news_explore_supporting > form.news_explore_form > div.fs-dropdown`
Info for Visiting Yale Campus Tours Maps & Directions Yale Visitor Center Museu… `div.footer_nav_section > div.region > form.visitor_form > 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.

Failing Elements
Yale School of Art EXPLORE THE SCHOOL Benjamin Franklin College EXPLORE THE … `div.fs-carousel-wrapper > div.fs-carousel-container > div.fs-carousel-canister > div.explore_carousel_item`
The Yale Stradivari EXPLORE THE COLLECTION Brewing history LEARN MORE `div.fs-carousel-wrapper > div.fs-carousel-container > div.fs-carousel-canister > div.explore_carousel_item`

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.

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.

Failing Elements
1 `div.explore_grid_wrapper > div#fs-carousel__1 > div.fs-carousel-pagination > button.fs-carousel-page`
2 `div.explore_grid_wrapper > div#fs-carousel__1 > div.fs-carousel-pagination > button.fs-carousel-page`
3 `div.explore_grid_wrapper > div#fs-carousel__1 > div.fs-carousel-pagination > button.fs-carousel-page`

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.

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`

○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

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

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

	URL	Displayed size	Actual size	Expected size
Man rubbing his eye `article.news_explore_article > figure.news_explore_figure_full > picture.news_explore_picture_full > img.news_explore_image_full`	/sites/default/files/styles/explore_news_295x198/public/a...	294 x 170	295 x 171	441 x 255

●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

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.02 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.28 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

44 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.004

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.02 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

2.11 s

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.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

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.

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

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

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.

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.

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

	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.

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.

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.

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

ARIA

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

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`

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.

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

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

Browse & Analyze

Learn

Results for https://www.yale.edu

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Best practices

Best Practices

User Experience

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Best Practices

SEO

Keyboard Shortcuts