Fernside Studio
Background
Archive
Journal Entry

Why Astro Beats Heavy Frameworks for Marketing Sites

Documented
Capacity
9 MIN READ
Domain
Website Performance & Ops

When UK SMB founders ask why Fernside Studio builds exclusively with Astro instead of React, Next.js, or Vue, the answer comes down to one metric: conversion rate. Marketing sites don’t need single-page applications. They need fast load times, clean HTML, and zero unnecessary JavaScript—precisely what Astro delivers.

Here’s why Astro consistently outperforms heavier frameworks for SMB marketing sites, what makes a framework “heavy” in the first place, and when those frameworks actually make sense.

What Makes a Framework “Heavy”

The term “heavy” refers to the amount of JavaScript a framework ships to the browser, measured in kilobytes and ultimately in milliseconds of parse time. Every framework carries overhead—the runtime code needed to make your site interactive.

Current framework bundle sizes (minified + gzipped):

  • Svelte: ~3KB (smallest runtime overhead)
  • Vue 3: ~34KB gzipped
  • React 18.x: ~42KB (react + react-dom combined)
  • Next.js: Adds additional routing and SSR code on top of React
  • Angular: ~130KB gzipped

These figures represent the baseline cost before your actual application code. A simple marketing page built in React ships at minimum 42KB of framework JavaScript—code that parses, compiles, and executes before the user sees interactive content. According to research from LogRocket, this overhead directly impacts Core Web Vitals metrics, particularly Largest Contentful Paint (LCP) and Interaction to Next Paint (INP).

For marketing sites where most content is static—hero sections, testimonials, pricing tables, case studies—this JavaScript overhead solves a problem you don’t have.

Why Marketing Sites Don’t Need Single-Page Applications

Single-page applications (SPAs) excel when you need persistent client-side state, real-time updates, or complex user interactions. Think dashboards, collaboration tools, or web apps where users spend extended sessions manipulating data.

Marketing sites operate differently:

  • Visitors scan pages, read copy, and click CTAs—not manipulating application state
  • Content changes infrequently (monthly or quarterly updates, not real-time data)
  • SEO and initial page speed matter more than client-side routing transitions
  • Bounce rates correlate directly with load time, not JavaScript interactivity

According to Cloudflare’s research, sites loading in one second achieve conversion rates around 3x higher than those requiring five seconds. For B2B SMB sites, this gap widens: a one-second load achieves conversion rates 5x higher than a ten-second load.

Every kilobyte of JavaScript delays this moment. Heavier frameworks ship that overhead by default because they assume you need client-side reactivity everywhere. Astro assumes the opposite: static HTML by default, JavaScript only where genuinely necessary.

How Astro’s Islands Architecture Works

Astro’s core philosophy treats static HTML as the baseline and JavaScript as an exception requiring justification. This approach—called islands architecture—ships zero JavaScript by default and lets you opt in component by component.

What happens at build time:

  1. Astro renders all components to static HTML and CSS
  2. Interactive components (contact forms, accordions, modals) are identified as “islands”
  3. Only those islands ship JavaScript to the browser
  4. The rest of the page remains pure HTML with no runtime overhead

Practical example from a Fernside Studio Site:

A typical marketing page includes a hero section, testimonials carousel, pricing comparison table, FAQ accordion, and contact form. With React or Next.js, all of these components ship JavaScript even though most are static. With Astro:

  • Hero section: Static HTML (0KB JavaScript)
  • Testimonials: Static HTML (0KB JavaScript)
  • Pricing table: Static HTML (0KB JavaScript)
  • FAQ accordion: Interactive island (~2KB JavaScript for toggle functionality)
  • Contact form: Interactive island (~4KB JavaScript for validation and submission)

Total JavaScript shipped: ~6KB instead of 42KB+ baseline framework cost. According to Octahedroid’s 2026 comparison, this architecture delivers measurable improvements in Time to First Byte (TTFB) and Largest Contentful Paint.

Real Performance Benefits (With Numbers)

Theoretical advantages matter less than real-world outcomes. Here’s what Astro’s architecture delivers for marketing sites:

Core Web Vitals benchmarks:

Astro sites consistently achieve “good” ratings across all three Core Web Vitals metrics:

  • LCP (Largest Contentful Paint): Typically under 1.5 seconds (target: under 2.5 seconds)
  • INP (Interaction to Next Paint): Under 100ms (target: under 200ms)
  • CLS (Cumulative Layout Shift): Near zero with proper image sizing (target: under 0.1)

According to Google’s 2026 Core Web Vitals data, only 54.6% of websites pass all three metrics. Astro’s minimal JavaScript approach makes passing straightforward rather than requiring extensive optimisation workarounds.

Conversion rate impact:

