Build and Asset Pipeline Performance Review
Make builds and shipped assets lean.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Review my front-end build and what it ships to users. Build tool and framework: [BUILD_TOOL_AND_FRAMEWORK]. Build configuration: [PASTE_BUILD_CONFIG]. Bundle analysis output or file sizes: [BUNDLE_REPORT]. Build time and CI time: [BUILD_TIMES]. Answer each item as Yes, No, or Cannot tell, with the evidence and one fix: [ ] Production build with minification and tree shaking [ ] Code splitting by route; large libraries loaded only where needed [ ] No duplicate versions of the same library in the bundle [ ] Heavy libraries replaced or trimmed (date libraries, icon sets, utility libraries) [ ] Modern output for modern browsers with a measured fallback [ ] Images in efficient formats with responsive sizes [ ] Fonts subsetted, with display strategy set [ ] CSS purged of unused rules [ ] Long-term caching with content-hashed file names [ ] Source maps not shipped publicly unless intended [ ] Build cache and incremental builds enabled in CI [ ] Performance budgets enforced in CI Then list the five biggest files or modules with a specific action for each, estimate the savings in kilobytes, and give a before-and-after measurement plan (build time, transfer size, first load). Do not claim savings you cannot compute from what I gave you.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.