perf: SSR homepage and load fonts progressively #3
Loading…
Reference in a new issue
No description provided.
Delete branch "perf/homepage-ssr-progressive-fonts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
/, including its poster and useful no-JavaScript content. Hydration adopts that card and continues with the cursor feed without duplication./watch, cache/ETag/gzip behavior, and full FFmpeg caption fonts.Measured results
Three cold Lighthouse 12.8.2 / Chromium 153 runs per case, matched 10-video fixture and simulated mobile network/CPU settings (412×823, 150 ms RTT, 1,638.4 Kbps, 4× CPU). Baseline
972b797; selected candidate includes CSSfeed-progressive-9and JSfeed-progressive-6.LCP is effectively at parity and CLS improves. FCP/TBT are noisy; candidate TBT median is 64 ms higher, so this PR does not claim a TBT improvement. In matched runs Style/Layout is similar and the major earlier regression traced to fonts has been removed. Desktop median LCP improves from 709 ms to 635 ms and font transfer drops from 244,261 B to 117,663 B (52%). See performance report for methods and caveats.
Current screenshots
Verification
just check: 59 tests passed; Ruff lint/format, ty, and FFmpeg render smoke all pass.s-maxage=60, ETag,Vary: Accept-Encoding; gzip response returnedcontent-encoding: gzip./createrenders the existing guest-gated shell. Creator-only operations were not exercised without creator credentials.CI and merge status
.forgejo/workflows/quality.ymlis removed per request; this repository will use its documented local checks (just check, backed by lockeduvdependencies). Historical Forgejo runs were red and their jobs endpoint returned 404, but no new Actions run is expected. The current local check passes. Mobile TBT remains noisy with a modestly higher median, which is documented as a tradeoff; LCP is near baseline and CLS improves.45912f74ade5813cde78