-
Notifications
You must be signed in to change notification settings - Fork 1
Performance Metrics and KPIs (Key Performance Indicators)
Richard edited this page May 15, 2024
·
1 revision
By Jennifer Tieu - github: @jennifertieu
For the performance metrics and KPIs, we’ll be focusing on providing a good user experience that is responsive/fast response time, accessible, mobile friendly, cross-browser support, and minimal errors. (*More metrics and KPIs to be added as needed)
TODO: KPIs - specific numbers, initial load time, example: application to load within 3 sec, northstar to load within 1.5 sec
- Specific browsers, version?
- Lighthouse score specific - 90 MVP, 95 Northstar
- Accessibility: 5 error MVP, 0 errors Northstar
- Error-free/reliable - 90% to 99%
- How fast to respond, how fast is response
- Usage metrics - # of users
run it against any web page, public or requiring authentication. It has audits for performance, accessibility, progressive web apps, SEO, and more
- Performance (Response Time)
- Best Practices
- Accessibility
- SEO
Accessibility evaluation tools
- WAVE
- Lighthouse
- Manual Testing of different browsers with the hope of scaling to automated testing tools like BrowserStack, LambdaTest, etc
- Automated testing run by CI/CD pipeline