Banja Lab / Benchmarks / Test
WEB-0001Websites · medium
Landing page with a working mobile nav toggle
The same task, run on 28 models. Compare the outputs side by side, or open any one in a popup to inspect it.
Top result: claude-opus-4-8 (high reasoning) at 100.0% composite. Lowest: claude-haiku-4-5 at 23.4%. 28 models compared on this task.
How it ran
- Each model was given the brief below in a fresh, isolated session with no access to our tools, and returned a single self-contained index.html (inline CSS and JS, no external requests, no build step).
- The rendered output was scored 1 to 5 on brief fidelity, visual design, craft, and impact by a four-family vision panel - Anthropic (Claude Opus 4.8), OpenAI (GPT-5.5), Google (Gemini 3.1 Pro), and xAI (Grok 4.3) - using one identical prompt so the scores compare. The published judge score is leave-one-family-out: a model is never scored by a judge of its own family, so same-family self-preference is removed.
The brief
Build a single self-contained landing page as one HTML file (`index.html`) that renders with no build step and no network calls (inline all CSS and JS, no external fonts or scripts). Requirements: - three sections: a hero with a single main heading, a features grid with at least three feature items, and a footer, - a navigation menu that is collapsed by default and a hamburger toggle button (give the button id="nav-toggle" and the nav id="site-nav"), and - clicking the hamburger must open the menu (make it visible), and clicking it again must close the menu (hide it). Keep the button's accessible state in sync (aria-expanded) and update its label. Use plain, readable, accessible markup.
