C — https://bund.de | BeaverCheck Audit

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Several regulatory requirements are not yet met.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Google Search Console · 2306 peers

You 74

Avg 73

At average

0 50 100

Better than 55% of Google Search Console sites See full Google Search Console benchmark →

Apache · 269 peers

You 74

Avg 73

At average

0 50 100

Better than 52% of Apache sites See full Apache benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure

87 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fbund.de)](https://beavercheck.com/results/ef1978c4-b558-4b0a-892b-fb9d2175ea66)

HTML

<a href="https://beavercheck.com/results/ef1978c4-b558-4b0a-892b-fb9d2175ea66"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbund.de" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fbund.de

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 5.2s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

1 accessibility issue excludes users who rely on assistive technology.

Your LCP is 5.2s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

3 critical 7 warning

10 barrier(s) likely increasing bounce by ~39%.

Speed (2)

Page takes 5.2s to load

+12% bounce

Users abandon at ~3s — you're 2.7s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

High main-thread blocking time

+2% bounce

Page is non-interactive for 306ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€450 investment → €3,185/month returns + EUR 120,500,000 risk avoided

Payback period: < 1 month First-year ROI: +8393%

Investment

€450

5h · 5 findings

Monthly returns

€3,185 /mo

~€38,220 / year

Conversions recovered €3,185
Bandwidth savings €0.26

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
DSGVO EUR 20,000,000
EAA EUR 500,000

Payback period

0 12mo 24mo

€135 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€450

5.0 developer hours at €90/hr

Based on Germany rates (€90/hr)

Quick wins

€135 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,003 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveDSGVOEAA

No privacy policy link detected
DSGVO: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
DSGVO: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
DSGVO: EUR 10,000 – EUR 20,000,000

+7 more

Bandwidth Waste

€0.26 /mo

3491.3 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~349 KB per page load
Saves €0.26/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.12 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.17 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

306 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.920

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

11.63 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.62 s

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.9201159999999999] map[node:map[boundingRect:map[bottom:5694 height:956 left:0 right:412 top:4738 width:412] lhId:page-19-FOOTER nodeLabel:footer.footer path:1,HTML,1,BODY,4,P-FOOTER,a,#document-fragment,0,MUSE-FOOTER,a,#document-fragment,1,FOOTER selector:footer.footer snippet:<footer class="footer"> type:node] score:0.563807 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:5392 height:48 left:67 right:143 top:5344 width:76] lhId:page-25-IMG nodeLabel:Logo OZG path:1,HTML,1,BODY,4,P-FOOTER,a,#document-fragment,0,MUSE-FOOTER,3,MUSE-FOOTER-LOGO,0,IMG selector:muse-footer > muse-footer-logo.footer__logo-link > img snippet:<img alt="Logo OZG" src="/portal/media/logo_ozg_18ac90f949.svg" class=""> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:5694 height:956 left:0 right:412 top:4738 width:412] lhId:page-19-FOOTER nodeLabel:footer.footer path:1,HTML,1,BODY,4,P-FOOTER,a,#document-fragment,0,MUSE-FOOTER,a,#document-fragment,1,FOOTER selector:footer.footer snippet:<footer class="footer"> type:node] score:0.251955 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:5392 height:48 left:67 right:143 top:5344 width:76] lhId:page-25-IMG nodeLabel:Logo OZG path:1,HTML,1,BODY,4,P-FOOTER,a,#document-fragment,0,MUSE-FOOTER,3,MUSE-FOOTER-LOGO,0,IMG selector:muse-footer > muse-footer-logo.footer__logo-link > img snippet:<img alt="Logo OZG" src="/portal/media/logo_ozg_18ac90f949.svg" class=""> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:5694 height:956 left:0 right:412 top:4738 width:412] lhId:page-19-FOOTER nodeLabel:footer.footer path:1,HTML,1,BODY,4,P-FOOTER,a,#document-fragment,0,MUSE-FOOTER,a,#document-fragment,1,FOOTER selector:footer.footer snippet:<footer class="footer"> type:node] score:0.058323 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:5392 height:48 left:67 right:143 top:5344 width:76] lhId:page-25-IMG nodeLabel:Logo OZG path:1,HTML,1,BODY,4,P-FOOTER,a,#document-fragment,0,MUSE-FOOTER,3,MUSE-FOOTER-LOGO,0,IMG selector:muse-footer > muse-footer-logo.footer__logo-link > img snippet:<img alt="Logo OZG" src="/portal/media/logo_ozg_18ac90f949.svg" class=""> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:811 height:540 left:12 right:400 top:271 width:388] lhId:page-22-DIV nodeLabel:Help us improve the federal portal! The Federal Portal is a central building b… path:1,HTML,1,BODY,2,P-HEADER,a,#document-fragment,0,P-COOKIE-BANNER,a,#document-fragment,0,DIV selector:div.cookie-banner-container snippet:<div class="cookie-banner-container" data-testid="cookie-banner" lang="EN"> type:node] score:0.023807 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:20 height:18 left:20 right:49 top:2 width:29] lhId:page-29-IMG nodeLabel:Flag of the Federal Republic of Germany path:1,HTML,1,BODY,2,P-HEADER,a,#document-fragment,2,MUSE-HEADER,0,P-HEADER-BANNER,a,#document-fragment,0,SECTION,0,DIV,0,IMG selector:section.header-banner > div > img snippet:<img src="data:image/webp;base64,UklGRkQAAABXRUJQVlA4TDcAAAAvf8JfABcwzgKBJJb9lXaJ+Q/…" alt="Flag of the Federal Republic of Germany" loading="lazy"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:5694 height:5694 left:0 right:412 top:0 width:412] lhId:page-15-BODY nodeLabel:body.is-home path:1,HTML,1,BODY selector:body.is-home snippet:<body class="is-home "> type:node] score:0.019441]]

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.

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
Construction work on a railway line `section.current-topics > div.current-topics__cards > muse-card > img`	/portal/media/small_Foto2_von_Kevin_Seibel_auf_Pixabay_ba...	103.7 KiB	57.7 KiB
Logo NextGenerationEU `muse-footer > muse-footer-logo.footer__logo-link > img.is-image-color`	/portal/media/EN_Funded_by_the_European_Union_RGB_POS_5d7...	37.8 KiB	37.5 KiB
Selfies by the sea `section.current-topics > div.current-topics__cards > muse-card > img`	verwaltung.bund.de/portal/media/small_Pelayo_Arbues_unsplash_258482be33.jpg	78.2 KiB	32.0 KiB
Logo Gründungswoche Deutschland `div.logos-teaser__logos-container > div > a.logos-teaser__logo-link > img.logos-teaser__logo-image`	verwaltung.bund.de/portal/media/thumbnail_gruenderwoche_c28782066d.jpeg	15.6 KiB	12.1 KiB
Logo Das Datenportal für Deutschland GOVDATA `div.logos-teaser__logos-container > div > a.logos-teaser__logo-link > img.logos-teaser__logo-image`	verwaltung.bund.de/portal/media/thumbnail_govdata_0a671bb0b9.jpeg	13.9 KiB	10.4 KiB
Logo Deutschland sicher im Netz `div.logos-teaser__logos-container > div > a.logos-teaser__logo-link > img.logos-teaser__logo-image`	verwaltung.bund.de/portal/media/thumbnail_banner_sicher_im_netz_7e09bbbe48.jpeg	12.7 KiB	9.2 KiB
Logo Gut Leben in Deutschland `div.logos-teaser__logos-container > div > a.logos-teaser__logo-link > img.logos-teaser__logo-image`	/portal/media/thumbnail_gut_leben_in_deutschland_4a5c314d...	12.6 KiB	9.1 KiB
Logo Deutsche Digitale Bibliothek `div.logos-teaser__logos-container > div > a.logos-teaser__logo-link > img.logos-teaser__logo-image`	/portal/media/thumbnail_banner_deutsche_digitale_biblioth...	11.8 KiB	8.2 KiB
Logo wir sind bund `div.logos-teaser__logos-container > div > a.logos-teaser__logo-link > img.logos-teaser__logo-image`	verwaltung.bund.de/portal/media/thumbnail_wir_sind_bund_Logo_fb9c868926.jpeg	11.0 KiB	7.5 KiB
Logo karriere.bund.de `div.logos-teaser__logos-container > div > a.logos-teaser__logo-link > img.logos-teaser__logo-image`	verwaltung.bund.de/portal/media/thumbnail_karriere_bund_klein02_b115201d42.png	10.6 KiB	7.0 KiB
Logo Deutschland Digital Sicher BSI `div.logos-teaser__logos-container > div > a.logos-teaser__logo-link > img.logos-teaser__logo-image`	/portal/media/thumbnail_banner_bsi_fuer_buerger_d71c7d78d...	10.0 KiB	6.4 KiB
Logo Stiftung Datenschutz `div.logos-teaser__logos-container > div > a.logos-teaser__logo-link > img.logos-teaser__logo-image`	/portal/media/thumbnail_banner_stiftungdatenschutz_ce0f5e...	9.1 KiB	5.6 KiB
Mother holding the hand of her infant `section.current-topics > div.current-topics__cards > muse-card > img`	/portal/media/small_mariano_rivas_WA_5g_C3_h78_unsplash_0...	31.0 KiB	4.6 KiB
Thoughtful woman `section.current-topics > div.current-topics__cards > muse-card > img`	/portal/media/small_denys_nevozhai_z0n_Vqfr_Oq_WA_unsplas...	28.6 KiB	4.3 KiB

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:5584.378 label:Time to first byte subpart:timeToFirstByte] map[duration:1783.316 label:Resource load delay subpart:resourceLoadDelay] map[duration:165.565 label:Resource load duration subpart:resourceLoadDuration] map[duration:21.822 label:Element render delay subpart:elementRenderDelay]]

