All DNA Categories
🌐

Web Browser

Rendering, CORS, service workers, storage, security

13 topics
ðŸĨš 1ðŸĢ 4ðŸĶ– 7👑 1
ðŸĨš

Egg

Fundamentals

ðŸĢ

Hatchling

Intermediate

ðŸĶ–

Dinosaur

Advanced

1

The Critical Rendering Path

Every pixel on screen is the result of a pipeline. Senior engineers who understand this pipeline don't guess at performance — they engineer it.

BrowserPerformanceRendering
2

SSR vs CSR vs Universal Rendering

The rendering strategy you choose defines your app's performance ceiling, SEO story, and infrastructure complexity. This isn't a syntax decision — it's an architecture decision.

BrowserArchitecturePerformance
3

DOM Performance & Why DOM Manipulation is Costly

The DOM is the most expensive API in the browser. Understanding why — and the mechanics of reflow and repaint — is fundamental to frontend performance.

BrowserPerformanceDOM
4

Web Workers & Service Workers

JavaScript is single-threaded — until it isn't. Workers let you run code off the main thread, and Service Workers give you control over the network layer.

BrowserPerformanceWorkers
5

Browser Networking & Resource Loading

HTTP/2, HTTP/3, resource hints, preload, prefetch — the network layer is where performance is won or lost. Architects who control the network control the user experience.

BrowserPerformanceNetworking
6

Browser Security Model

Same-origin policy, CORS, CSP, XSS, CSRF — the browser's security model is the foundation every web application is built on. Ignorance here means vulnerabilities.

BrowserSecurityArchitecture
7

CORS Deep Dive

CORS isn't a security feature you bolt on — it's the browser's enforcement of the same-origin policy for cross-origin requests. Understanding preflight, credentials, and header negotiation prevents the most common deployment bugs.

BrowserSecurityCORS
👑

Apex

Architect