Page MenuHomePhabricator

Spike (4 hours): Investigate existing site speed metrics
Closed, ResolvedPublic

Description

(half a day)

Questions

  • What, if any, are the existing site speed metrics we use for the desktop sites? https://gdash.wikimedia.org/dashboards/frontend/
  • How are they instrumented?
  • What site speed metrics have other high-traffic sites chosen?
  • How are they instrumented?

Outcomes

Either an email to mobile-tech/-l or a meeting with the rest of the team and analytics.

Event Timeline

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 added subscribers: phuedx, Aklapper.
JKatzWMF renamed this task from Investigate existing site speed metrics to Spike: Investigate existing site speed metrics.Apr 8 2015, 5:39 PM
JKatzWMF set Security to None.
KLans_WMF renamed this task from Spike: Investigate existing site speed metrics to Spike (4 hours): Investigate existing site speed metrics.Apr 10 2015, 7:24 PM

The events logged by the NavigationTiming extension already include a mobileMode property (description and implementation).

Google Analytics reports the average amount of time it takes the page to load, from the user clicking a link to that page being completely loaded. In NavigationTiming terms this'd be loadEventEnd - requestStart.

http://www.yottaa.com/bid/295062/Page-Load-Time-Is-Not-the-Only-Key-Performance-Metric argues that the time until the start of rendering is an important metric. In NavigationTiming this'd be renderStart - responseStart.