lhId: page-14-IMG

nodeLabel: img.start-stage__background-image

path: 1,HTML,1,BODY,3,MAIN,0,P-START-PAGE,a,#document-fragment,0,SECTION,0,P-START-STAGE,a,#document-fragment,0,SECTION,0,DIV,0,P-RESPONSIVE-IMAGE,a,#document-fragment,0,IMG

selector: img.start-stage__background-image

snippet: <img srcset="/portal/media/thumbnail_header_image_bundesportal_1_francesco_luca_labianc…" src="/portal/media/small_header_image_bundesportal_1_francesco_luca_labianca_s6…" sizes="100dvw" alt="" class="start-stage__background-image">

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-14-IMG

nodeLabel: img.start-stage__background-image

path: 1,HTML,1,BODY,3,MAIN,0,P-START-PAGE,a,#document-fragment,0,SECTION,0,P-START-STAGE,a,#document-fragment,0,SECTION,0,DIV,0,P-RESPONSIVE-IMAGE,a,#document-fragment,0,IMG

selector: img.start-stage__background-image

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

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.6 s

URL	Time Spent
bund.de/	807 ms
verwaltung.bund.de/	763 ms
verwaltung.bund.de/portal/	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
footer.footer `footer.footer`	0.564
footer.footer `footer.footer`	0.252
footer.footer `footer.footer`	0.058
Help us improve the federal portal! The Federal Portal is a central building b… `div.cookie-banner-container`	0.024
body.is-home `body.is-home`	0.019
header.header > div.header__main-wrapper > div.header__main > div.header__menu-area `header.header > div.header__main-wrapper > div.header__main > div.header__menu-area`	0.002
header.header > div.header__main-wrapper > div.header__main > div.header__menu-area `header.header > div.header__main-wrapper > div.header__main > div.header__menu-area`	0.000

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 600 ms 136.3 KiB

