OptiSigns · Customer experience

How quickly people can use the portal

LIVE METRICS

FOCUS NOWWaiting for measurements.

Performance Report

OptiSigns portal & GraphQL API

Signage view Saved demo

Performance that customers feel

Where are users waiting?

Start with the time it takes to use the product. Then connect the slow journeys to a measurable next step.

Loading real-user journeys…

Waiting for journey evidence.

What we should do next

Cold Screens readiness

Trace authentication, data loading and rendering on the same cold route.

Evaluate: prefetch gating (!2995) and dialog splitting (!2619).

Proof: compare the served builds with the same account, browser and cache state.

The browser gap

Use the browser breakdown to choose comparable traces.

Investigate: Safari, Firefox and Chromium on the same route.

Proof: reproduce the difference under matching conditions before assigning a cause.

Backend attribution

Check whether current operation-level measurements are available.

Next step: verify the metrics listener and scrape in both API clusters.

Proof: fresh operation rates that identify the requests contributing to slow journeys.

This report is a baseline, not proof of an improvement. Compare matching measurements from both builds before claiming a speedup.

Supporting evidence and diagnostics Browser timings, API health, source status and historical query samples

Status i

API latency and browser measurement

Crawlability i

Where every number comes from i

Recommended actions 5 priorities i

Page load real users i

Where the time goes

One scripted load, every 15 minutes — explains the number above, does not replace it.

What the page loads

Requests vs. weight

The same categories measured two ways. Where the bars disagree is where the cost is.

Slowest requests

Duration of the six slowest network requests.

API — by GraphQL operation i

Journeys — real users i

Journeys — synthetic canary the five from the brief i

Reliability — errors & availability i

Loading…

Synthetic origin probe origin observation i

Probing…

Database — query efficiency Atlas Performance Advisor i

API latency by host

Traffic share

Proportion of measured requests per host. Shown as a stacked bar rather than a pie because a 1.8% slice has to stay legible — and that slice is the finding.