Faster portal start

Project: Engineering
Type: Epic
Status: Done Done
Priority: Medium
Reporter: Aiko Tanaka <aiko.tanaka@acme-hq.example>
Assignee: Aiko Tanaka <aiko.tanaka@acme-hq.example>
Labels: performance
Components: portal
Fix versions: portal 4.6
Created: 22 Jun 2026, 08:00 UTC
Updated: 10 Jul 2026, 12:30 UTC
Resolved: 10 Jul 2026, 12:30 UTC

Description

Shaped in Emargen: Faster portal start.

Why

The portal takes 4.1 s to first load on a depot PC (mid-range laptop, depot Wi-Fi). Approvers at depots open it to decide one request and wait longer than the decision takes. Ridgeway and Parcelwise both asked (SUP-898, SUP-994).

What we build

Measure on a depot-PC profile, and keep measuring in CI.
Load each part of the portal when it's opened, not all at start.
Drop what we don't need from the bundle.
Fewer calls before the first screen.

Done when

First load under 1.5 s on the depot-PC profile. Target 10 July.

Child issues

ENG-1502 Measure first load on a depot-PC profile, in CI Done
ENG-1504 Load each part of the portal when it is opened Done
ENG-1518 Drop moment.js and the full icon set Done
ENG-1519 Fewer calls before the first screen: keep /api/me and client settings for the session Done
ENG-1535 Access report blank after a deploy (old chunk gone from the server) Done

Linked issues

relates to SUP-898 Ridgeway: portal takes 4–5 seconds to open Done
relates to SUP-994 Parcelwise: portal slow to open on hub PCs Done

Comments (1)

Aiko Tanaka · 10 Jul 2026, 12:30 UTC

1.3 s on the depot-PC profile (from 4.1). CI fails the build above 1.6 s. Closing.