URL	Transfer Size	Est Savings
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js	218.2 KiB	71.0 KiB
verwaltung.bund.de/leistungsverzeichnis/scripts/lv-search.v3.bundle.js	118.3 KiB	33.1 KiB
verwaltung.bund.de/konto/scripts/konto-frontend/p-58c65092.entry.js	62.1 KiB	32.2 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
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js	1.2 s	942 ms	4.5 ms
Unattributable	563 ms	40 ms	0.0 ms
verwaltung.bund.de/portal/	502 ms	7.4 ms	1.6 ms
verwaltung.bund.de/leistungsverzeichnis/scripts/lv-search.v3.bundle.js	215 ms	208 ms	1.9 ms
verwaltung.bund.de/konto/scripts/konto-frontend/p-bLMYUFxa.js	104 ms	70 ms	0.2 ms
verwaltung.bund.de/konto/scripts/konto-frontend/p-58c65092.entry.js	58 ms	49 ms	1.3 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	1.3 s
Other	848 ms
Style & Layout	346 ms
Rendering	129 ms
Parse HTML & CSS	72 ms
Script Parsing & Compilation	20 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 reason	Failure type
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not 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 4.4 KiB

URL	Transfer Size	Est Savings
html { font-family: sans-serif; text-size-adjust: 100%; } …	33.0 KiB	4.4 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 52.0 KiB

