Skip to content

Updated Repetition Wording #436

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AlexanderKaran merged 1 commit into from
Aug 30, 2026
Merged

Updated Repetition Wording #436

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 16 additions & 3 deletions packages/docs/src/content/docs/methodology.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -182,7 +182,14 @@ throughput, and load behavior for comparable production apps.
- Interaction latency is the sum of Lighthouse's input delay, processing
duration, and presentation delay. It represents this controlled interaction,
not the page-lifetime INP metric.
- Results are averaged across five production-build runs.
- CI creates one production build and starts one production server, which stays
running for all five measurements. Each measurement launches a fresh Chrome
process.
- The arithmetic mean is reported. Raw samples and their sample standard
deviation are retained.
- Valid slow results are kept rather than discarded as outliers. A measurement
is invalid only when a required Chrome paint or interaction value is missing
or not greater than zero.
- These tests measure route-based client rendering, not forced SPA
configurations. Each framework uses its supported production routing and
rendering controls.
Expand Down Expand Up @@ -211,8 +218,14 @@ throughput, and load behavior for comparable production apps.
preloading is allowed when it is part of the framework's default link
behavior, but the measured SSR routes are still rendered on demand rather than
converted to prerendered static output.
- Benchmarks run 5 times by default and require every Chrome paint and
interaction measurement to be present and greater than zero.
- CI creates one production build and starts one production server, which stays
running for all five measurements. Each measurement launches a fresh Chrome
process.
- The arithmetic mean is reported. Raw samples and their sample standard
deviation are retained.
- Valid slow results are kept rather than discarded as outliers. A measurement
is invalid only when a required Chrome paint or interaction value is missing
or not greater than zero.
- Astro keeps the default static output mode, but the measured
`/server-side-rendered` route and its detail route use
`export const prerender = false` so they are rendered on demand by the
Expand Down
Loading