As a team we'd like to get regular reports of mobile site speed so that we can better evaluate changes we make to the site.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Duplicate | • Jhernandez | T104432 [EPIC]: Improve mobile site performance | |||
Resolved | Jdlrobson | T94752 [EPIC] Continuously measure mobile site speed | |||
Resolved | None | T95296 Spike (4 hours): Investigate existing site speed metrics | |||
Invalid | phuedx | T95297 Spike (8 hours): Design site speed schemas | |||
Invalid | phuedx | T95299 (3) Instrument the schemas designed in T95297 | |||
Invalid | phuedx | T95301 Send regular mobile site speed reports | |||
Resolved | phuedx | T95300 Create a mobile site speed dashboard | |||
Resolved | Jdlrobson | T102036 Clean up mobile site speed dashboards | |||
Resolved | Jdlrobson | T105361 Spike [1 hour]: Browser performance metrics tools |
Event Timeline
Comment Actions
It would be good to scope this. There are many other things we can look into e.g. time for editor to load, responsiveness of toggling etc.. but by scoping we have the best chance of doing something very well.
Personally I think the biggest and most obvious win right now is page load time so instrumentation should be around that and we should reduce that drastically.
Comment Actions
@Jdlrobson: the first part of this epic, T95296, is an investigation and discussion of existing site speed metrics. This spike will inform the rest of the work in the epic.
Comment Actions
Blocking tasks are fixed so I'm calling this resolved. T112587 is the next evolution of this goal.