---
title: "Discussion on \"Tree Shaking and Code Splitting in JavaScript\" | Hashnode"
description: "Discussion on \"Tree Shaking and Code Splitting in JavaScript\". A 2MB gzipped JavaScript bundle is ~7MB for V8 to parse and compile. On a mid-range Android at 3G, that is 12 seconds before a single interaction is possible. Bundle size is not an abstract metric — i"
url: "https://hashnode.com/posts/tree-shaking-and-code-splitting-in-javascript/6a0a5d98efc439ecb8afbe3a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Tree Shaking and Code Splitting in JavaScript](https://helloashish.hashnode.dev/tree-shaking-and-code-splitting-in-javascript?utm_source=hashnode&utm_medium=feed)

A 2MB gzipped JavaScript bundle is ~7MB for V8 to parse and compile. On a mid-range Android at 3G, that is 12 seconds before a single interaction is possible. Bundle size is not an abstract metric — i

May 18 · 11 min read · helloashish.hashnode.dev  
Read the article

-   [#performance](https://hashnode.com/tag/performance)
-   [#bundling](https://hashnode.com/tag/bundling)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#codesplitting](https://hashnode.com/tag/codesplitting)
-   [#frontend](https://hashnode.com/tag/frontend)

## Written by

[Ashish Kumar](https://hashnode.com/@helloashish)

@helloashish · Delhi, India

  
[View profile](https://hashnode.com/@helloashish)

Senior frontend engineer writing about React internals, browser performance, and how big tech builds things. renderlog.in

Senior frontend engineer writing about React internals, browser performance, and how big tech builds things. renderlog.in

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
