Skip to content
https://ionos.fr

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.

62

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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:26.148 source:map[column:2847 line:1 type:source-location url:https://www.ionos.fr/_next/static/chunks/194098810fb2d942.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:2.49 source:map[column:43074 line:0 type:source-location url:https://www.ionos.fr/_next/static/chunks/261248758977f701.js urlProvider:network]] map[reflowTime:24.839 source:map[column:10493 line:0 type:source-location url:https://www.ionos.fr/_next/static/chunks/742e220768604767.js urlProvider:network]] map[reflowTime:0.991 source:map[column:8824 line:0 type:source-location url:https://www.ionos.fr/_next/static/chunks/22d2fb84955a1f72.js urlProvider:network]] map[reflowTime:0.306 source:map[column:59121 line:8 type:source-location url:https://www.ionos.fr/_next/static/chunks/ac07ff8c6e4af851.js urlProvider:network]] map[reflowTime:1.056 source:map[column:17128 line:0 type:source-location url:https://www.ionos.fr/_next/static/chunks/f1d30636e9b5a0a0.js urlProvider:network]] map[reflowTime:5.072 source:map[type:text value:[unattributed]]]]

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
948si5.ionos.fr/get/live/web/_/b44g5k.js0.0 ms74.3 KiB
var.uicdn.net/shopsshort/privacy/v1/bundle.js900.0 s73.4 KiB
cdn.ionos.fr/nk/9c2134ba72b4/6c2bd2fdffdc/launch-67fb473cc73f.min.js900.0 s60.6 KiB
frontend-services.ionos.com/t/ias/js/ias.js?v=6.12.1986400.0 s29.4 KiB
frontend-services.ionos.com/t/sentry/bundle.min.js86400.0 s20.8 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
/nk/9c2134ba72b4/6c2bd2fdffdc/8b3b79a8015f/RC341bfc75178d...900.0 s3.6 KiB
var.uicdn.net/shopsshort/ionos-datalayer/v1/ionos-datalayer.min.umd.js900.0 s3.4 KiB
/nk/9c2134ba72b4/6c2bd2fdffdc/8b3b79a8015f/RCdefebbc115bc...900.0 s559 B
/t/password-indicator/css/password-indicator.css?v=3.2.686400.0 s1.1 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.

URLResource SizeEst Savings
div#__next > button.tw-fixed > div.tw-relative > img#417871 div#__next > button.tw-fixed > div.tw-relative > img#417871
cs.uicdn.net/avif/ionos-core/psa/vi_psa-nlement-fr.png.avif8.8 KiB7.7 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.fr/abtesting-fr.js432 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: 777 ms
URLTime Spent
ionos.fr/777 ms
www.ionos.fr/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

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.

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.1 s
Other561 ms
Style & Layout248 ms
Script Parsing & Compilation129 ms
Parse HTML & CSS109 ms
Rendering102 ms
Garbage Collection45 ms

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.6 KiB
URLTransfer SizeEst Savings
www.ionos.fr/_next/static/chunks/b94077be48fea7cf.css43.9 KiB36.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 133.7 KiB
URLTransfer SizeEst Savings
www.ionos.fr/js/at_visitor.min.js54.0 KiB53.6 KiB
var.uicdn.net/shopsshort/privacy/v1/bundle.js72.9 KiB32.4 KiB
948si5.ionos.fr/get/live/web/_/b44g5k.js74.1 KiB27.1 KiB
www.ionos.fr/_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.2 MiB
www.ionos.fr/83.1 KiB
948si5.ionos.fr/get/live/web/_/b44g5k.js74.3 KiB
var.uicdn.net/shopsshort/privacy/v1/bundle.js73.4 KiB
www.ionos.fr/_next/static/chunks/194098810fb2d942.js63.7 KiB
cdn.ionos.fr/nk/9c2134ba72b4/6c2bd2fdffdc/launch-67fb473cc73f.min.js60.6 KiB
www.ionos.fr/js/at_visitor.min.js54.3 KiB
ce1.uicdn.net/exos/framework/2.1/ionos.min.css54.2 KiB
/avif/ionos-core/Campaigns/TV-2025/home/Content_Card_Gall...52.4 KiB
www.ionos.fr/_next/static/chunks/ac07ff8c6e4af851.js46.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
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 4 user timings
●JavaScript execution time 0.9 s
●Avoid long main-thread tasks 4 long tasks found
●Avoid non-composited animations 1 animated element found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 200 ms
●Server Backend Latencies 630 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 260 ms
●Avoid large layout shifts 3 layout shifts found
○INP breakdown
○LCP request discovery
84

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
Paramètres div.privacy-consent--intro > p.privacy-consent--text > p.svelte-1koe4rp > button#configButton
Politique d'utilisation div.privacy-consent--intro > p.privacy-consent--text > p.svelte-1koe4rp > a
Clause de confidentialité div.privacy-consent--intro > p.privacy-consent--text > p.svelte-1koe4rp > a
refuser div.privacy-consent--intro > p.privacy-consent--text > p.svelte-1koe4rp > button#confirmSelection
Accepter div.privacy-consent--intro > p.privacy-consent--text > p.svelte-1koe4rp > button#selectAll
Accepter div.privacy-consent--foot > div.privacy-consent--row > div.privacy-consent--button-container > button#selectAll
Paramètres div.privacy-consent--foot > div.privacy-consent--row > div.privacy-consent--button-container > button.link

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
0805 542 180 div.tw-container > div.tw-flex > div > a.whitespace-nowrap
À propos 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
Connexion div.tw-flex > div > div.tw-z-51 > button.tw-text-ellipsis
Nouveau Momentum AI nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_1
Domaines & SSL nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_2
Sites Internet nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_3
E-commerce nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_4
Hébergement 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
Email & Office nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_7
Serveurs 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

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
Domaine pertinent div.tw-flex > a.tw-min-h-300 > div > h3.tw-block
Services IONOS au top. 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

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.privacy-consent--body > div.privacy-consent--row > div.privacy-consent--imprint > a div.privacy-consent--body > div.privacy-consent--row > div.privacy-consent--imprint > a
div.privacy-consent--foot > div.privacy-consent--row > div.privacy-consent--imprint > a div.privacy-consent--foot > div.privacy-consent--row > div.privacy-consent--imprint > a

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
0805 542 180 div.tw-container > div.tw-flex > div > a.whitespace-nowrap
Exclu IONOS Conseiller personnel Plus 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.
●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.
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
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

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

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

Send Feedback