We're always striving towards keeping our website's JavaScript as small as possible.

Do you need DevOps-experts?

Your development team has a full backlog? No time for infrastructure architecture? Our DevOps team is ready to support you!

• We build reliable cloud solutions with Infrastructure as code
• We are experts in security, Linux and databases
• We support your dev team to perform

Read more Show archive.org snapshot

If you're using webpack(er), you can use the webpack-bundle-analyzer plugin Show archive.org snapshot to get a good overview, which of your JavaScript modules take up how much space, and where you can optimize.

To use it, add it via npm or yarn

yarn add webpack-bundle-analyzer

Then add this to your environment.js:

// Uncomment this code to show statistics of bundle sizes. Generated file will automatically open in your browser.
// Compile with NODE_ENV=production bin/rake assets:precompile
const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin;
environment.plugins.append(
  'BundleAnalyzer', new BundleAnalyzerPlugin({ analyzerMode: 'static' })
)

Then compile using the production environment. In a Webpacker project, this can be done with

NODE_ENV=production bin/webpack

An interactive graph like this will open in your browser:

The large chunks are the separate bundles (this application uses more than one). Important metrics are "Parsed size" (the amount of JavaScript the browser has to parse) and "Gzipped size" (the amount of data going over the wire).

When done, comment out the code in your environment.js.

You should do check your bundle size at least once before bringing an application into production.