◆ JavaScript

Measure performance

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need the page load and API timings for the new dashboard component measured end-to-end; run…+
I need the page load and API timings for the new dashboard component measured end-to-end; run Lighthouse and the browser timing suite against the dashboard route, capture First Contentful Paint, Time to Interactive, and API RTTs for the authenticated endpoints, and hand me a short list of the three slowest requests to fix before Tuesday's demo.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I hand this to the performance team, make the measurements reviewer-friendly: put the…+
Before I hand this to the performance team, make the measurements reviewer-friendly: put the key metrics (FCP, TTI, Largest Contentful Paint) at the top, include a short explanation of the test environment (Chrome stable, throttling: 4x CPU, 1x network), and highlight any requests or scripts that add more than 300ms to interactive time. Flag any single script over 50 KB parsed size.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentUsers reported the dashboard feels sluggish only on older laptops; I ran traces in staging and…+
Dashboard feels sluggish for some users
Users reported the dashboard feels sluggish only on older laptops; I ran traces in staging and saw TTI jump from 1.2s to 3.8s on those devices. I don't know whether heavy parsing, main-thread work, or network congestion is the main culprit. Which diagnostic should I run next to pinpoint the dominant cause and what exact metric will show it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery release I find myself firefighting a single slowdown that slipped past review and cost a…+
Performance regressions appear late in the sprint
Every release I find myself firefighting a single slowdown that slipped past review and cost a hotfix. I repeatedly wait until the demo to notice regressions. Where am I most likely failing in our review process and what single habit change would prevent these last-minute performance surprises?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.