Skip to content
https://ionos.de

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

89

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.

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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.

RequestCache TTLTransfer Size
6zqtim.ionos.de/get/live/web/_/aljmf5.js0.0 ms75.2 KiB
var.uicdn.net/shopsshort/privacy/v1/bundle.js900.0 s73.4 KiB
cdn.ionos.de/nk/9c2134ba72b4/6c2bd2fdffdc/launch-67fb473cc73f.min.js900.0 s60.6 KiB
apps.mypurecloud.de/journey/messenger-plugins/journey.min.js600.0 s17.0 KiB
frontend-services.ionos.com/t/ias/js/ias.js?v=6.12.1986400.0 s29.3 KiB
frontend-services.ionos.com/t/sentry/bundle.min.js86400.0 s20.7 KiB
/t/password-indicator/js/password-indicator.js?v=3.2.686400.0 s20.2 KiB
frontend-services.ionos.com/t/tag/IONOS/shop.js1800.0 s9.1 KiB
frontend-services.ionos.com/t/t/js/t.js?v=2.2.186400.0 s16.5 KiB
var.uicdn.net/shopsshort/privacy/v1/bundle.css900.0 s6.4 KiB
apps.mypurecloud.de/journey/messenger-plugins/offersHelper.min.js600.0 s5.5 KiB
/nk/9c2134ba72b4/6c2bd2fdffdc/8b3b79a8015f/RC341bfc75178d...900.0 s3.5 KiB
var.uicdn.net/shopsshort/ionos-datalayer/v1/ionos-datalayer.min.umd.js900.0 s3.4 KiB
/t/password-indicator/css/password-indicator.css?v=3.2.686400.0 s1.1 KiB
/nk/9c2134ba72b4/6c2bd2fdffdc/8b3b79a8015f/RCdefebbc115bc...900.0 s459 B

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.

URLResource SizeEst Savings
Ein freundlicher Mann aus dem IONOS-Support-Team telefoniert. div#__next > button.tw-fixed > div.tw-relative > img#273995
cs.uicdn.net/avif/user_upload/vi_psa-nlement-de.png.avif7.4 KiB6.2 KiB

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.

URLTransfer Size
www.ionos.de/abtesting-de.js420 B

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: 273 ms
URLTime Spent
ionos.de/273 ms
www.ionos.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

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.