URL	Transfer Size	Est Savings
html { font-family: sans-serif; text-size-adjust: 100%; } …	33.0 KiB	32.0 KiB
:root { --muse-font-family-default: "Fira Sans", sans-serif; --muse-icon-size-xxs: 16px; --muse-ico…	21.1 KiB	20.0 KiB

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

●Use efficient cache lifetimes

●Optimize DOM size

●Font display

●Forced reflow

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify JavaScript

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

●Avoid long main-thread tasks 10 long tasks found

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

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 10 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

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
Privacy Policy `div.cookie-banner > div.cookie-banner-body > p > a`

These are opportunities to improve the legibility of your content.

○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]`s are contained by their required parent element

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

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

●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

●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

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○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

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

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

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 93, col 4387	`Applying inline style violates the following Content Security Policy directive 'style-src 'self' 'nonce-9873936''. Either the 'unsafe-inline' keyword, a hash ('sha256-a+5iQLKgOMjX+/MfqtkveQnjdhaFHQkNmebfh/uZOQI='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 20, col 18884	`Applying inline style violates the following Content Security Policy directive 'style-src 'self' 'nonce-9873936''. Either the 'unsafe-inline' keyword, a hash ('sha256-a+5iQLKgOMjX+/MfqtkveQnjdhaFHQkNmebfh/uZOQI='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 21, col 979	`Applying inline style violates the following Content Security Policy directive 'style-src 'self' 'nonce-9873936''. Either the 'unsafe-inline' keyword, a hash ('sha256-a+5iQLKgOMjX+/MfqtkveQnjdhaFHQkNmebfh/uZOQI='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. The action has been blocked.`
verwaltung.bund.de/konto/scripts/konto-frontend/p-bLMYUFxa.js line 1, col 1581	`Applying inline style violates the following Content Security Policy directive 'style-src 'self' 'nonce-9873936''. Either the 'unsafe-inline' keyword, a hash ('sha256-AcTU+4WjdxTemFkSA7bsI5V8rEl0WiZUMEV2eGEZqKI='), or a nonce ('nonce-...') is required to enable inline execution. The action has been blocked.`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

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.

URL	Map URL
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js
verwaltung.bund.de/leistungsverzeichnis/scripts/lv-search.v3.bundle.js	verwaltung.bund.de/leistungsverzeichnis/scripts/lv-search.C33y4m0T.bundle.js.map

●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

●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

○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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Canonical links suggest which URL to show in search results. Learn more about canonical links.

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

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

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

100

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

649 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

690 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

4 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.004

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

5.59 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

700 ms

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.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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.

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.

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

lhId: page-0-SPAN

nodeLabel: a.link > span.link__content

path: 1,HTML,1,BODY,2,P-HEADER,a,#document-fragment,2,MUSE-HEADER,5,K-ACCOUNT-MENU,0,MUSE-LINK,a,#document-fragment,1,A,1,SPAN

selector: a.link > span.link__content

snippet: <span class="link__content">

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.

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

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

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 40 ms 81.7 KiB

URL	Transfer Size	Est Savings
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js	218.2 KiB	81.7 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
Internal error.	Not actionable

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

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: 407 ms

URL	Time Spent
bund.de/	200 ms
verwaltung.bund.de/	207 ms
verwaltung.bund.de/portal/	0.0 ms

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Time to Interactive 0.7 s

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 228 KiB

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.2 s

●Avoid long main-thread tasks 1 long task found

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

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 10 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

100

Accessibility

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

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

●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

●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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○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

○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

○Heading elements appear in a sequentially-descending order

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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

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

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 758, col 1711	`ApiError: Generic Error at MI (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:2993) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:3268`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 758, col 1868	`ApiError: Generic Error at MI (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:2993) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:3268`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 758, col 2047	`ApiError: Generic Error at MI (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:2993) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:434:3268`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 628, col 1155	`ApiError: Generic Error at tO (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:7971) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:8246`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 1931, col 11493	`ApiError: Generic Error at tO (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:7971) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:8246`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 713, col 1278	`ApiError: Generic Error at tO (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:7971) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:8246`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 289, col 1079	`ApiError: Generic Error at tO (https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:7971) at https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js:126:8246`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780213.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780216.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/footer	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/header	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/main-navigation	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/i18n/locales	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/start-page-deep	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780197.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/konto/scripts/konto-frontend/konto-frontend.esm.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/leistungsverzeichnis/scripts/lv-search.v3.bundle.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/api/frontend-config	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780186.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780202.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780200.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780201.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780185.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780187.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378084.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378033.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378056.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378037.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780147.js	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/header/	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/cms/api/EN/main-navigation/	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/img/favicon-32-4964ce435000594d79f4beb52f131baa.png	`Failed to load resource: the server responded with a status of 429 ()`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 91, col 20723	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780147.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780185.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780186.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780187.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780197.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780197.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780200.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780201.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780202.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 12, col 661	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780213.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 2046, col 12794	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780216.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 91, col 20723	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378033.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 91, col 20723	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378037.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 91, col 20723	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378056.js`
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js line 91, col 20723	`TypeError: Failed to fetch dynamically imported module: https://verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-293378084.js`

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
verwaltung.bund.de/portal/public/assets/portal-frontend.2.0.0-2933780.js

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

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Canonical links suggest which URL to show in search results. Learn more about canonical links.

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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

Results for https://bund.de

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Usability (2)

Content (3)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts