Performance

· 17 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Performance-focused optimization plan with CWV assessment, top offenders, and time estimates

Mobile Desktop

Performance

100

Accessibility

100

Best Practices

SEO

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

3.93 s

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

11.55 s

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

242 ms

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

0.000

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

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

11.67 s

Page Load Progression

375 ms

750 ms

1.1 s

1.5 s

1.9 s

2.2 s

2.6 s

3.0 s

Checks

8 PASS 4 REVIEW 3 FIX

Third-Party Impact

Action

100% third-party, 0 ms blocking

FIX

100% third-party, 0 ms blocking

Third-party code accounts for 100% of page weight (1.9 MiB of 1.9 MiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Bundles

Action

4 scripts, 451 KB unused

FIX

4 scripts, 451 KB unused

https://assets.baden-wuerttemberg.de/versions/5.1....: 451 KB unused (77%)

Consider code splitting or tree shaking to reduce unused code.

Total unused JavaScript: 451 KB

451 KB unused JavaScript

Downloaded but never executed on this page.

Script	Size	Unused	Minified	Party
https://assets.baden-wuerttemberg.de/versions/5.1.0/javascripts/main.js?v=5.1.0	602 KB	451 KB (77%)	✓	3rd
https://assets.baden-wuerttemberg.de/versions/5.1.0/javascripts/head.js	1 KB	—	✓	3rd
https://piwik.baden-wuerttemberg.de/matomo.js	41 KB	—	✓	3rd
https://piwik.baden-wuerttemberg.de/plugins/HeatmapSessionRecording/configs.php?idsite=1&trackerid=8uQhS9&url=https%3A%2F%2Fwww.baden-wuerttemberg.de%2Fde%2Fstartseite	0 KB	—	✓	3rd

Consider code splitting or tree shaking to reduce unused code.

Why this matters

This bundle has high unused code — code-split or tree-shake to ship only what executes.

Source: web.dev / Lighthouse coverage

Page Weight Inventory

Action

23 resources · 1.9 MB · 451 KB savings available

FIX

23 resources · 1.9 MB · 451 KB savings available

Page weight 946 KB over 1MB target

Got: 1.9 MB Expected: ≤ 1 MB

~451 KB of savings available

22 third-party resources (100% of weight)

2 resources over 200KB

23 resources · 1.9 MiB · 22 third-party 945.7 KiB over 1MB target

Image 42% · 834.3 KiB

JavaScript 33% · 643.7 KiB

CSS 12% · 233.2 KiB

Document 8% · 148.9 KiB

Font 6% · 108.7 KiB

Other 0% · 973 B

~450.9 KiB of savings available

Remove unused JavaScript: 450.9 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

23 resources			1.9 MiB

Page Weight Budget

Action

1.9 MB transferred, 23 requests

REVIEW

1.9 MB transferred, 23 requests

Page weighs 6.6 MB (1.9 MB transferred)

JavaScript is 644 KB — consider code splitting or lazy loading

Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.

Got: 644 KB

CSS is 233 KB — consider purging unused styles

Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size.

Got: 233 KB

23 HTTP requests

Estimated 0.40 g CO2 per page load

1.9 MB transferred

23 requests

0.40 g CO2 per page load

JavaScript 643.7 KiB 33%

Images 438.1 KiB 22%

Other 395.2 KiB 20%

CSS 233.2 KiB 12%

HTML 148.9 KiB 8%

Fonts 108.7 KiB 6%

Other 1.1 KiB 0%

Other 627 B 0%

Other 269 B 0%

0 2.4 MB 4.9 MB

Approaching limit

Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.

Why this matters

JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.

Source: web.dev

Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size.

Why this matters

CSS bundle is large — purge unused styles (PurgeCSS, Tailwind JIT) to reduce CSS payload.

Source: web.dev

Image Optimization

6 images, 0 KB saveable

REVIEW

6 images, 0 KB saveable

https://assets.baden-wuerttemberg.de/versions/5.1.... is missing width/height — may cause layout shift

Set explicit width and height to prevent CLS.

is missing width/height — may cause layout shift

Set explicit width and height to prevent CLS.

6 images 438 KB

0 oversized -0 KB

3 legacy format

2 missing dimensions CLS risk

Set explicit width and height to prevent CLS.

Why this matters

Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.

Source: web.dev / Core Web Vitals

Set explicit width and height to prevent CLS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

JS Execution Cost

Action

1742ms total JS execution

REVIEW

1742ms total JS execution

https://assets.baden-wuerttemberg.de/versions/5.1....: 711ms CPU time

https://piwik.baden-wuerttemberg.de/matomo.js: 437ms CPU time

https://www.baden-wuerttemberg.de/de/startseite: 239ms CPU time

Unattributable: 216ms CPU time

https://assets.baden-wuerttemberg.de/versions/5.1....: 77ms CPU time

Third-party scripts: 1742ms (100% of total)

Main Thread Breakdown

Script Evaluation 39% Other 22% Style & Layout 16% Parse HTML & CSS 11% Script Parsing & Compilation 11%

Script	Total	Scripting	Parse/Compile	Party
https://assets.baden-wuerttemberg.de/versions/5.1.0/javascripts/main.js?v=5.1.0	711ms	321ms	168ms	3rd
https://piwik.baden-wuerttemberg.de/matomo.js	437ms	329ms	14ms	3rd
https://www.baden-wuerttemberg.de/de/startseite	239ms	15ms	3ms	3rd
Unattributable	216ms	12ms	0ms	3rd
https://assets.baden-wuerttemberg.de/versions/5.1.0/stylesheets/print.css?v=5.1.0	77ms	0ms	0ms	3rd
https://assets.baden-wuerttemberg.de/versions/5.1.0/stylesheets/main.css?v=5.1.0	63ms	0ms	0ms	3rd

HTTP Caching

no-cache

REVIEW

no-cache

Cache-Control header is set

Got: no-cache

No ETag or Last-Modified header

Conditional requests (304 Not Modified) are not possible without validators.

Cache-Control

no-cache

Directive	Value	Meaning
no-cache	—	Cache but always revalidate first

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are properly compressed.

A+

Font Loading

4 fonts (109 KB)

PASS

4 fonts (109 KB)

4 font(s) use font-display: swap (FOUT risk but functional)

Web fonts

109 KB total

Render-blocking

of 4

Dominant font-display

swap

Most common across fonts

Font loading timeline

Transfer FOIT (block) FOUT (swap)

BaWueSansWeb-Regular.woff2 woff2 swap

Size 24 KB

Load time 180 ms

Start 318 ms

Risk FOUT — text flashes from fallback to web font

BaWueSansWeb-Bold.woff2 woff2 swap

Size 24 KB

Load time 198 ms

Start 319 ms

Risk FOUT — text flashes from fallback to web font

BaWueSerifWeb-Regular.w... woff2 swap

Size 30 KB

Load time 201 ms

Start 322 ms

Risk FOUT — text flashes from fallback to web font

BaWueSerifWeb-Bold.woff2 woff2 swap

Size 31 KB

Load time 220 ms

Start 322 ms

Risk FOUT — text flashes from fallback to web font

Optimization checklist

Preload critical fonts (priority=high)
Use woff2 format for all fonts
Set font-display to swap, optional, or fallback
Subset large fonts (≤100 KB each)

A+

Resource Caching

All resources properly cached

PASS

All resources properly cached

No caching issues found

All static resources have appropriate caching headers.

A+

Critical Rendering Path

No render-blocking resources

PASS

No render-blocking resources

No render-blocking resources detected

A+

Resource Hints

4 hints, 0 missing preconnects

PASS

4 hints, 0 missing preconnects

Page uses 4 resource hint(s)

Current Resource Hints

preconnect

—

preload

dns-prefetch

—

prefetch

—

4 resource hints configured

A+

Render-Blocking Resources

No render-blocking resources detected

PASS

No render-blocking resources detected

No render-blocking resources detected in <head>

A+

Third-Party Resources

No third-party resources detected

PASS

No third-party resources detected

A+

Green Hosting

Whether the site is served from green-energy infrastructure

PASS

Green Hosting

This site is hosted on green energy infrastructure

Provider: Internet AG

Network Waterfall

23 requests over 1595ms

INFO

HTML JavaScript CSS Images Fonts XHR/Fetch Other

Third-Party Script Cost

Per-script blocking time, transfer cost, and cache headers

INFO

100% of JavaScript execution is third-party

First-party Third-party 1742ms · 792KB · €19/mo

Script	Category	Execution	Transfer	Unused	Monthly Cost	Verdict
assets.baden-wuerttemberg.de assets.baden-wuerttemberg.de	Other	711ms	602 KB	77%	€8/mo	Costly
piwik.baden-wuerttemberg.de piwik.baden-wuerttemberg.de	Other	437ms	41 KB	—	€5/mo	Costly
www.baden-wuerttemberg.de www.baden-wuerttemberg.de	Other	239ms	149 KB	—	€3/mo	Costly
Unattributable Unattributable	Other	216ms	0 KB	—	€2/mo	Costly
assets.baden-wuerttemberg.de assets.baden-wuerttemberg.de	Other	77ms	0 KB	—	€1/mo	Optional
assets.baden-wuerttemberg.de assets.baden-wuerttemberg.de	Other	63ms	0 KB	—	€1/mo	Optional

assets.baden-wuerttemberg.de

Other

Costly

Execution 711ms

Transfer 602 KB

Unused 77%

Monthly Cost €8/mo

piwik.baden-wuerttemberg.de

Other

Costly

Execution 437ms

Transfer 41 KB

Monthly Cost €5/mo

www.baden-wuerttemberg.de

Other

Costly

Execution 239ms

Transfer 149 KB

Monthly Cost €3/mo

Unattributable

Other

Costly

Execution 216ms

Transfer 0 KB

Monthly Cost €2/mo

assets.baden-wuerttemberg.de

Other

Optional

Execution 77ms

Transfer 0 KB

Monthly Cost €1/mo

assets.baden-wuerttemberg.de

Other

Optional

Execution 63ms

Transfer 0 KB

Monthly Cost €1/mo

These scripts may cost more than they're worth

assets.baden-wuerttemberg.de adds 711ms and costs ~€8/month
piwik.baden-wuerttemberg.de adds 437ms and costs ~€5/month
www.baden-wuerttemberg.de adds 239ms and costs ~€3/month
Unattributable adds 216ms and costs ~€2/month

100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.

Why this matters

When third-party JS execution time exceeds your own, performance gains from frontend work are capped by code you don't own.

Learn more ▾

Every millisecond of third-party JS competes with your own for main-thread time. If their share is bigger than yours, optimization on your code base barely moves the needle. Audit, defer, or remove third-parties before further frontend optimization. Use Lighthouse's third-party audit to identify the worst offenders.

Source: web.dev

assets.baden-wuerttemberg.de takes 711ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

Source: web.dev

77% of assets.baden-wuerttemberg.de's code is unused. The script may be loading features you don't use.

Why this matters

Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.

Source: web.dev

piwik.baden-wuerttemberg.de takes 437ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

Source: web.dev

www.baden-wuerttemberg.de takes 239ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

Source: web.dev

Unattributable takes 216ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

Source: web.dev

How third-party costs are calculated

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.