Landing page.

01The brief: speed

MooManage is built for users on rural mobile networks, so performance is a real constraint, not a vanity metric — a slow landing page is the difference between a farmer waiting and a farmer closing the tab before they reach the Play Store link. I treated speed as the brief and owned the whole thing: positioning, copywriting, layout, component architecture, a working email pipeline and deployment.

02The headline: performance

The site scores near the ceiling across the board — and on Core Web Vitals, the metrics that describe what a user actually feels:

• First Contentful Paint 0.4s · Largest Contentful Paint 1.8s
• Total Blocking Time 0ms — interactive the moment it paints
• Cumulative Layout Shift 0.001 — nothing jumps while it loads
• Achieved by explicit image dimensions, lazy-loading below the fold, lean client JS and reflow-free font loading.

03Architecture

A single-page composition of focused, self-contained section components — the main page reads like a table of contents, each section owning its markup, state and interactions. Layout concerns (metadata, social cards, font, notifications) live in the root layout; the contact form posts to a dedicated server route handling real SMTP email via Nodemailer. That separation is what made the polish — smooth-scroll nav, a scroll-aware sticky navbar, an autoplaying carousel — affordable to add cleanly.

04What it demonstrates

Full ownership from copy to deployment, performance as a discipline rather than a default, and a current stack (Next.js 16, React 19, Tailwind v4) — production-grade with real SMTP email, real accessibility and real SEO, one tap from the Play Store.