Server-Side Rendered Page

SSR (Server-Side Rendering)

This page is rendered on the server and hydrated on the client.

Render Mode: Server-Side Rendering
Load Time: 0ms
Server Time: 11/6/2026, 2:41:17 PM
Client Hydration: 11/6/2026, 2:41:17 PM

Rendering Information:

Data Generated On: Server
Is Server Side: Yes
Initial Render: Server

SSR Benefits:

  • ✅ Better SEO - content is available to search engines
  • ✅ Faster First Contentful Paint
  • ✅ Better performance on slower devices
  • ✅ Improved Core Web Vitals

Server-Generated Data:

Server ID: server-0b5iu1lp2
Request ID: req-1793976077201-fx6850
Server Load: 22%
IP Address: 192.168.1.100
Server Version: 1.0.0
Environment: production
Uptime: 8h 30m
Memory Usage: 52% (1935MB / 4096MB)

Server-to-Client Data Transfer:

This data was generated on the Server and shows the actual rendering location:

{
  "serverTime": "11/6/2026, 2:41:17 PM",
  "serverId": "server-0b5iu1lp2",
  "requestId": "req-1793976077201-fx6850",
  "serverLoad": 22,
  "userAgent": "Node.js/22...",
  "ipAddress": "192.168.1.100",
  "serverVersion": "1.0.0",
  "environment": "production",
  "uptime": 30624,
  "memoryUsage": {
    "used": 1935,
    "total": 4096,
    "percentage": 52
  },
  "isServerSide": true,
  "renderLocation": "Server"
}

Client-Side Interactivity:

Click count: 0

Last client update:

How SSR Works:

  1. Initial Request: User requests the page
  2. Server Rendering: Angular renders the page on the server with data
  3. HTML Response: Server sends complete HTML to browser
  4. Client Hydration: JavaScript takes over and makes the page interactive
  5. Subsequent Navigation: Client-side routing handles navigation