Mosmox UI
Current version
GitHubnpmjs.com

Performance Test Results

Comparable browser performance measurements for Mosmox UI and popular React, Vue, and Angular UI frameworks.

This page contains reproducible local measurements for Mosmox UI and nine popular React, Vue, and Angular UI solutions. The results compare this specific workload, machine, browser, dependency lockfile, and viewport—not every possible use case. A separate button stress test is included below; it is intentionally not merged into the production-like ranking.

Test workload

Every implementation renders the same production page with 500 interactive cards, a filter input, a toggle, and four equivalent test actions. Playwright opens each page in headless Chrome at 1440×900, waits for the application-ready marker, and performs five runs per implementation.

Measured values:

  • Cold load — time from navigation until the page is loaded and ready.
  • App ready — time until the first application-ready marker after render.
  • Local update — time to update one local control without changing the card collection.
  • Bulk update — time after changing the content revision of all 500 visible cards.
  • Filter update — time to filter the collection to the matching cards.
  • Toggle update — time to toggle the controlled state.
  • DOM nodes — number of DOM nodes after the initial render.
  • Transfer — bytes transferred for page resources.
  • JS heap — approximate JavaScript heap usage reported by Chrome.

Browser render speed ranking

Because the primary goal of this benchmark is browser rendering speed, the main ranking is ordered by App ready: the time until the first complete application-ready marker after the initial render. Cold load is shown as a secondary loading signal. Lower values are better.

RankImplementationApp readyCold loadBulk updateDOM nodesTransferJS heap
1Mosmox UI46 ms88 ms97 ms2,536409.1 KB4.9 MB
2React · MUI79 ms129 ms117 ms2,537349.0 KB12.8 MB
3Angular · Material92 ms125 ms93 ms4,070465.3 KB8.1 MB
4Vue · Element Plus101 ms114 ms117 ms3,038511.0 KB14.0 MB
5Angular · NG-ZORRO112 ms138 ms95 ms2,538996.1 KB14.2 MB
6Vue · Quasar115 ms139 ms119 ms3,545479.1 KB15.2 MB
7React · Ant Design117 ms167 ms128 ms3,052553.5 KB25.8 MB
8Angular · PrimeNG124 ms150 ms92 ms2,038343.6 KB16.0 MB
9React · Chakra UI149 ms159 ms125 ms2,536500.0 KB18.7 MB
10Vue · Vuetify214 ms237 ms177 ms8,065508.8 KB44.9 MB

After removing the redundant simple-button wrapper, Mosmox UI remains first for initial browser render at 46 ms and now matches Chakra UI's DOM count at 2,536 nodes. The five-run median still shows other libraries leading some specialized interaction paths, so those results remain separate rather than being folded into a synthetic overall score.

Visual comparison

The charts below make the most important timing differences easier to scan. Each chart uses one scale for all implementations; a shorter bar means a faster result. The primary render chart and the interaction charts are separate tests.

Browser render speed ranking

Button stress test

2,000 direct Button components · five-run medians

React frameworks

RankImplementationCold loadApp readyBulk updateDOM nodesTransferJS heap
1React · MUI129 ms79 ms117 ms2,537349.0 KB12.8 MB
2React · Ant Design167 ms117 ms128 ms3,052553.5 KB25.8 MB
3React · Chakra UI159 ms149 ms125 ms2,536500.0 KB18.7 MB

Vue frameworks

RankImplementationCold loadApp readyBulk updateDOM nodesTransferJS heap
1Vue · Element Plus114 ms101 ms117 ms3,038511.0 KB14.0 MB
2Vue · Quasar139 ms115 ms119 ms3,545479.1 KB15.2 MB
3Vue · Vuetify237 ms214 ms177 ms8,065508.8 KB44.9 MB

Angular frameworks

RankImplementationCold loadApp readyBulk updateDOM nodesTransferJS heap
1Angular · Material125 ms92 ms93 ms4,070465.3 KB8.1 MB
2Angular · NG-ZORRO138 ms112 ms95 ms2,538996.1 KB14.2 MB
3Angular · PrimeNG150 ms124 ms92 ms2,038343.6 KB16.0 MB