Repository navigation
fix(site): improve performance, accessibility, and site reliability - #5
Merged
Merged
Conversation
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.
The website hid the mobile navigation's close control, downloaded oversized media, and allowed demo response timers to outlive the active chat. This PR preserves the existing branding while improving loading, responsive layouts, keyboard access, and demo reliability.
These are sequential Lighthouse 13.6.0 runs against both production builds on the same compressed local server (Chrome 157, default device profiles). The latest optimized mobile run scored 97. Mobile LCP improved from 3.37 s to 2.42 s, and observed homepage requests during the audit fell from about 1,053 KiB to 489 KiB. The demo scored 100 on mobile and desktop, with accessibility/SEO 100 and CLS 0.
The remaining local best-practices deduction comes from a blocked Google Analytics collection request; analytics was retained. These measurements do not claim that this branch is already deployed or that localhost scores equal field performance.
The latest independent CI run on the shared Ubuntu runner passed all checks. Its Lighthouse results were 88 / 100 / 100 / 100 on mobile and 100 / 100 / 100 / 100 on desktop. The mobile run recorded LCP 2.73 s and TBT 355 ms; the local comparison above uses the same macOS host for both builds. Performance results vary between these environments and are retained as measured. Download the complete CI reports.
Validation: clean
npm ci;npm run check(5 regression tests, successful production build with two SSG workers, and checks across 16 generated HTML pages); browser testing at 320, 390, 768, 1024, and 1440 px, both languages, navigation/keyboard controls, chat/session switching and copying, paper history loading, and release-video playback. The observed paper feed's initial DOM fell from 16,878 to about 1,477 nodes.Full audit and reproduction notes
Desktop and mobile previews