What is the purpose of this session?
- Define performance quick wins
- Define “fast” - what counts as success re: loading speed
- Define SLAs - what counts as success re: e.g. product numbers
- Prioritize critical pages for fixing
- Estimate ease vs value for each task
What outcomes/deliverables do we want?
Clear next actions
Clear target numbers re: loading time, product numbers SLA
Who is facilitating? Lynne
Who is scribing? Gen
Summary of decisions:
- 3-5 secs is the goal
Actions:
- Matt did /maps! 54 secs - 0.4 secs
- /maps; /shops; /producer - all in one pull request right now, so that goes first
- then work on the rest through 45 degree angle:
Outcomes:
Based on ease-value matrix the following pages are our development priorities:
- /maps - Awaiting PR merge and release
- /shops - Awaiting PR merge and release
- /producer - Awaiting PR merge and release
- /groups - Awaiting PR merge and release
- /admin/ edit order cycles - Spike
- /enterprise/shop
- /reports/orders+fulfillment
- /super-admin/enterprises
- /super-admin/order-cycles
- /bom
- /admin/products
- /admin/enterprises - only a problem for hubs with large numbers of producers
- /checkout
Number of products supported: 10,000
Acceptable page load time: 3-5 seconds
Pagination is an acceptable strategy in general.