Hvad er Code Splitting?
Hurtig definition
Code splitting er en optimeringsteknik, der opdeler en applikations JavaScript-kode i mindre bidder, der kan indlæses efter behov og reducerer størrelsen på den indledende bundle.
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.
Hvorfor det er vigtigt
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.
Eksempler fra den virkelige verden
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
Relaterede termer
Page Speed
Sidehastighed er et mål for, hvor hurtigt en webside indlæses og bliver interaktiv, og påvirker direkte brugeroplevelsen og rangeringer i søgemaskiner.
Lazy Loading
Lazy loading er en teknik, der udskyder indlæsningen af ikke-kritiske ressourcer, såsom billeder under folden, til de faktisk er nødvendige.
Minification
Minificering er processen med at fjerne unødvendige tegn — mellemrum, kommentarer, linjeskift — fra kildekoden (CSS, JavaScript eller HTML) for at reducere filstørrelse.
Core Web Vitals
Core Web Vitals er tre specifikke målinger defineret af Google, der måler den faktiske brugeroplevelse på websteder: indlæsningsydeevne (LCP), interaktivitet (INP) og visuel stabilitet (CLS).
Har du brug for hjælp med code splitting?
Vores team kan hjælpe dig med at omsætte dette i praksis. Få en gratis konsultation for at diskutere dit projekt.