Keep your projects lean, responsive, and maintainable so you can deliver the best experience and focus on more important jobs.

Lean Sass imports

When using Sass in your asset pipeline, make sure you optimize Bootstrap by only @importing the components you need. Your largest optimizations will likely come from the Layout & Components section of our bootstrap.scss.

                // Configuration
                @import "functions";
                @import "variables";
                @import "mixins";
                @import "utilities";

                // Layout & components
                @import "root";
                @import "reboot";
                @import "type";
                @import "images";
                @import "containers";
                @import "grid";
                @import "tables";
                @import "forms";
                @import "buttons";
                @import "transitions";
                @import "dropdown";
                @import "button-group";
                @import "nav";
                @import "navbar";
                @import "card";
                @import "breadcrumb";
                @import "pagination";
                @import "badge";
                @import "alert";
                @import "progress";
                @import "list-group";
                @import "close";
                @import "toasts";
                @import "modal";
                @import "tooltip";
                @import "popover";
                @import "carousel";
                @import "spinners";

                // Helpers
                @import "helpers";

                // Utilities
                @import "utilities/api";

If you’re not using a component, comment it out or delete it entirely. For example, if you’re not using the carousel, remove that import to save some file size in your compiled CSS. Keep in mind there are some dependencies across Sass imports that may make it more difficult to omit a file.

Lean JavaScript

Bootstrap’s JavaScript includes every component in our primary dist files (bootstrap.js and bootstrap.min.js), and even our primary dependency (Popper.js) with our bundle files (bootstrap.bundle.js and bootstrap.bundle.min.js). While you’re customizing via Sass, be sure to remove related JavaScript.

For instance, assuming you’re using your own JavaScript bundler like Webpack or Rollup, you’d only import the JavaScript you plan on using. In the example below, we show how to just include our modal JavaScript:

                // Import just what we need

                // If you're importing tooltips or popovers, be sure to include the Popper.js dependency
                // import "../../node_modules/popper.js/dist/popper.min.js";

                import "../../node_modules/bootstrap/js/dist/util.js";
                import "../../node_modules/bootstrap/js/dist/modal.js";

Autoprefixer .browserslistrc

Bootstrap depends on Autoprefixer to automatically add browser prefixes to certain CSS properties. Prefixes are dictated by our .browserslistrc file, found in the root of the Bootstrap repo. Customizing this list of browsers and recompiling the Sass will automatically remove some CSS from your compiled CSS, if there are vendor prefixes unique to that browser or version.

Unused CSS

Help wanted with this section, please consider opening a PR. Thanks!

While we don’t have a prebuilt example for using PurgeCSS with Bootstrap, there are some helpful articles and walkthroughs that the community has written. Here are some options:

Lastly, this CSS Tricks article on unused CSS shows how to use PurgeCSS and other similar tools.

Minify and gzip

Whenever possible, be sure to compress all the code you serve to your visitors. If you’re using Bootstrap dist files, try to stick to the minified versions (indicated by the .min.css and .min.js extensions). If you’re building Bootstrap from the source with your own build system, be sure to implement your own minifiers for HTML, CSS, and JS.

Nonblocking files

Help wanted with this section, please consider opening a PR. Thanks!

Always use https

Your website should only be available over HTTPS connections in production. HTTPS improves the security, privacy, and availability of all sites, and there is no such thing as non-sensitive web traffic. The steps to configure your website to be served exclusively over HTTPS vary widely depending on your architecture and web hosting provider, and thus are beyond the scope of these docs.

Sites served over HTTPS should also access all stylesheets, scripts, and other assets over HTTPS connections. Otherwise, you’ll be sending users mixed active content, leading to potential vulnerabilities where a site can be compromised by altering a dependency. This can lead to security issues and in-browser warnings displayed to users. Whether you’re getting Bootstrap from a CDN or serving it yourself, ensure that you only access it over HTTPS connections.