Skip to content
https://biapo.com

Performance

· 25 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.
SCORE
95
GRADE
A
FIX
1
REVIEW
5
PASS
17
INFO
2

Performance-focused optimization plan with CWV assessment, top offenders, and time estimates

Mobile Desktop
100
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
95
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
54
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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

774 ms

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

774 ms

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

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

774 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

774 ms

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
25
17 PASS 5 REVIEW 1 FIX
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
HTTP/3 (QUIC)
HTTP/3 not advertised
REVIEW
HTTP/3 not advertised
Info::
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.
C
Compression Algorithm
Action
Main response served uncompressed
REVIEW
Main response served uncompressed
Info::
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::
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::
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.
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW

Green Hosting

No green hosting detected

A+
Page Weight Budget
1 KB transferred, 2 requests
PASS
1 KB transferred, 2 requests
Info::
Page weighs 1 KB (1 KB transferred)
Info::
2 HTTP requests
Info::
Estimated 0.00 g CO2 per page load
1 KB / 2.4 MB budget
1 KB transferred
2 requests
0.00 g CO2 per page load
HTML 596 B 67%
Other 287 B 33%
0 2.4 MB 4.9 MB
Under budget
A+
Third-Party Impact
No third-party resources
PASS
No third-party resources
Info::
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
Info::
All text resources are compressed
All text resources are properly compressed.
A+
Image Optimization
No images on this page
PASS
No images on this page
Info::
No images on this page
0 images 0 KB
0 oversized -0 KB
0 legacy format
0 missing dimensions CLS risk
A+
JS Execution Cost
76ms total JS execution
PASS
76ms total JS execution
Info::
Unattributable: 76ms CPU time
Warning::
Third-party scripts: 76ms (100% of total)

Main Thread Breakdown

Other 72% Style & Layout 12% Script Evaluation 11%
ScriptTotalScriptingParse/CompileParty
Unattributable76ms5ms0ms3rd
A+
Font Loading
No web fonts (system fonts)
PASS
No web fonts (system fonts)
Info::
No web fonts loaded — system fonts are fastest
No web fonts loaded — system fonts are optimal.
A+
JS Bundles
No JavaScript
PASS
No JavaScript
Info::
No JavaScript bundles
No JavaScript files loaded.
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+
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
2 server-response signal(s) detected
PASS
2 server-response signal(s) detected
Info::
`Vary` header declared: Accept-Encoding
The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
Info::
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+
Page Weight Inventory
2 resources · 1 KB · 0 KB savings available
PASS
2 resources · 1 KB · 0 KB savings available
Info::
Within 1MB page-weight target
Got: 1 KB
2 resources · 883 B · 0 third-party Within 1MB page-weight target
Document 67% · 596 B
Image 33% · 287 B
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+
JavaScript Blocking
No render-blocking JS or document.write usage detected
PASS
No render-blocking JS or document.write usage detected
Info::
No JavaScript blocking issues 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
Network Waterfall
2 requests over 130ms
INFO
0 ms 200 ms 400 ms 600 ms 800 ms FCP 774 ms LCP 774 mshttps://biapo.com// https://biapo.com/ — 200 — 596 B — 84 ms — http/1.1https://biapo.com/favicon.ico/favicon.ico https://biapo.com/favicon.ico — 200 — 287 B — 23 ms — http/1.1
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
100% of JavaScript execution is third-party
First-party Third-party 76ms · 0KB · $1/mo
Unattributable
Other
Optional
Execution 76ms
Transfer 0 KB
Monthly Cost $1/mo

100% 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

How third-party costs are calculated

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

Send Feedback