Performance

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

100

SEO

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

1.26 s

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

2.78 s

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

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

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

2.78 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

15 PASS 7 REVIEW 1 FIX

HTTP Caching

Action

No cache headers

FIX

No cache headers

No Cache-Control header found

Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.

No Cache-Control header

Adding a Cache-Control header can significantly improve repeat-visit performance.

Third-Party Impact

46% third-party, 0 ms blocking

REVIEW

46% third-party, 0 ms blocking

Third-party code accounts for 46% of page weight (123.2 KiB of 265.3 KiB)

Third-party blocking time is low (0 ms)

54%

46%

First-party Third-party

JS Bundles

4 scripts, 51 KB unused

REVIEW

4 scripts, 51 KB unused

https://matomo.pluralog.de/js/container_auoXNaG1.j...: 51 KB unused (42%)

Consider code splitting or tree shaking to reduce unused code.

https://cividata.org/inc/modal.js?v=1790166873: unminified — 5 KB could be saved

Total unused JavaScript: 51 KB

51 KB unused JavaScript

Downloaded but never executed on this page.

Script	Size	Unused	Minified	Party
https://matomo.pluralog.de/js/container_auoXNaG1.js	123 KB	51 KB (42%)	✓	3rd
https://cividata.org/inc/vendor/bootstrap.bundle.min.js	23 KB	—	✓	1st
https://cividata.org/inc/script.js?v=1790166873	4 KB	—	✓	1st
https://cividata.org/inc/modal.js?v=1790166873	15 KB	—	✗	1st

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.

Document Compression

Action

Document response served uncompressed

REVIEW

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

Main HTML Cache-Control

No Cache-Control header on main HTML response

REVIEW

No Cache-Control header on main HTML response

Main HTML response has no Cache-Control header

Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift.

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

A+

Page Weight Budget

265 KB transferred, 15 requests

PASS

265 KB transferred, 15 requests

Page weighs 658 KB (265 KB transferred)

15 HTTP requests

Estimated 0.05 g CO2 per page load

265 KB transferred

15 requests

0.05 g CO2 per page load

JavaScript 165.7 KiB 62%

CSS 37.8 KiB 14%

Fonts 35.3 KiB 13%

Other 15.4 KiB 6%

HTML 11.1 KiB 4%

Other 57 B 0%

Images 0 B 0%

0 2.4 MB 4.9 MB

Under budget

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are properly compressed.

A+

Image Optimization

1 images, 0 KB saveable

PASS

1 images, 0 KB saveable

All images are well-optimized

1 images 0 KB

0 oversized -0 KB

0 legacy format

0 missing dimensions CLS risk

A+

JS Execution Cost

381ms total JS execution

PASS

381ms total JS execution

https://cividata.org/en/: 174ms CPU time

Unattributable: 138ms CPU time

https://matomo.pluralog.de/js/container_auoXNaG1.j...: 68ms CPU time

Third-party scripts: 68ms (18% of total)

Main Thread Breakdown

Other 36% Style & Layout 25% Script Evaluation 22% Script Parsing & Compilation 6% Parse HTML & CSS 6% Rendering 4%

Script	Total	Scripting	Parse/Compile	Party
https://cividata.org/en/	174ms	11ms	5ms	1st
Unattributable	138ms	12ms	0ms	1st
https://matomo.pluralog.de/js/container_auoXNaG1.js	68ms	56ms	11ms	3rd

A+

Font Loading

3 fonts (35 KB)

PASS

3 fonts (35 KB)

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

Web fonts

35 KB total

Render-blocking

of 3

Dominant font-display

swap

Most common across fonts

Font loading timeline

Transfer FOIT (block) FOUT (swap)

yrsa-v3-latin-regular.w... woff2 swap

Size 26 KB

Load time 92 ms

Start 245 ms

Risk FOUT — text flashes from fallback to web font

fa-solid-900-subset.woff woff swap

Size 6 KB

Load time 46 ms

Start 417 ms

Risk FOUT — text flashes from fallback to web font

Convert to woff2 for ~30% smaller file size

fa-brands-400-subset.woff woff swap

Size 4 KB

Load time 42 ms

Start 417 ms

Risk FOUT — text flashes from fallback to web font

Convert to woff2 for ~30% smaller file size

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)

Fixing the unchecked items could save ~3 KB and ~6 ms

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

Resource Hints

3 hints, 0 missing preconnects

PASS

3 hints, 0 missing preconnects

1 dns-prefetch redundant with preconnect on same origin

preconnect already does the DNS lookup; adding dns-prefetch to the same origin is at best a no-op. Sample: https://matomo.pluralog.de. Remove the redundant dns-prefetch entries.

1 URL(s) appear in multiple hints

The same href shouldn't appear in multiple hint rels -- one wins, the others are wasted markup and may confuse cache behavior. Sample: //matomo.pluralog.de (dns-prefetch+preconnect).

Page uses 3 resource hint(s)

Current Resource Hints

preconnect

preload

dns-prefetch

prefetch

—

3 resource hints configured

preconnect already does the DNS lookup; adding dns-prefetch to the same origin is at best a no-op. Sample: https://matomo.pluralog.de. Remove the redundant dns-prefetch entries.

Why this matters

Performance issues directly impact user engagement and conversion rates.

The same href shouldn't appear in multiple hint rels -- one wins, the others are wasted markup and may confuse cache behavior. Sample: //matomo.pluralog.de (dns-prefetch+preconnect).

Why this matters

Performance issues directly impact user engagement and conversion rates.

A+

LCP Image Preload

LCP preload audit not available

PASS

LCP preload audit not available

LCP image preload audit not available for this scan

A+

Server Response Intelligence

1 server-response signal(s) detected

PASS

1 server-response signal(s) detected

No `ETag` or `Last-Modified` -- conditional GET not supported

Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

Page Weight Inventory

15 resources · 265 KB · 51 KB savings available

PASS

15 resources · 265 KB · 51 KB savings available

Within 1MB page-weight target

Got: 265 KB

~51 KB of savings available

3 third-party resources (46% of weight)

15 resources · 265.3 KiB · 3 third-party Within 1MB page-weight target

JavaScript 62% · 165.7 KiB

CSS 14% · 37.8 KiB

Font 13% · 35.3 KiB

Image 6% · 15.1 KiB

Document 4% · 11.4 KiB

Other 0% · 57 B

~51.4 KiB of savings available

Remove unused JavaScript: 51.4 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

15 resources			265.3 KiB

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+

JavaScript Blocking

No render-blocking JS or document.write usage detected

PASS

No render-blocking JS or document.write usage detected

No JavaScript blocking issues detected

A+

CSS Performance Depth

No CSS performance depth issues detected

PASS

No CSS performance depth issues detected

Asset Compression

No text asset hosts to measure

INFO

No text asset hosts to measure

No third-party or subdomain host served enough text assets to measure

Asset compression is measured per host, from one HEAD request against a sampled resource. Pages that serve all their JS and CSS from the document's own origin are covered by the document compression check instead.

Network Waterfall

15 requests over 1553ms

INFO

HTML JavaScript CSS Images Fonts XHR/Fetch Other

Third-Party Script Cost

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

INFO

18% of JavaScript execution is third-party

First-party Third-party 68ms · 123KB · €1/mo

Script	Category	Execution	Transfer	Unused	Monthly Cost	Verdict
Matomo matomo.pluralog.de	Analytics	68ms	123 KB	42%	€1/mo	Optional

Matomo

Analytics

Optional

Execution 68ms

Transfer 123 KB

Unused 42%

Monthly Cost €1/mo

How third-party costs are calculated

Real-User Performance (CrUX)

Field metrics from the Chrome User Experience Report

INFO

Chrome User Experience (CrUX)

Real-user metrics from the Chrome UX Report (2026-08-26 — 2026-09-22)

LCP (p75)

3290 ms

58% good

INP (p75)

140 ms

87% good

CLS (p75)

0.010

81% good

FCP (p75)

3198 ms

TTFB (p75)

2625 ms

Image Optimization

1 images, 0 KB total, 0 KB wasted

INFO

Image Optimization Audit

Total Images

Total Size

0 KB

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