C — https://heise.de | BeaverCheck Audit

Site Health

Score: 76 / 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.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Lean and efficient — low environmental impact per visit.

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

CMS sites average 73

At average

Better than 65% of CMS sites

Apple sites average 73

At average

Better than 70% of Apple sites See full Apple benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

1 control(s) without accessible label

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

Accessibility › Form Accessibility

13 link(s) with no accessible text

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

Accessibility › Link & Button Quality

151 image-only link(s) without alt 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

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fheise.de)](https://beavercheck.com/results/8a9f5274-8cb1-4231-9092-d7a91764683b)

HTML

<a href="https://beavercheck.com/results/8a9f5274-8cb1-4231-9092-d7a91764683b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fheise.de" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fheise.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. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.

3 accessibility issues exclude users who rely on assistive technology.

Return on Investment

€495 investment → €5,480/month returns + EUR 120,500,000 risk avoided

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

Investment

€495

6h · 5 findings

Monthly returns

€5,480 /mo

~€65,759 / year

Conversions recovered €5,480
Bandwidth savings €0.19

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

€90 — 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

€495

5.5 developer hours at €90/hr

Based on Germany rates (€90/hr)

Quick wins

€90 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,002 / 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

+12 more

Bandwidth Waste

€0.19 /mo

2603.6 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~260 KB per page load
Saves €0.19/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

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

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

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

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.

4.34 s

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

8.90 s

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

1.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.000

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

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

9.19 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

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.

Request	Cache TTL	Transfer Size
www.heise.de/assets/akwa/v24/js/akwa.js	120.0 s	85.6 KiB
cmp.heise.de/Notice.8f529.js	3600.0 s	91.2 KiB
www.heise.de/assets/fonts/v1/source-sans-variable/ss3vf.woff2	120.0 s	53.8 KiB
cdn.mateti.net/mcp/onsite.min.js	300.0 s	35.2 KiB
cmp.heise.de/unified/wrapperMessagingWithoutDetection.js	3600.0 s	42.0 KiB
www.heise.de/assets/styles/index.css	120.0 s	23.5 KiB
xn2wkedljxxol.heise.de/files/site_script/heise.de.js	3600.0 s	19.9 KiB
www.heise.de/assets/akwa/v24/css/akwa.css	120.0 s	11.1 KiB
cmp.heise.de/Notice.30929.css	3600.0 s	6.7 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...	2020313.0 s	26.8 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...	2542270.0 s	22.3 KiB
cmp.heise.de/polyfills.01516.js	3600.0 s	2.3 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...	1950953.0 s	14.6 KiB
www.heise.de/icons/ho/h96-logo.svg	7200.0 s	1.5 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Desktop_...	2562016.0 s	11.8 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Desktop_...	1431276.0 s	10.3 KiB
/v7/_www-heise-de_/imgs/18/4/8/1/5/2/6/8/Podcast_Desktop_...	2557433.0 s	9.2 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...	2380298.0 s	7.8 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Mobil_ba...	2559532.0 s	7.6 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Mobil_ba...	2380297.0 s	6.1 KiB
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Desktop_...	2543933.0 s	5.6 KiB
/v7/_www-heise-de_/imgs/18/4/8/1/5/2/6/8/Podcast_Mobil_ba...	2509874.0 s	5.3 KiB
/v7/_www-heise-de_/imgs/18/4/8/1/5/2/6/8/Podcast_Mobil_ba...	2020312.0 s	4.6 KiB
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Desktop_...	2543932.0 s	4.5 KiB
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Mobil_ba...	663935.0 s	3.2 KiB
www.heise.de/icons/svg/icons/svg/comments_outline_grey_light.svg	7200.0 s	388 B
www.heise.de/icons/svg/icons/svg/comments_outline_grey_dark.svg	7200.0 s	386 B
www.heise.de/icons/svg/icons/svg/video_outline_grey_light.svg	7200.0 s	376 B
www.heise.de/icons/svg/icons/svg/video_outline_grey_dark.svg	7200.0 s	376 B
www.heise.de/icons/svg/logos/svg/heise_plus_blue_negativ.svg	7200.0 s	364 B
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Mobil_ba...	2543932.0 s	2.8 KiB
www.heise.de/assets/fonts/v1/source-sans-variable/ss3vf.woff2	120.0 s	274 B
www.heise.de/icons/svg/logos/svg/heise_plus_blue.svg	7200.0 s	327 B
www.heise.de/icons/svg/icons/svg/arrow-right-grey-dark.svg	7200.0 s	297 B
www.heise.de/icons/svg/icons/svg/arrow-right-grey-light.svg	7200.0 s	294 B

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:26.34 source:map[column:30147 line:0 type:source-location url:https://cmp.heise.de/unified/wrapperMessagingWithoutDetection.js urlProvider:network]] map[reflowTime:43.809 source:map[column:30753 line:0 type:source-location url:https://cmp.heise.de/unified/wrapperMessagingWithoutDetection.js urlProvider:network]]]

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:935.05 label:Time to first byte subpart:timeToFirstByte] map[duration:1242.428 label:Resource load delay subpart:resourceLoadDelay] map[duration:859.993 label:Resource load duration subpart:resourceLoadDuration] map[duration:25.489 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: Ein IBM-Mainframe in einem Rechenzentrum

path: 1,HTML,1,BODY,7,DIV,1,DIV,0,DIV,0,DIV,0,SECTION,0,ARTICLE,0,A,0,FIGURE,0,A-IMG,0,IMG

selector: a.group/teaser > figure.mb-4 > a-img > img

snippet: <img src="https://heise.cloudimg.io/v7/_www-heise-de_/imgs/18/5/0/6/4/3/2/4/IBM_z17-…" width="1442" height="811" alt="Ein IBM-Mainframe in einem Rechenzentrum" style="aspect-ratio:1442 / 811;object-fit:cover">

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: Ein IBM-Mainframe in einem Rechenzentrum

path: 1,HTML,1,BODY,7,DIV,1,DIV,0,DIV,0,DIV,0,SECTION,0,ARTICLE,0,A,0,FIGURE,0,A-IMG,0,IMG

selector: a.group/teaser > figure.mb-4 > a-img > img

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.heise.de/assets/akwa/v24/css/akwa.css	11.1 KiB	302 ms

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.2 s

URL	Time Spent
heise.de/	1.2 s
www.heise.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

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: 330 ms 15.2 KiB

URL	Transfer Size	Est Savings
www.heise.de/assets/styles/index.css	23.4 KiB	15.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: 600 ms 132.5 KiB

URL	Transfer Size	Est Savings
cmp.heise.de/Notice.8f529.js	90.9 KiB	62.9 KiB
www.heise.de/assets/akwa/v24/js/akwa.js	85.4 KiB	47.4 KiB
/resp/api/get/288689636920174?url=https%3A%2F%2Fwww.heise...	46.4 KiB	22.3 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.heise.de/	1.2 s	72 ms	5.3 ms
cmp.heise.de/Notice.8f529.js	953 ms	698 ms	50 ms
www.heise.de/assets/akwa/v24/js/akwa.js	757 ms	478 ms	39 ms
Unattributable	738 ms	42 ms	0.0 ms
cmp.heise.de/unified/wrapperMessagingWithoutDetection.js	553 ms	183 ms	18 ms
/resp/api/get/288689636920174?url=https%3A%2F%2Fwww.heise...	485 ms	409 ms	25 ms
cdn.mateti.net/mcp/onsite.min.js	176 ms	157 ms	14 ms
xn2wkedljxxol.heise.de/files/site_script/heise.de.js	122 ms	104 ms	8.1 ms
cmp.heise.de/unified/4.40.1/gdpr-tcf.27718c8cb9d29947d2c1.bundle.js	77 ms	55 ms	22 ms
/index.html?hasCsp=true&message_id=1454968&consentUUID=nu...	72 ms	0.6 ms	1.6 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.

Category	Time Spent
Script Evaluation	2.2 s
Style & Layout	1.2 s
Other	953 ms
Parse HTML & CSS	354 ms
Rendering	245 ms
Script Parsing & Compilation	186 ms
Garbage Collection	86 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
heise Plus `div.flex > a.relative > span.md:hidden > img.align-middle`	www.heise.de/icons/svg/logos/svg/heise_plus_blue.svg

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 848 KiB

●User Timing marks and measures 3 user timings

●Avoid long main-thread tasks 15 long tasks found

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 160 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

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.jd-module > div.md:flex > form.mb-4 > button.inline-block `div.jd-module > div.md:flex > form.mb-4 > button.inline-block`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a > figure > a-img > img `a > figure > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a > figure.md:hidden > a-img > img `a > figure.md:hidden > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`

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.jd-module > section.grid > article.ho-text > a.group/teaser `div.jd-module > section.grid > article.ho-text > a.group/teaser`
section.grid > div.us_ad > div.pt-8 > a `section.grid > div.us_ad > div.pt-8 > a`
div > div.jd-module > div.mb-6 > a.md:col-start-2 `div > div.jd-module > div.mb-6 > a.md:col-start-2`
div.flex-1 > div.relative > div.pt-8 > a `div.flex-1 > div.relative > div.pt-8 > a`
article.md:col-span-2 > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser `article.md:col-span-2 > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser`
article.ho-text > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser `article.ho-text > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser`
article.ho-text > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser `article.ho-text > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser`
div.shadow-modules > footer > div.mb-6 > a `div.shadow-modules > footer > div.mb-6 > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
Jetzt entdecken! `div#wtma_teaser_ho_vertrieb_pos1 > div.grid-cols-2 > div.md:mx-8 > a.inline-block`
Ausführliche Informationen zum Versandverfahren und zu Ihren Widerrufsmöglichke… `div.jd-module > div.theme-ho > div > p#input-email-help`
Datenschutzerklärung `div.theme-ho > div > p#input-email-help > a.underline`
Jetzt entdecken! `div#wtma_teaser_ho_vertrieb_pos2 > div.grid-cols-2 > div.md:mx-8 > a.inline-block`
Warum die Gehälter auf dem IT-Arbeitsmarkt stagnieren `header > h3.flex > span.text-lg > span`
15 `a.group/teaser > div.-translate-y-1.5 > footer.ho-text-muted > span.flex`
iX Magazin `div.-translate-y-1.5 > footer.ho-text-muted > div.flex > span.flex`
Classroom entdecken `div#wtma_teaser_ho_vertrieb_pos3 > div.grid-cols-2 > div.md:mx-8 > a.inline-block`
Classroom entdecken `div#wtma_teaser_ho_vertrieb_pos4 > div.grid-cols-2 > div.md:mx-8 > a.inline-block`
Hier bestellen `div.container > div.relative > a.inline-block > span`

These are opportunities to improve the legibility of your content.

○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]` values are valid

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

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

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

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

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

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

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●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

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

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

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.

Source	Description
www.heise.de/ line 9, col 7	`TypeError: Cannot read properties of null (reading 'consent') at https://www.heise.de/:10:8`

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a > figure > a-img > img `a > figure > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a > figure.md:hidden > a-img > img `a > figure.md:hidden > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

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.

2.34 s

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

2.85 s

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

14 ms

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

0.006

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

2.61 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.90 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 ▾

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:14.852 source:map[column:30147 line:0 type:source-location url:https://cmp.heise.de/unified/wrapperMessagingWithoutDetection.js urlProvider:network]] map[reflowTime:21.899 source:map[column:30753 line:0 type:source-location url:https://cmp.heise.de/unified/wrapperMessagingWithoutDetection.js urlProvider:network]] map[reflowTime:145.085 source:map[type:text value:[unattributed]]]]

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: Ein IBM-Mainframe in einem Rechenzentrum

path: 1,HTML,1,BODY,6,DIV,1,DIV,0,DIV,0,DIV,0,SECTION,0,ARTICLE,0,A,0,FIGURE,0,A-IMG,0,IMG

selector: a.group/teaser > figure.mb-4 > a-img > img

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.

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

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
www.heise.de/assets/akwa/v24/js/akwa.js	120.0 s	85.6 KiB
cmp.heise.de/Notice.8f529.js	3600.0 s	91.2 KiB
www.heise.de/assets/fonts/v1/source-sans-variable/ss3vf.woff2	120.0 s	53.8 KiB
cdn.mateti.net/mcp/onsite.min.js	300.0 s	35.2 KiB
cmp.heise.de/unified/wrapperMessagingWithoutDetection.js	3600.0 s	42.0 KiB
www.heise.de/assets/styles/index.css	120.0 s	23.5 KiB
xn2wkedljxxol.heise.de/files/site_script/heise.de.js	3600.0 s	19.9 KiB
www.heise.de/assets/akwa/v24/css/akwa.css	120.0 s	11.1 KiB
cmp.heise.de/Notice.30929.css	3600.0 s	6.7 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...	2020285.0 s	26.8 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...	2542242.0 s	22.3 KiB
cmp.heise.de/polyfills.01516.js	3600.0 s	2.3 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...	1950925.0 s	14.6 KiB
www.heise.de/icons/ho/h96-logo.svg	7200.0 s	1.5 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Desktop_...	2561988.0 s	11.8 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Desktop_...	1431248.0 s	10.3 KiB
/v7/_www-heise-de_/imgs/18/4/8/1/5/2/6/8/Podcast_Desktop_...	2557405.0 s	9.1 KiB
/v7/_www-heise-de_/imgs/18/5/0/6/4/3/2/4/IBM_z17-ed0e484f...	2565207.0 s	8.9 KiB
/v7/_www-heise-de_/imgs/18/4/8/1/5/2/6/8/Podcast_Desktop_...	2591972.0 s	8.3 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...	2380270.0 s	7.8 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Mobil_ba...	2559504.0 s	7.5 KiB
/v7/_www-heise-de_/imgs/18/5/0/6/3/6/7/2/734b06d0a4860535...	2537547.0 s	6.7 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Mobil_ba...	2380269.0 s	6.1 KiB
/v7/_www-heise-de_/imgs/18/5/0/6/3/7/8/6/shutterstock_139...	2533404.0 s	5.9 KiB
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Desktop_...	2543905.0 s	5.6 KiB
/v7/_www-heise-de_/imgs/18/4/8/1/5/2/6/8/Podcast_Mobil_ba...	2509846.0 s	5.3 KiB
/v7/_www-heise-de_/imgs/18/5/0/6/4/3/5/3/Waveshare-a9ae22...	2565207.0 s	4.7 KiB
/v7/_www-heise-de_/imgs/18/4/8/1/5/2/6/8/Podcast_Mobil_ba...	2020284.0 s	4.6 KiB
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Desktop_...	2543904.0 s	4.5 KiB
/v7/_www-heise-de_/imgs/18/5/0/4/5/5/2/7/guteappsauseurop...	2437156.0 s	4.3 KiB
/v7/_www-heise-de_/imgs/18/5/0/5/7/0/9/6/ChatGPT_Image_2-...	1888496.0 s	3.4 KiB
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Mobil_ba...	663907.0 s	3.2 KiB
/v7/_www-heise-de_/imgs/18/5/0/6/4/3/5/7/md4TsqPA-7074805...	2565208.0 s	3.1 KiB
/v7/_www-heise-de_/imgs/18/4/9/9/5/0/3/6/https___xp-22025...	2125686.0 s	3.0 KiB
www.heise.de/icons/svg/icons/svg/comments_outline_grey_light.svg	7200.0 s	388 B
www.heise.de/icons/svg/icons/svg/comments_outline_grey_dark.svg	7200.0 s	386 B
www.heise.de/icons/svg/icons/svg/video_outline_grey_light.svg	7200.0 s	376 B
www.heise.de/icons/svg/icons/svg/video_outline_grey_dark.svg	7200.0 s	376 B
/v7/_www-heise-de_/imgs/18/5/0/3/8/1/0/7/ChatGPT_Image_9-...	2105448.0 s	2.8 KiB
www.heise.de/icons/svg/logos/svg/heise_plus_blue_negativ.svg	7200.0 s	364 B
www.heise.de/assets/fonts/v1/source-sans-variable/ss3vf.woff2	120.0 s	274 B
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Mobil_ba...	2543904.0 s	2.8 KiB
www.heise.de/icons/svg/logos/svg/heise_plus_blue.svg	7200.0 s	327 B
www.heise.de/icons/svg/icons/svg/arrow-right-grey-dark.svg	7200.0 s	297 B
www.heise.de/icons/svg/icons/svg/arrow-right-grey-light.svg	7200.0 s	294 B
/v7/_www-heise-de_/imgs/18/5/0/6/0/3/0/1/aufmacher-capaci...	2432538.0 s	1.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.

URL	Transfer Size
www.heise.de/assets/akwa/v24/css/akwa.css	11.1 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: 655 ms

URL	Time Spent
heise.de/	655 ms
www.heise.de/	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

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 ▾

Source: Google web.dev / Lighthouse

Estimated savings: 40 ms 132.3 KiB

URL	Transfer Size	Est Savings
cmp.heise.de/Notice.8f529.js	90.9 KiB	62.8 KiB
www.heise.de/assets/akwa/v24/js/akwa.js	85.4 KiB	47.2 KiB
/resp/api/get/288689636920174?url=https%3A%2F%2Fwww.heise...	46.4 KiB	22.3 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

URL	Transfer Size	Est Savings
www.heise.de/assets/styles/index.css	23.4 KiB	13.5 KiB

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 868 KiB

●User Timing marks and measures 3 user timings

●JavaScript execution time 0.5 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 4 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 170 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

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.jd-module > section > a-scroll-container.ho-scroll-container-teaser-list > button.scroll-right `div.jd-module > section > a-scroll-container.ho-scroll-container-teaser-list > button.scroll-right`
div > div.jd-module > a-scroll-container.mb-8 > button.scroll-right `div > div.jd-module > a-scroll-container.mb-8 > button.scroll-right`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a > figure > a-img > img `a > figure > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a > figure.hidden > a-img > img `a > figure.hidden > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Alle Kategorien Hardware Software Games Video/Foto/TV Telefon & Co Audio/HiFi D… `div.md:flex > form.mb-4 > div.relative > select.focus:shadow-outline`

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.jd-module > section.grid > article.ho-text > a.group/teaser `div.jd-module > section.grid > article.ho-text > a.group/teaser`
section.grid > div.us_ad > div.pt-8 > a `section.grid > div.us_ad > div.pt-8 > a`
div > div.jd-module > div.mb-6 > a.md:col-start-2 `div > div.jd-module > div.mb-6 > a.md:col-start-2`
div.flex-1 > div.relative > div.pt-8 > a `div.flex-1 > div.relative > div.pt-8 > a`
article.md:col-span-2 > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser `article.md:col-span-2 > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser`
article.ho-text > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser `article.ho-text > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser`
article.ho-text > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser `article.ho-text > a-opt-in.mb-4 > div.opt-in__content-container > a.group/teaser`
div.shadow-modules > footer > div.mb-6 > a `div.shadow-modules > footer > div.mb-6 > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
Rabatt sichern! `div#wtma_teaser_ho_vertrieb_pos1 > div.grid-cols-2 > div.md:mx-8 > a.inline-block`
Ausführliche Informationen zum Versandverfahren und zu Ihren Widerrufsmöglichke… `div.jd-module > div.theme-ho > div > p#input-email-help`
Datenschutzerklärung `div.theme-ho > div > p#input-email-help > a.underline`
Rabatt sichern! `div#wtma_teaser_ho_vertrieb_pos2 > div.grid-cols-2 > div.md:mx-8 > a.inline-block`
ZUM WEBINAR `div#wtma_teaser_ho_vertrieb_pos3 > div.grid-cols-2 > div.md:mx-8 > a.inline-block`
Jetzt entdecken! `div#wtma_teaser_ho_vertrieb_pos4 > div.grid-cols-2 > div.md:mx-8 > a.inline-block`
Hier bestellen `div.container > div.relative > a.inline-block > span`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
E-Mail-Fehlversand und Datenabfluss verhindern `div.flex-1 > div.ad-microsites > div.pt-8 > a.ho-text`
So verbessern Sie Ihr Google-Ranking `div.flex-1 > div.ad-microsites > div.pt-8 > a.ho-text`
Wenn KI die Infrastruktur ans Limit bringt `div.flex-1 > div.ad-microsites > div.pt-8 > a.ho-text`
Wenn der Drucker die Störungen selbst reduziert `div.flex-1 > div.ad-microsites > div.pt-8 > a.ho-text`
Wie Unternehmen NIS2-ready werden `div.flex-1 > div.ad-microsites > div.pt-8 > a.ho-text`
Themenspecial: Digitale Souveränität `div.flex-1 > div.ad-microsites > div.pt-8 > a.ho-text`
Datenaustausch: Schluss mit dem „Flickenteppich“ `div.flex-1 > div.ad-microsites > div.pt-8 > a.ho-text`
Themenspecial: Secure IT für Unternehmen `div.flex-1 > div.ad-microsites > div.pt-8 > a.ho-text`
Wie die deutsche Fertigungsindustrie auf KI setzt `div.flex-1 > div.ad-microsites > div.pt-8 > a.ho-text`
Warum Europas IT-Entscheider umdenken müssen `div.flex-1 > div.ad-microsites > div.pt-8 > a.ho-text`

These items highlight common accessibility best practices.

○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]` values are valid

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

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

●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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

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

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

○`<object>` elements have alternate text

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

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

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.

Source	Description
www.heise.de/ line 9, col 7	`TypeError: Cannot read properties of null (reading 'consent') at https://www.heise.de/:10:8`

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a > figure > a-img > img `a > figure > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a > figure.hidden > a-img > img `a > figure.hidden > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure > a-img > img `a.group/teaser > figure > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`
a.group/teaser > figure.mb-4 > a-img > img `a.group/teaser > figure.mb-4 > a-img > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://heise.de

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Contrast

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Contrast

Best practices

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts