SolidStart
Dev Time
Section titled “Dev Time”Dev Time benchmarks use each meta-framework’s starter-* package.
Each starter follows its framework’s CLI or documented setup, with the selected options and adjustments recorded in the methodology.
See Default Benchmark Setup for the shared benchmark environment.
Dependency Counts
Section titled “Dependency Counts”Methodology: Dependency Counts.
Measuring a meta-framework’s dependencies isn’t as straightforward as you might think. You could:
- Measure just the meta-framework package itself
- Maybe a full project setup
Both approaches have flaws. Some meta-frameworks need many other packages to work. A full project setup can include more packages than necessary.
To provide a clearer picture, we run the dependency-count tests three times, starting small and expanding in scope. In this order, we:
- Start with the meta-framework package itself, for example,
@sveltejs/kit - We then expand this to the meta-framework and its first-party packages. Looking at
@sveltejs/kitagain, this means any package maintained by the meta-framework authors that’s needed to run a project, for example, thesveltepackage. - Finally, we count the dependencies for the entire
starter-*project. Their CLI or documentation recommends this setup by default, so this is the default most people will start with.
Core Package · Production Dependencies
| Framework version | Dependencies |
|---|---|
| 2.0.6 | 25 |
The latest release is shown as a filled point; earlier releases use outlined points.
Core Package · Development Dependencies
| Framework version | Dependencies |
|---|---|
| 2.0.6 | 4 |
The latest release is shown as a filled point; earlier releases use outlined points.
Core Package · All Dependencies
| Framework version | Dependencies |
|---|---|
| 2.0.6 | 29 |
The latest release is shown as a filled point; earlier releases use outlined points.
Starter Project · Production Dependencies
| Framework version | Dependencies |
|---|---|
| 2.0.6 | 6 |
The latest release is shown as a filled point; earlier releases use outlined points.
Starter Project · Development Dependencies
| Framework version | Dependencies |
|---|---|
| 2.0.6 | 1 |
The latest release is shown as a filled point; earlier releases use outlined points.
Starter Project · All Dependencies
| Framework version | Dependencies |
|---|---|
| 2.0.6 | 242 |
The latest release is shown as a filled point; earlier releases use outlined points.
Starter Project · Duplicate Dependencies
| Framework version | Duplicates |
|---|---|
| 2.0.6 | 5 |
The latest release is shown as a filled point; earlier releases use outlined points.
Node Modules Size
Section titled “Node Modules Size”Methodology: Node Modules Size.
Node Modules Size
| Framework version | MB |
|---|---|
| 2.0.6 | 128.50 MB |
The latest release is shown as a filled point; earlier releases use outlined points.
Dependency Install Size
| Framework version | MB |
|---|---|
| 2.0.6 | 104.51 MB |
The latest release is shown as a filled point; earlier releases use outlined points.
Build and Install Times
Section titled “Build and Install Times”Methodology: Build and Install Times.
Median Install Time
| Framework version | Seconds |
|---|---|
| 2.0.6 | 1.86s |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Cold Build Time
| Framework version | Seconds |
|---|---|
| 2.0.6 | 3.06s |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Warm Build Time
| Framework version | Seconds |
|---|---|
| 2.0.6 | 3.10s |
The latest release is shown as a filled point; earlier releases use outlined points.
Dev Server Startup
Section titled “Dev Server Startup”Methodology: Dev Server Startup.
Median Dev Server Startup Time
| Framework version | Seconds |
|---|---|
| 2.0.6 | 2.60s |
The latest release is shown as a filled point; earlier releases use outlined points.
Core-JS Polyfills
Section titled “Core-JS Polyfills”Methodology: Core-JS Polyfills.
Size of JS Files Containing Core-JS
Combined size of matching build output files, including any other code in those files.
| Framework version | KB |
|---|---|
| 2.0.6 | 0.00 KB |
The latest release is shown as a filled point; earlier releases use outlined points.
Browser Baseline
Section titled “Browser Baseline”Methodology: Browser Baseline.
| Version | Baseline | Feature | Year | Features |
|---|---|---|---|---|
| 2.0.6 | High | — | 2020 | 33 |
Run Time
Section titled “Run Time”Runtime apps implement comparable benchmark routes across frameworks. See Default Benchmark Setup for the shared environment and each framework’s build tool and adapter. Test-specific differences are documented in the linked methodology sections below.
Client Side Rendered Tests (Lighthouse)
Section titled “Client Side Rendered Tests (Lighthouse)”These CSR browser performance tests use Lighthouse to measure paint timings and a controlled navigation interaction.
Methodology: Client Side Rendered Tests (Lighthouse).
Some frameworks have been moved off their golden path to make client side tests fair when comparing. See the methodology link above for the full details.
Client First Paint (Lighthouse)
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 97.00 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Client FCP (Lighthouse)
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 96.52 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Client Interaction Breakdown by Version (Lighthouse)
Not enough data yet. This chart needs at least two versions.
Server Side Rendered Tests (Lighthouse)
Section titled “Server Side Rendered Tests (Lighthouse)”These SSR browser performance tests use Lighthouse to measure paint timings and a controlled navigation interaction.
Methodology: Server Side Rendered Tests (Lighthouse).
Server First Paint (Lighthouse)
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 86.00 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Server FCP (Lighthouse)
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 85.92 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Server Interaction Breakdown by Version (Lighthouse)
Not enough data yet. This chart needs at least two versions.
Server Side Throughput Tests
Section titled “Server Side Throughput Tests”Methodology: Server Side Throughput Tests.
Ops/sec
| Framework version | Operations per second |
|---|---|
| 2.0.6 | 404 |
The latest release is shown as a filled point; earlier releases use outlined points.
Body Size
| Framework version | Kilobytes |
|---|---|
| 2.0.6 | 224.26 KB |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Latency
Median of measured run average latencies; not a pooled request-level median.
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 2.52 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
SSR Load Test
Section titled “SSR Load Test”Methodology: SSR Load Test.
Each runtime app renders the same 1,000-row, three-column table using ordinary
<a> links. This compares server rendering under HTTP load without the extra work
of rendering framework router link components. Requests still pass through each
framework’s server routing. No browser runs and no links are clicked.
Total Measured Requests
| Framework version | Requests |
|---|---|
| 2.0.6 | 55494 |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Sweep P99 Latency at 25 Connections
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 90.00 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Sweep P99 Latency at 50 Connections
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 301.00 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Sweep P99 Latency at 100 Connections
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 1994.00 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Sweep P90 Latency at 25 Connections
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 64.00 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Sweep P90 Latency at 50 Connections
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 138.00 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Sweep P90 Latency at 100 Connections
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 139.00 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Sweep P75 Latency at 25 Connections
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 54.00 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Sweep P75 Latency at 50 Connections
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 87.00 ms |
The latest release is shown as a filled point; earlier releases use outlined points.
Median Sweep P75 Latency at 100 Connections
| Framework version | Milliseconds |
|---|---|
| 2.0.6 | 121.00 ms |
The latest release is shown as a filled point; earlier releases use outlined points.