Navigation Latency

Name: Navigation Latency
Author: nexus-labs-automation

ASecurity

Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.

116 stars
0 votes
0 copies
2 views
Added February 7, 2026

developmentgoreactperformance

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add nexus-labs-automation/mobile-observability --skill navigation-latency --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Navigation Latency?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Navigation Latency

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nexus-labs-automation-navigation-latency/badge)](https://www.skillsdirectory.com/skills/nexus-labs-automation-navigation-latency)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: navigation-latency
description: Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.
triggers:
  - "deep link performance"
  - "measure TTI"
  - "screen load time"
  - "slow screen navigation"
  - "tab switch latency"
  - "track screen transitions"
priority: 2
---

# Navigation Latency

Time from tap to destination screen interactive (TTI).

## Phases

```
TAP → TRANSITION → VIEW_INIT → DATA_LOAD → INTERACTIVE
     |_____________________________________________|
                   Navigation Latency
```

## When to Use

- Tab bar taps
- List item → detail screen
- Deep link → target screen
- Any screen-to-screen transition

## Key Thresholds

| Rating | Duration |
|--------|----------|
| Good | <400ms |
| Acceptable | <1s |
| Poor | >1s |

## Measurement Points

1. `onNavigationStart` - user taps (source screen)
2. `onViewAppear` - destination view visible
3. `onContentReady` - data loaded, interactive

## Implementation

See `references/ui-performance.md` (Navigation Latency section) for:
- iOS: NavigationLatencyTracker with os_signpost
- Android: Fragment/Activity lifecycle hooks
- React Native: React Navigation listeners

## Common Mistakes

- Measuring only view appear (missing data load)
- Not correlating source → destination
- Ignoring warm vs cold screen loads

## Related Skills

- See `skills/interaction-latency` for button/tap response times (vs full screen loads)
- Combine with `skills/user-journey-tracking` to correlate navigation with user intent