One command analyzes your webpack config, finds what's slow, runs a full Lighthouse audit, and generates a shareable report — then fixes everything with a diff preview and automatic backup.
npx pterospeed@latest full no install required · Node 20+ · works on any Pterodactyl fork
5 min → 78s
production build
5–10×
faster warm builds
0
code changes needed
30s
setup time
The problem
The default webpack config that ships with Pterodactyl Panel was written to work, not to be fast. Every build starts from zero and pays the full cost.
$ yarn build:production
webpack compiled in
352s
after pterospeed optimize --preset aggressive
~78s
same output · no code changes
How it works
pterospeed full runs build analysis and Lighthouse in one flow,
then generates a shareable report link.
analyze + audit in one run
apply optimizations
Features
0–100 score with per-finding detail, impact rating, and estimated time savings before you touch anything.
Run real Lighthouse against your live panel. Core Web Vitals, performance score, and actionable issues.
Config edits use recast — preserves your formatting. No regex, no fragile string replace.
Every `full` run generates a short URL at pterospeed.me/r. Share with your team in one line.
Snapshot saved to .pterospeed/backups before every write. `pterospeed revert` to undo instantly.
Auto-detects Pterodactyl, webpack version, package manager, and panel URL from .env.
Optimizations
| Optimization | Preset | Expected gain |
|---|---|---|
| Webpack filesystem cache | safe | Warm builds 5–10× faster |
| babel-loader disk cache | safe | Cold builds ~20–30% faster |
| Scope source-map-loader | safe | Skips all of node_modules |
| Explicit CPU parallelism | safe | Full core utilization |
| minimize: isProduction | safe | Dev skips minification |
| EsbuildPlugin (prod) | aggressive | Production minify 3–4× faster |
After aggressive preset, run yarn install to install esbuild-loader.
CLI Reference
pterospeed full [path] Build analysis + Lighthouse site audit in one run pterospeed analyze [path] Scan webpack config and report build health score pterospeed optimize [path] Diff → confirm → apply fixes with backup pterospeed optimize --auto Skip confirmation prompt pterospeed optimize --dry Show diff only, write nothing pterospeed optimize --preset aggressive Also replace TerserPlugin → EsbuildPlugin pterospeed audit [url] Run Lighthouse against your live panel pterospeed benchmark [path] Measure cold / warm / production build times pterospeed revert [path] Restore last backup No install. No config. No risk. Backup created before touching anything.
npx pterospeed@latest full