-
Performance
Audit my page weight and cut the fat
Measure what each page actually ships to the browser and cut the biggest offenders before launch.
Free Prompt
I want to know how heavy my pages actually are and slim down the worst ones before launch.
For my main pages (landing page, signup, login, and the primary authenticated screens), measure or estimate total transferred weight: HTML, CSS, JavaScript, images, fonts, and third-party scripts. If you can run a real audit with a tool like Lighthouse or a bundle analyzer, do that and cite the numbers. If not, analyze my bundles and assets statically.
Then:
1. Rank the pages by total weight and identify the largest single contributors on each.
2. Flag anything obviously wrong: unoptimized images measured in megabytes, full libraries imported for one function, duplicate dependencies, fonts loading in every weight when two are used.
3. For each finding, propose the specific fix and its expected size reduction.
Prioritize by impact: the landing page and signup flow matter most because they're the first impression and often the slowest, and mobile visitors feel every kilobyte.
Don't rewrite anything yet. Deliver the ranked findings and proposed fixes first, then I'll tell you which to implement.
What This Does / How This Helps
This measures what your pages actually ship to browsers, ranks the heaviest contributors, and proposes concrete cuts with expected savings. Page weight is a silent conversion killer. A three-megabyte landing page feels instant on your office fiber and broken on a phone over hotel wifi, which is exactly where a chunk of your launch traffic will come from. AI-generated frontends bloat easily: entire icon libraries, unused CSS frameworks, and hero images straight from the camera. An audit turns 'the site feels slow' into a list of fixes with numbers attached.
Want to skip doing this by hand?
Fortivibe audits your app for all of the areas these prompts cover (and more).