Framework Tracker

Framework Tracker compares the real cost of building with modern web frameworks. It looks at what developers inherit when they start a project and what users and servers experience when it runs.

The goal is not to crown one universal winner. It is to make trade-offs easier to see, from the dependencies you will inherit to the cost to your CI/CD pipelines, server performance, how fast the browser first paints, and more. It’s an ever-growing list of tests that we will add to with community support.

If you find an issue with a test or have an idea for new ones, please open an issue in our repo: Framework Tracker Github Project

What we measure and how

We currently split our tests into two sections: Dev Time and Run Time. Dev Time tests use a starter project set up with the Metaframeworks CLI or Docs, following the default or recommended setup. Runtime tests use a small app project set up for the measurements. We currently measure:

DevTime

Dependancy counts
Node Modules Size
Build and Install Times
Dev Server Startup
Core-JS Polyfills
Browser Baseline
Minimum Node Version

RunTime

Lighthouse Client-Side Rendered
Lighthouse Server-Side Rendered
Server-Side Throughput
SSR Load Tests
SS Framework Router Link Load Test
Exports from Core Web Vitals

Tests run in the CI pipeline, and we save the results to a JSON file that the Astro docs site loads. The Methodology page explains how we collect each metric.

We track metrics for all major and minor versions. Stats show the latest version we have. You can click into each Framework detail page to see changes over time

All of the testing and stat generation is run by our infrastructure partner Depot to ensure consistent, fairer, and faster testing.