Performance

· 22 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

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.

1.07 s

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

1.21 s

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

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

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

1.29 s

Page Load Progression

625 ms

1.3 s

1.9 s

2.5 s

3.1 s

3.8 s

4.4 s

5.0 s

Checks

8 PASS 8 REVIEW 3 FIX

Page Weight Budget

Action

5.4 MB transferred, 114 requests

FIX

5.4 MB transferred, 114 requests

Page weighs 7.7 MB (5.4 MB transferred)

114 HTTP requests — consider bundling or reducing

Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.

Estimated 1.1 g CO2 per page load

5.4 MB transferred

114 requests

1.1 g CO2 per page load

Other 4.2 MiB 78%

Images 610.7 KiB 11%

JavaScript 321.1 KiB 6%

Fonts 134.2 KiB 2%

HTML 54.8 KiB 1%

CSS 45.2 KiB 1%

Other 16.9 KiB 0%

Other 11.2 KiB 0%

Other 0 B 0%

0 2.4 MB 4.9 MB

Over budget

Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.

Why this matters

High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.

Source: web.dev

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 (5.4 MiB of 5.4 MiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

Page Weight Inventory

Action

114 resources · 5.4 MB · 131 KB savings available

FIX

114 resources · 5.4 MB · 131 KB savings available

Page weight 5.4 MB exceeds 1 MB target by 4.4 MB

Got: 5.4 MB Expected: ≤ 1 MB

~131 KB of savings available

113 third-party resources (100% of weight)

1 resources over 200KB

114 resources · 5.4 MiB · 113 third-party 4.4 MiB over 1MB target

Media 78% · 4.2 MiB

Image 11% · 621.8 KiB

JavaScript 6% · 321.1 KiB

Font 2% · 134.2 KiB

Document 1% · 55.0 KiB

CSS 1% · 45.2 KiB

Other 0% · 16.8 KiB

~131.2 KiB of savings available

Remove unused JavaScript: 131.2 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

114 resources			5.4 MiB

Image Optimization

77 images, 0 KB saveable

REVIEW

77 images, 0 KB saveable

All images are well-optimized

77 images 611 KB

0 oversized -0 KB

10 legacy format

0 missing dimensions CLS risk

JS Execution Cost

963ms total JS execution

REVIEW

963ms total JS execution

https://www.webnetz.de/build/assets/site-128f0841....: 419ms CPU time

https://privacy-proxy.usercentrics.eu/latest/uc-bl...: 189ms CPU time

https://www.webnetz.de/: 185ms CPU time

Unattributable: 171ms CPU time

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

Main Thread Breakdown

Script Evaluation 41% Other 27% Style & Layout 19% Rendering 7% Parse HTML & CSS 3%

Script	Total	Scripting	Parse/Compile	Party
https://www.webnetz.de/build/assets/site-128f0841.js	419ms	196ms	0ms	3rd
https://privacy-proxy.usercentrics.eu/latest/uc-block.bundle.js	189ms	173ms	2ms	3rd
https://www.webnetz.de/	185ms	1ms	1ms	3rd
Unattributable	171ms	4ms	0ms	3rd

JS Bundles

15 scripts, 131 KB unused

REVIEW

15 scripts, 131 KB unused

https://www.webnetz.de/build/assets/site-128f0841....: 96 KB unused (63%)

Consider code splitting or tree shaking to reduce unused code.

https://web.cmp.usercentrics.eu/ui/v/3.119.0/WebSd...: 35 KB unused (63%)

Consider code splitting or tree shaking to reduce unused code.

Total unused JavaScript: 131 KB

131 KB unused JavaScript

Downloaded but never executed on this page.

Script	Size	Unused	Minified	Party
https://www.webnetz.de/build/assets/site-128f0841.js	152 KB	96 KB (63%)	✓	3rd
https://web.cmp.usercentrics.eu/ui/v/3.119.0/WebSdk.lib.5ddd9ff8.js	56 KB	35 KB (63%)	✓	3rd
https://web.cmp.usercentrics.eu/ui/loader.js	16 KB	—	✓	3rd
https://www.webnetz.de/build/assets/barlow-v12-latin-600-4ed993c7.js	0 KB	—	✓	3rd
https://www.webnetz.de/build/assets/barlow-v12-latin-500-4ed993c7.js	0 KB	—	✓	3rd
https://privacy-proxy.usercentrics.eu/latest/uc-block.bundle.js	30 KB	—	✓	3rd
https://www.webnetz.de/build/assets/barlow-v12-latin-300-4ed993c7.js	0 KB	—	✓	3rd
https://crm.zoho.eu/crm/javascript/zcga.js	3 KB	—	✓	3rd
https://www.webnetz.de/build/assets/barlow-v12-latin-regular-4ed993c7.js	0 KB	—	✓	3rd
https://web.cmp.usercentrics.eu/ui/v/3.119.0/GdprCmpController.597ef4e9.js	9 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

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

HTTP/3 (QUIC)

HTTP/3 not advertised

REVIEW

HTTP/3 not advertised

HTTP/3 (QUIC) is not advertised

HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.

Compression Algorithm

Action

Main response served uncompressed

REVIEW

Main response served uncompressed

Main HTML response has no Content-Encoding (uncompressed)

The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads.

Server-Timing Observability

No Server-Timing header found

REVIEW

No Server-Timing header found

Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.

Green Hosting

Action

Whether the site is served from green-energy infrastructure

REVIEW

Green Hosting

No green hosting detected

HTTP Caching

max-age=0

REVIEW

max-age=0

Cache-Control header is set

Got: max-age=0

No ETag or Last-Modified header

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

Cache-Control

max-age=0

Directive	Value	Meaning
max-age	0	Cache for 0 seconds

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are properly compressed.

A+

Font Loading

10 fonts (134 KB)

PASS

10 fonts (134 KB)

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

Web fonts

134 KB total

Render-blocking

of 10

Dominant font-display

swap

Most common across fonts

Font loading timeline

Transfer FOIT (block) FOUT (swap)

barlow-v12-latin-300-4e... unknown swap

Size 0 KB

Load time 50 ms

Start 1.2 s