Fix · Speed

A page or action is slow because of the database or server

Blocks your work

What you may see

The page shows a spinner for seconds before data appears
It got slower as data grew

Most likely cause

Many small requests one after another, missing indexes, big result lists, or a database far from the server make answers slow.

Check first (about two minutes)

Time the request in the Network tab (waiting time). Is it the server or the download?

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior web performance engineer who explains speed problems to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

THE PROBLEM
A page or action is slow because of the database or server

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
Many small requests one after another, missing indexes, big result lists, or a database far from the server make answers slow.

DO THESE STEPS, IN THIS ORDER
1. Measure which requests are slowest and how many are made for one page.
2. Combine requests (fetch what the page needs in one go), run independent ones in parallel, and fetch only the needed columns with paging.
3. Add indexes for the columns used in filters and sorting (with a migration and a rollback that I run myself).
4. Cache data that rarely changes, and keep the server and the database in the same region.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The same page makes fewer requests, each answer is fast, and the data is the same as before.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not cache private data in a shared cache.
- Do not run changes on the live database yourself.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Measure which requests are slowest and how many are made for one page.
Combine requests (fetch what the page needs in one go), run independent ones in parallel, and fetch only the needed columns with paging.
Add indexes for the columns used in filters and sorting (with a migration and a rollback that I run myself).
Cache data that rarely changes, and keep the server and the database in the same region.

Do not do this

Do not fix slowness by showing less data without asking.
Do not cache private data in a shared cache.
Do not run changes on the live database yourself.

Try another entry