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

SEO

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

4.13 s

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

4.43 s

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

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

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

4.63 s

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

17 PASS 5 REVIEW 1 FIX

Third-Party Impact

Action

100% third-party, 0 ms blocking

FIX

100% third-party, 0 ms blocking

Third-party code accounts for 100% of page weight (257.2 KiB of 257.7 KiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Execution Cost

653ms total JS execution

REVIEW

653ms total JS execution

https://www.google.com/: 389ms CPU time

Unattributable: 162ms CPU time

https://www.gstatic.com/og/_/js/k=og.qtm.en_US.6Gg...: 103ms CPU time

Third-party scripts: 653ms (100% of total)

Main Thread Breakdown

Script Evaluation 30% Other 30% Style & Layout 22% Script Parsing & Compilation 7% Parse HTML & CSS 7%

Script	Total	Scripting	Parse/Compile	Party
https://www.google.com/	389ms	114ms	35ms	3rd
Unattributable	162ms	6ms	0ms	3rd
https://www.gstatic.com/og/_/js/k=og.qtm.en_US.6Gg_vhaORp0.2019.O/rt=j/m=qabr,q_dnp,qcwid,qapid,qads/exm=qaaw,qadd,qaid,qein,qhaw,qhba,qhbr,qhch,qhga,qhid,qhin/d=1/ed=1/rs=AA2YrTscrfpjYlephp7nLsDy1CMPBWZ2ow	103ms	77ms	15ms	3rd

JS Bundles

1 scripts, 55 KB unused

REVIEW

1 scripts, 55 KB unused

https://www.gstatic.com/og/_/js/k=og.qtm.en_US.6Gg...: 55 KB unused (68%)

Consider code splitting or tree shaking to reduce unused code.

Total unused JavaScript: 55 KB

55 KB unused JavaScript

Downloaded but never executed on this page.

Script	Size	Unused	Minified	Party
https://www.gstatic.com/og/_/js/k=og.qtm.en_US.6Gg_vhaORp0.2019.O/rt=j/m=qabr,q_dnp,qcwid,qapid,qads/exm=qaaw,qadd,qaid,qein,qhaw,qhba,qhbr,qhch,qhga,qhid,qhin/d=1/ed=1/rs=AA2YrTscrfpjYlephp7nLsDy1CMPBWZ2ow	82 KB	55 KB (68%)	✓	3rd

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

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

Action

Main HTML max-age=2592000 (~43200min) is aggressive

REVIEW

Main HTML max-age=2592000 (~43200min) is aggressive

Main HTML cached for 43200 minutes -- risks stale auth / SPA state

Long max-age on the main HTML document means users may see outdated auth state, SPA shells, or A/B variants until the cache expires. Consider Cache-Control: no-cache (or max-age=300) for HTML and let your hashed assets (JS/CSS/images) carry the long cache instead.

Got: public, max-age=2592000

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

258 KB transferred, 29 requests

PASS

258 KB transferred, 29 requests

Page weighs 754 KB (258 KB transferred)

29 HTTP requests

Estimated 0.05 g CO2 per page load

258 KB transferred

29 requests

0.05 g CO2 per page load

JavaScript 81.7 KiB 32%

HTML 76.3 KiB 30%

Other 64.7 KiB 25%

Fonts 24.0 KiB 9%

Images 7.3 KiB 3%

CSS 3.4 KiB 1%

Other 358 B 0%

Other 75 B 0%

Other 0 B 0%

0 2.4 MB 4.9 MB

Under budget

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are properly compressed.

Image Optimization

7 images, 0 KB saveable

PASS

7 images, 0 KB saveable

https://fonts.gstatic.com/s/i/productlogos/googleg... is missing width/height — may cause layout shift

Set explicit width and height to prevent CLS.

7 images 7 KB

0 oversized -0 KB

2 legacy format

1 missing dimensions CLS risk

Set explicit width and height to prevent CLS.

Why this matters

Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.

Source: web.dev / Core Web Vitals

A+

Font Loading

1 fonts (24 KB)

PASS

1 fonts (24 KB)

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

Web fonts

24 KB total

Render-blocking

of 1

Dominant font-display

swap

Most common across fonts

Font loading timeline

Transfer FOIT (block) FOUT (swap)

4UaRrENHsxJlGDuGo1OIlJf... woff2 swap

Size 24 KB

Load time 122 ms

Start 645 ms

Risk FOUT — 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

No caching issues found

All static resources have appropriate caching headers.

A+

Critical Rendering Path

No render-blocking resources

PASS

No render-blocking resources

No render-blocking resources detected

A+

Resource Hints

2 hints, 0 missing preconnects

PASS

2 hints, 0 missing preconnects

Page uses 2 resource hint(s)

Current Resource Hints

preconnect

—

preload

dns-prefetch

—

prefetch

—

2 resource hints configured

A+

HTTP/3 (QUIC)

HTTP/3 advertised via Alt-Svc

PASS

HTTP/3 advertised via Alt-Svc

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

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

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.

Page Weight Inventory

29 resources · 258 KB · 55 KB savings available

PASS

29 resources · 258 KB · 55 KB savings available

Within 1MB page-weight target

Got: 258 KB

~55 KB of savings available

28 third-party resources (100% of weight)

29 resources · 257.7 KiB · 28 third-party Within 1MB page-weight target

JavaScript 32% · 81.7 KiB

Document 30% · 77.4 KiB

Other 23% · 59.1 KiB

Font 9% · 24.0 KiB

Image 5% · 12.1 KiB

CSS 1% · 3.4 KiB

~55.1 KiB of savings available

Remove unused JavaScript: 55.1 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

29 resources			257.7 KiB

A+

Render-Blocking Resources

No render-blocking resources detected

PASS

No render-blocking resources detected

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

No JavaScript blocking issues detected

A+

CSS Performance Depth

No CSS performance depth issues detected

PASS

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: Google Cloud

HTTP Caching

max-age=2592000 (4 weeks)

PASS

max-age=2592000 (4 weeks)

Cache-Control header is set

Got: public, max-age=2592000

Effective TTL: 4 weeks (max-age=2592000)

No ETag or Last-Modified header

Conditional requests (304 Not Modified) are not possible without validators.

Cache-Control

public, max-age=2592000

Directive	Value	Meaning
public	—	Any cache may store this response
max-age	2592000	Cache for 4 weeks

Effective TTL: 2592000 seconds

Network Waterfall

29 requests over 2204ms

INFO

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 653ms · 158KB · CA$9/mo

Script	Category	Execution	Transfer	Unused	Monthly Cost	Verdict
www.google.com www.google.com	Other	389ms	76 KB	—	CA$5/mo	Costly
Unattributable Unattributable	Other	162ms	0 KB	—	CA$2/mo	Optional
www.gstatic.com www.gstatic.com	Other	103ms	82 KB	68%	CA$1/mo	Optional

www.google.com

Other

Costly

Execution 389ms

Transfer 76 KB

Monthly Cost CA$5/mo

Unattributable

Other

Optional

Execution 162ms

Transfer 0 KB

Monthly Cost CA$2/mo

www.gstatic.com

Other

Optional

Execution 103ms

Transfer 82 KB

Unused 68%

Monthly Cost CA$1/mo

These scripts may cost more than they're worth

www.google.com adds 389ms and costs ~CA$5/month

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

www.google.com takes 389ms 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

68% of www.gstatic.com'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.

Source: web.dev

How third-party costs are calculated

Image Optimization

11 images, 0 KB total, 0 KB wasted

INFO

Image Optimization Audit

Total Images

Total Size

0 KB

Oversized

10 missing alt text 11 missing dimensions 9 missing lazy loading

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