◆ HTML

Speed up website 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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCompress the large header image on the 'About Us' page. It's currently 5MB, and it needs to be…+
Compress the large header image on the 'About Us' page. It's currently 5MB, and it needs to be smaller for faster loading.
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 the Black Friday sale goes live, optimize the main landing page for speed. Make sure…+
Before the Black Friday sale goes live, optimize the main landing page for speed. Make sure images are properly sized, remove any unused CSS, and defer any non-critical JavaScript so it loads quickly on a mobile connection.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe marketing team is complaining the new campaign page is loading slowly, and they're worried…+
The marketing team is complaining the new campaign page is loading slowly.
The marketing team is complaining the new campaign page is loading slowly, and they're worried about conversion rates. I've already compressed the images, but it still feels sluggish. I'm afraid I've missed something obvious, or worse, introduced a hidden bottleneck. What are the most common overlooked culprits for slow page loads on a new campaign page, and what's the first thing I should check after image optimization?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI always seem to be scrambling to optimize page speed right before launches, leading to rushed…+
I always seem to be scrambling to optimize page speed right before launches.
I always seem to be scrambling to optimize page speed right before launches, leading to rushed fixes and missed opportunities. This last-minute stress is unsustainable. What habit should I change in my development process to consistently build fast-loading web pages from the start, rather than fixing them at the end?
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 HTML'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.