CategoryTime Spent
Script Evaluation1.2 s
Other585 ms
Style & Layout228 ms
Script Parsing & Compilation109 ms
Rendering99 ms
Parse HTML & CSS82 ms
Garbage Collection19 ms

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 67.0 KiB
URLTransfer SizeEst Savings
apps.mypurecloud.de/genesys-bootstrap/genesys.min.js154.9 KiB67.0 KiB

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 36.4 KiB
URLTransfer SizeEst Savings
www.ionos.de/_next/static/chunks/b94077be48fea7cf.css43.9 KiB36.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: 0.0 ms 211.5 KiB
URLTransfer SizeEst Savings
apps.mypurecloud.de/genesys-bootstrap/genesys.min.js154.9 KiB77.9 KiB
www.ionos.de/js/at_visitor.min.js54.0 KiB53.6 KiB
var.uicdn.net/shopsshort/privacy/v1/bundle.js72.9 KiB32.1 KiB
6zqtim.ionos.de/get/live/web/_/aljmf5.js75.0 KiB27.4 KiB
www.ionos.de/_next/static/chunks/194098810fb2d942.js63.4 KiB20.6 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
/fileadmin/ionos-core/Campaigns/TV-2025/home/IONOS_DE_Hea...4.1 MiB
apps.mypurecloud.de/messenger/muiVendor.min.js246.9 KiB
apps.mypurecloud.de/genesys-bootstrap/genesys.min.js155.3 KiB
/fileadmin/ionos-core/Navigation/navigation_mobilfunk-und...126.4 KiB
apps.mypurecloud.de/messenger/main.min.js92.5 KiB
apps.mypurecloud.de/messenger/messengerrenderer.min.js90.6 KiB
www.ionos.de/88.8 KiB
6zqtim.ionos.de/get/live/web/_/aljmf5.js75.2 KiB
var.uicdn.net/shopsshort/privacy/v1/bundle.js73.4 KiB
apps.mypurecloud.de/messenger/defaultVendors.min.js66.1 KiB

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
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●User Timing marks and measures 4 user timings
●JavaScript execution time 1.1 s
●Avoid long main-thread tasks 3 long tasks found
●Avoid non-composited animations 3 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 450 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 30 ms
●Avoid large layout shifts 4 layout shifts found
○INP breakdown
○LCP request discovery
88

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Einstellungen div.privacy-consent--intro > p.privacy-consent--text > p.svelte-1koe4rp > button#configButton
Richtlinie zur Verwendung von Cookies div.privacy-consent--intro > p.privacy-consent--text > p.svelte-1koe4rp > a
Datenschutzhinweisen div.privacy-consent--intro > p.privacy-consent--text > p.svelte-1koe4rp > a
ablehnen div.privacy-consent--intro > p.privacy-consent--text > p.svelte-1koe4rp > button#confirmSelection
Akzeptieren div.privacy-consent--intro > p.privacy-consent--text > p.svelte-1koe4rp > button#selectAll
Impressum div.privacy-consent--body > div.privacy-consent--row > div.privacy-consent--imprint > a
Akzeptieren div.privacy-consent--foot > div.privacy-consent--row > div.privacy-consent--button-container > button#selectAll
Ablehnen div.privacy-consent--foot > div.privacy-consent--row > div.privacy-consent--button-container > button#confirmSelection
Einstellungen div.privacy-consent--foot > div.privacy-consent--row > div.privacy-consent--button-container > button.privacy-consent--button

These are opportunities to improve the legibility of your content.

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
ionos logo div.tw-hidden > div.tw-container > div.tw-hidden > a#header-logo
0721 / 170 5522 div.tw-container > div.tw-flex > div > a.whitespace-nowrap
Über Uns div.tw-flex > div > div.tw-z-51 > button.tw-text-ellipsis
Support div.tw-flex > div > div.tw-z-51 > button.tw-text-ellipsis
Login div.tw-flex > div > div.tw-z-51 > button.tw-text-ellipsis
Neu Momentum KI nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_1
Domains & SSL nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_2
E-Mail & Office nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_3
Website nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_4
Onlineshop nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_5
WordPress nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_6
Hosting nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_7
Server nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_8
Cloud nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_9
Internet & Mobilfunk nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_10

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
Passende Domain div.tw-flex > a.tw-min-h-300 > div > h3.tw-block
Sehr empfehlenswert! div.!tw-w-[calc(100vw-1.5rem)] > div.keen-slider__slide > div > h5.tw-block

These are opportunities to improve keyboard navigation in your application.

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.tw-py-64 > div.tw-flex > div.tw-relative > img.tw-absolute div.tw-py-64 > div.tw-flex > div.tw-relative > img.tw-absolute

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.

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
Accéder au site français div#shopRecommendedBanner > div.tw-flex > div.tw-w-full > a.whitespace-nowrap
0721 / 170 5522 div.tw-container > div.tw-flex > div > a.whitespace-nowrap
Nur bei IONOS Ihr persönlicher Berater Mehr body.tw-font-sans-regular > div#__next > button.tw-fixed
○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
●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
●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
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●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
○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
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
96

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.

SourceDescription
www.ionos.de/_next/static/chunks/524e2519d7de1081.js line 1654, col 285
%cCan't register plugin %cJourney%c -- Name is already taken
www.ionos.de/_next/static/chunks/524e2519d7de1081.js line 1654, col 285
%cCan't register plugin %cJourney%c -- Name is already taken
●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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
85

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.ionos.de/terms-gtc/termsHier

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.tw-py-64 > div.tw-flex > div.tw-relative > img.tw-absolute div.tw-py-64 > div.tw-flex > div.tw-relative > img.tw-absolute

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 are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback