Skip to content

HAR analysis: Launchpad → Place view

Source: launchpage -> control room place.har — Launchpad → select Place view → click control room.

Flow: User is on the launchpad, switches to Place view, then opens a control room. The map shows events, places, and assets together — so all three data types are required at init.

Page timings:

  • Content load: ~1,278 ms
  • Full load: ~2,768 ms

Expected vs duplicated calls

The map needs events, places, and assets to render. A minimal init would be:

API Expected Observed Duplicates
GET /controlrooms/{id}/assets?size=500 1× (map) 2× 1 extra
GET /controlrooms/{id}/assets?size=500&page=1 1× (if >500 assets) 2× 1 extra
POST /controlrooms/{id}/events/search 1× (map) 3× initial 2 extra
GET /controlrooms/{id}/places 1× (map) 2× 1 extra
GET /controlrooms/{id} 1× 5× 4 extra
GET /controlrooms/{id}/collaborators 1× 4× 3 extra
GET /controlrooms?size=100 1× 2× 1 extra
GET /controlrooms/{id}/config 1× 2× 1 extra
POST /cycles/summary 1× (place types) 4× (2 pairs) 3 extra
POST /tasks/{id}/search 1× 3× 2 extra
GET /controlrooms/{id}/events/summary 1× (insights panel) 2× 1 extra
GET /me/preferences?namespace=control-room-... 1× 2× 1 extra

Duplicated API calls (summary)

API Count Notes
GET /controlrooms/{id} 5× Same pattern as Event view
GET /controlrooms/{id}/collaborators 4×
POST /cycles/summary?size=250 4× Two pairs of identical calls
POST /tasks/{id}/search 3×
POST /events/search (initial) 3× Map needs 1×; 2 extra
GET /controlrooms/{id}/assets?size=500 2× Map needs 1×; 1 extra
GET /controlrooms/{id}/assets?size=500&page=1 2× 1 extra
GET /controlrooms/{id}/places 2× Map needs 1×; 1 extra
GET /controlrooms/{id}/events/summary 2×
GET /controlrooms?size=100 2×
GET /controlrooms/{id}/config 2×
GET /me/preferences (control-room namespace) 2× Same namespace

Asset polling duplicate

  • assets?recordedAfter=2026-03-10T23:17:54.996Z fires 2× (23:17:55.484 and 23:17:56.727).

Improvement opportunities

Same as Map/Assets and Event view: deduplicate control room, collaborators, config, getControlRooms, cycles, tasks, events/search, assets, places. Route shared data through the store so the map and panels consume a single load.

Estimated impact

  • Before: ~35 API calls in first ~12s (initial load).
  • After fixes: ~15–18 calls — ~50% reduction (keeping 1× assets, 1× events, 1× places for map).