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 to make the trade-offs easier to see and help framework authors iterate and improve each meta-framework. Buidling on the E18E’s mission to improve the JavaScript ecosystem.

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 meta-framework’s CLI or documentation, following the default or recommended setup. Runtime tests use a small app project set up for the measurements. We currently measure:

Dev Time

Run Time

Core Web Vitals

Largest Contentful Paint (LCP): Desktop · Mobile
Cumulative Layout Shift (CLS): Desktop · Mobile
First Contentful Paint (FCP): Desktop · Mobile
Time to First Byte (TTFB): Desktop · Mobile
Interaction to Next Paint (INP): Desktop · Mobile

Dev Time and Run Time 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.

Frameworks

We measure the following frameworks using the versions listed below. The Dev Time, Run Time, and Core Web Vitals pages include all tracked frameworks with available measurements.