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
assets.adobedtm.com/04196e8f7bcd/74f40dedb607/launch-452613f09356.min.js	3600.0 s	45.6 KiB
scripts.clarity.ms/0.8.62/clarity.js	86400.0 s	25.1 KiB
app.usercentrics.eu/browser-ui/latest/loader.js	3600.0 s	10.8 KiB
www.webasto.com/.rum/@adobe/helix-rum-js@%5E2/dist/micro.js	3600.0 s	980 B
app.usercentrics.eu/session/1px.png?settingsId=Y0jU0ee2FiqH8P	1800.0 s	818 B
/etc.clientlibs/webasto/clientlibs/clientlib-site/resourc...	43200.0 s	837 B
/etc.clientlibs/webasto/clientlibs/clientlib-site/resourc...	43200.0 s	598 B
/etc.clientlibs/webasto/clientlibs/clientlib-site/resourc...	43200.0 s	588 B
/etc.clientlibs/webasto/clientlibs/clientlib-site/resourc...	43200.0 s	505 B
/etc.clientlibs/webasto/clientlibs/clientlib-site/resourc...	43200.0 s	445 B
/etc.clientlibs/webasto/clientlibs/clientlib-site/resourc...	43200.0 s	422 B
/etc.clientlibs/webasto/clientlibs/clientlib-site/resourc...	43200.0 s	291 B
/etc.clientlibs/webasto/clientlibs/clientlib-site/resourc...	43200.0 s	287 B
webasto.scene7.com/is/content/webasto/1-1_Home_Feel_the_drive	0.0 ms	0 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:33.762 source:map[column:203340 line:1 type:source-location url:https://www.webasto.com/etc.clientlibs/webasto/clientlibs/clientlib-site.lc-6e01ef64bee544f1920c68a4712fa44f-lc.min.js urlProvider:network]] map[reflowTime:9.431 source:map[column:115261 line:1 type:source-location url:https://www.webasto.com/etc.clientlibs/webasto/clientlibs/clientlib-site.lc-6e01ef64bee544f1920c68a4712fa44f-lc.min.js urlProvider:network]]]

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
div.cmp-hero__video-bg > div.plyr > div.plyr__video-wrapper > div.plyr__poster `div.cmp-hero__video-bg > div.plyr > div.plyr__video-wrapper > div.plyr__poster`	/adobe/dynamicmedia/deliver/dm-aid--822ef68e-a5d5-4625-ac...	589.1 KiB	251.6 KiB
div.cmp-hero > div.cmp-hero__img-bg > div.cmp-image > img.cmp-image__image `div.cmp-hero > div.cmp-hero__img-bg > div.cmp-image > img.cmp-image__image`	/adobe/dynamicmedia/deliver/dm-aid--822ef68e-a5d5-4625-ac...	239.9 KiB	221.5 KiB

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

nodeLabel:

path: 1,HTML,1,BODY,1,DIV,0,DIV,0,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV

selector: div.aem-Grid > div.hero > div.cmp-hero > div.cmp-hero__img-bg

snippet: <div class="cmp-hero__img-bg" hidden="true">

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

value: no origins were preconnected

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
/etc.clientlibs/webasto/clientlibs/clientlib-site.lc-ec59...	47.5 KiB	302 ms
/etc.clientlibs/webasto/clientlibs/clientlib-dependencies...	110 B
/etc.clientlibs/webasto/clientlibs/clientlib-dependencies...	196 B
/etc.clientlibs/webasto/clientlibs/clientlib-base.lc-a49e...	810 B

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.1 s

URL	Time Spent
www.webasto.com/	763 ms
www.webasto.com/en-int.html	330 ms
www.webasto.com/en-int.html	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

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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 180 ms 9.6 KiB

URL	Transfer Size	Est Savings
/etc.clientlibs/webasto/clientlibs/clientlib-base.lc-eaf7...	17.4 KiB	9.6 KiB

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: 300 ms 43.8 KiB

URL	Transfer Size	Est Savings
/etc.clientlibs/webasto/clientlibs/clientlib-site.lc-ec59...	47.3 KiB	43.8 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: 1.3 s 199.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=AW-11140615971	146.4 KiB	60.0 KiB
app.usercentrics.eu/browser-ui/3.101.0/index.module.js	120.6 KiB	55.0 KiB
/etc.clientlibs/webasto/clientlibs/clientlib-site.lc-6e01...	59.1 KiB	37.5 KiB
app.usercentrics.eu/browser-ui/3.101.0/VirtualServiceItem-ba2ffbd9.js	48.7 KiB	26.1 KiB
assets.adobedtm.com/04196e8f7bcd/74f40dedb607/launch-452613f09356.min.js	45.0 KiB	20.6 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
Unattributable	858 ms	93 ms	0.0 ms
/etc.clientlibs/webasto/clientlibs/clientlib-site.lc-6e01...	682 ms	414 ms	33 ms
/etc.clientlibs/webasto/clientlibs/clientlib-site/resourc...	464 ms	404 ms	12 ms
app.usercentrics.eu/browser-ui/3.101.0/index.module.js	320 ms	231 ms	1.5 ms
scripts.clarity.ms/0.8.62/clarity.js	264 ms	217 ms	5.7 ms
assets.adobedtm.com/04196e8f7bcd/74f40dedb607/launch-452613f09356.min.js	244 ms	218 ms	11 ms
www.googletagmanager.com/gtag/js?id=AW-11140615971	228 ms	192 ms	35 ms
www.webasto.com/en-int.html	176 ms	14 ms	4.0 ms
/etc.clientlibs/webasto/clientlibs/clientlib-base.lc-eaf7...	101 ms	81 ms	15 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.4 s
Other	865 ms
Style & Layout	363 ms
Script Parsing & Compilation	145 ms
Parse HTML & CSS	98 ms
Garbage Collection	65 ms
Rendering	42 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
webasto.scene7.com/is/content/webasto/1-1_Home_Feel_the_drive	5.8 MiB
/adobe/dynamicmedia/deliver/dm-aid--822ef68e-a5d5-4625-ac...	589.7 KiB
/adobe/dynamicmedia/deliver/dm-aid--6970d908-a342-446e-ad...	269.7 KiB
/adobe/dynamicmedia/deliver/dm-aid--0879a0d2-37e4-4ce8-b5...	264.1 KiB
/adobe/dynamicmedia/deliver/dm-aid--822ef68e-a5d5-4625-ac...	240.3 KiB
/adobe/dynamicmedia/deliver/dm-aid--2b5ddde0-d4c5-4d4a-a8...	187.0 KiB
/graphql/execute.json/webasto/products;region=int;locale=en	186.2 KiB
/etc.clientlibs/webasto/clientlibs/clientlib-site/resourc...	182.9 KiB
/adobe/dynamicmedia/deliver/dm-aid--e635bc62-d691-4a10-bc...	182.9 KiB
/etc.clientlibs/webasto/clientlibs/clientlib-site/resourc...	180.6 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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoid long main-thread tasks 12 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 30 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

100

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.

○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

●Image elements have `[alt]` attributes

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

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

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

●Elements with visible text labels have matching accessible names.

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

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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

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

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.webasto.com/en-int/newsroom/press-releases/air-flow-ptc-air-heaters.html	Read more
www.webasto.com/en-int/newsroom/press-releases/125-years-anniversary.html	Read more
www.webasto.com/en-int/newsroom/press-releases/cool-top-120-e.html	Read more
www.webasto.com/en-int/newsroom/press-releases/plant-india.html	Read more
www.webasto.com/en-int/newsroom/press-releases/social-days-2025.html	Read more
/en-int/newsroom/press-releases/webasto-and-maccor-collab...	Read more

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`