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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.167637] map[node:map[boundingRect:map[bottom:784 height:528 left:165 right:1185 top:256 width:1020] lhId:page-2-DIV nodeLabel:Unser Chat bringt Menschen zusammen. Jetzt kostenlos registrieren Mit dem Star… path:1,HTML,1,BODY,12,MAIN,4,DIV,0,DIV selector:body.relative > main.min-h-full > div.flex-1 > div.flex snippet:<div class="flex flex-col-reverse md:flex-row md:gap-xxlarge min-w-none"> type:node] score:0.167624 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1316 height:24 left:280 right:304 top:1292 width:24] lhId:page-5-IMG nodeLabel:div.mx-large > section.flex > div.flex > img.w-[24px] path:1,HTML,1,BODY,15,ARTICLE,0,DIV,6,SECTION,0,DIV,0,IMG selector:div.mx-large > section.flex > div.flex > img.w-[24px] snippet:<img loading="lazy" src="/_astro/flag-eu.webp" class="w-[24px]" data-astro-cid-u43ozx4m=""> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:68 height:44 left:1101 right:1191 top:24 width:90] lhId:page-1-DIV nodeLabel:Login path:1,HTML,1,BODY,11,HEADER,1,DIV,1,DIV selector:body.relative > header.absolute > div.max-w-container > div.ml-auto snippet:<div class="ml-auto hidden md:flex"> type:node] score:1.3e-05 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:1316 height:24 left:280 right:304 top:1292 width:24] lhId:page-5-IMG nodeLabel:div.mx-large > section.flex > div.flex > img.w-[24px] path:1,HTML,1,BODY,15,ARTICLE,0,DIV,6,SECTION,0,DIV,0,IMG selector:div.mx-large > section.flex > div.flex > img.w-[24px] snippet:<img loading="lazy" src="/_astro/flag-eu.webp" class="w-[24px]" data-astro-cid-u43ozx4m=""> type:node]]] type:subitems]]]

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

value: No additional origins are good candidates for preconnecting

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
www.knuddels.de/_astro/registration-native.DeFvVRHI.css	1.9 KiB
www.knuddels.de/_astro/registration-native.B9nFVOcO.css	79.7 KiB
www.knuddels.de/_astro/registration-native.CQ0D1Bu_.css	80.4 KiB	461 ms
www.knuddels.de/_astro/registration-native.DhzNyadj.css	9.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
cdn.consentmanager.net/delivery/js/cmp_en.min.js	86400.0 s	101.2 KiB
/delivery/customdata/bV8xLndfNzUwMDEucl9HRFBSLmxfZGUuZF8y...	3600.0 s	48.1 KiB

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.max-w-[360px] > div.flex-1 > picture > img `div.max-w-[360px] > div.flex-1 > picture > img`	www.knuddels.de/_astro/02-spielen_7Q62W.avif	84.7 KiB	64.5 KiB
div.max-w-[360px] > div.flex-1 > picture > img `div.max-w-[360px] > div.flex-1 > picture > img`	www.knuddels.de/_astro/01-kennenlernen_Z1tUU9g.avif	65.5 KiB	45.1 KiB
div.max-w-[360px] > div.flex-1 > picture > img `div.max-w-[360px] > div.flex-1 > picture > img`	www.knuddels.de/_astro/04-themen_6qRzS.avif	56.0 KiB	36.6 KiB
div.max-w-[360px] > div.flex-1 > picture > img `div.max-w-[360px] > div.flex-1 > picture > img`	www.knuddels.de/_astro/03-freunde_Z14ODeU.avif	53.3 KiB	34.4 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 699 ms

URL	Time Spent
knuddels.de/	699 ms
www.knuddels.de/	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
Unser Chat bringt Menschen zusammen. Jetzt kostenlos registrieren Mit dem Star… `body.relative > main.min-h-full > div.flex-1 > div.flex`	0.168
Login `body.relative > header.absolute > div.max-w-container > div.ml-auto`	0.000

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: 80 ms 159.6 KiB

URL	Transfer Size	Est Savings
www.knuddels.de/_astro/registration-native.CQ0D1Bu_.css	80.1 KiB	80.1 KiB
www.knuddels.de/_astro/registration-native.B9nFVOcO.css	79.4 KiB	79.4 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: 0.0 ms 36.6 KiB

URL	Transfer Size	Est Savings
cdn.consentmanager.net/delivery/js/cmp_en.min.js	100.8 KiB	36.6 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.max-w-[360px] > div.flex-1 > picture > img `div.max-w-[360px] > div.flex-1 > picture > img`	www.knuddels.de/_astro/01-kennenlernen_Z1tUU9g.avif
div.max-w-[360px] > div.flex-1 > picture > img `div.max-w-[360px] > div.flex-1 > picture > img`	www.knuddels.de/_astro/02-spielen_7Q62W.avif
div.max-w-[360px] > div.flex-1 > picture > img `div.max-w-[360px] > div.flex-1 > picture > img`	www.knuddels.de/_astro/04-themen_6qRzS.avif
div.max-w-[360px] > div.flex-1 > picture > img `div.max-w-[360px] > div.flex-1 > picture > img`	www.knuddels.de/_astro/03-freunde_Z14ODeU.avif
div.mx-large > section.flex > div.flex > img.w-[24px] `div.mx-large > section.flex > div.flex > img.w-[24px]`	www.knuddels.de/_astro/flag-eu.webp
Logo `body.relative > div#cmpbox > div.cmplogo > img.cmpdl`	cdn.consentmanager.net/delivery/img/logo1714641851x6154.gif
div.relative > div.flex > div.bg-purple-300 > img.w-[80px] `div.relative > div.flex > div.bg-purple-300 > img.w-[80px]`
div.relative > div.flex > div.bg-purple-300 > img.w-[80px] `div.relative > div.flex > div.bg-purple-300 > img.w-[80px]`
div.relative > div.flex > div.bg-purple-300 > img.w-[80px] `div.relative > div.flex > div.bg-purple-300 > img.w-[80px]`

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

●Max Potential First Input Delay 110 ms

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.8 s

●Avoid long main-thread tasks 1 long task found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 370 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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

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.mx-large > section.flex > div.flex > img.w-[24px] `div.mx-large > section.flex > div.flex > img.w-[24px]`

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●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

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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○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

●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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Registrieren `div.px-base > div.flex > div.bottom > a.max-w-[300px]`

To appear in search results, crawlers need access to your app.

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.mx-large > section.flex > div.flex > img.w-[24px] `div.mx-large > section.flex > div.flex > img.w-[24px]`

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

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`