Repository navigation
fix: preserve theme and Gravatar geometry, streamline font loading - #81
Merged
Merged
Conversation
This was referenced Oct 16, 2026
Preserve the established typefaces and complete Fontsource Unicode coverage. Share Noto variable glyph subsets across weights and keep prose fonts off Home, using Astro's generated CSS, assets and fallback metrics. Refs #85
Refs #85. Reuse the pinned Lighthouse harness with one immutable Docs snapshot for both builds and retain raw audit evidence.
6 tasks
Refs #85. Preserve the maintained variable Fontsource stylesheet rather than adding 79KB of Unicode declarations to every HTML document.
Refs #85. Record the accepted controlled comparison and keep the Home stylesheet unchanged.
Refs #85. Keep small Unicode shards external instead of Vite data URL inlining; retain the existing font-src policy.
Refs #85. Only the high-priority above-fold cover uses synchronous decoding; lazy decorative/list images remain asynchronous.
Refs #85. Retain default simulated scoring, allow the existing harness to measure real throttled navigation, and remove the unproven critical decoding change.
Refs #85. Use the cover aspect ratio for image height rather than a cyclic grid percentage; keep contain scaling.
ooMia
marked this pull request as ready for review
October 16, 2026 17:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Home 초기 로딩의 CSS·폰트 비용을 줄이고, Gravatar 카드의 여백과 테마 변경 직후 이동 시 선택이 유실되는 문제를 고칩니다. 모바일 LCP·화면 밀림은 일부 실행에서 재발하여 미해결이며, #85 완료를 주장하지 않습니다. 반복 실험은 중단하고 근거를 기록했습니다.
useTheme().setTheme를 클릭 시 동기 호출하여 즉시 Home↔Article로 이동해도 선택이 유지됩니다. 같은 provider/bootstrap을 사용합니다.font-src 'self'를 지킵니다. 폰트의 data URL 인라이닝으로 발생한 실제 CSP 실패를 고쳤으며 정책을 완화하지 않았습니다.검증:
5a2eaff17e6a8136d32c4eb9a32211adde0b9317을 사용했습니다.성능 결과와 제한:
4431d23과 viewport별 각 3회, request-level throttling으로 측정했습니다. 모바일 중앙값 FCP 1.841→1.648s, LCP 2.381→2.256s, Performance 97→98입니다.이 결과는 Home의 제한된 비교이며 모든 Article이나 공개 Pages CDN을 대표하지 않습니다. main 병합·Pages 배포·공개 MIME/보안 헤더·공개 성능 검증은 수행하지 않았습니다.
Refs #56
Refs #82
Refs #83
Refs #85