In order to define proper tests and comparisons we need specific information about the types of devices and networks we expect from users.
Devices
- Via https://commons.wikimedia.org/wiki/Category:New_Readers_user_personas
- XOLO Q700s
- iPhone 6
- Blackberry Z10
- Infinix Android Race Eagle X50
- Forme Discovery P9
- LeEco Le 1s
- Xolo Era
- Tecno L8
- Via Performance Budgets:
- Moto G4 or Moto G5 Plus
- Via https://meta.wikimedia.org/w/index.php?title=File:Movement_Strategy_-_New_Voices_Research_-_Findings_%26_Opportunities_from_Indonesia_%26_Brazil.pdf&page=2
- Motorola Moto X
- OPPO N1
- Moto G3
- Samsung Galaxy S5
- LG Optimus L3 2
- Samsung Grand Duo
- Samsung Galaxy S4
- Samsung Galaxy S3
Connection speeds, bundle sizes, time-to-interactivity, cache lifespan
TBD
- Via Performance Budgets:
- 400ms RTT, 400Kbps
- 130KiB total compressed data for critical path JS, CSS, client HTML / data request, and SSR HTML on the Barack Obama article endpoint (wiki route)?*
- 5s cold load TTI
- 2s warm load TTI
- What's our budget for the number of critical path HTTP requests? Batching requests may be opposed to cache lifespan.
- Since our content abstraction is so slim, do we want to budget or measure client requests? e.g., https://en.wikipedia.org/api/rest_v1/page/mobile-sections/Carrot_cake.
*This budget seems to imply only presenting a small portion of article content, such as a section, for SSRs.