Closed
Bug 1454574
Opened 7 years ago
Closed 7 years ago
[FrontEnd][Perf] DNS Prefetch and Preconnect to CDN
Categories
(developer.mozilla.org Graveyard :: Performance, enhancement)
developer.mozilla.org Graveyard
Performance
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: espressive, Assigned: espressive)
References
Details
In order to make subsequent requests for assets to the CDN faster(less latency), lets prefetch and preconnect as early as possible in the head.
| Assignee | ||
Updated•7 years ago
|
Assignee: nobody → schalk.neethling.bugs
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•7 years ago
|
||
Pull request opened: https://github.com/mozilla/kuma/pull/4738
Comment 2•7 years ago
|
||
Our plan is to serve developer.mozilla.org from a CDN (bug 1431259), to serve static assets from the same domain, and to retire cdn.mdn.mozilla.net. This strategy appears to work well for www.mozilla.org. This removes the need to pre-fetch the CDN domain.
See Also: → 1431259
Updated•7 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Comment 3•7 years ago
|
||
Ah ok, I thought we may still have a separate address at which we would call the CDN hosted assets.
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•