Skip to content
https://heise.de

Lighthouse Mobile

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

Detailed Report

Audit breakdown by category with detailed findings.

38

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
www.heise.de/assets/akwa/v24/js/akwa.js120.0 s85.6 KiB
cmp.heise.de/Notice.8f529.js3600.0 s91.2 KiB
www.heise.de/assets/fonts/v1/source-sans-variable/ss3vf.woff2120.0 s53.8 KiB
cdn.mateti.net/mcp/onsite.min.js300.0 s35.2 KiB
cmp.heise.de/unified/wrapperMessagingWithoutDetection.js3600.0 s42.0 KiB
www.heise.de/assets/styles/index.css120.0 s23.5 KiB
xn2wkedljxxol.heise.de/files/site_script/heise.de.js3600.0 s19.9 KiB
www.heise.de/assets/akwa/v24/css/akwa.css120.0 s11.1 KiB
cmp.heise.de/Notice.30929.css3600.0 s6.7 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...2020313.0 s26.8 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...2542270.0 s22.3 KiB
cmp.heise.de/polyfills.01516.js3600.0 s2.3 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...1950953.0 s14.6 KiB
www.heise.de/icons/ho/h96-logo.svg7200.0 s1.5 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Desktop_...2562016.0 s11.8 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Desktop_...1431276.0 s10.3 KiB
/v7/_www-heise-de_/imgs/18/4/8/1/5/2/6/8/Podcast_Desktop_...2557433.0 s9.2 KiB
/v7/_www-heise-de_/imgs/18/4/8/3/8/9/0/5/nerdword-6566d36...2380298.0 s7.8 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Mobil_ba...2559532.0 s7.6 KiB
/v7/_www-heise-de_/imgs/18/4/2/8/8/7/3/2/Podcast_Mobil_ba...2380297.0 s6.1 KiB
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Desktop_...2543933.0 s5.6 KiB
/v7/_www-heise-de_/imgs/18/4/8/1/5/2/6/8/Podcast_Mobil_ba...2509874.0 s5.3 KiB
/v7/_www-heise-de_/imgs/18/4/8/1/5/2/6/8/Podcast_Mobil_ba...2020312.0 s4.6 KiB
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Desktop_...2543932.0 s4.5 KiB
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Mobil_ba...663935.0 s3.2 KiB
www.heise.de/icons/svg/icons/svg/comments_outline_grey_light.svg7200.0 s388 B
www.heise.de/icons/svg/icons/svg/comments_outline_grey_dark.svg7200.0 s386 B
www.heise.de/icons/svg/icons/svg/video_outline_grey_light.svg7200.0 s376 B
www.heise.de/icons/svg/icons/svg/video_outline_grey_dark.svg7200.0 s376 B
www.heise.de/icons/svg/logos/svg/heise_plus_blue_negativ.svg7200.0 s364 B
/v7/_www-heise-de_/imgs/18/4/9/3/9/8/1/1/Podcast_Mobil_ba...2543932.0 s2.8 KiB
www.heise.de/assets/fonts/v1/source-sans-variable/ss3vf.woff2120.0 s274 B
www.heise.de/icons/svg/logos/svg/heise_plus_blue.svg7200.0 s327 B
www.heise.de/icons/svg/icons/svg/arrow-right-grey-dark.svg7200.0 s297 B
www.heise.de/icons/svg/icons/svg/arrow-right-grey-light.svg7200.0 s294 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
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">

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.

URLTransfer SizeDuration
www.heise.de/assets/akwa/v24/css/akwa.css11.1 KiB302 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
URLTime 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
URLTransfer SizeEst Savings
www.heise.de/assets/styles/index.css23.4 KiB15.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

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 600 ms 132.5 KiB
URLTransfer SizeEst Savings
cmp.heise.de/Notice.8f529.js90.9 KiB62.9 KiB
www.heise.de/assets/akwa/v24/js/akwa.js85.4 KiB47.4 KiB
/resp/api/get/288689636920174?url=https%3A%2F%2Fwww.heise...46.4 KiB22.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.

URLTotal CPU TimeScript EvaluationScript Parse
www.heise.de/1.2 s72 ms5.3 ms
cmp.heise.de/Notice.8f529.js953 ms698 ms50 ms
www.heise.de/assets/akwa/v24/js/akwa.js757 ms478 ms39 ms
Unattributable738 ms42 ms0.0 ms
cmp.heise.de/unified/wrapperMessagingWithoutDetection.js553 ms183 ms18 ms
/resp/api/get/288689636920174?url=https%3A%2F%2Fwww.heise...485 ms409 ms25 ms
cdn.mateti.net/mcp/onsite.min.js176 ms157 ms14 ms
xn2wkedljxxol.heise.de/files/site_script/heise.de.js122 ms104 ms8.1 ms
cmp.heise.de/unified/4.40.1/gdpr-tcf.27718c8cb9d29947d2c1.bundle.js77 ms55 ms22 ms
/index.html?hasCsp=true&message_id=1454968&consentUUID=nu...72 ms0.6 ms1.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.

CategoryTime Spent
Script Evaluation2.2 s
Style & Layout1.2 s
Other953 ms
Parse HTML & CSS354 ms
Rendering245 ms
Script Parsing & Compilation186 ms
Garbage Collection86 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 reasonFailure 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
84

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

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

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
www.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
92

SEO

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.group/teaser > figure.mb-4 > a-img > img a.group/teaser > figure.mb-4 > a-img > img
a.group/teaser > figure.mb-4 > a-img > img a.group/teaser > figure.mb-4 > a-img > img
a.group/teaser > figure.mb-4 > a-img > img a.group/teaser > figure.mb-4 > a-img > img
a.group/teaser > figure.mb-4 > a-img > img a.group/teaser > figure.mb-4 > a-img > img
a.group/teaser > figure.mb-4 > a-img > img a.group/teaser > figure.mb-4 > a-img > img
a.group/teaser > figure.mb-4 > a-img > img a.group/teaser > figure.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`

Send Feedback