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
collections.fes.de/publikationen/image/largethumb/1970601	0.0 ms	62.0 KiB
www.fes.de/_assets/vite/fes-theme.css	0.0 ms	62.0 KiB
collections.fes.de/publikationen/image/largethumb/1969447	0.0 ms	61.1 KiB
/_assets/39d34273ab30c098def3e42400bf98d1/dist/lottie-pla...	0.0 ms	51.7 KiB
www.fes.de/_assets/vite/desktop-navigation.js	0.0 ms	48.1 KiB
collections.fes.de/publikationen/image/largethumb/1972636	0.0 ms	36.7 KiB
collections.fes.de/publikationen/image/largethumb/1972977	0.0 ms	32.1 KiB
www.fes.de/_assets/vite/Ebert-Headline.woff2	0.0 ms	30.8 KiB
www.fes.de/_assets/vite/Ebert-Bold.woff2	0.0 ms	30.5 KiB
www.fes.de/_assets/vite/Ebert-Regular.woff2	0.0 ms	30.0 KiB
/index.php?eID=dumpFile&t=p&p=1404204&token=21976e0fcb95c...	0.0 ms	24.9 KiB
www.fes.de/_assets/vite/fes-theme.js	0.0 ms	24.2 KiB
/index.php?eID=dumpFile&t=p&p=1383779&token=85a2ccac7d136...	0.0 ms	22.7 KiB
/index.php?eID=dumpFile&t=p&p=1402498&token=19bb3713902b4...	0.0 ms	18.5 KiB
/_assets/9cec337f7d9b8a112ff7bc4a21068e10/Libs/eye-able-t...	0.0 ms	5.1 KiB
www.fes.de/_assets/9cec337f7d9b8a112ff7bc4a21068e10/Icons/General/logo-fes.svg	0.0 ms	4.4 KiB
/index.php?eID=dumpFile&t=p&p=1402709&token=5448e89451744...	0.0 ms	4.1 KiB
/_assets/e8c90b9983c1cf95dcc0174e76f0c198/JavaScript/cook...	0.0 ms	4.0 KiB
/_assets/e8c90b9983c1cf95dcc0174e76f0c198/Stylesheet/cook...	0.0 ms	2.2 KiB
www.fes.de/typo3temp/assets/js/7378d5dc5468da27b323e43dae530540.js?1763973398	0.0 ms	1.6 KiB
/_assets/39d34273ab30c098def3e42400bf98d1/dist/lottie-pla...	0.0 ms	744 B
/typo3temp/assets/compressed/merged-8a9a09a923cbb632a2c51...	0.0 ms	670 B
www.fes.de/_assets/vite/_commonjsHelpers.js	0.0 ms	632 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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.fes.de/_assets/vite/Ebert-Bold.woff2	50 ms
www.fes.de/_assets/vite/Ebert-Regular.woff2	30 ms
www.fes.de/_assets/vite/Ebert-Headline.woff2	30 ms

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:4187.468 label:Time to first byte subpart:timeToFirstByte] map[duration:179.529 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-H1

nodeLabel: Wir entwickeln Ideen für die Soziale Demokratie von heute und morgen.

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

selector: div#c406035 > div.hero > div.hero-content > h1.hero-content-header

snippet: <h1 class="hero-content-header">

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

value: No additional origins are good candidates for preconnecting

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
www.fes.de/_assets/vite/fes-theme.css	62.0 KiB	451 ms
/_assets/9cec337f7d9b8a112ff7bc4a21068e10/Libs/eye-able-t...	5.1 KiB
/_assets/e8c90b9983c1cf95dcc0174e76f0c198/Stylesheet/cook...	2.2 KiB
www.fes.de/typo3temp/assets/js/7378d5dc5468da27b323e43dae530540.js?1763973398	1.6 KiB
/_assets/39d34273ab30c098def3e42400bf98d1/dist/lottie-pla...	744 B
/typo3temp/assets/compressed/merged-8a9a09a923cbb632a2c51...	670 B

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
Vollbesetzter Saal mit Blick aufs Podium. `figure.image > a > picture > img.img-fluid`	/index.php?eID=dumpFile&t=p&p=1404204&token=21976e0fcb95c...	24.4 KiB	5.4 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: 864 ms

URL	Time Spent
fes.de/	864 ms
www.fes.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: 4.0 s

URL	Time Spent
www.fes.de/	4.1 s

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

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: 180 ms 14.3 KiB

URL	Transfer Size	Est Savings
www.fes.de/_assets/vite/fes-theme.css	62.0 KiB	14.3 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: 180 ms 86.8 KiB

URL	Transfer Size	Est Savings
/_assets/39d34273ab30c098def3e42400bf98d1/dist/lottie-pla...	51.4 KiB	48.1 KiB
www.fes.de/_assets/vite/desktop-navigation.js	47.7 KiB	38.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
/_assets/39d34273ab30c098def3e42400bf98d1/dist/lottie-pla...	3.8 s	3.4 s	37 ms
Unattributable	399 ms	44 ms	0.0 ms
www.fes.de/	362 ms	6.9 ms	1.4 ms
/_assets/e8c90b9983c1cf95dcc0174e76f0c198/JavaScript/cook...	54 ms	9.0 ms	1.1 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	3.5 s
Other	639 ms
Style & Layout	303 ms
Rendering	110 ms
Parse HTML & CSS	49 ms
Script Parsing & Compilation	43 ms
Garbage Collection	13 ms

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: 0.0 ms 17.4 KiB

URL	Transfer Size	Est Savings
www.fes.de/_assets/vite/desktop-navigation.js	47.7 KiB	10.9 KiB
www.fes.de/_assets/vite/fes-theme.js	23.8 KiB	6.5 KiB

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Reduce unused CSS

●Avoids enormous network payloads Total size was 1,123 KiB

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 1 animated element 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 280 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Links are distinguishable without relying on color.

●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

●Touch targets have sufficient size and spacing.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

○Document has a `<title>` element

○ARIA IDs are unique

○No form fields have multiple labels

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

○Heading elements appear in a sequentially-descending order

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

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

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

○Image elements have `[alt]` attributes

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

○No element has a `[tabindex]` value greater than 0

○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"]`

○Document has a main landmark.

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

○Identical links have the same purpose.

○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

●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

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

○Document has a `<title>` element

○Image elements have `[alt]` attributes