Skip to content

fix(site): improve performance, accessibility, and site reliability - #5

Merged
xhd0728 merged 5 commits into
mainfrom
codex/site-quality-audit
Nov 10, 2026
Merged

xhd0728 merged 5 commits into
mainfrom
codex/site-quality-audit

Conversation

@xhd0728

@xhd0728 xhd0728 commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

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.

  • Add responsive WebP assets, intrinsic media dimensions, hero priority, lazy secondary media, and on-demand article videos. Keep mobile actions above the artwork and remove tablet/narrow-desktop overflow.
  • Restore the mobile drawer header and keyboard dismissal/focus handling; make desktop dropdowns and carousel controls keyboard accessible. Improve contrast, heading structure, document language, sharing metadata, and the quick-start commands.
  • Cancel both demo response phases on session changes/unmount, fix asynchronous code copying, support IME composition, label controls, and clearly identify pre-recorded responses.
  • Initially render seven populated paper dates, retain history navigation/load-more, and add request cancellation, timeout/retry, and safe external links.
  • Update the audit/preview/image tools and vulnerable transitive packages; test patched worker, serialization, and SockJS UUID dependencies. Reduce npm audit findings from the main branch's 58 affected entries to 5 low entries, with no moderate/high/critical entries. The remaining upstream deepmerge advisory is documented in the audit.
  • Add regression tests, strict production link/asset checks, reproducible Lighthouse commands, and PR CI report artifacts. Deployments remain limited to pushes to main.
Homepage profile Before: P / A / BP / SEO After: P / A / BP / SEO
Mobile 92 / 96 / 96 / 92 97 / 100 / 96 / 100
Desktop 100 / 96 / 96 / 92 100 / 100 / 96 / 100

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

Desktop homepage

Mobile homepage

@xhd0728 xhd0728 changed the title fix(site): improve performance, accessibility, and demo reliability fix(site): improve performance, accessibility, and site reliability Nov 10, 2026
@xhd0728
xhd0728 merged commit 72f6863 into main Nov 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant