Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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

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.

Request	Cache TTL	Transfer Size
privacy-proxy.usercentrics.eu/latest/uc-block.bundle.js	3600.0 s	30.5 KiB
web.cmp.usercentrics.eu/ui/TvGdprCmpView.9fffdb6f.js	3600.0 s	30.1 KiB
web.cmp.usercentrics.eu/ui/loader.js	3600.0 s	15.7 KiB
crm.zoho.eu/crm/javascript/zcga.js	0.0 ms	3.3 KiB
app.usercentrics.eu/session/1px.png?settingsId=kQNcvi9X4w1jsN	1800.0 s	826 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:28.634 source:map[column:5582 line:373 type:source-location url:https://www.webnetz.de/build/assets/site-128f0841.js urlProvider:network]]]

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

items: [map[reflowTime:2.874 source:map[column:6076 line:54 type:source-location url:https://www.webnetz.de/build/assets/site-128f0841.js urlProvider:network]] map[reflowTime:8.393 source:map[column:6715 line:126 type:source-location url:https://www.webnetz.de/build/assets/site-128f0841.js urlProvider:network]] map[reflowTime:0.539 source:map[column:55593 line:126 type:source-location url:https://www.webnetz.de/build/assets/site-128f0841.js urlProvider:network]] map[reflowTime:13.634 source:map[column:12581 line:126 type:source-location url:https://www.webnetz.de/build/assets/site-128f0841.js urlProvider:network]] map[reflowTime:10.187 source:map[column:93528 line:126 type:source-location url:https://www.webnetz.de/build/assets/site-128f0841.js urlProvider:network]] map[reflowTime:0.48 source:map[column:549 line:126 type:source-location url:https://www.webnetz.de/build/assets/site-128f0841.js urlProvider:network]] map[reflowTime:0.119 source:map[column:623 line:126 type:source-location url:https://www.webnetz.de/build/assets/site-128f0841.js urlProvider:network]] map[reflowTime:0.306 source:map[column:32267 line:126 type:source-location url:https://www.webnetz.de/build/assets/site-128f0841.js urlProvider:network]] map[reflowTime:0.545 source:map[column:6792 line:22 type:source-location url:https://www.webnetz.de/build/assets/site-128f0841.js urlProvider:network]] map[reflowTime:2.054 source:map[column:50990 line:126 type:source-location url:https://www.webnetz.de/build/assets/site-128f0841.js urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
a.flex > div.aspect-[3/2] > div.@container > img.absolute `a.flex > div.aspect-[3/2] > div.@container > img.absolute`	www.webnetz.de/images/webinare/newsletter-marketing.jpg	39.6 KiB	30.2 KiB
body.flex > main#content > section#li08rfm6 > video#hero-video `body.flex > main#content > section#li08rfm6 > video#hero-video`	www.webnetz.de/images/poster-hero.webp	34.4 KiB	16.8 KiB
div#uc-main-dialog > div#main-view > header.has-custom-logo > img.logo `div#uc-main-dialog > div#main-view > header.has-custom-logo > img.logo`	www.webnetz.de/images/pressefotos/logo_webnetz.png	15.9 KiB	15.3 KiB
a.flex > div.aspect-[3/2] > div.@container > img.absolute `a.flex > div.aspect-[3/2] > div.@container > img.absolute`	www.webnetz.de/images/webinare/influencer-marketing.jpg	24.0 KiB	14.6 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: 838 ms

URL	Time Spent
webnetz.de/	838 ms
www.webnetz.de/	0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 963 ms

URL	Time Spent
www.webnetz.de/	1.1 s

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 37.2 KiB

URL	Transfer Size	Est Savings
www.webnetz.de/build/assets/site-f6261c38.css	39.3 KiB	37.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: 450 ms 131.2 KiB

URL	Transfer Size	Est Savings
www.webnetz.de/build/assets/site-128f0841.js	152.0 KiB	95.9 KiB
web.cmp.usercentrics.eu/ui/v/3.119.0/WebSdk.lib.5ddd9ff8.js	56.1 KiB	35.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.webnetz.de/build/assets/site-128f0841.js	1.6 s	653 ms	0.3 ms
privacy-proxy.usercentrics.eu/latest/uc-block.bundle.js	744 ms	632 ms	11 ms
Unattributable	686 ms	14 ms	0.0 ms
www.webnetz.de/	675 ms	7.1 ms	3.5 ms
web.cmp.usercentrics.eu/ui/v/3.119.0/WebSdk.lib.5ddd9ff8.js	121 ms	96 ms	21 ms
web.cmp.usercentrics.eu/ui/v/3.119.0/UcGdprCmpView.b05dbc41.js	66 ms	1.5 ms	6.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	1.6 s
Other	1.2 s
Style & Layout	762 ms
Rendering	351 ms
Parse HTML & CSS	121 ms
Garbage Collection	73 ms
Script Parsing & Compilation	59 ms

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

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,287 KiB

●Avoid long main-thread tasks 11 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 100 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

Accessibility

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
BLOG `div#swiper-wrapper-410d0a491032bdbe96 > div.swiper-slide > a.flex > span.mb-4`
WEBINARE `div#swiper-wrapper-410d0a491032bdbe96 > div.swiper-slide > a.flex > span.mb-4`
Jobs `div.relative > div.headlines > div.pretitle > span.pretitle--text`
Alle offenen Stellen `section#lieljzzn > div.mx-auto > a.button > span`
Akzeptieren `footer#uc-cmp-footer > div.buttons > div.buttons-row > button#accept`

These are opportunities to improve the legibility of your content.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.flex > div.aspect-[3/2] > div.@container > img.absolute `a.flex > div.aspect-[3/2] > div.@container > img.absolute`
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img `div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img`
a.flex > div.aspect-[3/2] > div.@container > img.absolute `a.flex > div.aspect-[3/2] > div.@container > img.absolute`
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img `div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img`
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img `div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img`
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img `div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img`
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img `div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img`

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.

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
Jetzt Artikel lesen `div#swiper-wrapper-410d0a491032bdbe96 > div.swiper-slide > a.flex > button.button`
Jetzt anmelden `div#swiper-wrapper-410d0a491032bdbe96 > div.swiper-slide > a.flex > button.button`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Jetzt kontaktieren `div.relative > div.flex > div > a.button`

○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

●Buttons have an accessible name

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

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

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

●Links have a discernible name

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●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

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

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

○Input buttons have discernible text.

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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

○`[lang]` attributes have a valid value

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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.flex > div.aspect-[3/2] > div.@container > img.absolute `a.flex > div.aspect-[3/2] > div.@container > img.absolute`
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img `div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img`
a.flex > div.aspect-[3/2] > div.@container > img.absolute `a.flex > div.aspect-[3/2] > div.@container > img.absolute`
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img `div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img`
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img `div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img`
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img `div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img`
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img `div.@container > div.absolute > div.tile-hosts > img.tile-hosts-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`