Group
  • Performance

    Measure my performance baseline before optimizing anything

    Get real numbers on where the time goes so you fix the actual bottleneck instead of guessing.

    • Plan & validate
    • Debug & fix
    • Beginner
    • General

Free Prompt

I want to make my app faster but I don't actually know where the time goes. Before changing anything, I want a measured baseline. Set up measurement and produce a baseline report: 1. Front end: for my key pages (landing, signup, the main app screen, the heaviest data screen), capture load metrics: time to first byte, first contentful paint, largest contentful paint, total blocking time, total page weight and request count. Use a throttled connection profile, not my fast dev machine on localhost. 2. Back end: identify my slowest endpoints and database queries. Add timing where it's missing (request duration logging, slow query logging). List the top offenders with actual numbers. 3. Separate the time into buckets per page: network, server processing, database, client rendering, third-party scripts. I want to know which bucket dominates. 4. Rank the findings by impact: what single fix would help the most users the most? Distinguish 'feels slow' issues (rendering, layout) from 'is slow' issues (server, queries). Don't optimize anything yet. Don't recommend changes without measurements behind them. The deliverable is the baseline report: numbers per page and per endpoint, the time breakdown, and a ranked list of where optimization effort will pay off. This becomes the 'before' I compare against after fixes.

What This Does / How This Helps

This sets up real measurement across your pages, endpoints, and queries, then produces a ranked report of where the time actually goes before you change any code. Teams routinely spend days optimizing the wrong thing: shaving the bundle while the real problem is a 2-second database query, or tuning queries while the page is actually slow because of a chat widget. Without a baseline you can't tell whether a change helped, and you'll feel productive while the app stays slow. An hour of measuring tells you exactly which fixes matter and gives you the before/after proof that they worked.

Want to skip doing this by hand?

Fortivibe audits your app for all of the areas these prompts cover (and more).

See What We Check

Related Prompts