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.

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
/media/pages/contribute/yamaha/f7e18e7d6a-1767490688/yama...	0.0 ms	17.4 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
obsproject.com/assets/css/blurple.min.css?20260123-1	0.0 ms	14.2 KiB
/media/pages/contribute/steinberg/281cf73c53-1771968421/s...	0.0 ms	11.8 KiB
/media/pages/contribute/logitech/b72383ff29-1767490686/lo...	0.0 ms	9.8 KiB
obsproject.com/media/pages/contribute/intel/13ce287a70-1767490687/logo-white.png	0.0 ms	8.6 KiB
/media/pages/contribute/amd/3c5048c741-1767490687/2010994...	0.0 ms	8.1 KiB
/media/pages/contribute/nvidia/ce87d64958-1767490686/nvid...	0.0 ms	6.5 KiB
/media/pages/contribute/youtube/d9d0b8500d-1767490686/yt_...	0.0 ms	4.1 KiB
images.opencollective.com/guest-41b944fe/avatar.png	86400.0 s	6.0 KiB
images.opencollective.com/overwolf/47c03a5/avatar.png	86400.0 s	5.2 KiB
/media/pages/contribute/twitch/683009550e-1767490685/twit...	0.0 ms	1.9 KiB

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
obsproject.com/assets/css/font/icomoon.woff	175 ms
fonts.gstatic.com/s/opensans/v15/mem5YaGs126MiZpBA-UN8rsOUuhp.woff2	20 ms
fonts.gstatic.com/s/opensans/v15/mem5YaGs126MiZpBA-UN7rgOUuhp.woff2	15 ms
/s/opensans/v15/u-WUoqrET9fUeobQW7jkRRJtnKITppOI_IvcXXDNr...	15 ms
/s/opensans/v15/RjgO7rYTmqiVp7vzi-Q5URJtnKITppOI_IvcXXDNr...	10 ms
/s/opensans/v15/cJZKeOuBrn4kERxqtaUH3VtXRa8TVwTICgirnJhmV...	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
div.kirbycolumns > div.kirbycolumn > figure.featureItem > img `div.kirbycolumns > div.kirbycolumn > figure.featureItem > img`	obsproject.com/assets/images/features-new/studio.png	213.9 KiB	199.7 KiB
div.kirbycolumns > div.kirbycolumn > figure.featureItem > img `div.kirbycolumns > div.kirbycolumn > figure.featureItem > img`	obsproject.com/assets/images/features-new/multiview.png	207.8 KiB	190.8 KiB
div.pagewidth > div.main_blurb > div.demo_obs-window > img `div.pagewidth > div.main_blurb > div.demo_obs-window > img`	obsproject.com/assets/images/features-new/hero_32_1_1.png	219.0 KiB	155.6 KiB
div.kirbycolumns > div.kirbycolumn > figure.featureItem > img `div.kirbycolumns > div.kirbycolumn > figure.featureItem > img`	obsproject.com/assets/images/features-new/layouts.png	167.5 KiB	151.1 KiB
OBS `div#wrapper > header#header > a.logo > img`	obsproject.com/assets/images/new_icon_small-r.png	34.1 KiB	33.5 KiB
div.kirbycolumns > div.kirbycolumn > figure.featureItem > img `div.kirbycolumns > div.kirbycolumn > figure.featureItem > img`	obsproject.com/assets/images/features-new/transitions.png	32.4 KiB	28.8 KiB
div.kirbycolumns > div.kirbycolumn > figure.featureItem > img `div.kirbycolumns > div.kirbycolumn > figure.featureItem > img`	obsproject.com/assets/images/features-new/hotkeys.png	25.7 KiB	24.1 KiB
div.kirbycolumns > div.kirbycolumn > figure.featureItem > img `div.kirbycolumns > div.kirbycolumn > figure.featureItem > img`	obsproject.com/assets/images/features-new/docks.png	20.3 KiB	18.1 KiB
div.kirbycolumns > div.kirbycolumn > figure.featureItem > img `div.kirbycolumns > div.kirbycolumn > figure.featureItem > img`	obsproject.com/assets/images/features-new/settings.png	18.5 KiB	16.5 KiB
div.kirbycolumns > div.kirbycolumn > figure.featureItem > img `div.kirbycolumns > div.kirbycolumn > figure.featureItem > img`	obsproject.com/assets/images/features-new/mixer.png	17.1 KiB	14.7 KiB
div.kirbycolumns > div.kirbycolumn > figure.featureItem > img `div.kirbycolumns > div.kirbycolumn > figure.featureItem > img`	obsproject.com/assets/images/features-new/properties.png	16.0 KiB	14.2 KiB
Yamaha logo `div#diamond_supports > div.support_item > a > img`	/media/pages/contribute/yamaha/f7e18e7d6a-1767490688/yama...	17.3 KiB	13.0 KiB
Steinberg logo `div#diamond_supports > div.support_item > a > img`	/media/pages/contribute/steinberg/281cf73c53-1771968421/s...	11.6 KiB	10.6 KiB
Intel logo `div#diamond_supports > div.support_item > a > img`	obsproject.com/media/pages/contribute/intel/13ce287a70-1767490687/logo-white.png	8.4 KiB	7.8 KiB
AMD logo `div#diamond_supports > div.support_item > a > img`	/media/pages/contribute/amd/3c5048c741-1767490687/2010994...	7.9 KiB	7.4 KiB
Logitech logo `div#premiere_supports > div.support_item > a > img`	/media/pages/contribute/logitech/b72383ff29-1767490686/lo...	9.7 KiB	5.4 KiB
NVIDIA logo `div#diamond_supports > div.support_item > a > img`	/media/pages/contribute/nvidia/ce87d64958-1767490686/nvid...	6.3 KiB	5.1 KiB
div.kirbycolumns > div.kirbycolumn > figure.featureItem > img `div.kirbycolumns > div.kirbycolumn > figure.featureItem > img`	obsproject.com/assets/images/features-new/scenes.png	5.9 KiB	4.4 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-2-IMG

nodeLabel: div.pagewidth > div.main_blurb > div.demo_obs-window > img

path: 1,HTML,1,BODY,0,DIV,1,DIV,4,DIV,0,DIV,5,DIV,0,IMG

selector: div.pagewidth > div.main_blurb > div.demo_obs-window > img

snippet: <img src="/assets/images/features-new/hero_32_1_1.png" style="width: 100%">

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
obsproject.com/assets/css/blurple.min.css?20260123-1	14.2 KiB	115 ms

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: 160 ms 11.6 KiB

URL	Transfer Size	Est Savings
obsproject.com/assets/css/blurple.min.css?20260123-1	14.0 KiB	11.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 200 ms 128.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-3C9PHRV452&cx=c&gtm=4e64h1	151.3 KiB	65.8 KiB
www.googletagmanager.com/gtag/js?id=UA-34644124-1	116.5 KiB	62.7 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.pagewidth > div.main_blurb > div.demo_obs-window > img `div.pagewidth > div.main_blurb > div.demo_obs-window > img`	obsproject.com/assets/images/features-new/hero_32_1_1.png

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

●Time to Interactive 1.7 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.3 s

●Avoid long main-thread tasks 1 long task found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 140 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 80 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

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

ARIA

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Windows `div.pagewidth > div.main_blurb > div#latestVersions > div.latest_icon`
macOS `div.pagewidth > div.main_blurb > div#latestVersions > div.latest_icon`
Linux `div.pagewidth > div.main_blurb > div#latestVersions > div.latest_icon`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contribute `div#SocialButtons > div#ContributeButton > a > i.icon-heart`

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
Resources section `div.fourth_blurb > div.blurb_text > p > a`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#SocialButtons > div#DiscordButton > a > img.icon-discord `div#SocialButtons > div#DiscordButton > a > img.icon-discord`
div#SocialButtons > div#MastodonButton > a > img.icon-mastodon `div#SocialButtons > div#MastodonButton > a > img.icon-mastodon`
div.pagewidth > div.main_blurb > div.demo_obs-window > img `div.pagewidth > div.main_blurb > div.demo_obs-window > img`
div.footer_left > div.footer_row > div.logo > img `div.footer_left > div.footer_row > div.logo > img`
div.footer_left > div.footer_row > a > img.icon-discord `div.footer_left > div.footer_row > a > img.icon-discord`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ideas `div.footer_extra > div.footer_right > div.footer_items > a`

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

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

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

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

○Buttons have an accessible name

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

○No element has a `[tabindex]` value greater than 0

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

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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#SocialButtons > div#DiscordButton > a > img.icon-discord `div#SocialButtons > div#DiscordButton > a > img.icon-discord`
div#SocialButtons > div#MastodonButton > a > img.icon-mastodon `div#SocialButtons > div#MastodonButton > a > img.icon-mastodon`
div.pagewidth > div.main_blurb > div.demo_obs-window > img `div.pagewidth > div.main_blurb > div.demo_obs-window > img`
div.footer_left > div.footer_row > div.logo > img `div.footer_left > div.footer_row > div.logo > img`
div.footer_left > div.footer_row > a > img.icon-discord `div.footer_left > div.footer_row > a > img.icon-discord`

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 have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`