I have read a few hundred portfolios over the years, first as a freelancer trading feedback and later on the other side of a hiring process. The good ones are boringly similar, and the forgettable ones are forgettable in exactly the same way: a hero with a wave emoji, a grid of six screenshots, a skills cloud, a contact form.

Here is what the good ones do instead.

Put the sentence at the top, not the greeting

The first line of the page has one job: tell a stranger what you build and who for. Compare:

Hi! I’m a passionate developer who loves clean code ☕

against

I build design systems for teams that ship on the web. Currently at a two-person studio; previously four years in fintech.

The second one is answerable. Someone can decide, in two seconds, whether to keep reading. That is all a hero has to do.

Three projects, written up properly

Six thumbnails say less than three case studies. For each project I want four paragraphs, in this order:

1. The problem in the client’s language, not yours. “Support was answering the same billing question forty times a week.”
2. What you built, in one paragraph, with the interesting technical decision called out.
3. What happened, with a number if you have one, and an honest “we never measured it” if you do not.
4. What you would change now. This paragraph is the one that makes people trust the other three.

If a project cannot survive that treatment, it is a screenshot, not a case study. Put it in a small list at the bottom.

Show the work, not only the result

A finished screenshot proves taste. A before/after, a wireframe, a paragraph about the approach you tried first and abandoned — that proves judgement, which is the thing being hired.

The cheapest version of this: one paragraph per project titled “the part that was harder than it looked.”

Make the page fast, because it is the demo

Everything on your portfolio is a claim about how you build. A front-end portfolio that ships 900KB of JavaScript to render a list of five links is making an argument you do not want to make.

The floor I hold myself to:

• Static HTML for anything that does not genuinely need a runtime.
• System fonts, or one variable font subset to the characters you use.
• No image over 200KB, no layout shift after first paint.
• Something visible in under a second on a mid-range phone.

You do not need a perfect score in a lab tool. You need the page to feel instant on the device the reader is holding.

Write four posts and stop apologising for the blog

A blog with four solid posts and no apology beats a blog with twelve posts, three of which begin “I know I haven’t posted in a while.”

Four is enough to show how you think:

• One deep technical piece — the thing you know better than most.
• One decision write-up — a trade-off you made and why.
• One teardown of an interface you admire.
• One short opinion you are willing to defend.

Delete the “hello world, welcome to my new blog” post. Nobody has ever been hired from it.

The contact section

Two things: an email address written as text, and one sentence about what you are open to. That is the whole section.

Contact forms are worse than an address in almost every way — people cannot attach anything, cannot keep a copy of what they sent, and cannot tell whether it went anywhere. If you keep the form, at least show a real confirmation and put the address next to it.

A structure you can copy

Top to bottom, this is the order that has worked every time I have rebuilt one of these:

1. One sentence: what you build, who for, where you are now.
2. Three case studies, in the format above.
3. A short list of everything else you have shipped.
4. Four posts.
5. Résumé link, email address, one line about availability.

No skills cloud. No animated counter. No “my journey” timeline that begins in secondary school.

The last check

Open the page on a phone, in daylight, and read it out loud. If you would not say any of those sentences to a person sitting across a table from you, cut them. That single pass removes about a third of most portfolios, and the third it removes is always the part nobody was reading.