Mobile 375 × 812

Desktop 1440 × 900

Score: 73 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
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.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Missing metadata means poor previews on social media and search.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 12.8 MB (11.9 MB transferred)
Performance issues directly impact user engagement and conversion rates.
74 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/255b3fa7-a08e-4010-9abd-be6002d71a27)<a href="https://beavercheck.com/results/255b3fa7-a08e-4010-9abd-be6002d71a27"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fcornell.edu" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fcornell.eduThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 12.6s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your user trust.
6 barrier(s) likely increasing bounce by ~24%.
Page takes 12.6s to load
+12% bounceUsers abandon at ~3s — you're 10.1s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
No HSTS header
+1% bounceReturning 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% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo 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, …)
1 broken link(s) on the page
+2% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$550 investment → $2,524/month returns + USD 7,500 risk avoided
$550
6h · 5 findings
$2,524 /mo
~$30,283 / year
USD 7,500
if kept compliant
$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.
5.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$628 / month at risk
~$7,536 / year if left unfixed
$7,500
+1 more
$3.00 /mo
37515.8 MB/mo × 0.080 USD/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 4 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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.
3.65 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
12.65 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
150 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.051
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.33 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.75 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Ezra Cornell statue imposed over a red background in front of a large floating … body.home > div#campaign > img#campaignCoverImg | www.cornell.edu/assets/images/campaign/ezra.jpg | 219.6 KiB | 173.7 KiB |
Three Cornellians sit on the Cornell Libe Slope on a warm March day. a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/360x360/AA35CCCB-A98C-F255-3FB3D87C97A41615.jpg | 188.2 KiB | 171.5 KiB |
The reflection of cherry blossoms seen in a window of Cornell's Sage Hall. a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/360x360/AA714B42-BFFF-B6A8-02E0E198925385AC.jpg | 110.4 KiB | 106.4 KiB |
A video of collage of various Cornell reasearhers and their work. div > div#cover-area > div#cover-video > video#cover-vid | cdn.universityrelations.cornell.edu/images/research-2025.jpg | 121.1 KiB | 101.4 KiB |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/1A07FF21-BAD7-6A1C-BB7C63EB8210FBE7.jpg | 120.1 KiB | 99.0 KiB |
Cornellian operating a dril press. a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/360x360/F4FD8094-E12B-0957-5E262F301DDD8B91.jpg | 96.9 KiB | 92.9 KiB |
Cornell's McGraw Tower, framed by cherry leaves, against a brilliant blue sky. a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/400x225/AA664986-C9E4-E7DB-D5AC14ED3C2BCD8D.jpg | 79.2 KiB | 69.8 KiB |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/A746AA91-F77D-AB4C-9F141556580C6E4C.jpg | 86.7 KiB | 65.6 KiB |
Students perform a wet aggregate stability experiment. div.slide-mask > div.slideshow > a.grid-box > img.image-replace | /photos/400x225/4F45AC93-09A5-5E26-B59B80F5D7E369F3.jpg | 77.5 KiB | 62.9 KiB |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/AB69298D-A62D-B445-9A92E772C3BAD9DD.jpg | 82.3 KiB | 61.2 KiB |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/76583D5F-E4A2-0A6C-F49C1FC9E7067410.jpg | 73.7 KiB | 52.6 KiB |
Gavin Sacks. div.slide-mask > div.slideshow > a.grid-box > img.image-replace | /photos/400x225/850FCA14-9FD4-867A-6CD5A1621A680F3E.jpg | 65.6 KiB | 50.9 KiB |
To do he greatest good: The Campaign for Cornell University li.ftr-item > div.ftr-item-campaign > a > img | media.univcomm.cornell.edu/photos/campaign/TDTGG.png | 12.8 KiB | 7.2 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| www.cornell.edu/assets/css/style.css?ver=20250512 | 12.4 KiB | 311 ms |
| www.cornell.edu/assets/css/print.css?ver=20250512 | 700 B | |
| www.cornell.edu/assets/core/css/cornell.css?ver=20250512 | 45.4 KiB | 621 ms |
| www.cornell.edu/assets/core/js/lib/modernizr.js?ver=20250512 | 6.4 KiB | |
| use.typekit.net/gog6dck.js | 7.0 KiB | |
| www.cornell.edu/assets/css/social-grid.css | 1.2 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| cornell.edu/ | 1.1 s |
| www.cornell.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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.cornell.edu/assets/core/css/cornell.css?ver=20250512 | 45.1 KiB | 40.3 KiB |
| www.cornell.edu/assets/css/style.css?ver=20250512 | 12.1 KiB | 10.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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-PMZ19X3F8W&cx=c>m=4e64f0 | 156.4 KiB | 110.4 KiB |
| www.googletagmanager.com/gtag/js?id=G-PMZ19X3F8W | 156.4 KiB | 67.2 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-WW83RG9 | 127.1 KiB | 64.2 KiB |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Other | 917 ms |
| Script Evaluation | 752 ms |
| Style & Layout | 478 ms |
| Rendering | 196 ms |
| Script Parsing & Compilation | 157 ms |
| Parse HTML & CSS | 61 ms |
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.cornell.edu/assets/core/css/cornell.css?ver=20250512 | 45.4 KiB | 9.0 KiB |
| www.cornell.edu/assets/css/style.css?ver=20250512 | 12.4 KiB | 3.8 KiB |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.cornell.edu/assets/core/js/lib/plugins.js | 9.9 KiB | 4.9 KiB |
| www.cornell.edu/assets/core/js/cornell.js?ver=20191023a | 9.5 KiB | 3.3 KiB |
| www.cornell.edu/assets/js/cornelledu.js?ver=20230613a | 7.1 KiB | 2.6 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
Ezra Cornell statue imposed over a red background in front of a large floating … body.home > div#campaign > img#campaignCoverImg | www.cornell.edu/assets/images/campaign/ezra.jpg |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/AB69298D-A62D-B445-9A92E772C3BAD9DD.jpg |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/A746AA91-F77D-AB4C-9F141556580C6E4C.jpg |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/76583D5F-E4A2-0A6C-F49C1FC9E7067410.jpg |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/1A07FF21-BAD7-6A1C-BB7C63EB8210FBE7.jpg |
Tweezers holding a tiny device. div.marquee-mask > div.marquee > span#panobg-1A023AAE-0694-71F8-FF05A7CAD582F72F > img.marquee-img | /photos/400x225/1A0BB4DE-BAC0-5DE3-C487894F3B5F68CE.jpg |
Gavin Sacks. div.slide-mask > div.slideshow > a.grid-box > img.image-replace | /photos/400x225/850FCA14-9FD4-867A-6CD5A1621A680F3E.jpg |
Students perform a wet aggregate stability experiment. div.slide-mask > div.slideshow > a.grid-box > img.image-replace | /photos/400x225/4F45AC93-09A5-5E26-B59B80F5D7E369F3.jpg |
To do he greatest good: The Campaign for Cornell University li.ftr-item > div.ftr-item-campaign > a > img | media.univcomm.cornell.edu/photos/campaign/TDTGG.png |
body.home > div#main > div.marquee-mask > img.image-replace body.home > div#main > div.marquee-mask > img.image-replace |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Research saves lives. Research feeds the world. Research helps animals. Researc… div.vcenter2 > div.container > div.typing-container > span#typedText |
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.
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Skip to content body.home > nav#skip-link > a |
These are opportunities to improve keyboard navigation in your application.
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Performance issues directly impact user engagement and conversion rates.
| Insecure URL | Request Resolution |
|---|---|
| www.cornell.edu/assets/core/social-icons/linkedin-in-logo.svg | Automatically upgraded to HTTPS |
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
body.home > div#main > div.marquee-mask > img.image-replace body.home > div#main > div.marquee-mask > img.image-replace | 412 x 232 | 16 x 9 | 618 x 348 | |
Tweezers holding a tiny device. div.marquee-mask > div.marquee > span#panobg-1A023AAE-0694-71F8-FF05A7CAD582F72F > img.marquee-img | /photos/400x225/1A0BB4DE-BAC0-5DE3-C487894F3B5F68CE.jpg | 412 x 232 | 400 x 225 | 618 x 348 |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Mixed content |
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.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
1 div.container > div.marquee-controls > nav.pager > a.active |
2 div.container > div.marquee-controls > nav.pager > a |
To appear in search results, crawlers need access to your app.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.24 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.80 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.006
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.76 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.82 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Spring cold snaps harm nesting tree swallows, but some show resilience div#main > div.marquee-mask > div.marquee > span#panobg-1A21C5EA-D9C3-DB12-5E04B41C36D9F705 | /photos/1280x720/1A2D5B63-0E6C-6D05-4B6F5FE1B2B7CEDA.jpg | 580.9 KiB | 430.9 KiB |
Cornellian walking through the arch at the Cornell War Memorial on a sunny day. a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/400x225/97ED1A7B-A4EA-2A1D-0682FB1FC93E4312.jpg | 212.8 KiB | 198.5 KiB |
Three Cornellians sit on the Cornell Libe Slope on a warm March day. a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/360x360/AA35CCCB-A98C-F255-3FB3D87C97A41615.jpg | 188.2 KiB | 179.9 KiB |
A Cornell University student sits in a tree on the Cornell University Arts Quad. a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/360x360/AA427B20-D637-6D0E-190A5C495943239C.jpg | 179.5 KiB | 177.5 KiB |
Four Cornell University students walk along a path on the Cornell University Ar… a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/360x360/AA505462-AF6E-14EB-391E7B23F0B05978.jpg | 170.6 KiB | 168.6 KiB |
The reflection of cherry blossoms seen in a window of Cornell's Sage Hall. a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/360x360/AA714B42-BFFF-B6A8-02E0E198925385AC.jpg | 110.4 KiB | 108.4 KiB |
A Cornell University student works on a sewing machine. a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/360x360/AA85866B-C44E-42F6-24C93F3A6A54E260.jpg | 113.6 KiB | 105.3 KiB |
Ezra Cornell statue imposed over a red background in front of a large floating … body.home > div#campaign > img#campaignCoverImg | www.cornell.edu/assets/images/campaign/ezra.jpg | 219.6 KiB | 102.3 KiB |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/1A07FF21-BAD7-6A1C-BB7C63EB8210FBE7.jpg | 120.1 KiB | 101.6 KiB |
Cornellian operating a dril press. a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/360x360/F4FD8094-E12B-0957-5E262F301DDD8B91.jpg | 96.9 KiB | 94.9 KiB |
Cornell's McGraw Tower, framed by cherry leaves, against a brilliant blue sky. a.socialmedia-grid-link > div.socialmedia-grid > div.socialmedia-item > img | /photos/400x225/AA664986-C9E4-E7DB-D5AC14ED3C2BCD8D.jpg | 79.2 KiB | 74.5 KiB |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/A746AA91-F77D-AB4C-9F141556580C6E4C.jpg | 86.7 KiB | 68.1 KiB |
Students perform a wet aggregate stability experiment. div.slide-mask > div.slideshow > a.grid-box > img.image-replace | /photos/400x225/4F45AC93-09A5-5E26-B59B80F5D7E369F3.jpg | 77.5 KiB | 64.5 KiB |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/AB69298D-A62D-B445-9A92E772C3BAD9DD.jpg | 82.3 KiB | 63.8 KiB |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/76583D5F-E4A2-0A6C-F49C1FC9E7067410.jpg | 73.7 KiB | 55.2 KiB |
Gavin Sacks. div.slide-mask > div.slideshow > a.grid-box > img.image-replace | /photos/400x225/850FCA14-9FD4-867A-6CD5A1621A680F3E.jpg | 65.6 KiB | 52.6 KiB |
A video of collage of various Cornell reasearhers and their work. div > div#cover-area > div#cover-video > video#cover-vid | cdn.universityrelations.cornell.edu/images/research-2025.jpg | 121.1 KiB | 51.1 KiB |
body.home > header#cu-hdr > div.cu-hdr-inner > a#cu-brand body.home > header#cu-hdr > div.cu-hdr-inner > a#cu-brand | www.cornell.edu/assets/core/images/logo-red@2x.png | 24.5 KiB | 13.9 KiB |
To do he greatest good: The Campaign for Cornell University li.ftr-item > div.ftr-item-campaign > a > img | media.univcomm.cornell.edu/photos/campaign/TDTGG.png | 12.8 KiB | 7.2 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| www.cornell.edu/assets/core/css/cornell.css?ver=20250512 | 45.4 KiB | 113 ms |
| www.cornell.edu/assets/css/style.css?ver=20250512 | 12.4 KiB | 56 ms |
| www.cornell.edu/assets/core/js/lib/modernizr.js?ver=20250512 | 6.4 KiB | |
| use.typekit.net/gog6dck.js | 7.0 KiB | |
| www.cornell.edu/assets/css/print.css?ver=20250512 | 694 B | |
| www.cornell.edu/assets/css/social-grid.css | 1.2 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| cornell.edu/ | 521 ms |
| www.cornell.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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.cornell.edu/assets/core/css/cornell.css?ver=20250512 | 45.1 KiB | 36.0 KiB |
| www.cornell.edu/assets/css/style.css?ver=20250512 | 12.1 KiB | 10.7 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtag/js?id=G-PMZ19X3F8W&cx=c>m=4e64f0 | 156.4 KiB | 110.4 KiB |
| www.googletagmanager.com/gtag/js?id=G-PMZ19X3F8W | 156.4 KiB | 67.2 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-WW83RG9 | 127.1 KiB | 64.2 KiB |
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.cornell.edu/assets/core/css/cornell.css?ver=20250512 | 45.4 KiB | 9.0 KiB |
| www.cornell.edu/assets/css/style.css?ver=20250512 | 12.4 KiB | 3.8 KiB |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.cornell.edu/assets/core/js/lib/plugins.js | 9.9 KiB | 4.9 KiB |
| www.cornell.edu/assets/core/js/cornell.js?ver=20191023a | 9.5 KiB | 3.3 KiB |
| www.cornell.edu/assets/js/cornelledu.js?ver=20230613a | 7.1 KiB | 2.6 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
Ezra Cornell statue imposed over a red background in front of a large floating … body.home > div#campaign > img#campaignCoverImg | www.cornell.edu/assets/images/campaign/ezra.jpg |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/AB69298D-A62D-B445-9A92E772C3BAD9DD.jpg |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/A746AA91-F77D-AB4C-9F141556580C6E4C.jpg |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/76583D5F-E4A2-0A6C-F49C1FC9E7067410.jpg |
div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace div.home-honeycomb > div#honeycomb > a.hc-item > img.image-replace | /photos/360x360/1A07FF21-BAD7-6A1C-BB7C63EB8210FBE7.jpg |
Gavin Sacks. div.slide-mask > div.slideshow > a.grid-box > img.image-replace | /photos/400x225/850FCA14-9FD4-867A-6CD5A1621A680F3E.jpg |
Students perform a wet aggregate stability experiment. div.slide-mask > div.slideshow > a.grid-box > img.image-replace | /photos/400x225/4F45AC93-09A5-5E26-B59B80F5D7E369F3.jpg |
To do he greatest good: The Campaign for Cornell University li.ftr-item > div.ftr-item-campaign > a > img | media.univcomm.cornell.edu/photos/campaign/TDTGG.png |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Skip to content body.home > nav#skip-link > a |
APPLY li.cu-nav-actions > ul > li > a#applyButton |
VISIT li.cu-nav-actions > ul > li > a |
GIVE li.cu-nav-actions > ul > li > a |
STUDENTS li.cu-nav-people > ul > li > a |
FAMILIES li.cu-nav-people > ul > li > a |
FACULTY & STAFF li.cu-nav-people > ul > li > a |
ALUMNI li.cu-nav-people > ul > li > a |
div#cu-nav-utility > form.search-main > div.container > input#search-query div#cu-nav-utility > form.search-main > div.container > input#search-query |
Search div#cu-nav-utility > form.search-main > div.container > button.icon-search |
These are opportunities to improve keyboard navigation in your application.
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Performance issues directly impact user engagement and conversion rates.
| Insecure URL | Request Resolution |
|---|---|
| www.cornell.edu/assets/core/social-icons/linkedin-in-logo.svg | Automatically upgraded to HTTPS |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Mixed content |
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.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
1 div.container > div.marquee-controls > nav.pager > a.active |
2 div.container > div.marquee-controls > nav.pager > a |
To appear in search results, crawlers need access to your app.
Send Feedback