Generate a Code Splitting Strategy
Design a code splitting plan for [frontend application]. Include bundle analysis, lazy loading rules, and performance targets. Improve load time.
Code splitting reduces initial bundle size and improves Core Web Vitals.
If you're struggling with slow frontend application load times, this Claude prompt helps you create a comprehensive code splitting strategy that can significantly improve your Core Web Vitals scores. Code splitting divides your JavaScript bundles into smaller chunks that load only when needed, reducing the initial payload your users download. This prompt is designed for developers and technical leads who want to implement professional-grade performance optimization without starting from scratch. Whether you're working with React, Vue, Angular, or vanilla JavaScript, Claude can analyze your application structure and recommend specific splitting points that matter most.
To use this prompt effectively, replace the [frontend application] placeholder with details about your specific project. For example, you might write "Design a code splitting plan for an e-commerce React application with a product catalog, shopping cart, checkout flow, and admin dashboard." The more specific you are about your application's features and user workflows, the more targeted Claude's recommendations will be. You can also mention your current bundle size, target load time, or specific performance problems you're experiencing.
Claude will generate a detailed code splitting plan that includes a bundle analysis showing which modules and dependencies consume the most space, clear lazy loading rules for different sections of your application, and concrete performance targets with metrics you should track. You'll receive actionable recommendations about where to implement dynamic imports, how to structure route-based splitting, and strategies for vendor chunk optimization.
Here's a pro tip: ask Claude to prioritize splitting based on user journey impact. Instead of just splitting everything equally, have Claude identify which parts of your application users interact with immediately versus later interactions. This helps you focus on splitting the features that will have the biggest immediate impact on your load time metrics and user experience.