Banja Lab / Benchmarks / Test
SCREE-0005Websites · hard
Reproduce the Banja home page hero from its screenshot
The same task, run on 27 models. Compare the outputs side by side, or open any one in a popup to inspect it.
Top result: grok-build-0.1 (default reasoning) at 93.7% composite. Lowest: claude-fable-5 at 71.1%. 27 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
You are given a reference screenshot of a real marketing home page (the Banja home page hero). Reproduce it as faithfully as you can as ONE self-contained HTML file (`index.html`) that renders with no build step and no network calls (inline all CSS, no external fonts, scripts, or images). Match what the screenshot shows: - a very dark, near-black background (around #0a0a12) with a faint grid pattern, - a top bar with the word-mark "Banja" on the left (in a violet/purple accent), a centre navigation row with the links About, Services, Products, Case Studies, Lab, Contact Us, and a white rounded pill button on the right reading "Let us pitch to you", - a large centred hero heading on two lines: "WE BUILD" in white, then "PRODUCTS." in a violet-to-pink gradient (use a single <h1>), - a muted sub-heading reading: For founders who move fast. Idea to product in weeks, not months. with the phrase "Idea to product in weeks" emphasised in white, - two call-to-action buttons below: a solid white "START A PROJECT" button and an outlined "VIEW OUR WORK" button. Keep the colours, the centred layout, and the relative sizes close to the screenshot. Use plain, readable, accessible markup. The page must stay readable when the window is narrowed (responsive).
