The latest articles on DEV Community by Md. Abu Noman (@md-abu-noman). https://dev.to/md-abu-noman https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4214509%2Fd13fe9f9-c2ef-4860-8583-7448b611a89e.png https://dev.to/md-abu-noman en Md. Abu Noman Thu, 29 Oct 2026 08:44:49 +0000 https://dev.to/md-abu-noman/frontend-performance-is-an-architecture-problem-not-an-optimization-problem-2c4c https://dev.to/md-abu-noman/frontend-performance-is-an-architecture-problem-not-an-optimization-problem-2c4c <p>We often treat frontend performance as something to fix after a page becomes slow.</p> <p>We optimize images, add memoization, reduce component re-renders, and run Lighthouse audits. These techniques can help—but what if the biggest performance problems were introduced much earlier, during architectural decisions?</p> <p>In modern React and Next.js applications, performance is influenced by several decisions:</p> <p>Rendering strategy: When should a page use static rendering, server rendering, or client-side rendering?</p> <p>JavaScript delivery: How much JavaScript does the browser actually need?</p> <p>Component boundaries: Which components need to be interactive, and which can remain server-rendered?</p> <p>Data fetching: Are requests unnecessarily sequential when they could run in parallel?</p> <p>Caching: Can we avoid repeating expensive work for every request?</p> <p>These decisions shape the amount of work required to deliver a page and make it interactive.</p> <p>Lighthouse is useful for identifying symptoms, but improving a score isn't the same as understanding the underlying cause.</p> <p>I explored these ideas in my latest article:</p> <p>Frontend Performance Is an Architecture Problem, Not an Optimization Problem</p> <p>Read the full article: [<a href="https://medium.com/@md-abu-noman/frontend-performance-is-an-architecture-problem-not-an-optimization-problem-4455e141aeee?sharedUserId=md-abu-noman" rel="noopener noreferrer">https://medium.com/@md-abu-noman/frontend-performance-is-an-architecture-problem-not-an-optimization-problem-4455e141aeee?sharedUserId=md-abu-noman</a>]</p> <p>I'm curious: When investigating a slow React or Next.js application, what do you examine first—rendering strategy, JavaScript bundle size, data fetching, or something else?</p> webdev react nextjs webperf