Skip to content
https://cert.org

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

67

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

URLEst Savings
www.sei.cmu.edu/static/fontawesome/webfonts/fa-regular-400.woff23.0 s
www.sei.cmu.edu/static/fontawesome/webfonts/fa-solid-900.woff23.0 s
www.sei.cmu.edu/static/fontawesome/webfonts/fa-light-300.woff23.0 s

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:117.123 source:map[type:text value:[unattributed]]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:799.734 label:Time to first byte subpart:timeToFirstByte] map[duration:2400.681 label:Resource load delay subpart:resourceLoadDelay] map[duration:2294.99 label:Resource load duration subpart:resourceLoadDuration] map[duration:18.724 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-SECTION
nodeLabel: body.sds-theme-plaid > div.page-content-wrapper > main.content-sections > section.hero-space
path: 1,HTML,1,BODY,1,DIV,4,MAIN,0,SECTION
selector: body.sds-theme-plaid > div.page-content-wrapper > main.content-sections > section.hero-space
snippet: <section class="hero-space" style="background-image: url(&quot;/media/images/fullbleed_full_About_Division.max-1920…&quot;);">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-SECTION
nodeLabel: body.sds-theme-plaid > div.page-content-wrapper > main.content-sections > section.hero-space
path: 1,HTML,1,BODY,1,DIV,4,MAIN,0,SECTION
selector: body.sds-theme-plaid > div.page-content-wrapper > main.content-sections > section.hero-space
snippet: <section class="hero-space" style="background-image: url(&quot;/media/images/fullbleed_full_About_Division.max-1920…&quot;);">

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.

URLTransfer SizeDuration
www.sei.cmu.edu/static/assets/main-B5gbO6no.css97.2 KiB88 ms
www.sei.cmu.edu/static/katex/katex.min.js64.4 KiB
www.sei.cmu.edu/static/katex/katex_frontend_renderer.js794 B
www.sei.cmu.edu/static/katex/katex.min.css3.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
analytics.silktide.com/a7d70b917ed89a9539b8a77ac24e9c2d.js0.0 ms16.4 KiB
snap.licdn.com/li.lms-analytics/insight.min.js60713.0 s18.7 KiB
/collect?v=2&fmt=js&pid=13415&time=1776897622105&url=http...0.0 ms694 B

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.

URLResource SizeEst Savings
Headshot of Gregory J Touhill. div.max-container > div.grid > div.flex > img.w-full
www.sei.cmu.edu/media/images/Greg-Touhill.height-661.format-webp.webp105.7 KiB84.5 KiB
body.sds-theme-plaid > div.page-content-wrapper > main.content-sections > section.hero-space body.sds-theme-plaid > div.page-content-wrapper > main.content-sections > section.hero-space
/media/images/fullbleed_full_About_Division.max-1920x1920...125.7 KiB11.8 KiB
Headshot of Chris Inacio. div.max-container > div.grid > div.flex > img.w-full
www.sei.cmu.edu/media/images/inacio-chris-96_2622.height-661.format-webp.webp30.7 KiB9.5 KiB
Headshot of Bill Wilson. div.max-container > div.grid > div.flex > img.w-full
/media/images/Wilson_William_324_200113.360x36.height-661...30.3 KiB9.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.4 s
URLTime Spent
cert.org/505 ms
www.sei.cmu.edu/certsite/709 ms
www.sei.cmu.edu/divisions/cert/147 ms
www.sei.cmu.edu/divisions/cert/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

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 330 ms 354.5 KiB
URLTransfer SizeEst Savings
www.sei.cmu.edu/static/assets/main-8td4Fy72.js419.5 KiB194.9 KiB
www.googletagmanager.com/gtag/js?id=G-87WECW6HCS&cx=c&gtm=4e64k1175.2 KiB69.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-M62LG9163.9 KiB66.5 KiB
www.sei.cmu.edu/static/katex/katex.min.js64.0 KiB23.7 KiB

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

●Max Potential First Input Delay 90 ms
●Layout shift culprits
●Optimize DOM size
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 2,330 KiB
●User Timing marks and measures 7 user timings
●JavaScript execution time 0.3 s
●Minimizes main-thread work 0.7 s
●Avoid long main-thread tasks 1 long task found
●Avoid non-composited animations 3 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 110 ms
●Server Backend Latencies 190 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 150 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
94

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.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Greg Touhill div.grid > div.flex > a > h4.text-2xl
Autonomy Security and Resilience div.max-container > div.grid > div.col-span-1 > h4
Associate Cybersecurity Operations Researcher div.carousel-item > div.bg-white > a > h4.text-xl
VU#518910: Ollama GGUF Quantization Remote Memory Leak div.flex > div > div.pb-6 > h4
APRIL 22, 2026 div.flex > div > div.pb-6 > h6
APRIL 21, 2026 div.flex > div > div.pb-6 > h6
APRIL 21, 2026 div.flex > div > div.pb-6 > h6
Cyber Lightning Case Study div.max-container > div.grid > div.col-span-1 > h4

These are opportunities to improve keyboard navigation in your application.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Carnegie Mellon University div.flex > div.flex > p > a
Richard Pethia div.grid > div.flex > p > a

These are opportunities to improve the legibility of your content.

○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●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
●`[role]` values are valid
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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 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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○ARIA attributes are used as specified for the element's role
○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 use only permitted ARIA attributes
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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.
○Elements with visible text labels have matching accessible names.
○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.
81

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting
snap.licdn.com/li.lms-analytics/insight.min.js

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLMap URL
www.sei.cmu.edu/static/assets/main-8td4Fy72.jswww.sei.cmu.edu/static/assets/main-8td4Fy72.js.map
www.sei.cmu.edu/static/assets/dist-CnRPR7bd.jswww.sei.cmu.edu/static/assets/dist-CnRPR7bd.js.map
●Uses HTTPS
●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
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Ensure proper origin isolation with COOP
○Mitigate clickjacking with XFO or CSP
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.sei.cmu.edu/projects/cyber-lightning-case-study/LEARN MORE
/projects/sei-hosts-crisis-simulation-exercise-for-cyber-...LEARN MORE
www.sei.cmu.edu/projects/usps-case-study/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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback