Quick answer. A documented connection route does not establish a measured latency advantage. This page does not claim that Native Mode is a specific number of milliseconds faster than a bypass route.
Start with the actual route
Cronus Zen Link setup documents native PS5 setup and recommends the A1 port for the Zen Link. Follow the current vendor instructions for the hardware model rather than combining steps from different connection methods.
Record the route, firmware, controller port and console settings before comparing timings. If a route requires different settings, it needs an appropriate baseline under those settings.
What would establish a difference?
Repeat the direct and device-connected measurements with the same response screen and display mode. Specify what detects the press, what detects the screen response, and which clock timestamps both events.
Resolution and variability matter. A difference of one sampling step is not automatically a repeatable improvement. A confidence interval describes uncertainty only when its input data and calculation are known.
Scope of this note
Earlier numerical comparisons have been withdrawn because the session readings were unavailable. This is a setup-and-interpretation guide, not an endorsement of either route or a compatibility guarantee. See the measurement checklist.
A figure looks wrong? Report an error
Further notes
- Cronus Zen on PS5 vs Xbox: how to compare input lag
Why console totals alone cannot isolate the latency added by a Cronus Zen.
- Cronus Zen firmware latency: what release notes establish
How to separate firmware fixes from measured input-lag improvements. Release notes do not establish a fastest firmware.
- Wired vs wireless through Cronus Zen: what to compare
Connection type alone does not determine latency. Compare the same controller, host and display under recorded conditions.