#664 - Automatic CDN detection
-
By Chris Graham
- Added
- 7 views
| Identifier | #664 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Automatic CDN detection |
| Status | Completed |
| Tags |
Type: Performance (custom) |
| Handling member | Chris Graham |
| Addon | core |
| Description | Limit where cookies are sent, and allow parallelisation, via automatic CDN detection. Do some auto-probing for common sub-domains. Have a config option that specifies what sub-domains to probe, which defaults to "www,mail,ftp,cdn,<IP>" ('www' would not be used if actual base URL is using that). <IP> should not be parsed into the config option value, but parsed at run time.
This should slightly increase performance by better parallelising image download. It should not hurt server performance as these are known by us to be static resources. It should improve Composr's grade on performance testing tools. |
| Steps to reproduce | |
| 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 |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
98% in Google PageSpeed. Remaining suggestions were:
- to minimize HTML (performance bottleneck on the PHP end, not useful due to existing gzip encoding, and risky as can easily break Javascript functionality if the compressor is naive). The Google server-side page speed extension can do this if really desired.
- defer some Javascript loading. As the JS is now merged into a single file to save requests, that means it can't be chopped up -- so this is a trade-off. It'd also be very problematic to do this due to how Composr is put together, as when HTML is parsed much code will assume the JS code for it is already ready, and it'd be confusing to the user for the page to have multiple levels of being loaded.