View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 663 | Composr | core | public | 2012-07-02 19:13 | 2012-09-15 16:14 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 663: Javascript and CSS include demodularisation | ||||
| Description | If the front page of a zone is viewed by a Guest, and we're loading up the Javascript/CSS dependencies via the initially-seeded self-learning cache, at this point: - save what CSS and Javascript files are used into the values table, under resources__<zone> - merge all the resources together when outputting CSS and Javascript (resources__<zone>.css and resources__<zone>.css), and just reference the merged copy Then whenever any user views any page of this zone, look to see if resources__<zone> is set, inside the CSS and Javascript output functions. If it is, don't output anything defined under resources__<zone> but do output resources__<zone>.css/resources__<zone>.js. This should slightly increase performance by reducing the number of scripts/CSS files. It should improve Composr's grade on performance testing tools. | ||||
| Additional Information | Success metrics (not guaranteed, but nice targets to check to after work is done, to avoid stopping short): - Top score in each area of Google PageSpeed - Top score in each area of YSlow | ||||
| Tags | Type: Performance | ||||
| Attach Tags | |||||
| Time estimation (hours) | 3 | ||||
| Sponsorship open | |||||
