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
F
HTTP Caching
Action
No cache headers
FIX
No cache headers
Warning::
!
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.
B
Page Weight Budget
1.1 MB transferred, 37 requests
REVIEW
1.1 MB transferred, 37 requests
Info::
✓
Page weighs 3.2 MB (1.1 MB transferred)
Warning::
!
JavaScript is 622 KB — consider code splitting or lazy loading
Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
Got: 622 KB
Info::
✓
37 HTTP requests
Info::
i
Estimated 0.24 g CO2 per page load
1.1 MBtransferred
37 requests
0.24 g CO2 per page load
JavaScript622.2 KiB53%
Images358.2 KiB30%
Fonts99.8 KiB8%
CSS55.3 KiB5%
HTML36.7 KiB3%
Other1.7 KiB0%
Other1.0 KiB0%
Other0 B0%
02.4 MB4.9 MB
Under budget
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
C
Document Compression
Action
Document response served uncompressed
REVIEW
Document 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.
B
Server-Timing Observability
No Server-Timing header found
REVIEW
No Server-Timing header found
Info::
i
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.
1 render-blocking <script src> tag(s) without async/defer
Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.
Warning::
!
Total JS execution time is 4.4 s -- over the 3.5s budget
Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.
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+
Image Optimization
9 images, 0 KB saveable
PASS
9 images, 0 KB saveable
Info::
✓
All images are well-optimized
9images358 KB
0oversized-0 KB
0legacy format
0missing dimensionsCLS risk
A+
Font Loading
6 fonts (100 KB)
PASS
6 fonts (100 KB)
Info::
i
6 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
6
100 KB total
Render-blocking
0
of 6
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
font-filewoff2swap
Size17 KB
Load time170 ms
Start1.6 s
RiskFOUT — text flashes from fallback to web font
font-filewoff2swap
Size17 KB
Load time161 ms
Start1.6 s
RiskFOUT — text flashes from fallback to web font
font-filewoff2swap
Size17 KB
Load time164 ms
Start1.6 s
RiskFOUT — text flashes from fallback to web font
font-filewoff2swap
Size17 KB
Load time155 ms
Start1.6 s
RiskFOUT — text flashes from fallback to web font
font-filewoff2swap
Size24 KB
Load time159 ms
Start1.8 s
RiskFOUT — text flashes from fallback to web font
font-filewoff2swap
Size7 KB
Load time163 ms
Start1.8 s
RiskFOUT — text flashes from fallback to web font
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)
A+
Resource Caching
All resources properly cached
PASS
All resources properly cached
Info::
✓
No caching issues found
All static resources have appropriate caching headers.
Each preconnect eagerly opens a TCP+TLS connection. On slow networks or low-end devices, too many parallel connections cause head-of-line blocking and starve the connections that matter for LCP. Trim to the 4-6 highest-value origins (the ones serving render-blocking or LCP resources).
Info::
i
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: https://cdn.zyrosite.com/u1/google-fonts/font-faces?family=Roboto:wght@400;500;600;700&family=Times+New+Roman:wght@400&family=Carlito:wght@400&family=Inter:wght@400;500&display=swap (preconnect+preload).
Info::
✓
Page uses 9 resource hint(s)
Current Resource Hints
preconnect
7
preload
1
dns-prefetch—
prefetch
1
9 resource hints configured
Each preconnect eagerly opens a TCP+TLS connection. On slow networks or low-end devices, too many parallel connections cause head-of-line blocking and starve the connections that matter for LCP. Trim to the 4-6 highest-value origins (the ones serving render-blocking or LCP resources).
Why this matters
Informational: a labeled value pair from the audit.
The same href shouldn't appear in multiple hint rels -- one wins, the others are wasted markup and may confuse cache behavior. Sample: https://cdn.zyrosite.com/u1/google-fonts/font-faces?family=Roboto:wght@400;500;600;700&family=Times+New+Roman:wght@400&family=Carlito:wght@400&family=Inter:wght@400;500&display=swap (preconnect+preload).
Why this matters
Performance issues directly impact user engagement and conversion rates.
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 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.
A+
Render-Blocking Resources
No render-blocking resources detected
PASS
No render-blocking resources detected
Info::
✓
No render-blocking resources detected in <head>
A+
Third-Party Resources
No third-party resources detected
PASS
No third-party resources detected
A+
CSS Performance Depth
No CSS performance depth issues detected
PASS
No CSS performance depth issues detected
Info::
✓
No CSS performance depth issues detected
A+
Green Hosting
Whether the site is served from green-energy infrastructure
PASS
Green Hosting
This site is hosted on green energy infrastructure
Provider: Hostinger
Asset Compression
No text asset hosts to measure
INFO
No text asset hosts to measure
Info::
i
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
37 requests over 4058ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
81%of JavaScript execution is third-party
First-party Third-party3577ms · 594KB · €39/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
www.mcpl.ai
www.mcpl.ai
Other
1976ms
37 KB
—
€21/mo
Costly
www.mcpl.ai
www.mcpl.ai
Other
1046ms
8 KB
—
€11/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
459ms
172 KB
42%
€5/mo
Costly
www.mcpl.ai
www.mcpl.ai
Other
96ms
378 KB
64%
€1/mo
Optional
www.mcpl.ai
Other
Costly
Execution1976ms
Transfer37 KB
Monthly Cost€21/mo
www.mcpl.ai
Other
Costly
Execution1046ms
Transfer8 KB
Monthly Cost€11/mo
Google Tag Manager
Tag Manager
Costly
Execution459ms
Transfer172 KB
Unused42%
Monthly Cost€5/mo
www.mcpl.ai
Other
Optional
Execution96ms
Transfer378 KB
Unused64%
Monthly Cost€1/mo
These scripts may cost more than they're worth
www.mcpl.ai adds 1976ms and costs ~€21/month
www.mcpl.ai adds 1046ms and costs ~€11/month
Google Tag Manager adds 459ms and costs ~€5/month
81% 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
www.mcpl.ai takes 1976ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
www.mcpl.ai takes 1046ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
Google Tag Manager takes 459ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
Why this matters
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
64% of www.mcpl.ai'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.