Skip to content

HAR analysis: Launchpad → Map/Assets navigation

Source: platform.skyledge.com.har — single navigation from control room launchpad to map/assets view.

Page timings:

  • Content load: ~1,367 ms
  • Full load: ~3,851 ms

Duplicated API calls (observed)

API Count Notes
GET /controlrooms/{id} 4× Same control room fetched 4 times in ~1.5s (breadcrumb + effects + page service + getMyControlRooms flow)
GET /controlrooms/{id}/collaborators 3× Collaborators loaded 3 times within ~2s
GET /controlrooms?size=100 2× Full control rooms list fetched twice (page service + another consumer)
GET /controlrooms/{id}/config 2× Config fetched twice within ~50ms
POST /cycles/summary?size=250 2× Identical request, same timestamp — clear duplicate
POST /tasks/{id}/search?size=1&page=0 2× Task count fetched twice
POST /events/search 2× initial + polling Initial search called twice; then polling every ~5s (by design)

Initial load sequence (first ~3 seconds)

  1. getControlRoom (×4), getCollaborators (×2), getPreferences, task/search — parallel burst
  2. getAssets, events/search, getPlaces, getPreferences (mapControls)
  3. getControlRoom again, getConfig (×2), getControlRooms, getApps
  4. events/search again, getPreferences (assetViewOrientation)
  5. getControlRooms again, cycles/summary (×2), task/search again, getCollaborators again
  6. assets?page=1 (pagination), events/summary
  7. POST /me/preferences

Polling (after initial load)

  • events/search?after=... — ~5s interval
  • assets?recordedAfter=... — ~5s interval (and sometimes 2× in quick succession with same recordedAfter)

Improvement opportunities

  1. Deduplicate getControlRoom — 4 calls → 1 (breadcrumb resolver + effects + page service consolidation).
  2. Deduplicate getCollaborators — 3 calls → 1.
  3. Deduplicate getControlRooms — 2 calls → 1 (page service vs another consumer).
  4. Deduplicate getConfig — 2 calls → 1.
  5. Fix cycles/summary — identical double call; likely two components subscribing without coordination.
  6. Fix tasks/search — task count requested twice.
  7. Fix initial events/search — 2× with same params; consolidate.
  8. Asset polling — occasional duplicate assets?recordedAfter=... with same timestamp; debounce or dedupe.

Estimated impact

  • Before: ~35 API calls in first 3s (excluding static assets, RUM, Amplitude, Maps).
  • After fixes: ~20–25 calls — potential 30–40% reduction in initial burst.