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.

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:7719.934 label:Time to first byte subpart:timeToFirstByte] map[duration:1357.171 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-SPAN

nodeLabel: a.link > span.link__content

path: 1,HTML,1,BODY,2,P-HEADER,a,#document-fragment,2,MUSE-HEADER,5,K-ACCOUNT-MENU,0,MUSE-LINK,a,#document-fragment,1,A,1,SPAN

selector: a.link > span.link__content

snippet: <span class="link__content">

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

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: 40 ms 81.7 KiB

URL	Transfer Size	Est Savings
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js	218.2 KiB	81.7 KiB

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
Internal error.	Not actionable

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

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: 407 ms

URL	Time Spent
bund.de/	200 ms
verwaltung.bund.de/	207 ms
verwaltung.bund.de/portal/	0.0 ms

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Time to Interactive 0.7 s

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 228 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.2 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 10 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 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

100

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.

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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○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

○Heading elements appear in a sequentially-descending order

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

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

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

○Identical links have the same purpose.

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

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 758, col 1711	`ApiError: Generic Error at MI (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:2993) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:3268`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 758, col 1868	`ApiError: Generic Error at MI (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:2993) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:3268`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 758, col 2047	`ApiError: Generic Error at MI (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:2993) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:3268`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 628, col 1155	`ApiError: Generic Error at tO (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:7971) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:8246`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 1931, col 11493	`ApiError: Generic Error at tO (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:7971) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:8246`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 713, col 1278	`ApiError: Generic Error at tO (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:7971) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:8246`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 289, col 1079	`ApiError: Generic Error at tO (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:7971) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:8246`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780213.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780216.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/footer	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/header	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/main-navigation	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/i18n/locales	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/start-page-deep	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780197.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/konto/scripts/konto-frontend/konto-frontend.esm.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/leistungsverzeichnis/scripts/lv-search.v3.bundle.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/api/frontend-config	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780186.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780202.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780200.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780201.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780185.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780187.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378084.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378033.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378056.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378037.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780147.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/header/	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/main-navigation/	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/img/favicon-32-4964ce435000594d79f4beb52f131baa.png	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 91, col 20723	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780147.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780185.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780186.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780187.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780197.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780197.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780200.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780201.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780202.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780213.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 2046, col 12794	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780216.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 91, col 20723	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378033.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 91, col 20723	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378037.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 91, col 20723	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378056.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 91, col 20723	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378084.js`

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
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js

●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 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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

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

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.

Canonical links suggest which URL to show in search results. Learn more about canonical links.

Why this matters

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

Source: MDN Permissions-Policy

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 have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid