Skip to main content

StorM Web Engine pages on a phone: main-thread blocking

StorM Web Engine1 min readBYTHECLOUD ENT

First-visit main-thread blocking on a phone profile, for the three kinds of StorM Web Engine pages and for award-selected sites measured the same way.

Result

0ms

StorM Web Engine, slowest of three page kinds

21ms

Award-selected sites, fastest quarter

109ms

Award-selected sites, median

Source: Phone-profile page measurement · measured October 17⁠, 2026

Total blocking time adds up every part of a long main-thread task beyond its first fifty milliseconds, from the first contentful paint until the page has been quiet for about two and a half seconds. While that time runs, the page cannot answer a tap. Measured on three kinds of StorM Web Engine pages, a live 3D scene, a walkable space and the engine's own interface site, none blocked for longer than 0 ms.

Of 59 award-winning or selected home pages measured with the same tool and phone profile, the fastest quarter stays at or under 21 ms and the median is 109 ms. The engine's pages do better than 83% of them and tie the rest. One tap on the space's first inner link took 16 ms to process and paint, against the common threshold of 200 ms for a good response.

Conditions

These are lab readings, not visitors' field data: a phone screen 390 pixels wide, the processor slowed 4 times, a throttled mobile connection, and three successful runs per page kind, with failed attempts retried. The reference sites were measured with the same tool and profile but without a GPU. The engine's pages ran with one, because its live scenes draw on it.

More from Research

  1. StorM Web EngineThe StorM Web Engine initial load
  2. BWSA path tracer against exact answers
  3. StorMSymbiosis as a research principle