Astro vs Next.js TTI on WooCommerce
Status: protocol, not measured result
This methodology compares Astro 5 and Next.js 15 on the same 50-product WooCommerce headless store.
Related pages: benchmark protocol and methodology index.
Test Corpus
- 50 product detail pages.
- 1 category listing page.
- 1 homepage.
- Shared WordPress 6.7+ origin with WooCommerce 9+.
- Identical product names, images, prices, descriptions, schema and canonical URLs.
Measurement Matrix
| Field | Required value |
|---|---|
| Device profile | Moto G4 |
| Network profile | 4G throttle |
| Run cities | Frankfurt, Warsaw, Amsterdam, Madrid, Stockholm |
| Cache states | cold, warm |
| Runs per route/stack/city/cache state | minimum 5 |
| Primary metric | TTI |
| Secondary metrics | LCP, INP, JS KB, Worker CPU time |
Result Table
| Stack | Cache | City | Median TTI | P75 TTI | Median LCP | P75 LCP | JS KB | Notes |
|---|---|---|---|---|---|---|---|---|
| Astro | pending | pending | pending | pending | pending | pending | pending | pending |
| Next.js | pending | pending | pending | pending | pending | pending | pending | pending |
Publication Gate
Do not call this a result until each route has at least five runs per stack, city and cache state.