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.

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
js.ui-portal.de/homepage/res/live/2.16/gmx/chunk-vendors.bundle.js	12594.0 s	101.0 KiB
js.ui-portal.de/consent-portal/2.0.0/consent.css	900.0 s	74.9 KiB
js.ui-portal.de/netid/cmp/release/v1/gmx/app.js	5720.0 s	81.9 KiB
js.ui-portal.de/homepage/res/live/2.16/gmx/chunk-common.css	12407.0 s	81.0 KiB
/tamago/2.5.0/tamago.js?loglevel=error&view=automatic&tm=...	8574.0 s	68.0 KiB
js.ui-portal.de/homepage/res/live/2.16/gmx/page.bundle.js	12263.0 s	59.4 KiB
dl.gmx.net/uim/connector/live/v2/service.min.js	1032.0 s	41.8 KiB
s.uicdn.com/fd/sentry/v7/bundle.tracing.min.js	180.0 s	32.6 KiB
s.uicdn.com/t/prod/iq/mam/beige/daq.js	157.0 s	16.7 KiB
s.uicdn.com/t/prod/iq/mam/purple/daq.js	446.0 s	16.9 KiB
dl.gmx.net/permission/live/portal/v1/ppp/js/permission-core.min.js	18856.0 s	15.8 KiB
img.ui-portal.de/pos-cdn/tracklib/4.3.0/tracklib.min.js	148.0 s	9.9 KiB
img.ui-portal.de/pos-cdn/tracklib/4.7.3/tracklib.min.js	87.0 s	9.7 KiB
dl.gmx.net/tcf/live/v1/js/tcf-api.js	72377.0 s	18.7 KiB
dl.gmx.net/permission/live/portal/v1/ppp/js/permission-client.js	15067.0 s	11.8 KiB
dl.gmx.net/uim/permission/_auth/authlib.js	1340.0 s	6.2 KiB
i0.gmx.net/image/474/41652474,pd=4,h=1820,w=1108/homepage.webp	1142930.0 s	45.3 KiB
js.ui-portal.de/netid/cmp/release/v1/gmx/app.css	5317.0 s	5.7 KiB
img.ui-portal.de/homepage/tcf/gmx/spinner.gif	375.0 s	3.3 KiB
js.ui-portal.de/netid/cmp/assets/img/spinner.gif	496.0 s	3.3 KiB
s.uicdn.com/permission/live/v1/ppp/js/permission-layer.min.js	18444.0 s	4.6 KiB
s.uicdn.com/t/prod/iq/mam/beige/utag.22.js?utv=ut4.54.202603251024	163.0 s	2.7 KiB
s.uicdn.com/t/prod/iq/mam/purple/utag.81.js?utv=ut4.54.202603251028	446.0 s	2.7 KiB
s.uicdn.com/t/prod/iq/mam/purple/utag.80.js?utv=ut4.54.202603251028	27.0 s	2.5 KiB
img.ui-portal.de/ci/gmx/global/fonts/roboto/RobotoCondensed-Regular-webfont.woff	609554.0 s	24.8 KiB
s.uicdn.com/t/prod/iq/mam/beige/utag.21.js?utv=ut4.54.202603251024	334.0 s	2.5 KiB
img.ui-portal.de/ci/gmx/global/fonts/roboto/Roboto-Medium-webfont.woff	2363942.0 s	24.6 KiB
img.ui-portal.de/ci/gmx/global/fonts/roboto/Roboto-Regular-webfont.woff	2363941.0 s	24.6 KiB
dl.gmx.net/account-avatar/account-avatar.esm.js	33.0 s	1.4 KiB
/mampkg/@mamdev/core-lab.libs.frontend-measurement@7.0.0/...	101.0 s	1.3 KiB
js.ui-portal.de/consent-portal/2.0.0/consent.js	9281.0 s	1.6 KiB
dl.gmx.net/permission/live/portal/v1/ppp/js/permission-client-compat.js	27559.0 s	1.7 KiB
dl.gmx.net/uim/live/config_homepage.js	560259.0 s	8.9 KiB
s.uicdn.com/tcf/live/v1/js/tcf-stub.js	10353.0 s	1.4 KiB
img.ui-portal.de/cd/permissionlayer-prototype/brand/gmx.net/brand-logo.svg	863.0 s	581 B
/t/prod/iq/mam/purple/utag.v.js?a=mam/purple/202603251028...	407.0 s	150 B
/wa/t.gif?timestamp=1776894804725&soft_name=pppcore&soft_...	7200.0 s	160 B
s.uicdn.com/fd/sentry/v7/bundle.tracing.min.js	180.0 s	0 B
s.uicdn.com/t/prod/iq/mam/purple/daq.js	446.0 s	0 B
dl.gmx.net/tcf/live/v1/js/tcf-api.js	72377.0 s	0 B
dl.gmx.net/tcf/live/v1/js/tcf-api.js	72377.0 s	0 B

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:1] map[node:map[boundingRect:map[bottom:940 height:940 left:0 right:1350 top:0 width:1350] lhId:page-1-IFRAME nodeLabel:body > div.ppp-layer > iframe.permission-core-iframe path:1,HTML,1,BODY,3,DIV,0,IFRAME selector:body > div.ppp-layer > iframe.permission-core-iframe snippet:<iframe class="permission-core-iframe" width="100%" border="0" frameborder="0" marginwidth="0" marginheight="0" allowtransparency="true" background="transparent" scrolling="no" sandbox="allow-forms allow-popups allow-popups-to-escape-sandbox allow-same-origin …" name="landingpage" src="https://dl.gmx.net/permission/live/portal/v1/ppp/core.html" style="position: fixed; inset: auto auto 0px 0px; display: block; width: 100%;"> type:node] score:1]]

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: homepage

