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

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.

2.25 s

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

3.41 s

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

0 ms

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

0.022

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

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

3.42 s

Page Load Progression

606 ms

1.2 s

1.8 s

2.4 s

3.0 s

3.6 s

4.2 s

4.8 s

Checks

10 PASS 6 REVIEW 3 FIX

Page Weight Budget

Action

3.7 MB transferred, 295 requests

FIX

3.7 MB transferred, 295 requests

Page weighs 4.7 MB (3.7 MB transferred)

Images are 1.5 MB — compress or use modern formats

Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.

Got: 1.5 MB

CSS is 1.1 MB — consider purging unused styles

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

Got: 1.1 MB

JavaScript is 861 KB — consider code splitting or lazy loading

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

Got: 861 KB

Fonts are 239 KB — consider subsetting or using system fonts

Subset fonts to include only used characters, or switch to system font stacks.

Got: 239 KB

295 HTTP requests — consider bundling or reducing

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

Estimated 0.77 g CO2 per page load

3.7 MB transferred

295 requests

0.77 g CO2 per page load

Images 1.5 MiB 40%

CSS 1.1 MiB 29%

JavaScript 861.2 KiB 23%

Fonts 239.2 KiB 6%

Other 47.2 KiB 1%

HTML 28.1 KiB 1%

Other 3.1 KiB 0%

Other 624 B 0%

Other 0 B 0%

0 2.4 MB 4.9 MB

Over budget

Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.

Why this matters

Image bandwidth is high — modern formats (WebP/AVIF) and resizing typically cut it 50%+.

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

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

Subset fonts to include only used characters, or switch to system font stacks.

Why this matters

Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).

Source: web.dev font loading

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

JS Bundles

Action

45 scripts, 362 KB unused

FIX

45 scripts, 362 KB unused

https://gesafe-hennel.de/components/com_baforms/as...: 102 KB unused (76%)