What Is Code Splitting?
Quick Definition
Code splitting is a technique that breaks a large JavaScript bundle into smaller chunks that are loaded on demand, so users only download the code needed for the page they're viewing.
Modern web applications can have millions of lines of JavaScript. Without code splitting, all of this code gets bundled into a single file that every user must download before the application becomes interactive — even if they only visit one page.
Code splitting divides the application bundle into smaller chunks based on routes, components, or features. When a user visits the homepage, they only download the homepage code. When they navigate to the settings page, that code loads on demand. Libraries used only in specific features are split into their own chunks.
There are several approaches to code splitting. Route-based splitting loads code for each page separately (the most common approach). Component-based splitting loads heavy components on demand (like a rich text editor that's only needed when editing). Library splitting separates third-party dependencies into their own cacheable chunks.
Frameworks like Next.js implement route-based code splitting automatically. For component-level splitting, React's lazy() and Suspense enable developers to load components on demand. Webpack, Vite, and other bundlers handle the actual chunk creation and loading logic.
Why It Matters
Without code splitting, every user downloads your entire application regardless of what they need. For a large application, this could mean 2-5MB of JavaScript that blocks the page from becoming interactive. Code splitting can reduce the initial download by 60-80%.
This directly impacts Time to Interactive (TTI) and First Input Delay (FID), both critical Core Web Vitals that affect user experience and SEO rankings.
Real-World Examples
A SaaS dashboard reduced their initial JavaScript bundle from 3.2MB to 450KB through route-based code splitting, making the login page load in under 2 seconds instead of 8
An e-commerce site lazy-loaded their product review component (which included a heavy rich-text editor), saving 200KB from the initial product page load
A Next.js application automatically code-splits by route, so their 50-page application's homepage only loads 120KB of JavaScript instead of the total 4MB
A web app split their charting library into a separate chunk, so users who never visit the analytics dashboard don't download the 500KB chart library
Related Terms
Page Speed
Page speed measures how quickly the content on a web page loads and becomes interactive, directly affecting user experience, search rankings, and conversion rates.
Lazy Loading
Lazy loading is a technique that delays the loading of non-critical resources, like images below the fold, until they are actually needed, improving initial page load speed.
Minification
Minification is the process of removing unnecessary characters from source code — like whitespace, comments, and long variable names — without changing functionality, reducing file size for faster loading.
Core Web Vitals
Core Web Vitals are a set of three specific metrics defined by Google that measure real-world user experience on websites: loading performance (LCP), interactivity (INP), and visual stability (CLS).
Need help with code splitting?
Our team can help you put this into practice. Get a free consultation to discuss your project.