> ## Documentation Index > Fetch the complete documentation index at: https://docs.superoffice.com/llms.txt > Use this file to discover all available pages before exploring further. # Performance benchmarking > How the pre-cutover DocFx performance baseline was captured (issue A post-launch **Performance Verification Period (PVP)** checks that the new platform performs acceptably once it's live and under real traffic. That check needs something real to compare against - this page documents how the pre-cutover baseline was captured, and how to rerun the same methodology once Mintlify is live so the comparison is methodologically sound. This is a manual, periodic exercise, not a CI check, so it lives here rather than in [Automated tests][1]. The scripts themselves are in `tools/benchmarks/` - see that folder's `README.md` for the full script-by-script reference and the captured results. ## Reading the numbers Every metric on this page is reported as **p50** and **p95** - percentiles across many repeated runs, not a single measurement. **p50** (the median) is the typical experience: half the runs were faster than this, half slower. **p95** is the near-worst-case: only 5% of runs were slower than this - useful for catching occasional bad experiences that an average would smooth over and hide. A page with a fast p50 but a much slower p95 is inconsistent (fast most of the time, but with a real minority of slow loads). A page where p50 and p95 sit close together is consistently fast or consistently slow, with little variance either way. ## Setup and running The scripts are plain Node - nothing about them is tied to the machine they were first run on. To run them (on any machine with a clone of this repo): ```bash theme={null} cd tools/benchmarks npm install npx playwright install chromium ``` Then run any script directly, for example: ```bash theme={null} node run-pageload-benchmark.mjs node search-latency-raw.mjs node search-latency.mjs node nav-responsiveness.mjs ``` Each writes into `results/