Lighthouse Desktop

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/webfonts/fa-solid-900.woff2	105 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.665 source:map[column:9596 line:1 type:source-location url:https://fast.wistia.com/assets/external/iframeApi.js@7abfa067db50317bd03abfaf14abe9008e4e0a3a urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:103.558 source:map[type:text value:[unattributed]]] map[reflowTime:0.128 source:map[column:7467 line:0 type:source-location url:https://fast.wistia.com/assets/external/iframeApi.js@7abfa067db50317bd03abfaf14abe9008e4e0a3a urlProvider:network]] map[reflowTime:1.008 source:map[column:6869 line:0 type:source-location url:https://fast.wistia.com/assets/external/iframeApi.js@7abfa067db50317bd03abfaf14abe9008e4e0a3a urlProvider:network]] map[reflowTime:0.372 source:map[column:85503 line:21 type:source-location url:https://js.hs-analytics.net/analytics/1778526600000/43896510.js 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
div.block > div.2xl:relative > div.lg:absolute > img.hero-image `div.block > div.2xl:relative > div.lg:absolute > img.hero-image`	threatmodeler.com/app/uploads/2026/05/TMR-MCP-hero.webp	251.2 KiB	196.2 KiB
div.flex > div.w-full > div.w-full > img.w-full `div.flex > div.w-full > div.w-full > img.w-full`	threatmodeler.com/app/uploads/2025/02/Steps-Home.png	161.6 KiB	125.4 KiB
div.flex > div.w-full > div.relative > img.hidden `div.flex > div.w-full > div.relative > img.hidden`	threatmodeler.com/app/uploads/2025/02/TextLeft-Image-bg-768x766.png	121.1 KiB	95.1 KiB
div.text-black > div.grid > div.col-span-7 > img.2xl:object-contain `div.text-black > div.grid > div.col-span-7 > img.2xl:object-contain`	threatmodeler.com/app/uploads/2025/02/conveyor-belt-1024x537.png	94.1 KiB	47.0 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.

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

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
/app/themes/threatmodeler/public/dist/js/app.4c3140.js?ve...	54.4 KiB	163 ms
/app/themes/threatmodeler/public/dist/js/components/video...	35.2 KiB	109 ms
/app/themes/threatmodeler/public/dist/js/runtime.132cd2.j...	1.1 KiB
/app/plugins/pressidium-cookie-consent/public/consent-mod...	837 B
/app/plugins/pressidium-cookie-consent/public/bundle.clie...	5.1 KiB
threatmodeler.com/wp/wp-includes/css/dist/block-library/style.min.css?ver=6.7.1	16.5 KiB	54 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/css/all.min.css?ver=6.7.1	19.0 KiB	338 ms
/app/themes/threatmodeler/public/dist/css/app.2fa94e.css?...	22.0 KiB	54 ms

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
js.hs-analytics.net/analytics/1778526600000/43896510.js	300.0 s	42.4 KiB
js.usemessages.com/conversations-embed.js	600.0 s	33.6 KiB
js.hubspot.com/web-interactives-embed.js	600.0 s	28.2 KiB
js.hscollectedforms.net/collectedforms.js	300.0 s	26.5 KiB
js.hs-banner.com/v2/43896510/banner.js	300.0 s	25.4 KiB
scripts.clarity.ms/0.8.64/clarity.js	86400.0 s	25.1 KiB
js.navattic.com/sdk.js?key=pkey_cm3rrxooy000h03mpb8na3x6t	1800.0 s	10.1 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	86400.0 s	18.9 KiB
static.hotjar.com/c/hotjar-5116314.js?sv=7	60.0 s	6.2 KiB
js.navattic.com/embeds.js	1800.0 s	6.2 KiB
js.hsadspixel.net/pixels.js	600.0 s	4.5 KiB
js.hs-scripts.com/43896510.js?integration=WordPress&ver=11.3.45	90.0 s	1.4 KiB
js.hs-scripts.com/43896510.js	90.0 s	1.1 KiB
static.hsappstatic.net/whisper-core/ex/whisper-core.js	60.0 s	1014 B
/collect?v=2&fmt=js&pid=8187369&time=1778526769773&url=ht...	0.0 ms	714 B
t.visitorqueue.com/p/tracking.min.js?id=8c61d174-761b-4c58-bc13-5c910ad1a93d	0.0 ms	567 B
/hs-fs/hubfs/ThreatModeler_mark_col CMYK 2.jpg?width=108&...	1209600.0 s	2.2 KiB

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

URL	Transfer Size	Est Savings
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/css/all.min.css?ver=6.7.1	18.3 KiB	18.2 KiB
/app/themes/threatmodeler/public/dist/css/app.2fa94e.css?...	21.7 KiB	17.0 KiB
threatmodeler.com/wp/wp-includes/css/dist/block-library/style.min.css?ver=6.7.1	16.2 KiB	16.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 80 ms 899.5 KiB

URL	Transfer Size	Est Savings
cdn.ldnfrpl.com/rpl/be4cdf1b5aecf00c898b96d09e67ff493a98929e/rpl.js	174.3 KiB	121.4 KiB
fast.wistia.com/assets/external/E-v1.js	161.7 KiB	120.2 KiB
www.googletagmanager.com/gtag/js?id=GT-MR4FWWL&cx=c&gtm=4e6570	177.2 KiB	115.0 KiB
www.googletagmanager.com/gtag/js?id=G-XYCE6Q02GG&cx=c&gtm=4e6570	177.2 KiB	115.0 KiB
www.googletagmanager.com/gtag/js?id=AW-10876448945	146.6 KiB	107.1 KiB
www.googletagmanager.com/gtag/js?id=GT-MR4FWWL	177.1 KiB	71.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-PQXJSXHN	156.6 KiB	66.7 KiB
www.googletagmanager.com/gtag/js?id=AW-10876448945&cx=c&gtm=4e6570	146.6 KiB	66.0 KiB
/app/themes/threatmodeler/public/dist/js/app.4c3140.js?ve...	54.1 KiB	47.0 KiB
script.hotjar.com/modules.6a0f3932cb1341a35c18.js	56.1 KiB	37.8 KiB
/app/themes/threatmodeler/public/dist/js/components/video...	34.9 KiB	31.8 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/deliveries/a84bc3c1b38cf4940e3d69d01caf01c7e9f43c4b.m3u8...	415.7 KiB
/conversations-visitor-ui/static-1.29009/bundles/visitor.js	352.2 KiB
threatmodeler.com/app/uploads/2026/05/TMR-MCP-hero.webp	251.8 KiB
www.googletagmanager.com/gtag/js?id=GT-MR4FWWL	177.5 KiB
www.googletagmanager.com/gtag/js?id=GT-MR4FWWL&cx=c&gtm=4e6570	177.2 KiB
www.googletagmanager.com/gtag/js?id=G-XYCE6Q02GG&cx=c&gtm=4e6570	177.2 KiB
cdn.ldnfrpl.com/rpl/be4cdf1b5aecf00c898b96d09e67ff493a98929e/rpl.js	174.9 KiB
threatmodeler.com/app/uploads/2025/02/Steps-Home.png	162.1 KiB
fast.wistia.com/assets/external/E-v1.js	162.1 KiB
fast.wistia.net/assets/external/E-v1.js	161.8 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

●Document request latency

●Optimize DOM size

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 7 user timings

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.3 s

●Avoid long main-thread tasks 2 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 180 ms

●Server Backend Latencies 220 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

●Avoid large layout shifts 4 layout shifts found

○INP breakdown

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
REQUEST A DEMO `div.lg:pe-9 > div.flex > div.mb-2 > a.button-40q`
EXPLORE THE PLATFORM `div.flex > div.flex > div.mb-2 > a.button-40q`
TAKE A TOUR `div.text-black > div.flex > div.static > a.button-40q`
READ CASE STUDY `div.flex > div.flex > div.flex > a.button-40q`
REQUEST A DEMO `div.flex > div.flex > div.mb-2 > a.button-40q`

○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

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

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

●`<frame>` or `<iframe>` elements have a title

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

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

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

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 / Warning	Source
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
fast.wistia.com/assets/external/E-v1.js	`[object Response]`
p.visitorqueue.com/styles/8c61d174-761b-4c58-bc13-5c910ad1a93d.css	`Failed to load resource: net::ERR_NAME_NOT_RESOLVED`
/p/personalisation.min.js?id=8c61d174-761b-4c58-bc13-5c91...	`Failed to load resource: net::ERR_NAME_NOT_RESOLVED`
aplo-evnt.com/api/v1/intent_pixel/track_request?app_id=66339d59f94aba043b05749d	`Failed to load resource: the server responded with a status of 400 ()`
pipedream.wistia.com/mput?topic=metrics	`Failed to load resource: the server responded with a status of 500 ()`
js.navattic.com/embeds.js line 134, col 2175	`Uncaught NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': the name "navattic-lightbox" has already been used with this registry`

●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 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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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
threatmodeler.com/why-threatmodeler/for-security-centers/	LEARN MORE
threatmodeler.com/why-threatmodeler/for-product-development/	LEARN MORE
threatmodeler.com/why-threatmodeler/for-cloud-teams/	LEARN MORE
threatmodeler.com/learn/the-ultimate-guide-to-threat-modeling/	READ MORE
threatmodeler.com/resource/white-papers/operationalizing-ai-in-threat-modeling/	READ 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`