https://cyan-lapwing-837262.hostingersite.com

Performance

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

100

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.

1.83 s

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

3.41 s

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

86 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.015

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

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

3.41 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 2 FIX

Page Weight Budget

Action

2.7 MB transferred, 46 requests

FIX

2.7 MB transferred, 46 requests

Page weighs 2.9 MB (2.7 MB transferred)

46 HTTP requests

Estimated 0.56 g CO2 per page load

2.7 MB transferred

46 requests

0.56 g CO2 per page load

Other 1.7 MiB 64%

Images 807.0 KiB 29%

Fonts 101.5 KiB 4%

HTML 44.2 KiB 2%

JavaScript 27.1 KiB 1%

Other 1.6 KiB 0%

CSS 1.1 KiB 0%

Other 630 B 0%

0 2.4 MB 4.9 MB

Over budget

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.

ETag present — enables conditional (304) responses

No Cache-Control header

Adding a Cache-Control header can significantly improve repeat-visit performance.

JS Execution Cost

Action

1785ms total JS execution

REVIEW

1785ms total JS execution

https://cyan-lapwing-837262.hostingersite.com/: 1045ms CPU time

Unattributable: 528ms CPU time

https://cyan-lapwing-837262.hostingersite.com/wp-c...: 109ms CPU time

https://embed.typeform.com/next/embed.js: 104ms CPU time

Third-party scripts: 104ms (6% of total)

Main Thread Breakdown

Other 39% Style & Layout 35% Script Evaluation 12% Rendering 7% Parse HTML & CSS 6%

Script	Total	Scripting	Parse/Compile	Party
https://cyan-lapwing-837262.hostingersite.com/	1045ms	36ms	8ms	1st
Unattributable	528ms	14ms	0ms	1st
https://cyan-lapwing-837262.hostingersite.com/wp-content/themes/tch/assets/js/tch-hero.js?ver=1790095402	109ms	18ms	1ms	1st
https://embed.typeform.com/next/embed.js	104ms	89ms	9ms	3rd

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.

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.

Page Weight Inventory

Action

46 resources · 2.7 MB · 0 KB savings available

REVIEW

46 resources · 2.7 MB · 0 KB savings available

Page weight 2.7 MB exceeds 1 MB target by 1.7 MB

Got: 2.7 MB Expected: ≤ 1 MB

4 third-party resources (1% of weight)

1 resources over 200KB

46 resources · 2.7 MiB · 4 third-party 1.7 MiB over 1MB target

Media 64% · 1.7 MiB

Image 29% · 807.6 KiB

Font 4% · 101.5 KiB

Document 2% · 44.2 KiB

JavaScript 1% · 27.1 KiB

Other 0% · 1.6 KiB

CSS 0% · 1.1 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

46 resources			2.7 MiB

A+

Third-Party Impact

1% third-party, 0 ms blocking

PASS

1% third-party, 0 ms blocking

Third-party code accounts for 1% of page weight (19.9 KiB of 2.7 MiB)

Third-party blocking time is low (0 ms)

99%

First-party Third-party

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are properly compressed.

A+

Image Optimization

27 images, 0 KB saveable

PASS

27 images, 0 KB saveable

All images are well-optimized

27 images 807 KB

0 oversized -0 KB

0 legacy format

0 missing dimensions CLS risk

A+

Font Loading

5 fonts (101 KB)

PASS

5 fonts (101 KB)

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

Web fonts

101 KB total

Render-blocking

of 5

Dominant font-display

swap

Most common across fonts

Font loading timeline

Transfer FOIT (block) FOUT (swap)

inter-400.woff2 woff2 swap

Size 20 KB

Load time 104 ms

Start 70 ms