Why Wegic Chose CSR

Understanding Wegic's Architecture

Wegic builds websites using Vite + React + TypeScript as Client-Side Rendered (CSR) Single-Page Applications (SPA).

CSR vs SSR: Why Wegic Chose CSR

What's the Difference?

Server-Side Rendering (SSR):

• Server generates full HTML for each page

• Browser receives complete content immediately

• Every navigation requests a new page from the server

Client-Side Rendering (CSR) – Wegic's approach:

• Server sends a lightweight HTML shell once

• Browser executes JavaScript to build the page

• Navigation happens instantly without server requests

Why CSR is Better for Wegic

1. Instant Navigation

• No page reloads, no loading spinners

• Smooth transitions and animations

• Native app-like experience

2. Rich Interactivity

• Advanced animations (GSAP, Framer Motion, Three.js) work seamlessly

• Complex UI components load once and reuse efficiently

• Better performance for interactive features

3. Simple Deployment

• Static files hosted on global CDN (faster worldwide)

• No server infrastructure to maintain

• Lower costs, higher reliability

4. Modern Development

• Faster builds and updates

• Real-time preview during development

• Easier to iterate and improve

---

What About SEO?

The Reality:

✅ Google indexes CSR sites perfectly (since 2015)

✅ Rankings are based on content quality, not rendering method

⏱️ Initial indexing takes a few days longer (not a ranking factor)

How It Works:

1. Google crawls your site and sees the HTML structure

2. Google returns later to run JavaScript and index full content

3. Your pages appear in search results normally

Social Media Sharing:

• Platforms like Facebook and Twitter don't wait for JavaScript

• They only see the initial HTML structure

• For unique preview images per page, configure Open Graph meta tags

Wegic Automatically Includes:

• Semantic HTML structure

• Clean URLs

• Mobile-responsive design

• Fast loading times

• Proper heading hierarchy