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.

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.

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: div.image-text > div.image-text__image > picture.picture > img.image

path: 1,HTML,1,BODY,1,DIV,2,MAIN,1,DIV,0,DIV,0,DIV,0,UL,0,LI,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,3,IMG

selector: div.image-text > div.image-text__image > picture.picture > img.image

snippet: <img src="https://cdn.test.de/file/image/95/bf/982274cd-96f5-44ef-91d1-c243e70dc990-…" class="image" alt="" width="2048" height="1365">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

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

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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
www.test.de/gtm.js?id=GTM-W9MTK4V	900.0 s	158.9 KiB
cdn-eu.piano.io/api/tinypass.min.js	14400.0 s	132.8 KiB
www.test.de/static/images/modules/quiz/quiz-bg_question-marks_desktop.webp	60.0 s	70.1 KiB
cdn.cxense.com/cx.js	3600.0 s	38.1 KiB
cdn.cxense.com/cx.cce.js	3600.0 s	6.8 KiB
experience-eu.piano.io/xbuilder/experience/load?aid=lzfikWNGpe	1800.0 s	2.3 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.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/25/31/3166c131-975a-444e-a2f7-83ce2ec2654e-we...	252.5 KiB	243.9 KiB
div.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/95/bf/982274cd-96f5-44ef-91d1-c243e70dc990-we...	240.7 KiB	148.3 KiB
div.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/17/23/b850131a-cce0-45e3-88dd-1c5f384f7577-we...	105.5 KiB	96.9 KiB
div.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/25/a3/2834dcc1-1923-42a4-9a83-6e81eaffc100-we...	68.0 KiB	60.3 KiB
div.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/a8/93/95d785c4-350c-412f-9e8f-b077373e9ba8-we...	60.7 KiB	53.8 KiB
div.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/c7/97/9f792b80-2432-4e1d-bb70-bd3c7286cba7-we...	56.5 KiB	50.1 KiB
div.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/a3/21/25c102b1-360c-41a0-8d92-fff42a1d6d8c-we...	55.2 KiB	48.9 KiB
div.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/08/a4/0059a454-a8b0-4bc6-95d6-01b0d7f71308-we...	47.8 KiB	42.4 KiB
div.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/21/81/813f088e-74fb-4275-aed8-d3ebc8e04aca-we...	37.3 KiB	33.1 KiB
div.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/d4/61/f6f6050f-7f1d-4184-afc2-0483393d197d-we...	36.0 KiB	31.9 KiB
div.marketing-teaser__wrapper > div.js-clickable__trigger > picture.picture > img.image `div.marketing-teaser__wrapper > div.js-clickable__trigger > picture.picture > img.image`	/file/image/15/57/e87c200e-c95c-4002-b51d-9d347494c145-we...	38.5 KiB	23.4 KiB
div.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/63/71/738acdce-36bd-4015-bbee-238704d334dc-we...	48.6 KiB	23.3 KiB
li.quick-start__item > div.quick-start__img-wrapper > picture.picture > img.image `li.quick-start__item > div.quick-start__img-wrapper > picture.picture > img.image`	/file/image/e8/72/7713e691-38c7-4495-956d-a1d4277f0eb8-we...	22.1 KiB	18.9 KiB
div.image-text > div.image-text__image > picture.picture > img.image `div.image-text > div.image-text__image > picture.picture > img.image`	/file/image/c0/7c/7f5fdd4b-e6a6-4eb4-b244-fc7806099f70-we...	20.9 KiB	18.5 KiB
li.quick-start__item > div.quick-start__img-wrapper > picture.picture > img.image `li.quick-start__item > div.quick-start__img-wrapper > picture.picture > img.image`	/file/image/46/11/1290492e-df34-44d7-8b46-194e55484e3f-we...	18.9 KiB	15.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: 904 ms

URL	Time Spent
test.de/	904 ms
www.test.de/	0.0 ms

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

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

URL	Transfer Size	Est Savings
/critical/ :root{--color-brand-test:	18.9 KiB	13.6 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 229.2 KiB

URL	Transfer Size	Est Savings
cdn-eu.piano.io/api/tinypass.min.js	132.1 KiB	81.1 KiB
www.test.de/gtm.js?id=GTM-W9MTK4V	158.9 KiB	75.0 KiB
/static/scripts/chunks/vendors-node_modules_vue_dist_vue_...	56.6 KiB	27.7 KiB
cdn.cxense.com/cx.js	37.5 KiB	24.6 KiB
cdn.test.de/static/scripts/main.min;v167309086.js	37.6 KiB	20.8 KiB

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

●Max Potential First Input Delay 80 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,165 KiB

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.7 s

●Avoid long main-thread tasks 1 long task found

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

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 220 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

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

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Direkt zum Inhalt `header.header-wrapper > ul.tab-navigation > li.tab-navigation__item > a.link`

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
Immobilieninvestments Betongold? Für wen sich Fonds, ETF und Anleihen eignen `div.image-text > div.image-text__content > a.link > h3.image-text__headline`
Demenz. Nicht Jetzt! `div.shop-products-teaser__item-wrapper > div.shop-products-teaser__content > a.link > p.h5`

These are opportunities to improve keyboard navigation in your application.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Steuern + Recht `div.portal-navigation-desktop__list-wrapper > ul.portal-navigation-desktop__list > li.portal-navigation-desktop__item > button.portal-navigation-desktop__link`

○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

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●Form elements have associated labels

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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

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

●Touch targets have sufficient size and spacing.

●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 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 type="image">` elements have `[alt]` text

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

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

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
70	`Legal notice: Stiftung Warentest expressly reserves the right to use its content for commercial text and data mining (para. 44 b UrhG).`	`Unknown directive`
72	`The use of robots or other automated means to access http://test.de or collect or mine data without the express permission of Stiftung Warentest is strictly prohibited.`	`Unknown directive`
74	`Stiftung Warentest may, in its discretion, permit certain automated access to certain http://test.de pages.`	`Unknown directive`
76	`The rights from para. 60d UrhG remain unaffected.`	`Syntax not understood`

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

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`