Skip to content
Audit Complete

Results for https://ionos.com

Visit site
E-commerce Tracking: purchases
Spain Spain · Madrid Completed: Apr 21, 2026 23:40 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C75

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Strong compliance posture across regulations.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Cart Functionality · 491 peers
You 75
·
Avg 72
At average
0 50 100
Better than 73% of Cart Functionality sites See full Cart Functionality benchmark →
WooCommerce · 86 peers
You 75
·
Avg 74
At average
0 50 100
Better than 46% of WooCommerce sites See full WooCommerce benchmark →

Top Priorities (5)

1

/.env is publicly accessible

Security gaps expose your site and users to attacks, eroding trust.

Security › Information Leakage
2

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

Page weighs 11.3 MB (5.4 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

15 link(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fionos.com)](https://beavercheck.com/results/f0948904-39fc-402d-be92-c3eb6d9a0158)
<a href="https://beavercheck.com/results/f0948904-39fc-402d-be92-c3eb6d9a0158"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fionos.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fionos.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 9.7s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 9.7s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.
B
Could reach Estimate based on resolving critical issues

Conversion Barriers

3 critical 5 warning

8 barrier(s) likely increasing bounce by ~32%.

Speed (2)

Page takes 9.7s to load

+12% bounce

Users abandon at ~3s — you're 7.2s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 2.2s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

Navigation (3)

16 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€450 investment → €4,773/month returns + EUR 120,500,000 risk avoided

Payback period: < 1 month First-year ROI: +12628%

Investment

€450

5h · 5 findings

Monthly returns

€4,773 /mo

~€57,274 / year

  • Conversions recovered €4,772
  • Bandwidth savings €1.25

Regulatory risk avoided

EUR 120,500,000

if kept compliant

  • ePrivacy Directive EUR 100,000,000
  • DSGVO EUR 20,000,000
  • EAA EUR 500,000

Payback period

0 12mo 24mo

€135 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€450

5.0 developer hours at €90/hr

Based on Germany rates (€90/hr)

Quick wins
€135 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,668 / month at risk

~€120,500,015 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveDSGVOEAA
  • No privacy policy link detected
    DSGVO: EUR 10,000 – EUR 20,000,000
  • Trackers detected but no cookie policy found
    DSGVO: EUR 5,000 – EUR 10,000,000
  • Trackers detected but no cookie policy found
    DSGVO: EUR 10,000 – EUR 20,000,000

+7 more

Bandwidth Waste

€1.25 /mo

16834.2 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~1.7 MB per page load
    Saves €1.25/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

12
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
82
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.46 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

9.72 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2.19 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.418

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

9.19 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

23.64 s

Detailed Report

Audit breakdown by category with detailed findings.

12

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

RequestCache TTLTransfer Size
/fileadmin/ionos-core/Stages/Scroll_Card_Gallery_Containe...0.0 ms2.9 MiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
54ft7i.ionos.com/get/live/web/_/48gpcp.js0.0 ms73.9 KiB
var.uicdn.net/shopsshort/privacy/v1/bundle.js900.0 s73.4 KiB
cdn.ionos.com/nk/9c2134ba72b4/6c2bd2fdffdc/launch-67fb473cc73f.min.js900.0 s60.6 KiB
js-eu1.hs-analytics.net/analytics/1776811200000/144960983.js300.0 s42.7 KiB
/signals/config/1270276017756546?v=2.9.303&r=stable&domai...1200.0 s45.2 KiB
js-eu1.hubspot.com/web-interactives-embed.js600.0 s28.4 KiB
dkgefcns0l.kameleoon.io/engine.js14400.0 s37.8 KiB
js-eu1.hs-banner.com/v2/144960983/banner.js300.0 s26.0 KiB
euob.seaskypro.com/sxp/i/ca06d1dce9f2080d34646010859966ac.js43200.0 s44.6 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
/fileadmin/ionos-core/Stages/Scroll_Card_Gallery_Containe...0.0 ms18.6 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.1 KiB
frontend-services.ionos.com/t/tag/IONOS/shop.js1800.0 s9.1 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
frontend-services.ionos.com/t/t/js/t.js?v=2.2.186400.0 s16.5 KiB
bat.bing.com/p/conversions/s/0.8.5986400.0 s15.6 KiB
static.hotjar.com/c/hotjar-6671439.js?sv=660.0 s6.2 KiB
d34r8q7sht0t9k.cloudfront.net/tag.js0.0 ms5.7 KiB
var.uicdn.net/shopsshort/privacy/v1/bundle.css900.0 s6.4 KiB
var.uicdn.net/shopsshort/performance/bowser-2.11.0-es5.js900.0 s6.3 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
var.uicdn.net/shopsshort/performance/web-vitals-5.0.3.iife.js900.0 s2.7 KiB
var.uicdn.net/shopsshort/performance/tagManagerIntegration.min.js900.0 s1.5 KiB
js-eu1.hs-scripts.com/144960983.js0.0 ms1.0 KiB
/collect?v=2&fmt=js&pid=65326&time=1776814722967&url=http...0.0 ms693 B
/rp.gif?ts=1776814722962&id=a2_guk1juaq5x84&event=PageVis...0.0 ms666 B
/nk/9c2134ba72b4/6c2bd2fdffdc/8b3b79a8015f/RCdefebbc115bc...900.0 s562 B
/t/password-indicator/css/password-indicator.css?v=3.2.686400.0 s1.1 KiB
/tag?action=view&user_id=e57161e7-790c-4707-80c0-40a21e8f...0.0 ms238 B
/fire?pixelid=d3ee9fb5-6424-442b-bc17-2a86a9e98fed&type=s...0.0 ms175 B
js-eu1.hs-scripts.com/144960983.js0.0 ms41 B
/tr/?id=1270276017756546&ev=PageView&dl=https%3A%2F%2Fwww...0.0 ms19 B
/fileadmin/ionos-core/Stages/Scroll_Card_Gallery_Containe...0.0 ms0 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:0.41801099999999997] map[node:map[boundingRect:map[bottom:1333 height:823 left:0 right:412 top:510 width:412] lhId:page-2-DIV nodeLabel:Launch a professional website in seconds with AI Start building path:1,HTML,1,BODY,5,DIV,8,DIV,0,DIV,1,DIV,0,DIV,0,DIV selector:div.tw-relative > div.tw-absolute > div > div.stage-highlight-item snippet:<div class="stage-highlight-item tw-relative tw-h-screen tw-w-full" component-type="stage-with-hightlights-slide"> type:node] score:0.417983] map[node:map[boundingRect:map[bottom:1030 height:18 left:159 right:253 top:1012 width:94] lhId:page-1-SPAN nodeLabel:Start building path:1,HTML,1,BODY,5,DIV,8,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,A,0,SPAN selector:div.tw-flex > div.tw-flex > a.whitespace-nowrap > span.tw-relative snippet:<span class="tw-relative tw-z-10"> type:node] score:2.8e-05]]

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:412.282 label:Time to first byte subpart:timeToFirstByte] map[duration:64.979 label:Resource load delay subpart:resourceLoadDelay] map[duration:224.788 label:Resource load duration subpart:resourceLoadDuration] map[duration:1882.411 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: IONOS Logo
path: 1,HTML,1,BODY,5,DIV,8,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div > div.stage-highlight-item > div.tw-flex > img.tw-pb-16
snippet: <img alt="IONOS Logo" loading="eager" width="288" height="85" decoding="async" data-nimg="1" class="tw-pb-16 tw-stage-drop-shadow" style="color:transparent" src="/_next/static/media/ionos.d8a1006d.svg">

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: IONOS Logo
path: 1,HTML,1,BODY,5,DIV,8,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div > div.stage-highlight-item > div.tw-flex > img.tw-pb-16
snippet: <img alt="IONOS Logo" loading="eager" width="288" height="85" decoding="async" data-nimg="1" class="tw-pb-16 tw-stage-drop-shadow" style="color:transparent" src="/_next/static/media/ionos.d8a1006d.svg">

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

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
Woman asking AI for bike shop name ideas, with suggested domain and email addre… div.tw-grid > div.keen-slider__slide > div.tw-relative > img.tw-mb-auto
cs-us.uicdn.net/fileadmin/ionos-core/Content-Card/US/Content-Card-moblie-1.png18.0 KiB7.0 KiB
Woman requesting an AI-generated website for her bike shop with a preview of sp… div.tw-grid > div.keen-slider__slide > div.tw-relative > img.tw-mb-auto
cs-us.uicdn.net/fileadmin/ionos-core/Content-Card/US/Content-Card-moblie.png16.4 KiB5.4 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.com/abtesting-us.js411 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: 1.0 s
URLTime Spent
ionos.com/1.0 s
www.ionos.com/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.

ElementLayout shift score
Launch a professional website in seconds with AI Start building div.tw-relative > div.tw-absolute > div > div.stage-highlight-item
0.418
Start building div.tw-flex > div.tw-flex > a.whitespace-nowrap > span.tw-relative
0.000

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

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: 250 ms 39.7 KiB
URLTransfer SizeEst Savings
www.ionos.com/_next/static/chunks/b94077be48fea7cf.css43.9 KiB39.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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
www.ionos.com/_next/static/chunks/194098810fb2d942.js1.2 s1.1 s15 ms
Unattributable1.0 s50 ms0.0 ms
www.googletagmanager.com/gtag/js?id=AW-10981602831490 ms345 ms127 ms
js-eu1.hs-analytics.net/analytics/1776811200000/144960983.js477 ms400 ms7.3 ms
www.ionos.com/428 ms17 ms2.5 ms
euob.seaskypro.com/sxp/i/ca06d1dce9f2080d34646010859966ac.js403 ms296 ms9.2 ms
www.ionos.com/_next/static/chunks/2b3fea4fe53b0095.js289 ms198 ms7.2 ms
www.googletagmanager.com/gtag/js?id=DC-13183894&cx=c&gtm=4e64h1263 ms236 ms24 ms
www.ionos.com/js/at_visitor.min.js255 ms242 ms12 ms
www.googletagmanager.com/gtag/destination?id=G-64JPJZ4XPG&cx=c&gtm=4e64h1243 ms210 ms32 ms
www.ionos.com/_next/static/chunks/turbopack-25796b008ee7b963.js197 ms195 ms1.2 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMA.js178 ms146 ms32 ms
www.ionos.com/_next/static/chunks/594c979eaaf737c4.js165 ms144 ms0.8 ms
54ft7i.ionos.com/get/live/web/_/48gpcp.js148 ms95 ms43 ms
dkgefcns0l.kameleoon.io/engine.js141 ms121 ms12 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js136 ms117 ms17 ms
connect.facebook.net/en_US/fbevents.js125 ms100 ms24 ms
www.ionos.com/_next/static/chunks/turbopack-090ab602242fbb5e.js105 ms103 ms1.6 ms
cdn.ionos.com/nk/9c2134ba72b4/6c2bd2fdffdc/launch-67fb473cc73f.min.js93 ms58 ms32 ms
www.ionos.com/_next/static/chunks/f145268738cd7807.js84 ms25 ms11 ms
/signals/config/1270276017756546?v=2.9.303&r=stable&domai...78 ms64 ms13 ms
bat.bing.com/p/conversions/s/0.8.5973 ms55 ms3.3 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js70 ms57 ms12 ms
www.ionos.com/_next/static/chunks/fc1da8772043cb37.js67 ms63 ms0.3 ms
var.uicdn.net/shopsshort/privacy/v1/bundle.js66 ms45 ms19 ms
snap.licdn.com/li.lms-analytics/insight.min.js52 ms48 ms3.5 ms
js-eu1.hubspot.com/web-interactives-embed.js51 ms43 ms6.3 ms
www.ionos.com/js/adobeTracking.js50 ms46 ms0.8 ms

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 Evaluation5.0 s
Other1.2 s
Script Parsing & Compilation641 ms
Style & Layout418 ms
Parse HTML & CSS194 ms
Garbage Collection138 ms
Rendering85 ms

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

Optimize DOM size
Font display
Forced reflow
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 20 user timings
Avoid long main-thread tasks 20 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 400 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 120 ms
INP breakdown
Avoid non-composited animations
82

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Language selector nav.tw-relative > div.tw-container > div.tw-absolute > div#language_selector

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tw-py-20 > div.tw-rd-container > form.tw-relative > button.tw-z-1 div.tw-py-20 > div.tw-rd-container > form.tw-relative > button.tw-z-1
div.tw-rounded-lg > div.tw-rd-container > form.tw-relative > button.tw-z-1 div.tw-rounded-lg > div.tw-rd-container > form.tw-relative > button.tw-z-1
section > div.tw-rd-container > div.tw-my-24 > button section > div.tw-rd-container > div.tw-my-24 > button
div.tw-rd-container > div.tw-my-24 > div.tw-flex > button.tw-h-4 div.tw-rd-container > div.tw-my-24 > div.tw-flex > button.tw-h-4
div.tw-rd-container > div.tw-my-24 > div.tw-flex > button.tw-h-4 div.tw-rd-container > div.tw-my-24 > div.tw-flex > button.tw-h-4
div.tw-rd-container > div.tw-my-24 > div.tw-flex > button.tw-h-4 div.tw-rd-container > div.tw-my-24 > div.tw-flex > button.tw-h-4
section > div.tw-rd-container > div.tw-my-24 > button section > div.tw-rd-container > div.tw-my-24 > button

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.

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
OK div.tw-container > div.-tw-mx-24 > div.tw-flex-shrink-0 > button.tw-border-1

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
Open menu div.tw-container > div.tw-inline-flex > div > button.tw-relative
ionos logo nav.tw-relative > div.tw-container > div.tw-inline-flex > a#header-logo
Open language selector div.tw-container > div.tw-absolute > div#language_selector > button.tw-items-top
Call now:+1484-424-7392 div.tw-container > div.tw-absolute > div > a.whitespace-nowrap
Sign in div.tw-absolute > div > div.tw-z-51 > button.tw-text-ellipsis

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
Secure your domain name div.tw-flex > a.tw-min-h-300 > div > h3.tw-block
VPS server & hosting 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.

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
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]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
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
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"]`
Image elements do not have `[alt]` attributes that are redundant text.
`[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
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
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
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.
81

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.

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

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.trustpilot.com/trust/how-reviews-workLearn more
www.ionos.com/cookiesMore Information

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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

75
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
87
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.55 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.86 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

101 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.098

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.47 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.98 s

Detailed Report

Audit breakdown by category with detailed findings.

75

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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
/fileadmin/ionos-core/Stages/Scroll_Card_Gallery_Containe...0.0 ms2.9 MiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
54ft7i.ionos.com/get/live/web/_/48gpcp.js0.0 ms73.9 KiB
var.uicdn.net/shopsshort/privacy/v1/bundle.js900.0 s73.4 KiB
cdn.ionos.com/nk/9c2134ba72b4/6c2bd2fdffdc/launch-67fb473cc73f.min.js900.0 s60.6 KiB
js-eu1.hs-analytics.net/analytics/1776811200000/144960983.js300.0 s42.7 KiB
/signals/config/1270276017756546?v=2.9.303&r=stable&domai...1200.0 s45.2 KiB
js-eu1.hubspot.com/web-interactives-embed.js600.0 s28.4 KiB
dkgefcns0l.kameleoon.io/engine.js14400.0 s37.8 KiB
js-eu1.hs-banner.com/v2/144960983/banner.js300.0 s26.0 KiB
euob.seaskypro.com/sxp/i/ca06d1dce9f2080d34646010859966ac.js43200.0 s44.6 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
/fileadmin/ionos-core/Stages/Scroll_Card_Gallery_Containe...0.0 ms18.6 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.8 KiB
/t/password-indicator/js/password-indicator.js?v=3.2.686400.0 s20.1 KiB
frontend-services.ionos.com/t/tag/IONOS/shop.js1800.0 s9.1 KiB
snap.licdn.com/li.lms-analytics/insight.min.js86400.0 s18.7 KiB
frontend-services.ionos.com/t/t/js/t.js?v=2.2.186400.0 s16.5 KiB
bat.bing.com/p/conversions/s/0.8.5986400.0 s15.6 KiB
static.hotjar.com/c/hotjar-6671439.js?sv=660.0 s6.2 KiB
d34r8q7sht0t9k.cloudfront.net/tag.js0.0 ms5.7 KiB
var.uicdn.net/shopsshort/privacy/v1/bundle.css900.0 s6.4 KiB
var.uicdn.net/shopsshort/performance/bowser-2.11.0-es5.js900.0 s6.3 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
var.uicdn.net/shopsshort/performance/web-vitals-5.0.3.iife.js900.0 s2.7 KiB
var.uicdn.net/shopsshort/performance/tagManagerIntegration.min.js900.0 s1.5 KiB
js-eu1.hs-scripts.com/144960983.js0.0 ms1.0 KiB
/collect?v=2&fmt=js&pid=65326&time=1776814751019&url=http...0.0 ms692 B
/rp.gif?ts=1776814751016&id=a2_guk1juaq5x84&event=PageVis...0.0 ms666 B
/nk/9c2134ba72b4/6c2bd2fdffdc/8b3b79a8015f/RCdefebbc115bc...900.0 s559 B
/t/password-indicator/css/password-indicator.css?v=3.2.686400.0 s1.1 KiB
/tag?action=view&user_id=e57161e7-790c-4707-80c0-40a21e8f...0.0 ms238 B
/fire?pixelid=d3ee9fb5-6424-442b-bc17-2a86a9e98fed&type=s...0.0 ms175 B
js-eu1.hs-scripts.com/144960983.js0.0 ms44 B
/tr/?id=1270276017756546&ev=PageView&dl=https%3A%2F%2Fwww...0.0 ms19 B
/fileadmin/ionos-core/Stages/Scroll_Card_Gallery_Containe...0.0 ms0 B

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.com/abtesting-us.js411 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: 482 ms
URLTime Spent
ionos.com/482 ms
www.ionos.com/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

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.4 s
Other443 ms
Script Parsing & Compilation204 ms
Style & Layout144 ms
Garbage Collection70 ms
Parse HTML & CSS55 ms
Rendering35 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 38.1 KiB
URLTransfer SizeEst Savings
www.ionos.com/_next/static/chunks/b94077be48fea7cf.css43.9 KiB38.1 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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

Max Potential First Input Delay 130 ms
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
Improve image delivery
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 18 user timings
JavaScript execution time 1.2 s
Avoid long main-thread tasks 3 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 15,560 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 130 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
LCP request discovery
Avoid non-composited animations
87

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English div.tw-hidden > div.tw-container > div.tw-flex > div#language_selector

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.

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
OK div.tw-container > div.-tw-mx-24 > div.tw-flex-shrink-0 > button.tw-border-1

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
English div.tw-container > div.tw-flex > div#language_selector > button.tw-items-top
1 484-424-7392 div.tw-container > div.tw-flex > div > a.whitespace-nowrap
About Us 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
Sign In div.tw-flex > div > div.tw-z-51 > button.tw-text-ellipsis
New Momentum AI 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
Email & Office nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_3
Websites nav.tw-relative > div.tw-container > div.tw--mx-12 > button#flyout_main_4
eCommerce 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
Servers 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
Secure your domain name div.tw-flex > a.tw-min-h-300 > div > h3.tw-block
VPS server & hosting 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.

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
English div.tw-container > div.tw-flex > div#language_selector > button.tw-items-top
1 484-424-7392 div.tw-container > div.tw-flex > div > a.whitespace-nowrap
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]`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
Image elements have `[alt]` attributes
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
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"]`
Image elements do not have `[alt]` attributes that are redundant text.
`[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
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
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
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.
77

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.

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
[object Response]
Error handling sales channel: Error at u (https://www.ionos.com/_next/static/chunks/366c2f874b4fbdfb.js:1:4199) at async https://www.ionos.com/_next/static/chunks/366c2f874b4fbdfb.js:1:7125
Failed to load resource: the server responded with a status of 502 ()
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
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

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.trustpilot.com/trust/how-reviews-workLearn more
www.ionos.com/cookiesMore Information

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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback