Next step · What to do next

Speed up the site before launch (performance pass)

What you may see

I want the site to open fast on phones

Why this step

A short, measured pass on images, scripts, fonts and caching gives most of the gain for little work.

Before you start

Can you test the live page on a real phone on mobile data?

The prompt for this step

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.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

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

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step 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.

WHAT I WANT NEXT
Speed up the site before launch (performance pass)

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
A short, measured pass on images, scripts, fonts and caching gives most of the gain for little work.

DO THESE STEPS, IN THIS ORDER
1. Measure the main pages on a throttled phone profile and record load time, weight and biggest files.
2. Fix in this order: images (size, format, lazy loading, dimensions), fonts (two at most, swap), scripts (remove unused, defer third parties), caching and compression, then server speed.
3. Measure again after each change and keep a before and after table.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The table shows clear improvements and the page looks and works the same.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not change design or remove features for a score.
- 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 the main pages on a throttled phone profile and record load time, weight and biggest files.
Fix in this order: images (size, format, lazy loading, dimensions), fonts (two at most, swap), scripts (remove unused, defer third parties), caching and compression, then server speed.
Measure again after each change and keep a before and after table.

Do not do this

Do not optimise things that are already fast.
Do not change design or remove features for a score.

Try another entry