C — https://princeton.edu | BeaverCheck Audit

Site Health

Score: 79 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Mostly accessible, but some users still face barriers.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

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.

How the composite score is calculated

How you compare

Drupal sites average 75

At average

Better than 89% of Drupal sites See full Drupal benchmark →

Adobe Fonts sites average 73

+6 above average

Better than 96% of Adobe Fonts sites See full Adobe Fonts benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

1 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility

1 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fprinceton.edu)](https://beavercheck.com/results/465818ba-5d76-43f4-8d95-43a66749c71f)

HTML

<a href="https://beavercheck.com/results/465818ba-5d76-43f4-8d95-43a66749c71f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fprinceton.edu" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

2 accessibility issues exclude users who rely on assistive technology.

Could reach Estimate based on resolving critical issues

Conversion Barriers

1 critical 6 warning

7 barrier(s) likely increasing bounce by ~26%.

Speed (2)

Page takes 6.1s to load

+12% bounce

Users abandon at ~3s — you're 3.6s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

High main-thread blocking time

+2% bounce

Page is non-interactive for 208ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (2)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$450 investment → $4,600/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +12166%

Investment

$450

4h · 5 findings

Monthly returns

$4,600 /mo

~$55,197 / year

Conversions recovered $4,599
Bandwidth savings $0.29

Regulatory risk avoided

USD 157,500

if kept compliant

ADA Title III USD 150,000
CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

$150 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$450

4.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$150 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,125 / month at risk

~$157,504 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA

No privacy policy link detected
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no cookie policy found
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no privacy policy found
CCPA/CPRA: USD 2,500 – USD 7,500

+2 more

Bandwidth Waste

$0.29 /mo

3660.6 MB/mo × 0.080 USD/GB

Optimize transfer: save ~366 KB per page load
Saves $0.29/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

100

Accessibility

100

Best Practices

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.

4.48 s

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

6.11 s

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

208 ms

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

0.057

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

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

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

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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
/sites/default/files/styles/half_1x/public/images/2026/02...	86400.0 s	239.5 KiB
/sites/default/files/styles/half_1x/public/images/2026/01...	86400.0 s	94.2 KiB
/themes/custom/hobbes/fonts/princetonmonticello_regular/h...	900.0 s	34.2 KiB
/sites/default/files/styles/half_1x_crop/public/images/20...	86400.0 s	46.3 KiB
www.princeton.edu/themes/custom/hobbes/images/logo-white.svg	900.0 s	7.7 KiB
/sites/default/files/css/css_z7jtN4CMh_f2LrvxeTjxmj7MPv_N...	1209600.0 s	65.2 KiB
/sites/default/files/js/js_n_4nz7oMlCkH0q4hR8K78HjM_rgGDf...	1209600.0 s	61.2 KiB
/sites/default/files/js/js_VHwiQXABniyTQ5hjlZvVRtZrYuDQdp...	1209600.0 s	30.0 KiB
/sites/default/files/css/css_7P8V6wldKNzQtYx4zsHvFLPpgevR...	1209600.0 s	1.9 KiB
www.princeton.edu/modules/contrib/google_tag/js/gtag.js?tcretc	1209600.0 s	789 B
/p.css?s=1&k=stk8lop&ht=tk&f=12784.12785.12786.12788.1278...	604800.0 s	172 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.

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
/themes/custom/hobbes/fonts/princetonmonticello_regular/h...	40 ms
/af/8d9b32/0000000000000000000118bf/27/l?primer=7cdcb44be...	10 ms
/af/82db8a/000000000000000077359dfa/30/l?primer=7cdcb44be...	10 ms
/af/9cb78a/0000000000000000000118ad/27/l?primer=7cdcb44be...	5.0 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:29.383 source:map[column:49637 line:2 type:source-location url:https://www.princeton.edu/sites/default/files/js/js_VHwiQXABniyTQ5hjlZvVRtZrYuDQdpJ1pdKmiT6mdFo.js?scope=header&delta=0&language=en&theme=hobbes&include=eJxVzVEOgyAQRdENQVlS89BxHIsOYcCWrr7GxCb-3OR8XVblRM8KDnzE8d0PLPi4WWMkCzHh2y8MFR5FcHkm7H2xP3WlDCY_EWorNPoJQ0u1e0syUnFJtlduJatRkE2q24XeFs6e1x_B4jsV urlProvider:network]] map[reflowTime:22.172 source:map[column:50335 line:2 type:source-location url:https://www.princeton.edu/sites/default/files/js/js_VHwiQXABniyTQ5hjlZvVRtZrYuDQdpJ1pdKmiT6mdFo.js?scope=header&delta=0&language=en&theme=hobbes&include=eJxVzVEOgyAQRdENQVlS89BxHIsOYcCWrr7GxCb-3OR8XVblRM8KDnzE8d0PLPi4WWMkCzHh2y8MFR5FcHkm7H2xP3WlDCY_EWorNPoJQ0u1e0syUnFJtlduJatRkE2q24XeFs6e1x_B4jsV urlProvider:network]] map[reflowTime:0.238 source:map[column:50393 line:2 type:source-location url:https://www.princeton.edu/sites/default/files/js/js_VHwiQXABniyTQ5hjlZvVRtZrYuDQdpJ1pdKmiT6mdFo.js?scope=header&delta=0&language=en&theme=hobbes&include=eJxVzVEOgyAQRdENQVlS89BxHIsOYcCWrr7GxCb-3OR8XVblRM8KDnzE8d0PLPi4WWMkCzHh2y8MFR5FcHkm7H2xP3WlDCY_EWorNPoJQ0u1e0syUnFJtlduJatRkE2q24XeFs6e1x_B4jsV urlProvider:network]] map[reflowTime:0.212 source:map[column:50457 line:2 type:source-location url:https://www.princeton.edu/sites/default/files/js/js_VHwiQXABniyTQ5hjlZvVRtZrYuDQdpJ1pdKmiT6mdFo.js?scope=header&delta=0&language=en&theme=hobbes&include=eJxVzVEOgyAQRdENQVlS89BxHIsOYcCWrr7GxCb-3OR8XVblRM8KDnzE8d0PLPi4WWMkCzHh2y8MFR5FcHkm7H2xP3WlDCY_EWorNPoJQ0u1e0syUnFJtlduJatRkE2q24XeFs6e1x_B4jsV urlProvider:network]]]

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
A close up of hands wearing gloves in a science lab. `div.field > div.view-mode-captionless-full-width > div.field > img`	/sites/default/files/styles/half_1x/public/images/2026/02...	239.0 KiB	191.4 KiB
Illustration of scientists `div.field > div.view-mode-subhero > div.field > img`	/sites/default/files/styles/half_1x_crop/public/images/20...	108.0 KiB	72.8 KiB
Moasic of Princetonians sporting Standup messages. `div.field > div.view-mode-captionless-full-width > div.field > img`	/sites/default/files/styles/half_1x/public/images/2026/01...	93.8 KiB	46.2 KiB
Princeton staff members attend luncheon `div.field > div.view-mode-subhero > div.field > img`	/sites/default/files/styles/half_1x_crop/public/images/20...	79.0 KiB	46.0 KiB
A woman pipettes a fluid into a tiny container while students look on. `div.field > div.view-mode-subhero > div.field > img`	/sites/default/files/styles/half_1x_crop/public/images/20...	46.0 KiB	26.8 KiB
Sophia Yoo gestures toward a large projection of her slide as she presents her … `div.field > div.view-mode-subhero > div.field > img`	/sites/default/files/styles/half_1x_crop/public/images/20...	45.5 KiB	26.5 KiB
Princeton quantum graduate students in a lab `div.field > div.view-mode-subhero > div.field > img`	/sites/default/files/styles/half_1x_crop/public/images/20...	44.8 KiB	26.1 KiB
Students examine a rare printing of the Declaration of Independence in a Specia… `div.field > div.view-mode-cover-image > div.field > img`	/sites/default/files/styles/half_1x_crop/public/images/20...	53.7 KiB	20.2 KiB

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-1-IMG

nodeLabel: Illustration of scientists

path: 1,HTML,1,BODY,1,DIV,1,MAIN,1,SECTION,1,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,A,0,DIV,0,DIV,0,DIV,0,DIV,0,IMG

selector: div.field > div.view-mode-subhero > div.field > img

snippet: <img loading="eager" srcset="/sites/default/files/styles/third_1x_crop/public/images/2026/04/Advancemen…" sizes="(min-width:120em) 26vw, (min-width:40em) 45vw, 90vw" width="960" height="540" src="/sites/default/files/styles/half_1x_crop/public/images/2026/04/Advancement…" alt="Illustration of scientists ">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
use.typekit.net/stk8lop.css	1.3 KiB	755 ms
/sites/default/files/js/js_VHwiQXABniyTQ5hjlZvVRtZrYuDQdp...	30.0 KiB	663 ms
/sites/default/files/css/css_z7jtN4CMh_f2LrvxeTjxmj7MPv_N...	65.2 KiB	829 ms
/p.css?s=1&k=stk8lop&ht=tk&f=12784.12785.12786.12788.1278...	172 B	751 ms
www.princeton.edu/modules/contrib/google_tag/js/gtag.js?tcretc	789 B
/sites/default/files/css/css_7P8V6wldKNzQtYx4zsHvFLPpgevR...	1.9 KiB

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: 1.0 s

URL	Time Spent
princeton.edu/	1.0 s
www.princeton.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 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: 330 ms 58.5 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_z7jtN4CMh_f2LrvxeTjxmj7MPv_N...	65.0 KiB	58.5 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 170 ms 100.7 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-92L6B9PQCG	159.8 KiB	64.8 KiB
/sites/default/files/js/js_n_4nz7oMlCkH0q4hR8K78HjM_rgGDf...	61.0 KiB	35.9 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
The page was evicted from the cache because an active network connection received too much data. Chrome limits the amount of data that a page may receive while cached.	Not actionable

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
div.subfooter > div.subfooter-first > a > img `div.subfooter > div.subfooter-first > a > img`	www.princeton.edu/themes/custom/hobbes/images/logo-white.svg

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.5 s

●Minimizes main-thread work 1.2 s

●Avoid long main-thread tasks 5 long tasks found

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 30 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 30 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

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

○Form elements have associated labels

○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

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 destination	Link Text
www.princeton.edu/one-community/student-life	LEARN MORE

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

100

Accessibility

100

Best Practices

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.21 s

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

1.52 s

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

0 ms

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

0.019

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

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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
/sites/default/files/styles/scale_1440/public/images/2026...	86400.0 s	447.2 KiB
/sites/default/files/styles/scale_1440/public/images/2026...	86400.0 s	179.6 KiB
/themes/custom/hobbes/fonts/princetonmonticello_regular/h...	900.0 s	34.3 KiB
/sites/default/files/styles/third_1x_crop/public/images/2...	86400.0 s	25.7 KiB
www.princeton.edu/themes/custom/hobbes/images/logo-white.svg	900.0 s	7.7 KiB
/sites/default/files/css/css_z7jtN4CMh_f2LrvxeTjxmj7MPv_N...	1209600.0 s	65.2 KiB
/sites/default/files/js/js_n_4nz7oMlCkH0q4hR8K78HjM_rgGDf...	1209600.0 s	61.2 KiB
/sites/default/files/js/js_VHwiQXABniyTQ5hjlZvVRtZrYuDQdp...	1209600.0 s	30.0 KiB
/sites/default/files/css/css_7P8V6wldKNzQtYx4zsHvFLPpgevR...	1209600.0 s	1.9 KiB
www.princeton.edu/modules/contrib/google_tag/js/gtag.js?tcretc	1209600.0 s	790 B
/p.css?s=1&k=stk8lop&ht=tk&f=12784.12785.12786.12788.1278...	604800.0 s	172 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.

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
/themes/custom/hobbes/fonts/princetonmonticello_regular/h...	35 ms
/af/8d9b32/0000000000000000000118bf/27/l?primer=7cdcb44be...	5.0 ms
/af/b825af/0000000000000000000118b1/27/l?primer=7cdcb44be...	5.0 ms
/af/82db8a/000000000000000077359dfa/30/l?primer=7cdcb44be...	5.0 ms

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
A close up of hands wearing gloves in a science lab. `div.field > div.view-mode-captionless-full-width > div.field > img`	/sites/default/files/styles/scale_1440/public/images/2026...	446.5 KiB	276.9 KiB
Illustration of scientists `div.field > div.view-mode-subhero > div.field > img`	/sites/default/files/styles/third_1x_crop/public/images/2...	44.7 KiB	40.0 KiB
Princeton staff members attend luncheon `div.field > div.view-mode-subhero > div.field > img`	/sites/default/files/styles/third_1x_crop/public/images/2...	40.6 KiB	25.0 KiB
Princeton quantum graduate students in a lab `div.field > div.view-mode-subhero > div.field > img`	/sites/default/files/styles/third_1x_crop/public/images/2...	24.8 KiB	21.7 KiB
A woman pipettes a fluid into a tiny container while students look on. `div.field > div.view-mode-subhero > div.field > img`	/sites/default/files/styles/third_1x_crop/public/images/2...	25.5 KiB	14.9 KiB
Sophia Yoo gestures toward a large projection of her slide as she presents her … `div.field > div.view-mode-subhero > div.field > img`	/sites/default/files/styles/third_1x_crop/public/images/2...	24.6 KiB	14.4 KiB
Moasic of Princetonians sporting Standup messages. `div.field > div.view-mode-captionless-full-width > div.field > img`	/sites/default/files/styles/scale_1440/public/images/2026...	179.1 KiB	10.6 KiB

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.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/sites/default/files/js/js_VHwiQXABniyTQ5hjlZvVRtZrYuDQdp...	30.0 KiB	56 ms
www.princeton.edu/modules/contrib/google_tag/js/gtag.js?tcretc	790 B
use.typekit.net/stk8lop.css	1.3 KiB	203 ms
/sites/default/files/css/css_z7jtN4CMh_f2LrvxeTjxmj7MPv_N...	65.2 KiB	111 ms
/p.css?s=1&k=stk8lop&ht=tk&f=12784.12785.12786.12788.1278...	172 B	201 ms
/sites/default/files/css/css_7P8V6wldKNzQtYx4zsHvFLPpgevR...	1.9 KiB

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

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: 60 ms 57.0 KiB

URL	Transfer Size	Est Savings
/sites/default/files/css/css_z7jtN4CMh_f2LrvxeTjxmj7MPv_N...	65.0 KiB	57.0 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 100.7 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-92L6B9PQCG	159.8 KiB	64.8 KiB
/sites/default/files/js/js_n_4nz7oMlCkH0q4hR8K78HjM_rgGDf...	61.0 KiB	35.9 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
div.subfooter > div.subfooter-first > a > img `div.subfooter > div.subfooter-first > a > img`	www.princeton.edu/themes/custom/hobbes/images/logo-white.svg

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

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: 488 ms

URL	Time Spent
princeton.edu/	488 ms
www.princeton.edu/	0.0 ms

●Time to Interactive 1.5 s

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 30 ms

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.4 s

●Avoid long main-thread tasks 1 long task found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 30 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 30 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

100

Accessibility

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

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

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

○Form elements have associated labels

○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

SEO

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 destination	Link Text
www.princeton.edu/one-community/student-life	LEARN MORE

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`

Results for https://princeton.edu

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Usability (1)

Content (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

SEO

Content Best Practices

Keyboard Shortcuts