Skip to main content
Next.jsPerformanceadvanced

Next.js Turbopack Bundle Analyzer & Streaming Suspense Optimizer

Optimize Core Web Vitals (LCP, TTFB) using React Suspense streaming, dynamic imports, and modular package tree-shaking.

Compatibility & Specs

Compatible AI Models
ClaudeChatGPTGemini
Last UpdatedOct 3, 2026
Customizable Variables3 parameters

How to Use This Prompt

Follow this 3-step workflow to extract high-signal responses from any compatible AI model.

01

1. Tailor the Parameters

Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.

02

2. Send to AI Model

Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.

03

3. Review and Iterate

Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.

Prompt Variables & Parameters

Reference breakdown of every dynamic variable embedded in this prompt template.

PlaceholderParameter NameTypeStatusDescription & Guidance
[bundle_metrics]Build & Bundle MetricstextareaRequiredFirst-load JS shared by all chunks and page sizesDefault: First Load JS shared by all chunks: 195 kB. `/analytics` page bundle size is 480 kB (First Load JS 675 kB), triggering Next.js yellow warning.
[observed_regressions]Observed RegressionstextareaRequiredLCP, TTFB, or interaction lagDefault: LCP is 3.6s on mobile 4G. TTFB is 1,200ms because the root page `await`s 4 sequential database queries before sending any initial HTML byte.
[heavy_dependencies]Heavy DependenciestextRequiredLibraries loaded into client bundleDefault: Recharts (340 kB), date-fns, and full Lucide icon library imported via root index.

Example Execution & Benchmark Output

Sample input arguments and the verified AI response demonstrating expected quality and formatting.

Sample VariablesInputs
[bundle_metrics]
First Load JS shared by all chunks: 195 kB. `/analytics` page bundle size is 480 kB (First Load JS 675 kB), triggering Next.js yellow warning.
[observed_regressions]
LCP is 3.6s on mobile 4G. TTFB is 1,200ms because the root page `await`s 4 sequential database queries before sending any initial HTML byte.
[heavy_dependencies]
Recharts (340 kB), date-fns, and full Lucide icon library imported via root index.
Expected AI ResponseVerified Result
### Next.js Performance & Streaming Blueprint #### 1. Eliminate TTFB Blocking via Streaming `<Suspense>` Currently, the page awaits 4 queries sequentially, blocking the response stream for 1.2s. Remove the `await` from the page root. Stream the shell immediately: ```tsx // src/app/analytics/page.tsx import { Suspense } from 'react'; import { MetricCardsSkeleton, ChartSkeleton } from './skeletons'; import { MetricCards } from './MetricCards'; import { RevenueChart } from './RevenueChart'; export default function AnalyticsPage() { return ( <div> {/* Shell HTML sends to browser in <100ms! */} <h1>Analytics Overview</h1> {/* Fast queries resolve first */} <Suspense fallback={<MetricCardsSkeleton />}> <MetricCards /> </Suspense> {/* Heavy 1.2s query streams in asynchronously without blocking shell */} <Suspense fallback={<ChartSkeleton />}> <RevenueChart /> </Suspense> </div> ); } ``` #### 2. Dynamic Code Splitting for Recharts (Save 340 kB) ```tsx import dynamic from 'next/dynamic'; // Lazy load heavy chart bundle; zero impact on initial page JS const InteractiveRechartsArea = dynamic( () => import('./InteractiveRechartsArea').then(mod => mod.InteractiveRechartsArea), { ssr: false, loading: () => <div className="h-64 animate-pulse bg-muted" /> } ); ``` #### 3. `next.config.ts` Package Import Optimization ```typescript const nextConfig = { experimental: { optimizePackageImports: ['lucide-react', 'date-fns', 'recharts'], }, }; ``` *Impact:* First Load JS drops from 675 kB to 142 kB; mobile LCP drops from 3.6s to 1.1s.

Best Use Cases

Scenarios and roles where this prompt produces maximum leverage.

Next.js engineers optimizing sluggish dashboards and data-heavy analytics views
Developers improving Core Web Vitals to pass Google SEO performance thresholds
Teams resolving build warnings by code-splitting heavy chart and editor libraries

Tips for Best Results

Techniques to elevate response fidelity

  • •Specify your exact runtime and dependency versions (e.g. Next.js 15, React 19, TypeScript 5.4) to eliminate outdated syntax hallucinations.
  • •Ask the model to enumerate potential runtime failure modes, concurrency issues, or null boundary states before generating code.
  • •Request idiomatic, type-safe solutions with clear unit test skeletons rather than monolithic scripts.

Common Mistakes to Avoid

Frequent failure modes and anti-patterns

  • •Pasting large unformatted code dumps without indicating the specific function or error you want analyzed.
  • •Deploying AI-generated code directly to production without verifying memory safety, edge cases, and security vulnerabilities.
  • •Omitting architectural constraints (such as SSR vs. client component boundaries or database indexing).

Part of Curated Collections

This prompt is sequenced as part of these goal-oriented workflows

View all collections

Related AI Prompts

Complementary workflows in Next.js

View all Next.js prompts
Codingadvanced

OWASP Security Vulnerability & Dependency Auditor

Inspect code modules for injection vulnerabilities, insecure deserialization, broken access controls, and auth flaws.

claudechatgptgemini
#security-audit#owasp#vulnerability-scanning
Next.jsadvanced

Next.js Server vs. Client Component Boundary Decision Matrix

Audit page trees to push 'use client' directives to the leaves, minimize JS bundles, and maximize server streaming.

claudechatgptgemini
#nextjs#server-components#client-components
Reactadvanced

React Re-render Cascade & Context API Performance Profiler

Isolate and eliminate redundant React re-render cascades caused by unmemoized Context providers and inline props.

claudechatgptgemini
#react#react-performance#re-renders