Skip to content
https://Diehl.com

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.

65

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.

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:19.007 source:map[column:97870 line:1 type:source-location url:https://new.diehl.com/build/vendor.bf8f103d.js urlProvider:network]] map[reflowTime:18.022 source:map[column:187252 line:1 type:source-location url:https://new.diehl.com/build/vendor.bf8f103d.js urlProvider:network]] map[reflowTime:6.228 source:map[column:192992 line:1 type:source-location url:https://new.diehl.com/build/vendor.bf8f103d.js urlProvider:network]] map[reflowTime:5.784 source:map[column:8763 line:0 type:source-location url:https://new.diehl.com/build/main.9611bcc4.js urlProvider:network]] map[reflowTime:0.961 source:map[column:37866 line:1 type:source-location url:https://new.diehl.com/build/vendor.bf8f103d.js urlProvider:network]] map[reflowTime:5.54 source:map[column:105922 line:1 type:source-location url:https://new.diehl.com/build/vendor.bf8f103d.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.

URLResource SizeEst Savings
ul.swiper-wrapper > li.swiper-slide > div.video-container > video ul.swiper-wrapper > li.swiper-slide > div.video-container > video
/var/site/storage/images/4/0/6/4/24604-1-eng-GB/4591246a3...181.1 KiB173.4 KiB
Diehl_Video_Loading-Screen.jpg div.video-container > div.video-overlay > figure.aspect-ratio-1-78 > img.video-thumbnail
/var/site/storage/images/_aliases/800px/4/0/6/4/24604-1-e...194.2 KiB152.3 KiB
li.news-teaser > a.link-card > figure.aspect-ratio-1-78 > img.lazyload li.news-teaser > a.link-card > figure.aspect-ratio-1-78 > img.lazyload
/var/site/storage/images/_aliases/400px/9/0/7/9/449709-1-...133.3 KiB118.7 KiB
diehl-metering_gaia_2025_smart-metering-et-reduction-des-pertes-deau (1).jpg li.news-teaser > a.link-card > figure.aspect-ratio-1-78 > img.lazyload
/var/site/storage/images/_aliases/400px/8/6/6/6/446668-1-...97.6 KiB83.0 KiB
202604_ifat_meet-the-experts_diehl-metering_news_distri-page-pic_2x1.png li.news-teaser > a.link-card > figure.aspect-ratio-1-78 > img.lazyload
/var/site/storage/images/_aliases/400px/1/0/1/5/445101-1-...91.7 KiB77.1 KiB
li > a.link-card > figure.aspect-ratio-1-78 > img.lazyload li > a.link-card > figure.aspect-ratio-1-78 > img.lazyload
/var/site/storage/images/_aliases/400px/3/9/5/2/2593-1-en...74.4 KiB59.8 KiB
li > a.link-card > figure.aspect-ratio-1-78 > img.lazyload li > a.link-card > figure.aspect-ratio-1-78 > img.lazyload
/var/site/storage/images/_aliases/400px/8/7/8/5/25878-1-g...69.9 KiB55.3 KiB
li > a.link-card > figure.aspect-ratio-1-78 > img.lazyload li > a.link-card > figure.aspect-ratio-1-78 > img.lazyload
/var/site/storage/images/_aliases/400px/5/7/2/2/22275-1-g...68.3 KiB53.6 KiB
Diehl_Video_Loading-Screen.jpg div.video-container > div.video-overlay > figure.aspect-ratio-1-78 > img.video-thumbnail
/var/site/storage/images/_aliases/400px/4/0/6/4/24604-1-e...65.6 KiB51.1 KiB
li.news-teaser > a.link-card > figure.aspect-ratio-1-78 > img.lazyload li.news-teaser > a.link-card > figure.aspect-ratio-1-78 > img.lazyload
/var/site/storage/images/_aliases/400px/3/7/6/8/448673-1-...55.8 KiB41.3 KiB
div.locations-teaser > div.map > figure.aspect-ratio-1-78 > img.lazyload div.locations-teaser > div.map > figure.aspect-ratio-1-78 > img.lazyload
/var/site/storage/images/_aliases/200px/2/6/1/2/22162-1-g...16.2 KiB13.3 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-1-IMG
nodeLabel: Diehl_Video_Loading-Screen.jpg
path: 1,HTML,1,BODY,0,DIV,2,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,SECTION,0,DIV,0,DIV,0,UL,0,LI,0,DIV,0,DIV,0,FIGURE,0,IMG
selector: div.video-container > div.video-overlay > figure.aspect-ratio-1-78 > img.video-thumbnail
snippet: <img class="video-thumbnail lazyloaded" alt="Diehl_Video_Loading-Screen.jpg" src="https://new.diehl.com/var/site/storage/images/_aliases/800px/4/0/6/4/24604…" data-srcset="/var/site/storage/images/_aliases/400px/4/0/6/4/24604-1-eng-GB/4591246a327…" data-lightbox="false" srcset="/var/site/storage/images/_aliases/400px/4/0/6/4/24604-1-eng-GB/4591246a327…">

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.

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.9 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 41.1 KiB
URLTransfer SizeEst Savings
new.diehl.com/build/main.3f4bd2ec.css50.3 KiB41.1 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 190.5 KiB
URLTransfer SizeEst Savings
new.diehl.com/build/vendor.bf8f103d.js207.9 KiB168.5 KiB
analytics.diehl.com/js/container_44dHNPNt.js34.5 KiB22.0 KiB

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
Other816 ms
Style & Layout727 ms
Script Evaluation353 ms
Rendering90 ms
Script Parsing & Compilation57 ms
Parse HTML & CSS38 ms
Garbage Collection20 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
The page was evicted from the cache because an active network connection received too much data. Chrome limits the amount of data that a page may receive while cached.Not actionable

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
●Minify JavaScript
●JavaScript execution time 0.3 s
●Avoid long main-thread tasks 5 long tasks found
●Avoid non-composited animations 2 animated elements found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 90 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 0 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
92

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
Diehl Defence li.news-teaser > a.link-card > div.news-meta > span

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Diehl Metall offers a broad spectrum of innovative products and technologies in… div.division-teaser > div.module-wrapper-inner > div.swiper > ul#swiper-wrapper-1058f6173594106c7b

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[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
●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 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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with 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.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
100

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Ensure proper origin isolation with COOP
○Mitigate clickjacking with XFO or CSP
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

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.

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`

Send Feedback