If you want to start using minified Drupal core JavaScript files now checkout the Speedy module. There is a reason jQuery calls the minified version the production version and the original source the development version. Minifying files can have a real world performance difference. This file already includes a minified version of jquery.js so the improvements we will see are from JavaScript files bundled with Drupal and contributed modules. To do one last test I took an aggregated from from. By minifying files we can reduce the bandwidth and save on round trip requests giving our users a performance improvement without sacrificing functionality. Now lets extend this to ajax.js, form.js, jQuery UI, and all the other JavaScript in Drupal. Here I’ve only touched on the base JavaScript included in Drupal. By minifying the JavaScript in addition to gzip compression we save 2 more round trip requests to get the same functionality. To downloaded the gzipped version would take 6 round trip requests.
JQUERY MINIFY DOWNLOAD
To download the original uncompressed set of files would take 10 round trip requests. Saving time on these files means the rest of the assets in a page start downloading sooner. Drupal puts these assets in the head of a page. JavaScript files can block the rest of the assets in a page from being downloaded. With JavaScript files in the head of a page this can be extra important. So, to speed up performance for an individual user it can be helpful to remove unneeded requests. On mobile networks this delay can be several times that of a wired connection for each of the round trip requests. Each of these round trips has a delay as communications travel between a browser and a server. To put it way to simply, when a browser fetches a file from a server it does it in multiple round trip requests. To understand why this matters I would first suggest reading TCP and the Lower Bound of Web Performance by Steve Souders where he talks about connections, TCP slow-start, and how it matters. The real fun starts to appear when we look round trip requests. Even though drupal.js and are small we have over a 3 Meg savings in bandwidth for just these two files at 10,000 downloads a month. If you figure you have 10,000 downloads of this bundle of files per month that’s a savings of 420 Megs of bandwidth savings in a month.
JQUERY MINIFY PLUS
The savings between gzip compression and gzip plus being minified is 44067 bytes. Well documented files like these can really benefit from being minified. When the file is compressed with gzip all of this text is compressed and shipped. When a file is minified this is stripped out as it’s not needed for functionality. These two files have lots of fantastic documentation in them. One thing that surprised me right off the bat was that drupal.js and are smaller minified than compressed with gzip. Why Are drupal.js and Smaller When Minified? JavaScript files and their sizes when minified and gzipped. The three files used in the example here were chosen because they are used on ever page in Drupal where JavaScript is used. The table below has a breakdown for discussion. So, here is a case for minifying JavaScript.Ī good place to start is with size examples for different files.
Over the past couple weeks I’ve received push back from numerous people who’ve told that me if you use gzip (or deflate) compression there’s no need to minify JavaScript. After all, the major JavaScript packages do it and the performance recommendation tools all recommend it. This seemed like something simple that I wouldn’t get any push back on.
JQUERY MINIFY CODE
I just copy and paste the javascript code into the box and hit generate. When I was at DrupalCon Denver I suggested that all production JavaScript should be minified. If you are minfying the plugins as separate files, the process may be renaming a symbol that is part of the jQuery API, because the minifier is not aware of the interaction.
0 kommentar(er)
