C — https://discourse.org | BeaverCheck Audit

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Strong compliance posture across regulations.

Rich content metadata — your pages look great everywhere.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Amazon Route 53 · 975 peers

You 78

Avg 72

+6 above average

0 50 100

Better than 92% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Google Search Console · 3592 peers

You 78

Avg 73

At average

0 50 100

Better than 88% of Google Search Console sites See full Google Search Console benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

Page weighs 5.4 MB (4.5 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

5 image(s) missing alt attribute

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

Accessibility › Alt Text Quality

7 link(s) with no accessible text

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

Accessibility › Link & Button Quality

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fdiscourse.org)](https://beavercheck.com/results/f43e8e1b-8dd5-4bd9-ac7c-132e3a4e64af)

HTML

<a href="https://beavercheck.com/results/f43e8e1b-8dd5-4bd9-ac7c-132e3a4e64af"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdiscourse.org" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fdiscourse.org

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 17.4s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

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

Your LCP is 17.4s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

2 accessibility issues exclude users who rely on assistive technology.

Could reach Estimate based on resolving critical issues

Conversion Barriers

1 critical 4 warning

5 barrier(s) likely increasing bounce by ~22%.

Speed (2)

Page takes 17.4s to load

+12% bounce

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

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

High main-thread blocking time

+2% bounce

Page is non-interactive for 212ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (1)

No Content-Security-Policy header

+1% bounce

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

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

Navigation (2)

7 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

1 broken link(s) on the page

+2% bounce

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

Return on Investment

€510 investment → €1.05/month returns + EUR 120,500,000 risk avoided

Payback period: > 2 years First-year ROI: -98%

Investment

€510

6h · 5 findings

Monthly returns

€1.05 /mo

~€13 / year

Bandwidth savings €1.05

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
GDPR EUR 20,000,000
EAA EUR 500,000

€85 — in quick wins — start here for the fastest payback

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

Full methodology & sources

Estimated Remediation Cost

€510

6.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins

€85 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,668 / month at risk

~€120,500,013 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA

No privacy policy link detected
GDPR: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
GDPR: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
GDPR: EUR 10,000 – EUR 20,000,000

+5 more

Bandwidth Waste

€1.05 /mo

14114.2 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~1.4 MB per page load
Saves €1.05/mo

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

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

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

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.46 s

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

17.38 s

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

212 ms

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

0.000

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

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

18.25 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

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

Learn more ▾

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

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

A 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:15.48 source:map[column:56 line:1 type:source-location url:https://discourse.org/a/js/homepage-hero-animation.js?1776465492432244338 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:58.986 source:map[column:13 line:122 type:source-location url:https://discourse.org/a/js/mainnav.js?v=20260417223814 urlProvider:network]] map[reflowTime:0.225 source:map[column:27 line:13 type:source-location url:https://discourse.org/a/js/index.js?1776465492432244338 urlProvider:network]] map[reflowTime:22.758 source:map[column:7 line:3586 type:source-location url:https://discourse.org/a/js/gsap.min.js?v=20260417223814 urlProvider:network]] map[reflowTime:1.735 source:map[column:15 line:3859 type:source-location url:https://discourse.org/a/js/gsap.min.js?v=20260417223814 urlProvider:network]] map[reflowTime:3.743 source:map[column:12 line:3853 type:source-location url:https://discourse.org/a/js/gsap.min.js?v=20260417223814 urlProvider:network]] map[reflowTime:2.172 source:map[column:13 line:687 type:source-location url:https://discourse.org/a/js/scroll-trigger.min.js?v=20260417223814 urlProvider:network]] map[reflowTime:1.317 source:map[column:28 line:4231 type:source-location url:https://discourse.org/a/js/gsap.min.js?v=20260417223814 urlProvider:network]] map[reflowTime:0.195 source:map[column:20 line:890 type:source-location url:https://discourse.org/a/js/scroll-trigger.min.js?v=20260417223814 urlProvider:network]] map[reflowTime:0.1 source:map[column:15 line:246 type:source-location url:https://discourse.org/a/js/scroll-trigger.min.js?v=20260417223814 urlProvider:network]]]

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

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
Support community preview `div.switcher__grid > div.switcher__preview > div.switcher__media > img`	discourse.org/a/img/use-case-support.png	119.5 KiB	116.7 KiB
Jonathan Bulava `div.community-section__inner > div.support-quote > div.support-quote__author > img.support-quote__avatar`	discourse.org/a/img/avatar-jonathan.png	91.4 KiB	91.0 KiB
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-grow.png	39.8 KiB	38.8 KiB
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-manage.png	34.1 KiB	33.2 KiB
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-connect.png	31.4 KiB	30.6 KiB
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-build.png	17.7 KiB	17.2 KiB
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-themes-plugins.png	16.6 KiB	16.2 KiB

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
discourse.org/css/newsletter.css?1776465492432244338	8.9 KiB	150 ms
discourse.org/css/home.css?1776465492432244338	12.7 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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 300 ms 55.0 KiB

URL	Transfer Size	Est Savings
discourse.org/a/js/lucide.min.js?v=20260417223814	93.1 KiB	27.6 KiB
discourse.org/a/js/gsap.min.js?v=20260417223814	36.1 KiB	16.5 KiB
discourse.org/a/js/scroll-trigger.min.js?v=20260417223814	22.0 KiB	10.9 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Other	972 ms
Style & Layout	656 ms
Script Evaluation	612 ms
Rendering	82 ms
Script Parsing & Compilation	80 ms
Parse HTML & CSS	42 ms

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
discourse.org/a/img/discover/trusted-housesitters.png	399.2 KiB
discourse.org/a/fonts/Inter-Italic-Variable.woff2	379.8 KiB
discourse.org/a/fonts/Inter-Variable.woff2	344.8 KiB
discourse.org/a/img/discover/niantic-wayfarer.png	310.5 KiB
discourse.org/a/img/use-case-developer.png	156.2 KiB
discourse.org/a/img/discover/make.png	154.0 KiB
discourse.org/a/img/discover/epic.png	131.8 KiB
discourse.org/a/img/use-case-product-feedback.png	130.0 KiB
discourse.org/a/img/discover/sailpoint.png	121.8 KiB
discourse.org/a/img/discover/uipath.png	120.3 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
Support community preview `div.switcher__grid > div.switcher__preview > div.switcher__media > img`	discourse.org/a/img/use-case-support.png
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-build.png
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-connect.png
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-manage.png
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-grow.png
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-themes-plugins.png
Katalon logo `div.testimonials-grid > figure.testimonial-card > div.testimonial-card__logo > img`	discourse.org/a/img/customers/logo/katalon-2x.png
Get Discourse Hub on Google Play `div.site-footer__col > div.app-badges > a > img`	discourse.org/a/img/badge-google-play.png
Carwow logo `div.testimonials-grid > figure.testimonial-card > div.testimonial-card__logo > img`	discourse.org/a/img/customers/logo/carwow.svg
Discourse logo `div.site-footer__top > div.site-footer__col > a.site-footer__logo > img`	discourse.org/a/img/logo.svg
Download Discourse Hub on the App Store `div.site-footer__col > div.app-badges > a > img`	discourse.org/a/img/badge-app-store.svg
Atlassian logo `div.hero-section__inner > div.logos-wrapper > div.logo-item > img`	discourse.org/a/img/customers/logo/atlassian-light.svg
Asana logo `div.hero-section__inner > div.logos-wrapper > div.logo-item > img`	discourse.org/a/img/customers/logo/asana-light.svg
GitLab logo `div.hero-section__inner > div.logos-wrapper > div.logo-item > img`	discourse.org/a/img/customers/logo/gitlab-light.svg
OpenAI logo `div.hero-section__inner > div.logos-wrapper > div.logo-item > img`	discourse.org/a/img/customers/logo/openai-light.svg
Zoom logo `div.hero-section__inner > div.logos-wrapper > div.logo-item > img`	discourse.org/a/img/customers/logo/zoom-light.svg

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

●Reduce unused JavaScript

●JavaScript execution time 0.6 s

●Avoid long main-thread tasks 4 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 430 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 0 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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
Features & Pricing `div.site-footer__wrapper > div.site-footer__top > div.site-footer__col > h6`

These are opportunities to improve keyboard navigation in your application.

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.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.site-header-container > header.site-header > div.site-header-logo-container > a.logo `div.site-header-container > header.site-header > div.site-header-logo-container > a.logo`
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link `div.site-footer__col > ul.site-footer__list > li > a.site-footer__link`
div.site-footer__col > ul.site-footer__list > li > a `div.site-footer__col > ul.site-footer__list > li > a`
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link `div.site-footer__col > ul.site-footer__list > li > a.site-footer__link`
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link `div.site-footer__col > ul.site-footer__list > li > a.site-footer__link`
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link `div.site-footer__col > ul.site-footer__list > li > a.site-footer__link`
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link `div.site-footer__col > ul.site-footer__list > li > a.site-footer__link`

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.

○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

●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

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

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

●Buttons have an accessible name

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○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

General

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.

URL	Map URL
discourse.org/a/js/lucide.min.js?v=20260417223814	discourse.org/a/js/lucide.min.js.map

●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

○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.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`

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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

334 ms

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

1.21 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.000

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

1.28 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.23 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

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

Learn more ▾

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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:48.436 source:map[column:13 line:122 type:source-location url:https://discourse.org/a/js/mainnav.js?v=20260417223814 urlProvider:network]] map[reflowTime:5.573 source:map[type:text value:[unattributed]]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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
Support community preview `div.switcher__grid > div.switcher__preview > div.switcher__media > img`	discourse.org/a/img/use-case-support.png	119.5 KiB	105.5 KiB
Epic Games Enterprise `div.enterprise-section__right > div.enterprise-section__image-wrapper > div.enterprise-section__screenshots > img.enterprise-section__screenshot`	discourse.org/a/img/enterprise-epic-thumb.png	58.2 KiB	42.9 KiB
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-grow.png	39.8 KiB	37.4 KiB
Cloudflare Enterprise `div.enterprise-section__right > div.enterprise-section__image-wrapper > div.enterprise-section__screenshots > img.enterprise-section__screenshot`	discourse.org/a/img/enterprise-cloudflare-thumb.png	50.2 KiB	37.0 KiB
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-manage.png	34.1 KiB	32.0 KiB
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-connect.png	31.4 KiB	29.5 KiB
Monzo Enterprise `div.enterprise-section__right > div.enterprise-section__image-wrapper > div.enterprise-section__screenshots > img.enterprise-section__screenshot`	discourse.org/a/img/enterprise-monzo-thumb.png	32.2 KiB	23.7 KiB
Asana Enterprise `div.enterprise-section__right > div.enterprise-section__image-wrapper > div.enterprise-section__screenshots > img.enterprise-section__screenshot`	discourse.org/a/img/enterprise-asana-thumb.png	28.1 KiB	20.7 KiB
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-build.png	17.7 KiB	16.6 KiB
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-themes-plugins.png	16.6 KiB	15.5 KiB

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
discourse.org/css/home.css?1776465492432244338	12.7 KiB
discourse.org/css/newsletter.css?1776465492432244338	8.9 KiB

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

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 55.0 KiB

URL	Transfer Size	Est Savings
discourse.org/a/js/lucide.min.js?v=20260417223814	93.1 KiB	27.6 KiB
discourse.org/a/js/gsap.min.js?v=20260417223814	36.1 KiB	16.5 KiB
discourse.org/a/js/scroll-trigger.min.js?v=20260417223814	22.0 KiB	10.9 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
discourse.org/a/img/discover/trusted-housesitters.png	399.2 KiB
discourse.org/a/fonts/Inter-Italic-Variable.woff2	379.8 KiB
discourse.org/a/fonts/Inter-Variable.woff2	344.8 KiB
discourse.org/a/img/discover/niantic-wayfarer.png	310.5 KiB
discourse.org/a/img/use-case-developer.png	156.2 KiB
discourse.org/a/img/discover/make.png	154.0 KiB
discourse.org/a/img/discover/epic.png	131.8 KiB
discourse.org/a/img/use-case-product-feedback.png	130.0 KiB
discourse.org/a/img/discover/sailpoint.png	121.8 KiB
discourse.org/a/img/discover/uipath.png	120.3 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
Support community preview `div.switcher__grid > div.switcher__preview > div.switcher__media > img`	discourse.org/a/img/use-case-support.png
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-build.png
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-connect.png
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-manage.png
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-grow.png
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`	discourse.org/a/img/block-themes-plugins.png
Katalon logo `div.testimonials-grid > figure.testimonial-card > div.testimonial-card__logo > img`	discourse.org/a/img/customers/logo/katalon-2x.png
Get Discourse Hub on Google Play `div.site-footer__col > div.app-badges > a > img`	discourse.org/a/img/badge-google-play.png
Carwow logo `div.testimonials-grid > figure.testimonial-card > div.testimonial-card__logo > img`	discourse.org/a/img/customers/logo/carwow.svg
Discourse logo `div.site-footer__top > div.site-footer__col > a.site-footer__logo > img`	discourse.org/a/img/logo.svg
Download Discourse Hub on the App Store `div.site-footer__col > div.app-badges > a > img`	discourse.org/a/img/badge-app-store.svg
Atlassian logo `div.hero-section__inner > div.logos-wrapper > div.logo-item > img`	discourse.org/a/img/customers/logo/atlassian-light.svg
Asana logo `div.hero-section__inner > div.logos-wrapper > div.logo-item > img`	discourse.org/a/img/customers/logo/asana-light.svg
GitLab logo `div.hero-section__inner > div.logos-wrapper > div.logo-item > img`	discourse.org/a/img/customers/logo/gitlab-light.svg
OpenAI logo `div.hero-section__inner > div.logos-wrapper > div.logo-item > img`	discourse.org/a/img/customers/logo/openai-light.svg
Zoom logo `div.hero-section__inner > div.logos-wrapper > div.logo-item > img`	discourse.org/a/img/customers/logo/zoom-light.svg

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.2 s

●Max Potential First Input Delay 30 ms

●Minify CSS

●Reduce unused CSS

●Reduce unused JavaScript

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.7 s

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 300 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 0 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

Navigation

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Features & Pricing `div.site-footer__wrapper > div.site-footer__top > div.site-footer__col > h6`

These are opportunities to improve keyboard navigation in your application.

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.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.site-header-container > header.site-header > div.site-header-logo-container > a.logo `div.site-header-container > header.site-header > div.site-header-logo-container > a.logo`
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link `div.site-footer__col > ul.site-footer__list > li > a.site-footer__link`
div.site-footer__col > ul.site-footer__list > li > a `div.site-footer__col > ul.site-footer__list > li > a`
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link `div.site-footer__col > ul.site-footer__list > li > a.site-footer__link`
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link `div.site-footer__col > ul.site-footer__list > li > a.site-footer__link`
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link `div.site-footer__col > ul.site-footer__list > li > a.site-footer__link`
div.site-footer__col > ul.site-footer__list > li > a.site-footer__link `div.site-footer__col > ul.site-footer__list > li > a.site-footer__link`

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.

○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

●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

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

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

●Buttons have an accessible name

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

●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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

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

100

Best Practices

General

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Map URL
discourse.org/a/js/lucide.min.js?v=20260417223814	discourse.org/a/js/lucide.min.js.map

●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

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

SEO

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.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`
div.features-section__inner > div.feature-card > div.feature-card__media > img `div.features-section__inner > div.feature-card > div.feature-card__media > img`

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`

Results for https://discourse.org

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (1)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Navigation

Names and labels

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Navigation

Names and labels

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts