Skip to content
https://dw.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.

56

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
consent.dw.com/delivery/js/cmp_final_en.min.js66981.0 s100.7 KiB
static.dw.com/image/76762634_603.jpeg19082.0 s42.0 KiB
/delivery/customdata/bV8xLndfNzAxNjYucl9HRFBSLmxfZW4uZF81...1229.0 s26.6 KiB
static.dw.com/image/76352425_803.webp19064.0 s16.2 KiB
s.go-mpulse.net/boomerang/J2XBJ-XZGSZ-2254J-GTRXP-PD7UX604800.0 s56.6 KiB
static.dw.com/image/76762634_600.jpeg17978.0 s1.7 KiB
static.dw.com/image/76747335_800.jpg20594.0 s1.6 KiB

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:58.38 source:map[column:14503 line:2 type:source-location url:https://www.dw.com/static/index-Bgv_qheB.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:30.721 source:map[column:543 line:154 type:source-location url:https://www.dw.com/static/index-Bgv_qheB.js urlProvider:network]] map[reflowTime:87.607 source:map[column:1827 line:138 type:source-location url:https://www.dw.com/static/index-Bgv_qheB.js urlProvider:network]] map[reflowTime:21.811 source:map[column:12628 line:23 type:source-location url:https://www.dw.com/static/index-Bgv_qheB.js urlProvider:network]] map[reflowTime:36.569 source:map[column:6862 line:138 type:source-location url:https://www.dw.com/static/index-Bgv_qheB.js urlProvider:network]]]

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: Iranian women pass next to an anti-US mural
path: 1,HTML,2,BODY,2,DIV,3,DIV,3,DIV,3,DIV,2,DIV,0,SPAN,0,SECTION,2,A,0,PICTURE,6,IMG
selector: section#top-story-76331652 > a.ts-hero > picture.s9gezr6 > img
snippet: <img alt="Iranian women pass next to an anti-US mural" fetchpriority="high" height="56.25" src="https://static.dw.com/image/76352425_803.webp" srcset="https://static.dw.com/image/76352425_600.jpg 78w, https://static.dw.com/im…" width="100">

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.dw.com/static/index-CxC0yKOY.css18.9 KiB302 ms

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
Sudan Südkordofan 2026 | An RSF fighter sells goods | Konflikt in den Nuba ber… div.teaser-image-wrap > a.teaser-image > figure.srnoiv7 > img.hq-img
static.dw.com/image/76762634_603.jpeg41.9 KiB14.7 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: 859 ms
URLTime Spent
dw.com/859 ms
www.dw.com/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 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 115.3 KiB
URLTransfer SizeEst Savings
www.dw.com/static/index-Bgv_qheB.js107.0 KiB42.2 KiB
s.go-mpulse.net/boomerang/J2XBJ-XZGSZ-2254J-GTRXP-PD7UX56.5 KiB37.0 KiB
consent.dw.com/delivery/js/cmp_final_en.min.js100.3 KiB36.1 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.dw.com/static/index-Bgv_qheB.js2.1 s1.3 s2.5 ms
www.dw.com/1.3 s26 ms5.2 ms
Unattributable613 ms176 ms0.0 ms
/delivery/customdata/bV8xLndfNzAxNjYucl9HRFBSLmxfZW4uZF81...482 ms445 ms21 ms
www.dw.com/static/consentScript-B9SokloN.js243 ms228 ms0.2 ms
consent.dw.com/delivery/js/cmp_final_en.min.js117 ms41 ms75 ms
s.go-mpulse.net/boomerang/J2XBJ-XZGSZ-2254J-GTRXP-PD7UX101 ms60 ms32 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.3 s
Style & Layout1.2 s
Other1.2 s
Rendering200 ms
Script Parsing & Compilation141 ms
Garbage Collection49 ms
Parse HTML & CSS31 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.6 KiB
URLTransfer SizeEst Savings
.cmpstyleroot,.cmpstyleroot *{--x6pt:6pt;--x7pt:7pt;--x8pt:8pt;--x9pt:9pt;--x10pt:10pt;--x11pt:11pt; … } …17.6 KiB2.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: 0.0 ms 14.2 KiB
URLTransfer SizeEst Savings
.cmpstyleroot,.cmpstyleroot *{--x6pt:6pt;--x7pt:7pt;--x8pt:8pt;--x9pt:9pt;--x10pt:10pt;--x11pt:11pt; … } …17.6 KiB14.2 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 JavaScript
●Avoids enormous network payloads Total size was 454 KiB
●Avoid long main-thread tasks 14 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 160 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 10 ms
○INP breakdown
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
89

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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Latest videos div.page-header > nav.s10dzqs3 > div.nav-position > div.nav-height

These are opportunities to improve the usage of ARIA in your application which 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
div.auto-bg-color > section#av-magazine-63033921 > div.c2fyhwl > h2.cp7bjxx div.auto-bg-color > section#av-magazine-63033921 > div.c2fyhwl > h2.cp7bjxx
div.s1b19e59 > div.mrac31i > div.t16l2fqg > span.kicker div.s1b19e59 > div.mrac31i > div.t16l2fqg > span.kicker
div.mrac31i > div.t16l2fqg > span.date-time > time div.mrac31i > div.t16l2fqg > span.date-time > time
div.auto-bg-color > section#cross-promotion > div.c2fyhwl > h2.cp7bjxx div.auto-bg-color > section#cross-promotion > div.c2fyhwl > h2.cp7bjxx
Slideshow — Thailand, Myanmar new year celebrations soaked in tradition div.teaser-data-wrap > div.teaser-data > h3.title > a.rdu7i8u
div.s1b19e59 > div.teaser-data-wrap > div.t16l2fqg > span.kicker div.s1b19e59 > div.teaser-data-wrap > div.t16l2fqg > span.kicker
div.teaser-data-wrap > div.t16l2fqg > span.date-time > time div.teaser-data-wrap > div.t16l2fqg > span.date-time > time
div.s1b19e59 > div.teaser-data-wrap > div.t16l2fqg > span.l1l9ne58 div.s1b19e59 > div.teaser-data-wrap > div.t16l2fqg > span.l1l9ne58
div.teaser-data-wrap > div.teaser-data > h3.title > a.rdu7i8u div.teaser-data-wrap > div.teaser-data > h3.title > a.rdu7i8u

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
footer#footer > section.hh5424a > div > ul.section-list footer#footer > section.hh5424a > div > ul.section-list

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
●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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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.
●`[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
○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
○Buttons have an accessible name
○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
○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.
96

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Pakistan Islamabad 2026 | Pressezentrum bei den US-iranischen Friedensgesprächen div.teaser-image-wrap > a.teaser-image > figure.srnoiv7 > img.lq-img
static.dw.com/image/76747335_800.jpg50 x 5050 x 5075 x 75
●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
●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
100

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.

○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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback