I followed the awesome Blender Donut tutorial by Blender Guru. This was my final result:

I followed the awesome Blender Donut tutorial by Blender Guru. This was my final result:
TL;DR Browserify bundles too big? Use Disc to find trouble points. Then replace big utility-knife packages with smaller, narrow-focus equivalents from sites like microjs.com
Our cobrowsing web app was taking too many precious seconds (read: an eternity) to pop in the browser. We had focused on adding features without keeping an eye on steadily-increasing load times. The code consisted of 3 Browserified bundles totaling 1.9mb minified-yikes. I brought that size down to 730kb with my two new favorite methods: light discs and lies.
The first step to losing those extra bytes is finding out who is contributing what to your bundle. Disc by @hughskennedy is a tool that analyzes every module inside your bundle and displays a graphical breakdown of bytes per module. You can install Disc with [sudo] npm install -g disc
Let’s say you want to analyze the bundle core.js. Create a Disc diagram with these steps:
browserify --full-paths core.js > core-bundle.js
discify core-bundle.js > core-bundle.html
open core-bundle.html
Now you’ve got a radial diagram of all the modules that make up your bundle. Each colored graph segment represents one module. Mouseover any segment to see the module name and size. Disc provides additional convenience options such as automatically highlighting particular module types; see the official Disc page for more.
Now it’s time to act on the information generated by Disc.
That’s all I got. Hope this helps your Browserify bundles get ready for summer.