Environment-based bundling and minificationĪs a best practice, the bundled and minified files of your app should be used in a production environment. However, it's important to recognize that bundling and minification increases build complexity and only works with static files. Bundling and minifying before deployment provides the advantage of reduced server load. By using bundling and minification, the minified files are created prior to the app's deployment. Third-party tools, such as Gulp and Webpack, provide workflow automation for bundling and minification, as well as linting and image optimization. ASP.NET Core doesn't provide a native bundling and minification solution. For set up instructions and sample projects, see WebOptimizer. Choose a bundling and minification strategyĪSP.NET Core is compatible with WebOptimizer, an open-source bundling and minification solution. We recommend testing an app to determine if bundling and minification yields an improved load time. The test app used to generate the figures in the preceding table demonstrates typical improvements that might not apply to a given app. Greater performance gains are realized when using bundling and minification with assets transferred over a network. The load time improved, but this example ran locally. The following table outlines differences between individually loading assets and using bundling and minification for a typical web app. In addition to removing the comments and unnecessary whitespace, the following parameter and variable names were renamed as follows: Original Common side effects of minification include shortening variable names to one character and removing comments and unnecessary whitespace.Ĭonsider the following JavaScript function: AddAltToImg = function (imageTagAndImageID, imageContext) The result is a significant size reduction in requested assets (such as CSS, images, and JavaScript files). Minification removes unnecessary characters from code without altering functionality. This results in improved first page load performance. Fewer files mean fewer HTTP requests from the browser to the server or from the service providing your application. You can create any number of individual bundles specifically for CSS, JavaScript, etc. Bundling reduces the number of server requests that are necessary to render a web asset, such as a web page. Bundlingīundling combines multiple files into a single file. In this case, bundling and minification provide a performance improvement even after the first page request. Additionally, the browser requires a validation request for each asset. If the expires header isn't set correctly on the assets and if bundling and minification isn't used, the browser's freshness heuristics mark the assets stale after a few days. So, bundling and minification don't improve performance when requesting the same page, or pages, on the same site requesting the same assets. Once a web page has been requested, the browser caches the static assets (JavaScript, CSS, and images). Used together, bundling and minification improve performance by reducing the number of server requests and reducing the size of the requested static assets.īundling and minification primarily improve the first page request load time. What is bundling and minificationīundling and minification are two distinct performance optimizations you can apply in a web app. This article explains the benefits of applying bundling and minification, including how these features can be used with ASP.NET Core web apps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |