InterviewStack.io LogoInterviewStack.io

Frontend Performance Optimization Questions

Comprehensive techniques and trade offs for improving client side performance in web applications and single page applications. Candidates should understand the browser rendering pipeline and critical rendering path including parsing, style calculation, layout, paint, and compositing, and how layout and paint costs produce reflow and repaint. They should know how component design and code patterns affect rendering and how to avoid layout thrashing and unnecessary re rendering. Candidates must be able to diagnose and mitigate JavaScript execution bottlenecks and long tasks that block the main thread using browser developer tools and performance application programming interfaces. Key topics include bundling and module strategies such as code splitting, lazy loading, tree shaking, and bundle size reduction; image optimization and responsive image techniques; network optimization including resource prioritization, compression, and caching strategies; service workers for offline capabilities and advanced caching patterns; and use of web workers to offload computation. Advanced considerations include virtual scrolling for large lists, progressive enhancement, server side rendering and client side rendering trade offs and hydration cost for universal applications, browser memory management and garbage collection implications, and how frontend decisions interact with backend constraints and overall system architecture. Candidates should also be familiar with measuring user experience using Core Web Vitals such as Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift, with real user monitoring and synthetic testing, and with establishing performance budgets and continuous performance monitoring.

MediumSystem Design
84 practiced
For an API-driven product catalog, design a caching strategy that balances freshness and performance for endpoints: product-listing (frequently read, occasionally updated) and product-stock (real-time). Include headers, CDN settings, and any edge-side patterns like stale-while-revalidate or surrogate-keys.
HardSystem Design
74 practiced
Design an end-to-end performance strategy for a global customer-facing web app (10M monthly users): include build-time optimizations, CDN and edge strategies, image delivery, CI checks, and how frontend choices should interact with backend APIs to reduce perceived latency.
EasyTechnical
84 practiced
Explain the three Core Web Vitals: Largest Contentful Paint (LCP), First Input Delay (FID), and Cumulative Layout Shift (CLS). For each metric, give one concrete optimization technique that typically improves it and explain briefly why.
EasyTechnical
60 practiced
Explain what 'critical CSS' is and how inlining critical CSS can improve perceived load time. Describe the trade-offs of inlining vs. deferring styles and outline a simple process to extract and serve critical CSS for the above-the-fold content of a page.
HardTechnical
82 practiced
Create a realistic performance budget for a medium-sized SPA (home page LCP target 2.5s). Include numeric budgets for: total JS bundle size, initial server payload (HTML), number of critical requests, time-to-first-byte, LCP, CLS, and max long task duration. Explain how you'd enforce this budget in CI and handle false positives.

Unlock Full Question Bank

Get access to hundreds of Frontend Performance Optimization interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.