Web Fundamentals for Frontend Interviews (Complete Guide for 2026)

This hub covers the fundamentals interviewers actually test: rendering strategies, browser internals, performance budgets, security (XSS/CSRF/CORS/CSP), state management, data fetching, accessibility, and React hooks. Use the sidebar to go deep β€” or start with the curated path below.

Start Here (High-Signal Topics)

Recommended order: Rendering β†’ Browser Internals β†’ Performance β†’ Security β†’ State/Data.

Pick Your Goal

What Interviewers Commonly Ask

  • βœ“ Compare CSR vs SSR vs SSG vs ISR. When would you choose each?
  • βœ“ What is hydration? What causes hydration mismatch and how do you debug it?
  • βœ“ Walk through the Critical Rendering Path. What blocks first paint?
  • βœ“ Explain microtasks vs macrotasks. Why do Promise callbacks run β€œbefore” setTimeout?
  • βœ“ Explain XSS vs CSRF vs CORS. What defenses do you add in a real app?
  • βœ“ How do you reduce bundle size safely? (tree shaking, code splitting, lazy loading)
  • βœ“ What are Core Web Vitals and how do you improve LCP/CLS in production?
  • βœ“ How would you cache server state on the client and handle invalidation?

FAQ

Is this section only for beginners?
No β€” it’s structured for interview readiness. Start with Rendering + Browser Internals, then go deeper into Performance, Security, and State/Data depending on your level.
What should I study first for frontend interviews?
Rendering Strategies + Critical Rendering Path + Event Loop. These unlock most β€œwhy is my UI slow / broken / inconsistent?” interview questions.
Do I need to memorize everything?
No. Focus on tradeoffs + debugging. Interviewers want structured reasoning and the ability to explain choices under constraints.