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.

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
www.united-domains.de/assets/fonts/neo-icons.cb-e4cb3.woff2	145 ms

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

nodeLabel: Domain-Check Suchen. Sichern. Starten. Neue Domain finden Domain mit KI gener…

path: 1,HTML,1,BODY,4,MAIN,2,DIV

selector: body.gen-layer__body-open > main#mainContent > div#molid5705148

snippet: <div id="molid5705148" class=" mol-stage mol-stage--full-width mol-st…">

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.united-domains.de/assets/css/atomic-common.cb-e4cb3.css	55.2 KiB	84 ms
www.united-domains.de/assets/js/atomic-common.cb-e4cb3.js	24.0 KiB

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

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: 10 ms 46.1 KiB

URL	Transfer Size	Est Savings
www.united-domains.de/assets/css/atomic-common.cb-e4cb3.css	54.8 KiB	46.1 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
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

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.column > div.mol-container-grid__molecule > div.mol-standalone-image > img `div.column > div.mol-container-grid__molecule > div.mol-standalone-image > img`	www.united-domains.de/file/761533159362228500
a > span.mol-teaser-vertical__image-aspect-ratio > span.mol-teaser-vertical__image > img `a > span.mol-teaser-vertical__image-aspect-ratio > span.mol-teaser-vertical__image > img`	www.united-domains.de/file/117560897578801117
American Express-Logo `div.elm-footer__meta-payment > div > a > img.american-express`	www.united-domains.de/assets/img/footer/icon-payment-american-express.svg
div.row > div.mol-usp-bar__contains-elements > div.mol-usp-bar__logo > img `div.row > div.mol-usp-bar__contains-elements > div.mol-usp-bar__logo > img`	www.united-domains.de/file/649870975262184827
Hosted in Germany Logo `div.elm-footer__meta > div.elm-footer__meta-certificates > div > img.elm-footer__meta-certificates-hosted-in-germany`	www.united-domains.de/assets/img/footer/logo-hosted-in-germany.svg
Mastercard-Logo `div.elm-footer__meta-payment > div > a > img.mastercard`	www.united-domains.de/assets/img/footer/icon-payment-mastercard.svg
VISA-Logo `div.elm-footer__meta-payment > div > a > img.visa`	www.united-domains.de/assets/img/footer/icon-payment-visa.svg
IONOS-Logo `div.elm-footer__meta-ionos > div > a > img`	www.united-domains.de/assets/img/footer/logo-ionos.svg
Diners Club-Logo `div.elm-footer__meta-payment > div > a > img.diners-club`	www.united-domains.de/assets/img/footer/icon-payment-diners-club.svg
SEPA-Logo `div.elm-footer__meta-payment > div > a > img.sepa`	www.united-domains.de/assets/img/footer/icon-payment-sepa.svg
25 Jahre united-domains Logo `div.elm-footer__meta > div.elm-footer__meta-certificates > div > img.elm-footer__meta-certificates-25-years-united-domains`	www.united-domains.de/assets/img/footer/25-jahre-united-domains-logo-footer.svg
Youtube-Icon `div.elm-footer__meta-social > div > a > img.youtube`	www.united-domains.de/assets/img/footer/icon-youtube.svg
LinkedIn-Icon `div.elm-footer__meta-social > div > a > img.linkedin`	www.united-domains.de/assets/img/footer/icon-linkedin.svg
ICANN-Logo `div.elm-footer__meta > div.elm-footer__meta-certificates > div > img.elm-footer__meta-certificates-icann`	www.united-domains.de/assets/img/footer/logo-icann.svg
Google-Logo `div.elm-footer__meta-google > div.elm-footer__meta-google-contains-logo-and-details > div.elm-footer__meta-google-logo > img`	www.united-domains.de/assets/img/footer/logo-google.svg
PayPal-Logo `div.elm-footer__meta-payment > div > a > img.paypal`	www.united-domains.de/assets/img/footer/icon-payment-paypal.svg
united-domains-Logo `div.elm-footer__meta > div.elm-footer__meta-copyright > div > img`	www.united-domains.de/assets/img/footer/logo-united-domains.svg
div.row > div.mol-usp-bar__contains-elements > div.mol-usp-bar__logo > img `div.row > div.mol-usp-bar__contains-elements > div.mol-usp-bar__logo > img`	www.united-domains.de/file/76231138960853150
Secured by Sectigo Logo `div.elm-footer__meta > div.elm-footer__meta-certificates > div > img.elm-footer__meta-certificates-sectigo`	www.united-domains.de/assets/img/footer/logo-sectigo-trust-seal.webp
div.mol-container-grid__molecule > div.mol-text-icon-combination > div.mol-text-icon-combination__icon > img `div.mol-container-grid__molecule > div.mol-text-icon-combination > div.mol-text-icon-combination__icon > img`

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

URL	Time Spent
united-domains.de/	472 ms
www.united-domains.de/	0.0 ms

●Time to Interactive 1.8 s

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 30 ms

●Minify CSS

●Minify JavaScript

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 987 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.4 s

●Avoid long main-thread tasks 1 long task found

●Network Requests

●Network Round Trip Times 90 ms

●Server Backend Latencies 140 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 490 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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Cookie-Einstellungen Wir setzen Cookies ein, um unsere Website optimal für Sie… `body.gen-layer__body-open > dialog.gen-layer`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Datenschutzhinweisen `div.gen-layer__white > form.cookie-layer-form > p.intro-text > a`

○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

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

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

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

○Document has a `<title>` element

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○Heading elements appear in a sequentially-descending order

○`<html>` element has a `[lang]` attribute

○`<html>` element has a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

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

○`[lang]` attributes have a valid value

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

○Document has a main landmark.

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

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

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

○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
Hilfe `ul.mol-responsive-menu > li.help-layer > div.mol-responsive-menu__dropdown-accordion-trigger > a`
Neue Domain finden `div.mol-search-box__contains-tabs-and-forms > div.mol-search-box__contains-tabs > div.mol-search-box__tabs > a.mol-search-box__tab`
Domain mit KI generieren `div.mol-search-box__contains-tabs-and-forms > div.mol-search-box__contains-tabs > div.mol-search-box__tabs > a.mol-search-box__tab`

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

○Structured data is valid

●Page isn’t blocked from indexing

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

○Document has a `<title>` element

○Image elements have `[alt]` attributes