Skip to content

Put benchmark results first and simplify the homepage - #5

Merged
RodCor merged 1 commit into
mainfrom
feat/homepage-benchmarks
Sep 12, 2026
Merged

RodCor merged 1 commit into
mainfrom
feat/homepage-benchmarks

Conversation

@RodCor

@RodCor RodCor commented Sep 12, 2026

Copy link
Copy Markdown
Owner

The homepage buried its benchmark results beneath repeated product explanations. It now opens with a short introduction and a prominent benchmark panel: BEAM 100K at 73.3% versus a 62.3% flat-retrieval baseline on the same 400 probes, LoCoMo at 89.4%, and LongMemEval S at 83.0% on a 200-question stratified slice. Sample sizes, historical-run context, and methodology links accompany the scores.

The remaining page follows one sequence: how it works, installation, About, and Contact. Repeated feature cards, FAQ, sharing illustration, project grid, and slogans are removed from the homepage. Projects remain accessible through navigation and About. Benchmarks lead the navigation and link to the homepage results. The page also uses the layout's existing main landmark instead of nesting another one.

Corrects the linked documentation's outdated Mem0 BEAM 1M figure from 62% to the currently reported 64.1%, with the check date and differences in reader and sample size stated. Source: https://mem0.ai/blog/ai-memory-benchmarks-in-2026

Validation: npm run check passed, including lint, TypeScript, all 29 tests, production export, and required static routes. Browser checks passed in both themes at widths from 320 to 1440 pixels, with no WCAG A/AA violations or horizontal overflow. Verified visible benchmark scores, source links, cross-page anchor navigation, copied installation commands for all five hosts, LinkedIn destination, and rendering without JavaScript. Reviewed desktop and mobile screenshots.

@RodCor
RodCor merged commit ebc0023 into main Sep 12, 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