path: 1,HTML,1,BODY,0,PICTURE,1,IMG

selector: body > picture > img.background-image

snippet: <img alt="homepage" loading="lazy" src="https://i0.gmx.net/image/474/41652474,pd=4,h=1820,w=1108/homepage.webp" class="background-image">

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
dl.gmx.net/tcf/live/v1/js/tcf-api.js	0 B
s.uicdn.com/t/prod/iq/mam/purple/daq.js	0 B
dl.gmx.net/permission/live/portal/v1/ppp/js/permission-client.js	11.8 KiB	203 ms
dl.gmx.net/permission/live/portal/v1/ppp/js/permission-client-compat.js	1.7 KiB
js.ui-portal.de/consent-portal/2.0.0/consent.js	1.6 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: 40 ms 73.6 KiB

URL	Transfer Size	Est Savings
js.ui-portal.de/consent-portal/2.0.0/consent.css	74.7 KiB	73.6 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 with cache-control:no-store header cannot enter back/forward cache.	Actionable
The page has an unload handler in a sub frame.	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
Only pages loaded via a GET request are eligible for back/forward cache.	Not actionable

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.7 KiB

URL	Transfer Size	Est Savings
inline: (function (window) { functio…	14.3 KiB	5.7 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 127.5 KiB

URL	Transfer Size	Est Savings
js.ui-portal.de/netid/cmp/release/v1/gmx/app.js	81.7 KiB	43.1 KiB
/tamago/2.5.0/tamago.js?loglevel=error&view=automatic&tm=...	67.8 KiB	35.0 KiB
s.uicdn.com/fd/sentry/v7/bundle.tracing.min.js	32.5 KiB	26.0 KiB
s.uicdn.com/fd/sentry/v7/bundle.tracing.min.js	32.5 KiB	23.4 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
homepage `body > picture > img.background-image`	i0.gmx.net/image/474/41652474,pd=4,h=1820,w=1108/homepage.webp

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

URL	Time Spent
gmx.net/	295 ms
www.gmx.net/	574 ms
www.gmx.net/consent-management/	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
body > div.ppp-layer > iframe.permission-core-iframe `body > div.ppp-layer > iframe.permission-core-iframe`	1.000

●Time to Interactive 1.7 s

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify CSS

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

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.4 s

●Avoid non-composited animations 1 animated element found

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

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-hidden="true"]` is not present on the document `<body>`

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Document has a `<title>` element

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

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

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

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○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 use only permitted ARIA attributes

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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○Background and foreground colors have a sufficient contrast ratio

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

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

○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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○Touch targets have sufficient size and spacing.

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

○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

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	s.uicdn.com/fd/sentry/v7/bundle.tracing.min.js line 1, col 98918

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
oauth2.gmx.net/token	`Failed to load resource: the server responded with a status of 400 ()`
/netid-user-status?q.tapp_id.eq=ef48100e-ab6f-41e8-9dbb-2...	`Failed to load resource: the server responded with a status of 400 ()`
/netid-user-status?q.tapp_id.eq=ef48100e-ab6f-41e8-9dbb-2...	`Failed to load resource: the server responded with a status of 400 ()`

●Uses HTTPS

●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

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

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.

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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`