You wrote the same sentence five ways and called it clarity.

The page keeps repeating variants of “understand systems by simulating them” (headings: “Understand how systems behave —by simulating them”, “Understand Systemsby Watching Them Behave”, “See real behavior, not diagrams”). There are typos/spacing errors (“Systemsby”), a stray “Loading…”, and duplicated metric blocks — it reads like half-baked copy pasted together.

Hero rewrite. Replace the jumble with a single clean headline + subhead: Headline: “Simulate real system behavior — not diagrams.” Subhead: “Run live load, inject failures, and watch latency, queues, and retries unfold—interactive lessons for engineers.” Remove duplicate metric/​

You speak engineer, which is good — but you never say which engineer.

Copy uses technical concepts (backpressure, token bucket, p99) so it’s aimed at engineers, but there’s no explicit signal about seniority or learning goal (practice interview? onboard new hires? master architecture patterns?). Lines like “Build intuition engineers use to explain systems clearly” hint at outcomes but don’t commit.

Add a single audience line under the hero: “For junior-to-mid backend engineers and SREs who need hands‑on system-design intuition fast.” If you want to target interviews, add a second micro-line: “Includes interview-style scenarios.”

Promises ‘more than a course’ and ‘less than a coffee’ but never explains what you actually finish with.

You claim ‘40+ interactive concepts’ and ‘5 scenarios. One engineering mindset.’ but don’t say what a learner achieves (can design a reliable service? pass interviews? debug production?). The line ‘Build intuition faster’ is hopeful, not measurable. Also the coffee metaphor (‘Less than a coffee.More than a course.’) is cute but vague.

Concrete value line: “Master 40+ system‑design concepts through 5 hands‑on scenarios — gain deployable intuition in 60 minutes, not slides.” Add a short outcome bullet list: “After one scenario you’ll be able to: identify backpressure, pick a rate‑limit strategy, and reason about

You show numbers that look like fake metrics and then bail on evidence.

The page repeats metrics (latency, throughput, uptime) but there’s no context or provenance. No logos, no testimonials, no team or case studies. ‘Free to start · No credit card required’ helps, but it isn’t social proof or credibility.

Add three trust elements in the hero strip: (1) small logo row (“Used by teams at …”) or ‘Trusted by 1,200 engineers’ (use real data), (2) one short testimonial: “SystemDecoder made system design click — I can now reason about backpressure.” —Jane, SRE at Acme, (3) a short footer

Too many CTAs and theatrical copies like ‘Enter the Arena’ vs bland ‘Start Exploring’ — pick a personality.

Buttons list shows many competing CTAs: “Start Exploring”, “Get Started”, “Enter the Arena”, “Unlock All →”, “Get Premium”. The hero doesn’t force a clear next step. Also no time-to-value in the primary CTA (what happens when I click?).

Pick a primary and one secondary. Primary button text: “Start a 10‑minute simulation — Free” (prominent, top-left). Secondary: “See concepts” (scrolls to the 40+ concepts). Move sign-in to top-right: “Sign in” and a small “Continue with Google” option.