When Fernside Studio migrated client sites from WordPress or React-based stacks to Astro + Cloudflare Pages, we observed:

  • Bounce rates dropping 20-35% on average
  • Mobile conversion rates improving 15-28%
  • Organic traffic increasing 12-18% within three months post-migration

These outcomes align with broader industry data. Research cited by SiteBuilder Report shows that landing pages loading in under one second convert at 31.79%, dropping to 29% at three seconds and levelling at around 25% at six seconds.

Developer experience benefits:

Astro doesn’t sacrifice modern development practices for performance:

  • Write components in React, Vue, Svelte, or pure HTML—Astro supports all of them
  • Built-in image optimisation with automatic WebP/AVIF conversion
  • TypeScript support out of the box
  • File-based routing identical to Next.js
  • Markdown and MDX support for content-heavy sites

This flexibility matters for agencies and in-house teams inheriting projects or working across different tech stacks.

When Heavier Frameworks Actually Make Sense

Astro isn’t universally superior—it’s optimised for specific use cases. Heavier frameworks solve real problems when your site genuinely needs their capabilities.

Choose React, Next.js, or Vue when you need:

  1. Complex client-side state management: User-generated content, multi-step forms with conditional logic, real-time collaboration features
  2. Frequent data mutations: Dashboards updating every few seconds, live notifications, collaborative editing
  3. Rich interactivity throughout: Apps where most UI elements respond to user actions rather than displaying static content
  4. Existing team expertise: If your developers are already proficient in React and you’re building an application (not a marketing site), forcing a switch wastes time

When Astro is the right choice:

  1. Marketing sites and landing pages: Content-focused sites where conversions matter more than interactivity
  2. Blogs and documentation: Text-heavy sites where SEO and read speed are priorities
  3. Portfolio and agency sites: Showcasing work with minimal interactive requirements
  4. SMB business sites: Service pages, case studies, pricing tables, contact forms—standard SMB web presence

The test is simple: if more than 30% of your page requires JavaScript interactivity, consider a heavier framework. If most content is static with isolated interactive components (forms, accordions, modals), Astro delivers better performance with less complexity.

How Fernside Studio Uses Astro for SMB Marketing Sites

Every Fernside Launch Sprint and Studio Site builds on Astro for three strategic reasons:

1. Performance guarantees conversion outcomes

We can confidently promise sub-2-second load times because Astro’s architecture makes slow sites difficult to build. Clients don’t need to trust vague “we optimise for speed” claims—the tech stack enforces it by default.

2. Future-proof without framework churn

Astro compiles to static HTML. Even if Astro disappeared tomorrow (unlikely given its rapid growth in the Netlify 2024 developer survey), your site remains functional HTML. React sites depend on continuous React runtime updates; Astro sites depend on browsers rendering HTML—a 30-year-old standard.

3. Hosting simplicity with Cloudflare Pages

Static HTML deploys to edge networks trivially. Fernside hosts all client sites on Cloudflare Pages with automatic SSL, global CDN distribution, and zero server management. Heavier frameworks often require Node.js servers, serverless function complexity, or hybrid rendering modes—unnecessary infrastructure for marketing sites.

When clients add the Fernside CMS add-on, they edit content through a hosted panel whilst maintaining Astro’s static output. Content changes trigger rebuilds that deploy globally in under 60 seconds—fast enough to feel immediate, static enough to remain fast.

What This Means for Your Next Website Project

If you’re scoping a new marketing site or evaluating frameworks for a rebuild, ask one question: does this site need a single-page application, or does it need fast HTML that converts visitors?

For most UK SMB teams, the answer is the latter. You need prospects to load your homepage in under two seconds, scan your services without layout shifts, and submit contact forms without hesitation. Astro delivers this without requiring extensive performance optimisation, bundle analysis, or code-splitting strategies.

Practical next steps:

  1. Audit your current site’s JavaScript payload using Chrome DevTools Network tab—filter by JS and check the total transferred size
  2. Run your site through PageSpeed Insights and note your Core Web Vitals scores
  3. Compare your current conversion rate against industry benchmarks (3-5% for B2B landing pages is typical)

If you’re shipping more than 100KB of JavaScript for a marketing site, or failing Core Web Vitals, or seeing bounce rates above 60%, your framework choice likely contributes to the problem.

Fernside Studio’s Launch Sprint delivers a custom one-page Astro site in five days. Multi-page Studio Sites use the same performance-first architecture. Every build includes managed Cloudflare Pages hosting, analytics wiring, and Core Web Vitals that pass by default—not as an added optimisation phase.

Book a Launch Sprint if you need a fast marketing page without the framework overhead, or scope a Studio Site for a full marketing presence built on Astro’s performance-first foundation.

Sources

Say hello

Quick intro