Build developer level performance detection capabilities while auditing 4 major areas of the application for performance improvements. (shared with SoftwareMansion)

### What is this about?

The tiger team focusing on performance made a large impact on application start up times and built out a production monitoring system for performance. This KR focuses on building developer level capabilities that make it easier for developers to identify performance bottlenecks while developing. The four major areas that will be reviewed are based on MixPanel data:

- Wallet View Load
- Switch Networks
- Navigation with the Tab Bar
- Browser View Open

Tactics:

- Establish baseline measurements using developer tooling (implement if needed)
- Document process and provide guidelines

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

Start by reviewing the existing developer performance tooling and the four target areas: Wallet View Load, Switch Networks, tab-bar navigation, and Browser View Open. Establish baseline measurements for these flows, then document the measurement process and performance guidelines; completion should cover all four areas with usable developer-level detection capabilities and documentation.

Written by the indexing model from the issue text.