Wumty vs Next.js

Next.js and Wumty are both excellent tools - for different jobs. Next.js is a full-stack React framework designed for web applications. Wumty is a collection of Astro templates designed for content sites. Understanding the difference helps you pick the right tool and avoid over-engineering your project.

Architecture Comparison

The core difference is what happens when someone visits a page.

Next.js ships the React runtime (80-90KB gzipped minimum) on every page. Even with Server Components and static generation, the client still receives JavaScript that hydrates the page. This hydration step delays interactivity and can cause layout shifts.

Wumty (Astro) ships zero JavaScript by default. Pages are pre-built as static HTML at build time. When a visitor loads a page, they get HTML and CSS immediately - no JavaScript to download, parse, or execute. Interactive elements (theme toggle, mobile menu) use Astro’s island architecture to load JavaScript only where needed.

Architecture Factor	Next.js	Wumty (Astro)
Default page output	React + HTML	Static HTML only
JavaScript shipped	80-90KB minimum	0KB (unless you add islands)
Hydration required	Yes	No
Build output	Server functions + static	Pure static files
Hosting requirements	Node.js server or edge functions	Any CDN or static host
Framework dependency	React (locked in)	Any (React, Solid, Vue, Svelte, none)

Performance Comparison

We built identical 10-page marketing sites in both frameworks and ran Lighthouse on the production builds.

Metric	Next.js (App Router)	Wumty
Lighthouse Performance	85-92	100
Largest Contentful Paint	1.2-1.8s	0.6-0.9s
Total Blocking Time	80-200ms	0ms
Time to Interactive	1.4-2.0s	0.6-0.9s
JavaScript Bundle	85-120KB	0-5KB
First Contentful Paint	0.9-1.3s	0.4-0.7s

Next.js App Router with Server Components improved performance significantly over Pages Router, but the React runtime still ships. For content pages, that runtime produces zero user-facing benefit while adding measurable load time.

The performance gap widens on mobile. On a 4G connection, every kilobyte of JavaScript adds noticeable delay. Wumty’s zero-JS pages load instantly on any connection speed.

Complexity Comparison

Next.js brings the entire React ecosystem. That is powerful for applications, but it is unnecessary complexity for content sites.

Complexity Factor	Next.js	Wumty
Learning curve	React + Next.js APIs + App Router	HTML + Markdown + optional framework
Build configuration	Webpack/Turbopack + React compiler	Simple Vite-based build
Content management	MDX or headless CMS	Content Collections with Zod validation
State management	React state, context, or external libs	Not needed (static pages)
Routing	File-based + dynamic + API routes	File-based (static)
Build time (15 sites)	25-45 seconds per site	8-15 seconds per site

For a developer building their portfolio, a freelancer making a business site, or an agency shipping client sites, the simpler tool wins. Less complexity means fewer bugs, faster onboarding, and lower maintenance.

SEO Comparison

Both platforms produce HTML that Google can crawl. The differences are in the details.

Next.js SEO requires careful handling of hydration to avoid layout shifts (CLS). Server Components help, but client-side JavaScript can still cause content reflow after initial render. Meta tags and structured data require manual setup or third-party packages.

Wumty SEO is inherently simpler. Static HTML means what Google’s crawler sees is exactly what users see - no hydration, no JavaScript-dependent content, no layout shifts. Meta tags, structured data, sitemaps, and Open Graph tags are generated automatically from content collection schemas.

SEO Factor	Next.js	Wumty
Core Web Vitals	Good (with optimization)	Perfect (by default)
Content stability	Hydration can cause shifts	Static - zero shifts
Structured data	Manual or library	Auto-generated from schemas
Sitemap	Package required	Built-in integration
Build-time validation	Custom setup required	Zod schemas catch errors at build

Use Case Guide

Choose Next.js When:

• You are building a web application (dashboards, SaaS, e-commerce with complex cart logic)
• You need server-side logic (API routes, authentication, database queries)
• You need middleware for request-level processing
• Your team is deeply invested in the React ecosystem
• Real-time features are core to your product

Choose Wumty When:

• You are building a content site (blog, portfolio, marketing site, service business)
• Performance and SEO are top priorities
• You want the simplest path to 100/100 Lighthouse scores
• You are building templates or multi-site systems for clients
• You want framework flexibility instead of React lock-in
• You prefer one-time pricing over ongoing infrastructure costs

The decision is about matching the tool to the job. Next.js is a Swiss Army knife. Wumty is a scalpel for content sites - purpose-built, sharper, and faster for the specific task.

Framework Flexibility

One of Astro’s underappreciated advantages is framework freedom. Next.js locks you into React for every component. Astro lets you choose per-component.

Wumty templates use SolidJS for interactive islands because it compiles to 1/4 the bundle size of React. But you can swap to React, Vue, Svelte, or Preact for any component without changing your page templates. You can even mix frameworks on the same page.

This means if React’s direction changes (as it has with Server Components, Suspense, and the compiler), your content site is not forced to follow. Your pages are static HTML. Only the interactive islands depend on a framework, and those can be swapped independently.

Frequently Asked Questions

Is Next.js bad for content sites?

Not bad - just overkill. Next.js ships the React runtime on every page, even static ones. For content sites where 95% of pages are static text and images, that runtime is pure overhead. Wumty eliminates it entirely. For a detailed technical comparison, read our Astro vs Next.js deep dive.

Can I use React components with Wumty?

Yes. Astro’s island architecture supports React, SolidJS, Vue, Svelte, and Preact. You can use React for interactive components while keeping the rest of your site as zero-JS static HTML.

What if I need API routes or authentication?

Use Next.js. If your site needs server-side logic, database queries, or complex authentication flows, Next.js is the right tool. Wumty is purpose-built for content sites, not web applications.

---

Build content sites with the right tool. Start with the free Starter Kit and see what zero-JS performance feels like. Or explore our template pricing to find the right plan for your project.