We definitely need to improve the way we are processing and serving JS and CSS in order to increase front-end performance (especially for mobile devices).

Tasks

  • Write media queries into the cached and aggregated CSS files
    Write media queries into the cached and aggregated CSS files instead of forcing a new aggregation group for each media query (#1488910: Incorporate media queries in aggregated CSS files, don't create a new group for each new media query)
  • Minify JS files
    Minify JS files while aggregating / caching them. There already is an issue for that (from 2007) but we might want to think about the possibility of adding a PHP library to core that does that for us. Minifying JS can, in many cases, reduce the file size to about half (even more with gzip compression of course). #119441: Compress JS aggregation
  • Turn aggregation of CSS and JS files into a pluggable system
    The JS / CSS pre render callback could look up the aggregation handler that it should use by checking something like $config->get('performance.css_aggregation_handler') // $config->get('performance.js_aggregation_handler'). There already is an issue for that (#352951: Make JS & CSS Preprocessing Pluggable) but the latest patch there is from late 2009.
  • Intelligently sort CSS and JS files so that we don't break aggregation groups
    This currently happens when CSS or JS that can not be preprocessed (because it is external, inline or conditional) is added in the middle of a group. Possible solution: Move such CSS / JS to the end of their group so that they end up in between 2 aggregates instead of splitting an aggregation group. This slightly changes the order of the CSS / JS output which, in some cases, affects CSS overrides, but with proper documentation that shouldn't be a problem (themers can just use more or less specific CSS rules).
  • Remove the CSS_SYSTEM aggregation group
    #1490336: Weight the system CSS at the top of the CSS_DEFAULT group instead of placing it in a separate aggregation group (CSS_SYSTEM)

Related Issues

Comments

fubhy’s picture

Issue summary: View changes

Related Issues

fubhy’s picture

Issue summary: View changes

Updated issue summary.

fubhy’s picture

Issue summary: View changes

Updated issue summary.

fubhy’s picture

Issue summary: View changes

Updated issue summary.

JohnAlbin’s picture

Issue tags: +mobile

Lost track of this. :-) Tagging.

JohnAlbin’s picture

Whoops. wrong tag.

JohnAlbin’s picture

Issue summary: View changes

Updated issue summary.

nod_’s picture

Issue summary: View changes

add related task

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

andypost’s picture

Version: 8.1.x-dev » 8.2.x-dev
Category: Task » Plan
Issue summary: View changes

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

nod_’s picture

Issue tags: +JavaScript

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.