06 // connect
Escape framework bloat: migrate from Next.js to lightweight Astro.
Breaking App Router changes, complex server actions, and runaway hosting costs turned a simple site into a burden. We extract your React into Astro layouts and islands while your CMS stays untouched.
the problem
(01) Upgrade churn
App Router rewrites, caching semantics changes, and server-action complexity consume roadmap after roadmap.
(02) Client-side bloat
Pages that could be static HTML hydrate entire React trees, punishing mobile users on every visit.
(03) Runaway hosting bills
Per-request serverless rendering and image optimization turn marketing traffic into infrastructure invoices.
approach
(01) Component triage
We audit every React component and classify it as static layout, island, or server-rendered — most become static.
(02) Astro layout extraction
Static content moves to zero-JS Astro layouts while genuinely interactive pieces become isolated islands.
(03) CMS preservation
Existing Storyblok content stays intact behind adapted queries and preview wiring; Sanity or Contentful estates are preserved the same way.
(04) Hosting simplification
Edge-cached static output with surrogate-key invalidation replaces per-request rendering and its bill.
scope
(01) Fully migrated production Astro platform
(02) Island inventory documenting what stayed interactive and why
(03) Preserved CMS content with adapted queries and previews
(04) Before-and-after bundle, Lighthouse, and hosting-cost report
Fixed scope, fixed timeline. You keep the report and the roadmap whether or not we build the fix.
why 2sh
Direct systems engineering versus traditional front-end agencies.
| dimension | 2sh | traditional agencies |
|---|---|---|
| JavaScript shipped | 80%+ bundle reduction via static layouts and islands | Same React tree re-shipped under a new theme |
| Upgrade burden | Stable content-driven architecture with minimal churn | Framework upgrade treadmill with breaking changes |
| Hosting model | Edge-cached static with predictable costs | Per-request serverless rendering |
| CMS risk | Existing CMS preserved with adapted queries | Rip-and-replace content migration |
Speak directly with the engineers building your platform.
No account managers. No 6-week discovery slides. Two senior operators inspect your stack, pinpoint bottlenecks, and deliver clean, working code.