Framework Tracker
Framework Tracker compares the practical cost of building with modern web frameworks. It looks at what developers inherit when starting a project, and what users and servers experience when that project runs.
The goal is not to crown one universal winner. It is to make tradeoffs easier to see: dependency footprint, install and build cost, browser support, rendering performance, server behavior, throughput, load handling, and real-world Core Web Vitals signals.
What we include
Section titled “What we include”The tracker currently covers two kinds of comparable projects: starter projects for developer-time measurements, and small implemented apps for runtime measurements. Each framework is measured with the same benchmark intent wherever the framework model allows it.
- Dependency counts, duplicate dependencies, and install size.
- Clean install time, cold build time, warm build time, and output size.
- Core-JS usage and browser baseline support.
- Client-rendered and server-rendered browser performance metrics.
- Server-side request throughput and staged load-test results.
- Desktop and Mobile Core Web Vitals data sourced from HTTP Archive.
Focused frameworks
These are the frameworks shown by default on the focused comparison pages.
All tracked frameworks
These are the additional frameworks included on the all-frameworks page alongside the focused set.
What we are doing
Section titled “What we are doing”These stats are intended to be repeatable, inspectable, and useful for framework discussions that otherwise tend to become anecdotal. The data is still in active development, and the methodology will continue to tighten as more frameworks, versions, and benchmark cases are added.
For the full list of planned comparison areas, see the roadmap.
How it works
Section titled “How it works”Stats are collected from the repository’s framework packages, normalized into JSON, and published into the docs site. The comparison pages then use that data to render charts, tables, and framework detail pages.
Start with Dev Time for project footprint and build costs, or Run Time for browser and server behavior. The Methodology page explains how each metric is collected.