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
joinmastodon.org/fonts/manrope-variable.woff2	3600.0 s	49.7 KiB
scripts.simpleanalyticscdn.com/auto-events.js	10800.0 s	2.1 KiB
scripts.simpleanalyticscdn.com/latest.js	604800.0 s	4.8 KiB

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

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-IMG

nodeLabel: section.full-width-bg > div.absolute > span > img

path: 1,HTML,1,BODY,0,DIV,0,DIV,2,MAIN,0,SECTION,1,DIV,0,SPAN,0,IMG

selector: section.full-width-bg > div.absolute > span > img

snippet: <img alt="" src="/_next/static/media/home_hero_mobile.76a87209.webp" decoding="async" data-nimg="fill" style="position: absolute; inset: 0px; box-sizing: border-box;">

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
joinmastodon.org/fonts/manrope-variable.woff2	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.full-width-bg__inner > div.row-span-full > span > img `div.full-width-bg__inner > div.row-span-full > span > img`	/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Ffeatures_tim...	122.2 KiB	89.1 KiB

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

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: 0.0 ms 199.0 KiB

URL	Transfer Size	Est Savings
joinmastodon.org/_next/static/chunks/223-8dfb04dccb7295c1.js	51.9 KiB	47.8 KiB
joinmastodon.org/_next/static/chunks/pages/hosting-d1a4a58a9f20aaf2.js	48.9 KiB	43.0 KiB
joinmastodon.org/_next/static/chunks/802-c44bed76d8b58842.js	56.0 KiB	36.0 KiB
joinmastodon.org/_next/static/chunks/716-e5aa5df69cce9777.js	29.5 KiB	25.9 KiB
joinmastodon.org/_next/static/chunks/pages/apps-79b70f1eb01b8319.js	64.6 KiB	24.4 KiB
joinmastodon.org/_next/static/chunks/463-4d4fbcf0cfd07cb2.js	26.8 KiB	21.9 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Network dependency tree

●Render blocking requests

●Optimize viewport for mobile

●Time to Interactive 1.0 s

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

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

●User Timing marks and measures 4 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.7 s

●Avoid long main-thread tasks 2 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 10 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

●Avoid large layout shifts 1 layout shift 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.

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
Join mastodon.social `section.full-width-bg > div.full-width-bg__inner > div.flex > a.flex`
Pick another server `section.full-width-bg > div.full-width-bg__inner > div.flex > a.flex`
Learn more `div.full-width-bg > div.full-width-bg__inner > div.row-span-full > a.flex`
Learn more `div.full-width-bg > div.full-width-bg__inner > div.row-span-full > a.flex`
Find a server `div.full-width-bg > div.full-width-bg__inner > div.row-span-full > a.flex`
Learn more `div.full-width-bg > div.full-width-bg__inner > div.row-span-full > a.flex`
Donate on Patreon `div.py-20 > div.lg:col-span-8 > div.flex > a.flex`
Donate directly `div.py-20 > div.lg:col-span-8 > div.flex > a.flex`
Learn more `div.py-20 > div.lg:col-span-8 > div.flex > a.flex`
Sponsorship does not equal influence. Mastodon is fully independent. `div.mx-auto > main#main > section.grid > p.mt-8`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`
Go to slide `div.full-width-bg__inner > div > div.flex > button.rounded-[50%]`

These items highlight common accessibility best practices.

○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

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

●Elements use only permitted ARIA attributes

●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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

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

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

○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

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

○Use a strong HSTS policy

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
docs.joinmastodon.org/user/moderating/	Learn more
docs.joinmastodon.org/user/run-your-own/	Learn more
docs.joinmastodon.org/user/posting/	Learn more
joinmastodon.org/sponsors	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

●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