Lighthouse Desktop

· 0 checks — Desktop 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
cdn.privacy-mgmt.com/Notice.8f529.js	3600.0 s	91.3 KiB
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	3600.0 s	42.0 KiB
j.dejure.org/jcg/ba_djo.js	3600.0 s	20.2 KiB
cdn.privacy-mgmt.com/Notice.30929.css	3600.0 s	6.7 KiB
cdn.privacy-mgmt.com/polyfills.01516.js	3600.0 s	2.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-0-IMG

nodeLabel: Rechts-KI Partnerschaft von Doctrine und dejure.org

path: 1,HTML,1,BODY,0,DIV,4,CONTENT,0,DIV,0,DIV,0,A,0,IMG

selector: div#top2 > div#top_inner > a.o_u > img

snippet: <img src="https://j.dejure.org/jcg/doctrine/doctrine_banner.svg" width="100%" alt="Rechts-KI Partnerschaft von Doctrine und dejure.org">

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.

URL	Transfer Size	Duration
j.dejure.org/jcg/ba_djo.js	20.2 KiB	238 ms
j.dejure.org/jcg/style-51.css	39.2 KiB	1.2 s

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#neues_inner > p.nachrichten_kasten > a.link_extern > span.favicon `div#neues_inner > p.nachrichten_kasten > a.link_extern > span.favicon`	j.dejure.org/jcg/sprite_favicon.png	12.5 KiB	5.9 KiB

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

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 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: 240 ms 63.3 KiB

URL	Transfer Size	Est Savings
j.dejure.org/jcg/style-51.css	38.9 KiB	35.0 KiB
j.dejure.org/jcg/style_mobile-21.css	28.2 KiB	28.2 KiB

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 reason	Failure type
The page has an unload handler in the main frame.	Actionable

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 13.1 KiB

URL	Transfer Size	Est Savings
j.dejure.org/jcg/style-51.css	39.2 KiB	7.6 KiB
j.dejure.org/jcg/style_mobile-21.css	28.5 KiB	5.6 KiB

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 18.0 KiB

URL	Transfer Size	Est Savings
j.dejure.org/jcg/formular2b-99.js	80.6 KiB	15.6 KiB
j.dejure.org/jcg/einzelseite-75.js	13.9 KiB	2.4 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: 0.0 ms 117.4 KiB

URL	Transfer Size	Est Savings
j.dejure.org/jcg/formular2b-99.js	80.6 KiB	60.2 KiB
j.dejure.org/jcg/jquery-ui-1.14.1/jquery-ui.min.js	65.7 KiB	57.2 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Rechts-KI Partnerschaft von Doctrine und dejure.org `div#top2 > div#top_inner > a.o_u > img`	j.dejure.org/jcg/doctrine/doctrine_banner.svg
Vernetzungslogo `div#ersterkasten > div#aktuell > div#aktion > img`	j.dejure.org/jcg/logo_70x70.png

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 30 ms

●Avoids enormous network payloads Total size was 744 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.4 s

●Network Requests

●Network Round Trip Times 210 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

○Avoid large layout shifts

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
Doctrine entdecken `div#main > div#doctrine_banner > div.doctrine_promo_item_content > a.doctrine_button`
Gesetze `div#nav_wrapper > ul.nav-menu > li#nav-item-gesetze > a`
Bundesgesetzblatt `div#nav_wrapper > ul.nav-menu > li#nav-item-bgbl > a`
Rechtsprechung `div#nav_wrapper > ul.nav-menu > li#nav-item-rechtsprechung > a`
neu Rechts-KI `div#nav_wrapper > ul.nav-menu > li#nav-item-doctrine > a#doctrine_item`
Stellenmarkt `div#nav_wrapper > ul.nav-menu > li#nav-item-stellenmarkt > a`
Merkliste `div#nav_wrapper > ul.nav-menu > li#nav-item-merkliste > a.get_option`
Verlauf `div#nav_wrapper > ul.nav-menu > li#nav-item-verlauf > a`
heute `div.zettel_innen > div#bgbl_zettel_inner > a > span`
Juristische Vernetzungs- funktion `div#ersterkasten > div#aktuell > div#aktion > h2`
Kostenloser Zusatzdienst für jur. Internetpublikationen. Mehr... `div#ersterkasten > div#aktuell > div#aktion > p`
Mehr... `div#aktuell > div#aktion > p > a`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
A `div.content_inner > div#alphabetisch > div#alpha > h4`
Nachrichten `div.schatten > div.schatten > div#neues_inner > h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#suche > form#suchfeldform_ajax > span#suchfeldset_ajax > input#suchfeld_ajax `div#suche > form#suchfeldform_ajax > span#suchfeldset_ajax > input#suchfeld_ajax`

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.

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
Gesetze Bundesgesetzblatt Rechtsprechung Werbefrei neu Rechts-KI Stellenmarkt M… `div#main > nav#navigation > div#nav_wrapper > ul.nav-menu`

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

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
Gesetze und Rechtsprechung `div#footer > div#footer_inhalt > div.was_ist_dejureorg > a`
AGB & Datenschutzerklärung `div#footer > div#footer_inhalt > div.was_ist_dejureorg > a`
Kontakt/Impressum `div#footer > div#footer_inhalt > div.was_ist_dejureorg > a`
Vertrag kündigen `div#footer > div#footer_inhalt > div.was_ist_dejureorg > a`
Datenschutzeinstellungen `div#footer > div#footer_inhalt > div.was_ist_dejureorg > a`
Wird-zitiert-von `div#footer > div#footer_inhalt > div > a`
Merkfunktion `div#footer > div#footer_inhalt > div > a`
"Lesefreundlicher" `div#footer > div#footer_inhalt > div > a`
Vernetzungsfunktion `div#footer > div#footer_inhalt > div > a`
Stellenmarkt `div#footer > div#footer_inhalt > div > a`
Zitierfunktion `div#footer > div#footer_inhalt > div > a`
Erweiterung Multi-Suche `div#footer > div#footer_inhalt > div > a`
Rechtsfenster `div#footer > div#footer_inhalt > div > a`
COVID-19-Übersichten `div#footer > div#footer_inhalt > div > a.bg_virus`

These items highlight common accessibility best practices.

○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

●`[accesskey]` values are unique

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`button`, `link`, and `menuitem` elements 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

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

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

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

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
div#pur_mobil > a > picture > img `div#pur_mobil > a > picture > img`	dejure.org/jcg/pur_mockups.webp	100 x 1864 (0.05)	3314 x 1864 (1.78)

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	j.dejure.org/jcg/einzelseite-75.js line 167, col 6

●Uses HTTPS

●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

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

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
div#alpha > div#Absatz > div#Absatztext > a.close `div#alpha > div#Absatz > div#Absatztext > a.close`
Datenschutzeinstellungen `div#footer > div#footer_inhalt > div.was_ist_dejureorg > a`

To appear in search results, crawlers need access to your app.

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`