Lighthouse Mobile

· 0 checks — Mobile 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
cdn.consentmanager.net/delivery/js/cmp_en.min.js	86400.0 s	101.2 KiB
/delivery/customdata/bV8xLndfNzUwMDEucl9HRFBSLmxfZGUuZF8y...	3600.0 s	47.5 KiB

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.

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

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:1228.055 label:Time to first byte subpart:timeToFirstByte] map[duration:1548.634 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-DIV

nodeLabel: Wir verwenden Cookies und andere Technologien, um Informationen auf Deinem Gerä…

path: 1,HTML,1,BODY,1,DIV,0,DIV,0,DIV,0,DIV,1,DIV

selector: div.cmpboxinner > div#cmpboxcontent > div.cmpboxtxtdiv > div.cmpboxtxt

snippet: <div class="cmpboxtxt cmptxt_txt">

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

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.CQ0D1Bu_.css	80.4 KiB	664 ms
www.knuddels.de/_astro/registration-native.B9nFVOcO.css	79.7 KiB	332 ms
www.knuddels.de/_astro/registration-native.DhzNyadj.css	9.5 KiB
www.knuddels.de/_astro/registration-native.DeFvVRHI.css	1.9 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	39.3 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	19.5 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	12.4 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	10.8 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: 1.2 s

URL	Time Spent
knuddels.de/	1.2 s
www.knuddels.de/	0.0 ms

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.

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: 890 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: 300 ms 36.7 KiB

URL	Transfer Size	Est Savings
cdn.consentmanager.net/delivery/js/cmp_en.min.js	100.8 KiB	36.7 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	1.5 s
Script Evaluation	983 ms
Style & Layout	530 ms
Rendering	158 ms
Script Parsing & Compilation	125 ms
Parse HTML & CSS	115 ms
Garbage Collection	17 ms

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 1.1 s

●Avoid long main-thread tasks 8 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 340 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

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

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

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