Put benchmark results first and simplify the homepage - #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 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 checkpassed, 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.