Performance

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

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

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

5.13 s

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

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

2.28 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.20 s

Page Load Progression

407 ms

814 ms

1.2 s

1.6 s

2.0 s

2.4 s

2.8 s

3.3 s

Checks

16 PASS 5 REVIEW 2 FIX

JS Execution Cost

Action

4927ms total JS execution

FIX

4927ms total JS execution

https://appsgolem.com/en/: 3269ms CPU time

Unattributable: 1533ms CPU time

https://appsgolem.com/static/js/htmx-2.0.3.min.930...: 126ms CPU time

Main Thread Breakdown

Other 40% Style & Layout 32% Rendering 21% Script Evaluation 4%

Script	Total	Scripting	Parse/Compile	Party
https://appsgolem.com/en/	3269ms	36ms	8ms	1st
Unattributable	1533ms	21ms	0ms	1st
https://appsgolem.com/static/js/htmx-2.0.3.min.93063fe04ea3.js	126ms	112ms	11ms	1st

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.

Image Optimization

45 images, 0 KB saveable

REVIEW

45 images, 0 KB saveable

All images are well-optimized

45 images 325 KB

0 oversized -0 KB

44 legacy format

0 missing dimensions CLS risk

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.

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.

A+

Page Weight Budget

613 KB transferred, 57 requests

PASS

613 KB transferred, 57 requests

Page weighs 1.0 MB (613 KB transferred)

Fonts are 236 KB — consider subsetting or using system fonts

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

Got: 236 KB

57 HTTP requests

Estimated 0.13 g CO2 per page load

613 KB transferred

57 requests

0.13 g CO2 per page load

Images 324.9 KiB 53%

Fonts 236.0 KiB 38%

HTML 20.4 KiB 3%

JavaScript 16.2 KiB 3%

CSS 12.7 KiB 2%

Other 2.9 KiB 0%

0 2.4 MB 4.9 MB

Under budget

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

A+

Third-Party Impact

No third-party resources

PASS

No third-party resources

No third-party resources detected

No third-party resources detected — all resources are first-party.

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are properly compressed.

A+

Font Loading

5 fonts (236 KB)

PASS

5 fonts (236 KB)

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

Web fonts

236 KB total

Render-blocking

of 5

Dominant font-display

swap

Most common across fonts

Font loading timeline

Transfer FOIT (block) FOUT (swap)

inter-Cp50SjIa1ZL7.260c... woff2 swap

Size 48 KB

Load time 48 ms

Start 187 ms