Case study · 2026
The best evidence available is the page you are standing on.
Most portfolios ask you to take the screenshots on trust. This one does not need you to. Every decision below is visible in the thing you are reading it on, and every number is measurable from your own browser, right now.

- 260 KB
- Published budget
- 0
- Third party requests
- 0
- Layout shift
- 100%
- Keyboard reachable
Measured live on the homepage, every visit
No trackers, no fonts from elsewhere
Every image reserves its space first
Visible focus on every control
The decisions
Six calls, and what each one cost or saved.
- 01
No animation library
One fade and a short rise is the whole motion vocabulary here. Shipping a library for that costs about 70 KB of JavaScript to do what four lines of CSS already do.
70 KB removed. Motion now collapses under reduced-motion settings whether or not the page has finished hydrating.
- 02
No smooth scroll
Smooth-scroll libraries put a delay between the wheel and the page. It reads as luxury in a screen recording and as lag in the hand, and it degrades find-on-page and keyboard scrolling.
Native scroll. Nothing sits between the visitor and their input device.
- 03
Ten sections, not seventy
Each section has to answer a question a buyer actually has. Anything that only answered 'what else could go here' was cut before it shipped.
The page ends, and people reach the bottom of it.
- 04
A published speed budget
Anyone can call a site fast. A budget printed on the page and checked against a live measurement cannot be quietly missed.
260 KB and one second, read from the Performance API on every visit.
- 05
Photography that costs nothing until it is wanted
Images are the heaviest thing on most sites and most of them are never scrolled to. Every picture here is lazy, responsive, and sized per breakpoint.
Zero image bytes in the initial load, so the published figure stays honest.
- 06
Works without JavaScript
Reveal animations that depend on script are reveal animations that hide your content permanently the day script fails.
A timer failsafe and a noscript override. Text on this site cannot end up invisible.
This is the standard your project starts from.
None of it is a premium tier or a stretch goal. It is simply what leaving the studio looks like. Bring a real problem to the first call and you will get a straight answer about whether it can be solved and what it takes.