Spike: Data Loading Checklist for Engineers to document loading times under various conditions

[cottonchristopher]

Dependency

• [ ] Reopen when there is a need to analyze these results, or add more entries based on a new commit hash

Overview

We need a checklist for engineers to document loading times under various conditions so that we can improve load times, upload alerts about load times or create load time fillers to enhance user experience, minimize confusion.

Template

• copy the template below
• fill in each section

Action Items

• [ ] measure and document load times based on selection
• [ ] measure and document load times based on local machine vs github pages site
• [ ] Identify various conditions that can impact data loading performance (e.g., network latency, server load, data volume
• [ ] Document any changes made to the system or environment

### Load Time Criteria
- Platform: (local / hosted)
- Request Status: (Open / All / Closed)
- Commit Hash: (get latest commit hash)
- Operating System: (Windows / MacOs / Linux)
- Browser: (Chrome / Firefox / Safari)

### Results
- [ ] choose 3 months, 3 request types
- [ ] choose 3 months, 1 request type  
- [ ] choose 1 week, chose all requests
- [ ] choose 1 week with 2 request types

Consider splitting up work based on

• using local machine
• using https://hackforla.github.io/311-data

Resources/Instructions

• hosted site: https://hackforla.github.io/311-data

Archived Info

• [ ] offer suggestions to update/ improve loading time (Ryan says that by completing this checklist, we can arrive at the suggestions for improvement)
• [ ] provide recommendations for optimizing data loading performance based on test findings (same as above)
• [ ] Provide recommendations to optimize wait experience (same as above)

[ryanfchase]

Thanks @cottonchristopher -- now going to meet with @Skydodle and consider next steps for making this available for devs to pick up.