Turbo mode delays async script execution on JavaScript-heavy pages
0 reputation · 20 Jul 2023, 20:18 UTC
Goal
Assess how Opera Turbo mode's compression proxy influences the execution timing of asynchronous scripts on JavaScript-heavy pages when the free VPN tier is active.
Constraints involve Turbo's routing of HTML, CSS, JavaScript, and images through Opera's compression servers, the free VPN's additional proxy hop that may throttle bandwidth, and the potential for combined routing to increase round-trip time. Uncertainty remains regarding the degree of script delay, which modern web standards (e.g., HTTP/2, WebSockets) the compression proxy does not support, and whether domain-specific policies disable Turbo.
- Does Turbo mode's compression proxy block or delay the execution of async/deferred scripts on JavaScript-heavy pages when the free VPN is enabled?
- What is the measurable increase in round-trip time for script-initiated network requests under dual-proxy (Turbo + VPN) routing?
- Which web standards, such as HTTP/2 or WebSockets, are unsupported by the Turbo compression proxy, leading to functional regressions on modern web applications?