Skip to content
Audit Complete

Results for https://ardmediathek.de

Visit site
DE · EUR (€) · Estimated Applicable regulations: DSGVO · ePrivacy Directive · EAA Dev cost: €90/hr How jurisdiction is detected
United Stated United Stated · New York Completed: Apr 21, 2026 22:07 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)
C74

Site Health

Score: 74 / 100

Based on 6 categories, 44 sections

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

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.

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

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

How the composite score is calculated

How you compare

core-js · 1488 peers
You 74
·
Avg 72
At average
0 50 100
Better than 65% of core-js sites See full core-js benchmark →
Facebook · 1367 peers
You 74
·
Avg 72
At average
0 50 100
Better than 60% of Facebook sites See full Facebook benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

HSTS 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

10 button(s) with no accessible text

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

Accessibility › Link & Button Quality
5

17 image(s) missing alt attribute

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

Accessibility › Alt Text 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%2Fardmediathek.de)](https://beavercheck.com/results/a859e08e-11ea-403f-b5e1-2ab4e35cdf59)
<a href="https://beavercheck.com/results/a859e08e-11ea-403f-b5e1-2ab4e35cdf59"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fardmediathek.de" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fardmediathek.de

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. 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.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

1 critical 6 warning

7 barrier(s) likely increasing bounce by ~17%.

Speed (1)

Page feels frozen for 869ms

+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

Content (1)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (3)

5 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

1 broken link(s) on the page

+2% 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

€405 investment → €0.00/month returns + EUR 20,500,000 risk avoided

First-year ROI: -100%

Investment

€405

4h · 5 findings

Monthly returns

€0.00 /mo

~€0.00 / year

    Regulatory risk avoided

    EUR 20,500,000

    if kept compliant

    • DSGVO EUR 20,000,000
    • EAA EUR 500,000

    €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

    €405

    4.5 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

    €1,708,333 / month at risk

    ~€20,500,000 / year if left unfixed

    Compliance Risk

    €20,500,000

    DSGVOEAA
    • No privacy policy link detected
      DSGVO: EUR 10,000 – EUR 20,000,000
    • Privacy Policy not detected
      DSGVO: EUR 10,000 – EUR 20,000,000
    • 10 of 14 <nav> elements are unlabeled
      EAA: EUR 1,000 – EUR 500,000

    +3 more

    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.

    75
    Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
    91
    Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
    92
    Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
    100
    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.

    2.25 s

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

    2.25 s

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

    869 ms

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

    0.010

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

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

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

    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:30.061 source:map[column:13780 line:2 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.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.14 source:map[column:41385 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]] map[reflowTime:18.155 source:map[column:86674 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]] map[reflowTime:1.766 source:map[column:93273 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]] map[reflowTime:1.085 source:map[column:41811 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]] map[reflowTime:3.14 source:map[column:458462 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]] map[reflowTime:5.486 source:map[column:6357 line:0 type:source-location url:https://www.ardmediathek.de/19394.1773910146334.js urlProvider:network]] map[reflowTime:0.311 source:map[column:2712 line:0 type:source-location url:https://www.ardmediathek.de/19394.1773910146334.js urlProvider:network]] map[reflowTime:0.786 source:map[column:124356 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]]]

    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: JD Vance steht vor dem Weißen Haus und blickt applaudierend in die Kamera, hint…
    path: 1,HTML,1,BODY,0,DIV,0,DIV,1,DIV,3,MAIN,0,DIV,1,DIV,0,SECTION,1,DIV,0,DIV,0,DIV,0,DIV,1,A,0,DIV,0,IMG
    selector: div#1FdQ5oz2JK6o2qmyqMsqiI:7799462537932006265 > a.b1rq2tr > div.bt3d8jq > img.swiper-lazy
    snippet: <img srcset="/img?imwidth=320&amp;url=https%3A%2F%2Fapi.ardmediathek.de%2Fimage-service%2Fi…" alt="JD Vance steht vor dem Weißen Haus und blickt applaudierend in die Kamera,…" class="swiper-lazy swiper-lazy-loaded" data-srcset="/img?imwidth=320&amp;url=https%3A%2F%2Fapi.ardmediathek.de%2Fimage-service%2Fi…" sizes="">

    Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

    Why this matters

    Performance issues directly impact user engagement and conversion rates.

    description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
    title: Preconnected origins
    description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
    title: Preconnect candidates
    value: No additional origins are good candidates for preconnecting

    Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

    Why this matters

    Performance issues directly impact user engagement and conversion rates.

    URLTransfer SizeDuration
    www.ardmediathek.de/swiper-bundle.1773910146334.css4.4 KiB150 ms

    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
    Wehrdienst reloaded · Schöne, neue Bundeswehr? div#1FdQ5oz2JK6o2qmyqMsqiI:-9048697480131219761 > a.b1rq2tr > div.bt3d8jq > img.swiper-lazy
    /img?imwidth=768&url=https%3A%2F%2Fapi.ardmediathek.de%2F...154.0 KiB69.4 KiB
    a.b1e83sjn > div.bxyitdw > div.bt3d8jq > img a.b1e83sjn > div.bxyitdw > div.bt3d8jq > img
    /img?imwidth=272&url=https%3A%2F%2Fapi.ardmediathek.de%2F...11.2 KiB4.4 KiB

    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: 751 ms
    URLTime Spent
    ardmediathek.de/751 ms
    www.ardmediathek.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 reduce Javascript execution time.

    Why this matters

    Performance issues directly impact user engagement and conversion rates.

    URLTotal CPU TimeScript EvaluationScript Parse
    www.ardmediathek.de/clientApp.1773910146334.js2.4 s1.7 s86 ms
    Unattributable542 ms8.4 ms0.0 ms
    www.ardmediathek.de/460 ms6.4 ms0.6 ms
    www.ardmediathek.de/35449.1773910146334.js278 ms208 ms62 ms
    www.ardmediathek.de/72837.1773910146334.js56 ms53 ms2.3 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 Evaluation2.0 s
    Other893 ms
    Style & Layout427 ms
    Script Parsing & Compilation171 ms
    Rendering148 ms
    Garbage Collection100 ms
    Parse HTML & CSS67 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 28.0 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

    Estimated savings: 0.0 ms 217.1 KiB
    URLTransfer SizeEst Savings
    www.ardmediathek.de/35449.1773910146334.js147.0 KiB124.8 KiB
    www.ardmediathek.de/clientApp.1773910146334.js225.3 KiB92.4 KiB

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

    Use efficient cache lifetimes
    Layout shift culprits
    Optimize DOM size
    Font display
    LCP breakdown
    Modern HTTP
    Optimize viewport for mobile
    Minify CSS
    Minify JavaScript
    Avoids enormous network payloads Total size was 1,306 KiB
    Avoid long main-thread tasks 11 long tasks found
    Image elements have explicit `width` and `height`
    Page didn't prevent back/forward cache restoration
    Network Requests
    Network Round Trip Times 80 ms
    Server Backend Latencies 90 ms
    Tasks
    Diagnostics
    Metrics
    Screenshot Thumbnails
    Final Screenshot
    Script Treemap Data
    Resources Summary
    Initial server response time was short Root document took 80 ms
    Avoid large layout shifts 1 layout shift found
    INP breakdown
    User Timing marks and measures
    Avoid non-composited animations
    91

    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.

    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.bb65sj8 > div.b1y4zfs4 > div.by2mhcu > button.b1jqo9hg div.bb65sj8 > div.b1y4zfs4 > div.by2mhcu > button.b1jqo9hg
    div.bb65sj8 > div.b1y4zfs4 > div.by2mhcu > button.b1jqo9hg div.bb65sj8 > div.b1y4zfs4 > div.by2mhcu > button.b1jqo9hg

    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#swiper-wrapper-c5d3254a12b42a610 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:7733698639301175988 > a.b1rq2tr div#swiper-wrapper-c5d3254a12b42a610 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:7733698639301175988 > a.b1rq2tr
    div#swiper-wrapper-c5d3254a12b42a610 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:988450483882220657 > a.b1rq2tr div#swiper-wrapper-c5d3254a12b42a610 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:988450483882220657 > a.b1rq2tr
    div#swiper-wrapper-c5d3254a12b42a610 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:-8184481788118226989 > a.b1rq2tr div#swiper-wrapper-c5d3254a12b42a610 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:-8184481788118226989 > a.b1rq2tr
    div#swiper-wrapper-c5d3254a12b42a610 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:8711206178581805189 > a.b1rq2tr div#swiper-wrapper-c5d3254a12b42a610 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:8711206178581805189 > a.b1rq2tr
    div#swiper-wrapper-c5d3254a12b42a610 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:-8055258610461268649 > a.b1rq2tr div#swiper-wrapper-c5d3254a12b42a610 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:-8055258610461268649 > a.b1rq2tr

    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.

    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
    Image elements have `[alt]` attributes
    `[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
    ARIA attributes are used as specified for the element's role
    Elements use only permitted ARIA attributes
    Background and foreground colors have a sufficient contrast ratio
    Document has a `<title>` element
    `<html>` element has a `[lang]` attribute
    `<html>` element has a valid value for its `[lang]` attribute
    Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
    List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
    No element has a `[tabindex]` value greater than 0
    Touch targets have sufficient size and spacing.
    Heading elements appear in a sequentially-descending order
    Document has a main landmark.
    Deprecated ARIA roles were not used
    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-hidden="true"]` elements do not contain focusable descendents
    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
    ARIA IDs are unique
    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
    Form elements have associated labels
    Links are distinguishable without relying on color.
    The document does not use `<meta http-equiv="refresh">`
    `<object>` elements have alternate text
    Select elements have associated label elements.
    Skip links are focusable.
    Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
    `<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
    `[lang]` attributes have a valid value
    `<video>` elements contain a `<track>` element with `[kind="captions"]`
    Tables have different content in the summary attribute and `<caption>`.
    All heading elements contain content.
    Uses ARIA roles only on compatible elements
    Image elements do not have `[alt]` attributes that are redundant text.
    Elements with visible text labels have matching accessible names.
    Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
    `<td>` elements in a large `<table>` have one or more table headers.
    92

    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
    Loading the script 'https://apis.google.com/js/api.js?onload=__iframefcb746795' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' *.nmrodam.com *.imrworldwide.com *.sensic.net *.gstatic.com". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.

    Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

    Why this matters

    Performance issues directly impact user engagement and conversion rates.

    Issue type
    Content security policy

    Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

    Why this matters

    Performance issues directly impact user engagement and conversion rates.

    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
    Ensure CSP is effective against XSS attacks
    Use a strong HSTS policy
    Mitigate DOM-based XSS with Trusted Types
    Detected JavaScript libraries
    Redirects HTTP traffic to HTTPS
    Ensure proper origin isolation with COOP
    Mitigate clickjacking with XFO or CSP
    100

    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.

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

    97
    Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
    97
    Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
    100
    Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
    100
    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.

    987 ms

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

    987 ms

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

    63 ms

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

    0.017

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

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

    2.14 s

    Detailed Report

    Audit breakdown by category with detailed findings.

    97

    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.

    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:28.496 source:map[column:13780 line:2 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.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:4.237 source:map[column:41385 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]] map[reflowTime:13.697 source:map[column:86674 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]] map[reflowTime:2.141 source:map[column:93273 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]] map[reflowTime:1.459 source:map[column:41811 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]] map[reflowTime:5.373 source:map[column:458462 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]] map[reflowTime:4.062 source:map[column:6357 line:0 type:source-location url:https://www.ardmediathek.de/19394.1773910146334.js urlProvider:network]] map[reflowTime:0.328 source:map[column:2712 line:0 type:source-location url:https://www.ardmediathek.de/19394.1773910146334.js urlProvider:network]] map[reflowTime:2.345 source:map[column:124356 line:1 type:source-location url:https://www.ardmediathek.de/clientApp.1773910146334.js urlProvider:network]]]

    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: JD Vance steht vor dem Weißen Haus und blickt applaudierend in die Kamera, hint…
    path: 1,HTML,1,BODY,0,DIV,0,DIV,1,DIV,3,MAIN,0,DIV,1,DIV,0,SECTION,1,DIV,0,DIV,0,DIV,0,DIV,1,A,0,DIV,0,IMG
    selector: div#1FdQ5oz2JK6o2qmyqMsqiI:7799462537932006265 > a.b1rq2tr > div.bt3d8jq > img.swiper-lazy
    snippet: <img srcset="/img?imwidth=320&amp;url=https%3A%2F%2Fapi.ardmediathek.de%2Fimage-service%2Fi…" alt="JD Vance steht vor dem Weißen Haus und blickt applaudierend in die Kamera,…" class="swiper-lazy swiper-lazy-loaded" data-srcset="/img?imwidth=320&amp;url=https%3A%2F%2Fapi.ardmediathek.de%2Fimage-service%2Fi…" sizes="">

    Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

    Why this matters

    Performance issues directly impact user engagement and conversion rates.

    description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
    title: Preconnected origins
    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

    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
    Wehrdienst reloaded · Schöne, neue Bundeswehr? div#1FdQ5oz2JK6o2qmyqMsqiI:-9048697480131219761 > a.b1rq2tr > div.bt3d8jq > img.swiper-lazy
    /img?imwidth=1440&url=https%3A%2F%2Fapi.ardmediathek.de%2...240.6 KiB110.9 KiB
    a.b1e83sjn > div.bxyitdw > div.bt3d8jq > img a.b1e83sjn > div.bxyitdw > div.bt3d8jq > img
    /img?imwidth=272&url=https%3A%2F%2Fapi.ardmediathek.de%2F...11.4 KiB4.7 KiB
    Jonah Mulray steht in der Metropole Hongkong und versucht herauszufinden, warum… a.b1e83sjn > div.bxyitdw > div.bt3d8jq > img
    /img?imwidth=272&url=https%3A%2F%2Fapi.ardmediathek.de%2F...11.4 KiB4.6 KiB
    a.b1e83sjn > div.bxyitdw > div.bt3d8jq > img a.b1e83sjn > div.bxyitdw > div.bt3d8jq > img
    /img?imwidth=272&url=https%3A%2F%2Fapi.ardmediathek.de%2F...10.9 KiB4.1 KiB
    Der Psycho-Coach - Mörderische Therapie: v.l.n.r: Keane (John Magaro), Kollmick… a.b1e83sjn > div.bxyitdw > div.bt3d8jq > img
    /img?imwidth=272&url=https%3A%2F%2Fapi.ardmediathek.de%2F...20.1 KiB4.0 KiB
    Margaret Schlegel sitzt nachdenklich im Gras vor dem Landhaus Howards End. Die … a.b1e83sjn > div.bxyitdw > div.bt3d8jq > img
    /img?imwidth=272&url=https%3A%2F%2Fapi.ardmediathek.de%2F...10.8 KiB4.0 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.

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

    Diagnostics

    Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

    Why this matters

    Performance issues directly impact user engagement and conversion rates.

    Estimated savings: 0.0 ms 28.2 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

    Estimated savings: 0.0 ms 218.8 KiB
    URLTransfer SizeEst Savings
    www.ardmediathek.de/35449.1773910146334.js147.0 KiB125.3 KiB
    www.ardmediathek.de/clientApp.1773910146334.js225.3 KiB93.5 KiB

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

    Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

    Why this matters

    Performance issues directly impact user engagement and conversion rates.

    Estimated savings: 200 ms
    URLTime Spent
    ardmediathek.de/200 ms
    www.ardmediathek.de/0.0 ms
    Max Potential First Input Delay 120 ms
    Time to Interactive 2.1 s
    Use efficient cache lifetimes
    Layout shift culprits
    Optimize DOM size
    Font display
    LCP breakdown
    Modern HTTP
    Optimize viewport for mobile
    Minify CSS
    Minify JavaScript
    Avoids enormous network payloads Total size was 1,562 KiB
    JavaScript execution time 0.5 s
    Minimizes main-thread work 1.0 s
    Avoid long main-thread tasks 5 long tasks found
    Image elements have explicit `width` and `height`
    Page didn't prevent back/forward cache restoration
    Network Requests
    Network Round Trip Times 80 ms
    Server Backend Latencies 130 ms
    Tasks
    Diagnostics
    Metrics
    Screenshot Thumbnails
    Final Screenshot
    Script Treemap Data
    Resources Summary
    Initial server response time was short Root document took 80 ms
    Avoid large layout shifts 2 layout shifts found
    INP breakdown
    User Timing marks and measures
    Avoid non-composited animations
    97

    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.

    Names and labels

    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#swiper-wrapper-a9f4695898e209e6 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:7733698639301175988 > a.b1rq2tr div#swiper-wrapper-a9f4695898e209e6 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:7733698639301175988 > a.b1rq2tr
    div#swiper-wrapper-a9f4695898e209e6 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:988450483882220657 > a.b1rq2tr div#swiper-wrapper-a9f4695898e209e6 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:988450483882220657 > a.b1rq2tr
    div#swiper-wrapper-a9f4695898e209e6 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:-8184481788118226989 > a.b1rq2tr div#swiper-wrapper-a9f4695898e209e6 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:-8184481788118226989 > a.b1rq2tr
    div#swiper-wrapper-a9f4695898e209e6 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:8711206178581805189 > a.b1rq2tr div#swiper-wrapper-a9f4695898e209e6 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:8711206178581805189 > a.b1rq2tr
    div#swiper-wrapper-a9f4695898e209e6 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:-8055258610461268649 > a.b1rq2tr div#swiper-wrapper-a9f4695898e209e6 > div.swiper-slide > div#1FdQ5oz2JK6o2qmyqMsqiI:-8055258610461268649 > a.b1rq2tr

    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.

    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
    Image elements have `[alt]` attributes
    `[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
    `button`, `link`, and `menuitem` elements have accessible names
    ARIA attributes are used as specified for the element's role
    Elements use only permitted ARIA attributes
    Background and foreground colors have a sufficient contrast ratio
    Document has a `<title>` element
    `<html>` element has a `[lang]` attribute
    `<html>` element has a valid value for its `[lang]` attribute
    Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
    List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
    No element has a `[tabindex]` value greater than 0
    Touch targets have sufficient size and spacing.
    Heading elements appear in a sequentially-descending order
    Document has a main landmark.
    Deprecated ARIA roles were not used
    Identical links have the same purpose.
    Elements with visible text labels have matching accessible names.
    `[accesskey]` values are unique
    Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
    `[aria-hidden="true"]` elements do not contain focusable descendents
    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
    ARIA IDs are unique
    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
    Form elements have associated labels
    Links are distinguishable without relying on color.
    The document does not use `<meta http-equiv="refresh">`
    `<object>` elements have alternate text
    Select elements have associated label elements.
    Skip links are focusable.
    Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
    `<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
    `[lang]` attributes have a valid value
    `<video>` elements contain a `<track>` element with `[kind="captions"]`
    Tables have different content in the summary attribute and `<caption>`.
    All heading elements contain content.
    Uses ARIA roles only on compatible elements
    Image elements do not have `[alt]` attributes that are redundant text.
    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

    General

    Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

    Why this matters

    Performance issues directly impact user engagement and conversion rates.

    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
    Mitigate DOM-based XSS with Trusted Types
    Detected JavaScript libraries
    Redirects HTTP traffic to HTTPS
    Ensure proper origin isolation with COOP
    Mitigate clickjacking with XFO or CSP
    100

    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.

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

    Send Feedback