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
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
C
Compression Algorithm
Action
Main response served uncompressed
REVIEW
Main response served uncompressed
Info::
i
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.
B
Main HTML Cache-Control
No Cache-Control header on main HTML response
REVIEW
No Cache-Control header on main HTML response
Info::
i
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.
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW
Green Hosting
No green hosting detected
A+
Page Weight Budget
668 KB transferred, 36 requests
PASS
668 KB transferred, 36 requests
Info::
✓
Page weighs 2.7 MB (668 KB transferred)
Info::
✓
36 HTTP requests
Info::
i
Estimated 0.14 g CO2 per page load
668 KBtransferred
36 requests
0.14 g CO2 per page load
JavaScript373.8 KiB56%
HTML185.2 KiB28%
Fonts62.0 KiB9%
CSS21.5 KiB3%
Images14.6 KiB2%
Other9.2 KiB1%
Other1.7 KiB0%
Other383 B0%
02.4 MB4.9 MB
Under budget
A+
Text Compression
All text resources are compressed
PASS
All text resources are compressed
Info::
✓
All text resources are compressed
All text resources are properly compressed.
A+
JS Execution Cost
202ms total JS execution
PASS
202ms total JS execution
Info::
i
https://s.go-mpulse.net/boomerang/GSBXY-PQNAK-UCPM...: 77ms CPU time
Info::
i
https://www.googletagmanager.com/gtm.js?id=GTM-59X...: 69ms CPU time
3 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
3
62 KB total
Render-blocking
0
of 3
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
TitlingGothicFBComp-Sta...woffswap
Size20 KB
Load time54 ms
Start417 ms
RiskFOUT — text flashes from fallback to web font
Convert to woff2 for ~30% smaller file size
TitlingGothicFBNarrow-L...woffswap
Size21 KB
Load time40 ms
Start418 ms
RiskFOUT — text flashes from fallback to web font
Convert to woff2 for ~30% smaller file size
TitlingGothicFBNarrow-S...woffswap
Size21 KB
Load time40 ms
Start418 ms
RiskFOUT — 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 ~19 KB and ~38 ms
A+
Resource Caching
All resources properly cached
PASS
All resources properly cached
Info::
✓
No caching issues found
All static resources have appropriate caching headers.
A+
Critical Rendering Path
No render-blocking resources
PASS
No render-blocking resources
Info::
✓
No render-blocking resources detected
A+
Resource Hints
No optimization needed
PASS
No optimization needed
Info::
✓
No resource hint issues
A+
HTTP/3 (QUIC)
HTTP/3 advertised via Alt-Svc
PASS
HTTP/3 advertised via Alt-Svc
Info::
✓
HTTP/3 (QUIC) is supported
First-load mobile users on cellular networks see meaningful latency improvements with HTTP/3. The QUIC transport collapses TLS + TCP handshakes into one and recovers faster from packet loss.
A+
LCP Image Preload
LCP preload audit not available
PASS
LCP preload audit not available
Info::
✓
LCP image preload audit not available for this scan
A+
Server-Timing Observability
3 Server-Timing entries advertised
PASS
3 Server-Timing entries advertised
Info::
✓
Server-Timing header advertises 3 timing entries
A+
Server Response Intelligence
1 server-response signal(s) detected
PASS
1 server-response signal(s) detected
Info::
i
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.
Per-script blocking time, transfer cost, and cache headers
INFO
72%of JavaScript execution is third-party
First-party Third-party146ms · 187KB · €2/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
s.go-mpulse.net
s.go-mpulse.net
Other
77ms
56 KB
50%
€1/mo
Optional
Google Tag Manager
www.googletagmanager.com
Tag Manager
69ms
131 KB
51%
€1/mo
Optional
s.go-mpulse.net
Other
Optional
Execution77ms
Transfer56 KB
Unused50%
Monthly Cost€1/mo
Google Tag Manager
Tag Manager
Optional
Execution69ms
Transfer131 KB
Unused51%
Monthly Cost€1/mo
72% 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
51% of Google Tag Manager'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.