Page MenuHomePhabricator

Spike (8 hours): Design site speed schemas
Closed, InvalidPublic

Description

(half task)
Given the outcome of T95296, design and review (with Analytics) or adopt EventLogging schemas for measuring mobile site speed.

Event Timeline

phuedx renamed this task from Design and review site speed schemas to Design site speed schemas.
phuedx raised the priority of this task from to Needs Triage.
phuedx updated the task description. (Show Details)
phuedx added a project: Web-Team-Backlog.
phuedx set Security to None.
phuedx added subscribers: phuedx, Aklapper.
JKatzWMF renamed this task from Design site speed schemas to Spike: Design site speed schemas.Apr 8 2015, 5:40 PM
KLans_WMF renamed this task from Spike: Design site speed schemas to Spike (4 hours): Design site speed schemas.Apr 10 2015, 7:26 PM
KLans_WMF renamed this task from Spike (4 hours): Design site speed schemas to Spike (8 hours): Design site speed schemas.

AFAICT this is mostly done for us by the NavigationTiming extension, Graphite, and gdash – the graphs over at WMF stats. If you take a look at the NavigationTiming data in Graphite, you'll see that all frontend.navtiming.* series are split into mobile and desktop components already. We just need to graph the ones that we want and separate 'em from the desktop graphs.

phuedx claimed this task.