EditorStack benchmarks

• Bundle size — the JavaScript your users download for the editor core: installed alone, imported through its documented entry point, bundled with esbuild 0.25.10 (bundle, minify, format=esm, platform=browser, target=es2020, NODE_ENV=production), gzipped with zlib level 9. CSS is excluded. Peer dependencies such as React are treated as external, because your app already ships them.
• Time to first editor — Time from navigation start until the editor’s own root element is present in the DOM, measured with performance.now() inside the page. Median of 5 runs in Chromium (Playwright build 1194), headless.

Limitations. Measured on a warm local HTTP server with no network latency and no CPU throttling. Treat these as relative costs between libraries, not as field performance. Bundle size says nothing about features: a small core that needs five plugins can end up larger than a big one that needs none. Neither number measures editing performance on large documents, accessibility or output quality. Hosted SDKs and platforms cannot be installed and bundled locally, so they are not benchmarked — that is a limit of the method, not a verdict on the product.

Every number is reproducible: the scripts are in the repository, and the build fails if a number on the site differs from the recorded run. The full method is on the methodology page.